Locomotive Improvement #1302
sebastienbeau
started this conversation in
Workshop
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Locomotive Improvement
Documentation for rake task for cleaning up cache
Cache - stored on mongodb - maintenance on the server side - we should add documentation in order for anybody to be able to launch the “rake task” (ruby scripts) to cleanup
Issue in multi-lang with sitemap.xml
Issue with recaptcha for account registration : locomotive issue ?
PR to merge :
locomotivecms/engine#1393 (hack done here : shopinvader/docker-locomotive-shopinvader#34)
Build fails:
https://quay.io/repository/akretion/shopinvader
Log level:
Be able to define the log level, in order to show only error
Login Issue:
In case that the customer have an account in locomotive but not in odoo, we should raise a specific error
## Be able to customize the error page :
Possible with customizing the page in docker or in nginx
https://github.com/shopinvader/docker-locomotive-shopinvader/blob/master/shopinvader/public/500.html
Less Prioritary
Locomotive Backoffice set password without logging-out
Actions in locomotive are limited :
Improving the JS engine : we can ask didier to do it, but we need budget
adding the possibility to call the erp directly from the actions, in order to avoid calling it in liquid
Locomotive Section:
redefining all the time the same field (reuse block in block)
including section into other section
duplicate a page or a section
Roadmap of the Locomotive replacement
Having a Demo on new version
Shopinvader vuejs template
components
choose a repo
using actions: checking linter and eventually testing on github
using projects and discussion features on github
Beta Was this translation helpful? Give feedback.
All reactions