@Bakual Great proposal. One thing I think should be different is that the information that it is J3 ready should not be an i icon as tooltip but maybe use the Joomla 3.x tag like we use at the JED and add the tooltip to that. What do you say?

The current icon is just the default icon from Joomla. So we sure can change this.

However using a "Joomla 3.x" icon isn't appropriate and could be misleading: The code currently doesn't check if the extension is compatible with J3 or not, it just compiles the information and shows it in the tooltip. So if we show a J3 icon but the extension isn't compatible it would give a wrong sign to the user.

tested /administrator/index.php?option=com_installer&view=manage on 2.5.17 multilingual, with old PHP 5.2 work as expected, tool tips in English

@Bakual Fair point. Good to go for me. Test is good.

Moving to RTC as we have 2 succesful tests.

This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5015.

Do I understand well that, although the infos will show in the Extension Manager->manage, there is no other way for the site administrator to be aware of this?

@infograf768 Correct, this PR only adds the information there.

Hmm...
What do you think folks about setting a fixed message in CPanel with something like:
"When you decide to update your site to version 3.x.x, make sure to check the compatibility of your extensions at [link]"

The message could be displayed in bold/red on top of the modules.

in both templates Hathor and bluestork

For example:

@infograf768 if you're going to have the message then wouldn't it be better to place it on the com_joomlaupdate screen ?

This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5015.

The user will not go to the joomlaupdate screen except if he changes from LTS to STS I guess.
Also he could decide to update via the Extensions Manager->install.

I thought more interesting to put it in the CPanel to let users know for sure and also to promote upgrade to version 3... :)

The issue with that is they may be using a custom admin template
On 15 Nov 2014 11:20, "infograf768" notifications@github.com wrote:

The user will not go to the joomlaupdate screen except if he changes from
LTS to STS I guess.
Also he could decide to update via the Extensions Manager->install.

I thought more interesting to pit it in the CPanel to let users know for
sure and also to promote upgrade to version 3... :)

—
Reply to this email directly or view it on GitHub
#5015 (comment).

I think it would make most sense to have it on the EOL notification plugin (#5063) or as part of the doc page linked from that plugin.

Sounds good to me to make it part of the EOL notification plugin. One place to rule them all :)

@Bakual i can add this functionality to the documentation that is linked from the EOL notification plugin (#5063). since addressing each and every extension is given in the planning and step by step, i can direct people to this functionality in the manage tab once i totally understand what it does and doesn't do.

question (and i'm sorry i haven't tested it yet): does this only give the tooltip if the extension grabs update info from the extension manager -> update tab? said another way, if the extension doesn't update via the one-click updater, the site admin will need to go physically look at the extension (via the JED or the dev website) and whether it is compatible with Joomla! 3, correct?

and then, just because the extension is compatible with 3 doesn't necessarily mean that it doesn't need to be uninstalled in 2.5.x and then reinstalled with the 3.x version. what you've done up here doesn't substitute for still checking each extension to verify the mini-migration path, correct?

thanks very much!! quite nice. :)
jenn

does this only give the tooltip if the extension grabs update info from the extension manager -> update tab? said another way, if the extension doesn't update via the one-click updater, the site admin will need to go physically look at the extension (via the JED or the dev website) and whether it is compatible with Joomla! 3, correct?

Exactly. It only works if the extension uses the Joomla one-click updater.

and then, just because the extension is compatible with 3 doesn't necessarily mean that it doesn't need to be uninstalled in 2.5.x and then reinstalled with the 3.x version. what you've done up here doesn't substitute for still checking each extension to verify the mini-migration path, correct?

It will show the compatibility for the currently installed version and for the latest available version.
The tooltip will look like this:

Installed version (4.5.0) works with Joomla! versions 2.5, 3,3.
Latest available version (5.3.0) works with Joomla! versions 3,2, 3,3."

I'd say if the currently installed version is compatible with J3, then you don't have to uninstall it. For most extensions it should work. Except maybe for extensions which have two different codebases for the same version, one for 2.5 and one for 3. I know there are a few developers which took that approach.
I wouldn't uninstall the incompatible extensions however. I would just deactivate them. Uninstalling will also remove the data, at least if the extension is properly written.

thank you @Bakual your explanation is helpful. now i can word things properly when i add it to the docs.

yes, the great debate to deactivate or uninstall. i go with it depends. a lot of us uninstall everything we can to minimize the white screen of death. and let's face it, a content plugin is no big deal to uninstall in 2.5 and reinstall in 3.x. but that's a different topic.

when it comes on where to place this in case of a different admin template in use, i agree with @brianteeman to have it on the update page if it needs to be somewhere else besides in the documentation linked from the EOL plugin.

that being said, we're still in discussion on the same issue in the update working group as to the problem of if the site is using a different admin template and then the EOL plugin wouldn't appear either. good to see this discussed. i guess we better have a quick link for EOL as well as the notification across the top to make sure they get to where they need to go to upgrade properly.

so this notification for versions in Extension Manager -> Manage is going to be in 2.5.28 yes?

thanks again, well done.

so this notification for versions in Extension Manager -> Manage is going to be in 2.5.28 yes?

I'd say yes. Nobody complained so far

About the EOL plugin. are there really any admin template which doesn't show regular messages (like "article saved"). That would be quite a stupid template imho. I'd say it should work always.

for including it in 2.5.28. Good job.

About the EOL plugin. are there really any admin template which doesn't show regular messages (like "article saved"). That would be quite a stupid template imho. I'd say it should work always.

agreed and we were just talking about that in the group so no worries. i'll change the documentation once 2.5.28 is released to include this functionality and how people can use it.

Merged into 2.5.x.