[6.1] Provide #__extensions.custom_data for components, menus, modules and template styles #46622
+24
−13
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.
Summary of Changes
We have nice
#__extensions.custom_dataMEDIUMTEXT column to store custom extension data, but it's not available in Joomla get extension methods.Example: currently, if a template stores any own data in
#__extensions.custom_data, it can be only retrieved via separate SQL query.It would be nice to be able to have access to
custom_datavia native$app->getTemplate(true)I.e. YooTheme will be able to use this workaround to reduce extra SQL query per page load.
Same for components, menus and modules.
Testing Instructions
Install patch.
Actual result BEFORE applying this Pull Request
You can't get
custom_datavia$app->getTemplate(true)and other extension get methods:Expected result AFTER applying this Pull Request
You can get
custom_datain all methods above.Link to documentations
Please select:
Documentation link for docs.joomla.org:
No documentation changes for docs.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed