-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[5.4] Backward Compatibility Module #46424
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
Conversation
|
Its missing sql to add it to the extensions and assets tables on update |
@brianteeman Assets table we never insert on updates and leave that to the asset being created when the settings are saved. But with the extensions table you are right. |
administrator/modules/mod_backward/src/Dispatcher/Dispatcher.php
Outdated
Show resolved
Hide resolved
administrator/modules/mod_backward/src/Dispatcher/Dispatcher.php
Outdated
Show resolved
Hide resolved
Doesnt that lead to missing assets |
@brianteeman Yes, but that's not a problem as modules inherit from the component (part before the first dot in the asset name), so when you have no asset and now edit the module settings and save, the asset will be created exactly in that way. So when we added modules in update SQL scripts in past, we always added the extension record with asset id zero to the extensions table. |
Co-authored-by: Brian Teeman <brian@teeman.net>
Co-authored-by: Brian Teeman <brian@teeman.net>
Co-authored-by: Brian Teeman <brian@teeman.net>
Co-authored-by: Brian Teeman <brian@teeman.net>
Co-authored-by: Brian Teeman <brian@teeman.net>
Co-authored-by: Brian Teeman <brian@teeman.net>
|
@alikon The name of the MySQL update script is still wrong, it contains a dot in the date where there should be a dash. |
Co-authored-by: Richard Fath <richard67@users.noreply.github.com>
Co-authored-by: Richard Fath <richard67@users.noreply.github.com>
administrator/components/com_admin/sql/updates/mysql/5.4.2-2025-11-08.sql
Show resolved
Hide resolved
|
@alikon See alikon#144 for a proposal for more version agnostic code. |
[CMS PR 46424] Make code more version agnostic
|
@alikon, I'm retesting this PR but I seem to have found a bug (perhaps one that wasn't there earlier or that I missed can't remember) - either that or I'm going crazy. With the PR applied, I see the🛡️Backward: 5, 6 message next to the 5.4.2-dev... for whatever reason, instead of going to went to the Plugins page: https://www.domain.com/_j540/administrator/index.php?option=com_plugins&view=plugins, I went to the Manage Extensions page: https://www.domain.com/_j540/administrator/index.php?option=com_installer&view=manage, I pulled up the keyword: Backward and got 3 lines: Behaviour - Backward Compatibility - Plugin and here's the RUB, when I clicked on the Status ✅ on Behaviour - Backward Compatibility 6, the menu's 🛡️Backward: 5, 6 stayed the SAME - unless my brain is fried, I would expect it to show: 🛡️Backward: 5, IF I go into the Plugins page and deactivate Behaviour - Backward Compatibility 6 from there, the status changes to 🛡️Backward: 5 as I expect... |
|
I have tested this item ✅ successfully on 717f31d
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46424. |
|
I have tested this item ✅ successfully on 717f31d This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46424. |
|
RTC This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46424. |
|
RTC as it has 2 successful human tests ... but as it is a new feature I've also set the RMDQ (release managers decision queue) to flag that it needs a further decision if it shall be merged or be moved to 6.1-dev. We will decide that soon. |
|
In maintainer meeting we discussed this PR and it was decided not to integrate it into 5.4 or at all. The reason for this is that the information may be misleading, the information is irrelevant when the website is working, behavier plugins are checked during the update, and the information for 'Behaviour - Backward Compatibility' plugin, including the settings, is already included in the system information. Nevertheless, thank you very much to @alikon for contribution, @richard67 for support and @exlemor for testing. |
|
bad decision imho |
|
better if the maintainer can close issues before someone come out with a pr and spend times for nothing |



Pull Request for Issue #46400 .
Summary of Changes
This module displays the which Joomla! Backward Compatibility plugins are enabled and is intended to be displayed in the 'status' position.
Testing Instructions
use the Prebuilt package of this pr
Actual result BEFORE applying this Pull Request
N/A
Expected result AFTER applying this Pull Request
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