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

Use with FileField #108

Open
submarcos opened this issue Jun 5, 2020 · 1 comment
Open

Use with FileField #108

submarcos opened this issue Jun 5, 2020 · 1 comment

Comments

@submarcos
Copy link
Member

Hi,
I had develop a similar (but incomplete) app to store template in database.
In combination with a custom ODTTemplate Engine, It allows to store and use ODT files as template.

Your app is very very usefull and complete, but I can't use it because I can't set my ODT content manually, only by upload a template file.

What do you think about transform Template content field in real FielField, and keep content as cached property ? (Well, it is possible in admin to keep content field to handle text content and store it as file)

I can propose a PR for this.
Thank you for your advice

@mpasternak
Copy link
Contributor

Hi @submarcos and thank you very much for the suggestions.

I remember using ODT templates in one of my apps and it worked very well.

I imagine that your plan was to use different templating engines with every in-database template. This would be pretty cool but as it is not exactly my use case (or anybody else, as this issue is hanging here for about 2 years or so), I'm not sure how well would it work.

If you want to propose a pull request, it would surely need to be very well tested.

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

No branches or pull requests

2 participants