@joomdonation Could you check this one here? Thanks in advance.

@richard67 Yes, it works. But I would like to take this chance to clean up the method a bit more: Some check should be performed earlier, some check is redundant, the mis-leading comment... @Elfangor93 Could you please check and merge my PR Elfangor93#2 to your branch if it is OK for you?

Thanks @joomdonation I merged your PR.
But I had to add a token to the function strtok() you used as a replacement for explode(). Since php 8.3, strtok() requires a token (string) as the second function parameter.

https://www.php.net/manual/de/function.strtok.php#refsect1-function.strtok-changelog

Thanks @joomdonation I merged your PR. But I had to add a token to the function strtok() you used as a replacement for explode(). Since php 8.3, strtok() requires a token (string) as the second function parameter.

https://www.php.net/manual/de/function.strtok.php#refsect1-function.strtok-changelog

I was just about to comment in the same way, but @Elfangor93 you were was faster.

But I had to add a token to the function strtok()

Yes, I missed it in my code. Thanks for adding it. Busy at the moment, so I will test it later today.

BTW, we do not use this plugin in core anymore. So to test it, we will need to test and make sure version history still work for extensions use this plugin. I guess we can use Weblinks for testing https://downloads.joomla.org/extensions/weblinks/5-0-0

I have tested this item ✅ successfully on 154102f

Version history in Weblinks is broken at the moment (due to invalid data in #__content_types database table, happens since the time we namespaced the extension but I no-one knows about the bug), so it could not be used for testing. I made correction to the data manually, tested weblinks version history and it worked

So for other testers, all you need to test is making sure version history still works OK for article and maybe contact still work as expected. A bonus test would be making sure JoomGallery is being installed properly as mentioned in testing instructions, but it is not really required.

I applied the code changes from this PR in an existing J6.0.0 installation.
Afterwards, the installation of JoomGallery also worked (without problems or workarounds) with Joomla 6.
Versioning of articles and categories still works as expected.
I have tested this item ✅ successfully.

@MrMusic Please go to this PR in the issue tracker here https://issues.joomla.org/tracker/joomla-cms/46360 and mark your test result by using the blue "Test this" button at the top left corner, selecting your test result and submitting. Posting a comment with a green check mark is not sufficient for the result being properly counted. Thanks in advance.

In the famous words of @brianteeman ;), if you don't match the BEFORE condition, then something is wrong ;) lol

Possibly, I did something wrong but I installed Joomla 6 Nightly, installed Weblinks, and when I tried to check versioning after having made a couple of versions, I receive this error message:

An error has occurred.
0 Class must be an instance of Joomla\CMS\Table\TableInterface
[ Return to Dashboard]

Did I do something wrong? ;(

@exlemor see #46360 (comment)

I have tested this item ✅ successfully on 154102f

I was able to test this successfully! (Thanks @brianteeman)

Thanks @Elfangor93 for the fix/PR.

@MrMusic Please mark your test result as instructed here #46360 (comment) .

@MrMusic As you haven't reacted on my request to mark your test result, I will do that for you.

Every PR needs 2 human tests to be accepted, and marking the test result makes sure that the tests are counted and helps maintainers to find these PRs.

Not marking the test result causes additional work for maintainers.

RTC

I have tested this item ✅ successfully on 154102f

@MrMusic As you haven't reacted on my #46360 (comment), I will do that for you.

@richard67 Thank you for taking care of that.

Every PR needs 2 human tests to be accepted, and marking the test result makes sure that the tests are counted and helps maintainers to find these PRs.
Not marking the test result causes additional work for maintainers.

Sorry, but for personal reasons, I am not always able to respond quickly.

thank you @Elfangor93 and the testers for your hard work