-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Enable Translate Inline only per-session #183
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
Comments
Hello Colin. Great feature request, unfortunately not on our roadmap for now. If you can contribute such enhancement we should be able to accept it. |
There is a related problem with the translations and caching. If you for example want to translate something in the header it requires you to disable the cache for everyone on the site (or else you are unable to translate the header or after cache clearing everyone else has the {{{ tags in the header), so in an ideal case the cache should be disabled for the session that is currently translating. |
Hello @paales - which cache you need to disable? |
Translation cache would be handy 😉. The header and footer are block-cached (in Magento 1) so the block cache should be disabled as well. |
@paales Unfortunately this is not on our roadmap but we encourage everyone to provide a pull request with fix. |
…URL-with-https-is-enabled-with-errors [Ogres] Bugfixes
Merging to create more changes to the task
The Translate Inline feature is awesome. However, to use it in production is a little problematic since it uses an ip filter to enable it. In an office environment there are easily multiple users using the site simultaneously, some of which should not be allowed to use the inline translate feature and some of which need it disabled so they can use the site. It would be better if the inline translate feature required a specific admin user permission and was enabled by perhaps visiting a special url, or clicking a url/button in the backend that forwarded to a page with the feature enabled only for the given session.
Example:
The text was updated successfully, but these errors were encountered: