@rdeutz please follow the convention to out the joomla version in the PR title - it makes it easier to see the version the pr should be tested against

Please add the version note field

Please add Maximum Versions setting

all is looking good so far

For other testers, if you try to test this PR via Joomla Patch Tester even with the latest Nightly Build, you will get the error:
The file marked for modification does not exist: phpstan-baseline.neon

Use the Download package instead :)

@brianteeman version note and history limit added

Content versioning is available in both the site and admin so I would expect the same for module versioning. Currently its only enabled for the admin

Tested with core modules in the admin ui and module versioning is working as expected - cool stuff

Content versioning is available in both the site and admin so I would expect the same for module versioning. Currently its only enabled for the admin

I think it is a fair request. I have looked into it and a polite description how module edit is implemented in the frontend is: interesting. I would like to discuss this with the maintainers and don't start implementing it at this stage. I will come back with a decision.

Getting this error on locally while applying the patch
The file marked for modification does not exist: phpstan-baseline.neon

@vishalchincholi1

For other testers, if you try to test this PR via Joomla Patch Tester even with the latest Nightly Build, you will get the error:
The file marked for modification does not exist: phpstan-baseline.neon

Use the Download package instead :)

I have tested this item 🔴 unsuccessfully on 473ab99

Getting error while applying patch as The file marked for modification does not exist: phpstan-baseline.neon

@manojLondhe

#46772 (comment)

I have reverted the PHP Stan fixes to make testing easier. Now PHP Stan fails, please ignore this, it is expected.

I have tested this item ✅ successfully on 24ca80a

---
Tested as:

1. Enabled versioning

2. From admin area:

• Verified versioning for couple of core modules
• Verified versioning for couple of 3rd party modules

3. From site area:

• Verified versioning for couple of core modules
• Verified versioning for couple of 3rd party modules

4. Verified version note, compare versions, restore versions.

Works as expected

@manojLondhe how did you test versioning on the front end as that functionality does not exist

1. Changes to module settings from site area are getting captured:

Edited module settings from site area

Changes can be seen in version history diff

2. I, however, could not see Version Note field in site area

I have tested this item 🔴 unsuccessfully on 24ca80a

The button [Versions] appears correctly, but no versions are available after submitting several changes to the module. I tested modules of the type «Custom», «Tags popular» and «Articles».

@crimle did you run the sql before testing

@crimle did you run the sql before testing

No, I did not, sorry. There is no testing instruction that tells me to run SQL before testing. Apart from that, how could I possibly do this on my Test Server?

I have tested this successfully. I used core custom module and a 3rd party slider module.

I have tested this item ✅ successfully on 24ca80a

After retesting I can confirm: it works!

I have tested this item ✅ successfully on 24ca80a

Tested with a small module "Custom HTML" and with a third party module ("DWD Weather Warning" from Thomas Hunziker).

I have tested this item ✅ successfully on 24ca80a

The ‘Versions’ button is also displayed when versioning is deactivated. This is somewhat confusing, as it does not occur to you that versioning still needs to be activated.

@paternax that is not the intended behaviour. the versions button should not be present if versions is not enabled. can you please retest. Otherwise you should change your success to a failed test

@paternax @brianteeman
On my test site, the "Versions" button is only displayed, when versioning is enabled in the configuration. I just tested this again.

@dautrich thats my experience as well which is why I asked for a retest - maybe there is some scenario we didnt consider causing the button to be permanently visible

I have tested this item ✅ successfully on 24ca80a

I have successfully tested this with Olivier watching during PBF 2026 Friday... @rdeutz - please validate if this passes based on below:
Tested this on 2 installations, same results!

1. Applying the PR, did NOT update the SQL for me, had to add SQL code into database via phpMyAdmin
2. With core module and 3rd party extension changing 5-6 fields in multiples tabs including playing with Associations on a multi-lingual site, the PR does what it claims and shows/restores previous versions of the Module

HOWEVER, and this may be outside of scope or on purpose, the Permissions Tab values/data does NOT get restored (i.e. if you Allow, Deny or Inherit) the values stay the same even after a or multiple restores

Personally impressed that Versioning worked even with complex setup + multilingual associations = 🥰 😍

I have tested this item ✅ successfully on 24ca80a

I applied the patch, but id=14 is not reported in the database.

@gioacchino54
As mentioned in the testing instructions, you need to apply the SQL script from the patch manually, i.e. via phpMyAdmin.

I was able to test this successfully.
However, I did not see any (id=14) in #__content_types in the database.
Not even after clearing the browser cache.

@dusries
As mentioned in the testing instructions, you need to apply the SQL script from the patch manually, i.e. via phpMyAdmin.

I have tested this item ✅ successfully on 24ca80a

Tested with multiple modules.

eg:

I have tested this item ✅ successfully on 24ca80a

Successfully applied

@dautrich Sorry, I didn't see that.

I have tested this item ✅ successfully on 24ca80a

Successfully applied

Tested correctly and I can see the module versions.

I reapplied the PHP Stan fix to get the testing green, I would say we have enough manual tests and it is save to merge.

Thanks to all the testers, RTC.

@rdeutz are you leaving front end versioning to a new issue?

@rdeutz are you leaving front end versioning to a new issue?

Kind of, I will wait till a decision is made and then look what we can do.

I have tested this item ✅ successfully on 0bdb14b