Skip to content

Conversation

@HLeithner
Copy link
Member

@HLeithner HLeithner commented Apr 16, 2025

In the today's maintainer meeting we came to the conclusion that making a new plugin with a new name makes it easier
for us to update and maintain in the future.

Considerations:

  • We need to activate the b/c plugin before upgrading 5.4 to 6.0 (it's not possible in the upgrade process)
  • We would like to force the user to disable the b/c plugin in 5.4 before upgrading (if it site crashes in 5.4 it could be easily recovered by reactivating the plugin, but if it crashes after uninstall in the 6.0 upgrade process there is no way back)
  • Both checks can be done in the pre update checker but only if we have 2 separated plugins

Summary of Changes

  • Create the compat6 plugin
  • Removed the compat plugin
  • Moved already merged changes from old to compat6 plugin
  • Removed all b/c functionally for 5 with the old compat plugin as discussed in the maintainers meeting from February

Testing Instructions

  • New install and test with and without extensions
  • Update from the latest 5.4 nightly build to the patched package or custom update URL created by Drone for this PR, having an extension installed on the 5.4 which will require the compat6 plugin to be enabled on Joomla 6.

Actual result BEFORE applying this Pull Request

Everything works without the old b/c plugin

After updating from 5.4, the old b/c plugin is still there.

Expected result AFTER applying this Pull Request

Everything works with the new b/c plugin

After updating from 5.4, the old b/c plugin is removed.

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

@joomla-cms-bot joomla-cms-bot added Language Change This is for Translators PR-6.0-dev labels Apr 16, 2025
@joomla-cms-bot joomla-cms-bot added the NPM Resource Changed This Pull Request can't be tested by Patchtester label Apr 17, 2025
@richard67
Copy link
Member

@HLeithner You also have to change the extensions helper from "compat" to "compat6" here: https://github.com/joomla/joomla-cms/blob/6.0-dev/libraries/src/Extension/ExtensionHelper.php#L176

@richard67
Copy link
Member

Upgrade testing needs a separate PR which installs the extension in 5.4, so can't be tested yet ( @richard67 when done please update this section)

@HLeithner PR for 5.4 is #45371 . Question:

I did my PR in the same way as PR PR #41738 did it on 4.4 for the 5 plugin. That means the plugin does not have any configuration parameters set in the database.

That would not be a problem when the default values which the 6 plugin uses when reading its configuration are always so that all functionality is enabled.

Is this the case?

If not: Shall I add the right configuration parameters in the database to my PR?

But this would mean we have to maintain them there and in 6.0-dev here when we add some new ones.

@HLeithner
Copy link
Member Author

by default, all parameters will be active in the code, so no parameters in the sql config is needed.

thanks for the PR

@richard67
Copy link
Member

richard67 commented Apr 24, 2025

@HLeithner Is the file name of file "plugins/behaviour/compat6/src/Extension/Compat.php" right? Or shouldn't it be "Compat6.php"

Update: I've just tested with my PR, and yes, the file name has to fit to the class name, so it has to be "Compat6.php".

@richard67
Copy link
Member

richard67 commented Apr 24, 2025

@HLeithner Is the file name of file "plugins/behaviour/compat6/src/Extension/Compat.php" right? Or shouldn't it be "Compat6.php"

Update: I've just tested with my PR, and yes, the file name has to fit to the class name, so it has to be "Compat6.php".

@HLeithner I've allowed myself to rename the file in your PR.

@HLeithner
Copy link
Member Author

thanks

@richard67 richard67 added this to the Joomla! 6.0.0 milestone Apr 24, 2025
@heelc29
Copy link
Contributor

heelc29 commented Apr 29, 2025

UPDATE: Please DISable the new compat6 plugin during installation in system-tests (#45414).

@richard67
Copy link
Member

richard67 commented Apr 29, 2025

Please enable the new compat6 plugin during installation in system-tests (#45414).

@heelc29 Sure you want to enable it? The PR you refer to disables the J5 plugin. In this PR here that should be changed to disable the new J6 plugin.

@heelc29
Copy link
Contributor

heelc29 commented Apr 29, 2025

Please enable the new compat6 plugin during installation in system-tests (#45414).

@heelc29 Sure you want to enable it? The PR you refer to disables the J5 plugin. In this PR here that should be changed to disable the new J6 plugin.

Sorry I mean DISABLE ;)

@HLeithner HLeithner marked this pull request as ready for review April 29, 2025 20:33
@richard67
Copy link
Member

Please enable the new compat6 plugin during installation in system-tests (#45414).

@heelc29 Sure you want to enable it? The PR you refer to disables the J5 plugin. In this PR here that should be changed to disable the new J6 plugin.

Sorry I mean DISABLE ;)

@heelc29 We will handle that after the upmerge when we update this PR to the upmerged changes in the base branch and solve the conflicts.

* Load class names which are deprecated since joomla 4.0 and which will
* likely be removed in Joomla 7.0
*/
if ($this->params->get('classes_aliases', '1')) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
if ($this->params->get('classes_aliases', '1')) {
if ($this->params->get('classes_aliases')) {

label="PLG_COMPAT6_FIELD_CLASSES_ALIASES_LABEL"
description="PLG_COMPAT6_FIELD_CLASSES_ALIASES_DESCRIPTION"
layout="joomla.form.field.radio.switcher"
default="1"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
default="1"
default="0"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I keep them active for now and wait till we have a maintainer decision and what gets added to the list.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a decission, check the last meeting report.

@richard67
Copy link
Member

@HLeithner Now as @laoneo 's PR #44925 has been merged, this PR here has conflicts which can't be solved on GitHub. I think you know how to solve them. If not, let me know.

@HLeithner HLeithner enabled auto-merge (squash) May 14, 2025 17:57
@HLeithner HLeithner merged commit cb6cb1d into joomla:6.0-dev May 14, 2025
3 checks passed
@HLeithner HLeithner deleted the 6.0/feature/compat-6 branch May 15, 2025 06:01
HLeithner added a commit that referenced this pull request May 15, 2025
@HLeithner HLeithner restored the 6.0/feature/compat-6 branch May 15, 2025 08:48
HLeithner added a commit that referenced this pull request May 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Language Change This is for Translators NPM Resource Changed This Pull Request can't be tested by Patchtester PR-6.0-dev

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants