You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: