Load helix only in front-end application of Joomla. #10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank for pull. we will check later. Did you check Helix3 ? ;) |
|
We were working on iStore II and it doesn't have Helix 3. However, I will check Helix 3 too. Which template comes with Helix3? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Helix should affect only the front-end of Joomla CMS. That is 'site'. Since there is no check for the application in the helix plugin, it loads everywhere.
When loaded in backend and other application such as 'sellacious' it starts affecting them too.
PS:
Ideally it should not be loaded as system plugin as it is relevant only when the current active template is based on Helix itself. This plugin (Helix) should be loaded via the template only.