Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement alternative panel content storage (experimental) #4

Open
potzenheimer opened this issue Mar 4, 2016 · 1 comment
Open
Assignees

Comments

@potzenheimer
Copy link
Contributor

potzenheimer commented Mar 4, 2016

Provide a less content dependent storage for content panels by adding a small json storage layer. Most of the infrastructural bindings could easily be adopted from customer projects like rms or the ade25.assetmanager approach.

[Update 04.08.2016]

Since sentry logs errors steaming from unauthorized access to the panel objects using a simple and clean JSON data storage might also serve to resolve these issues.

Taking the idea even further we might need to deal with the content assets in a different manner, also storing uploaded images inside the panel page might still work as expected.

@potzenheimer
Copy link
Contributor Author

A deliverable could be a storage.py tool that just deals with setting/getting and normalizing the JSON contents while providing a behavior for storing the Page data in a string or potentially file object.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant