[#48372] - [5.4] Composer update joomla/registry from 3.0.2 to 3.0.3
- Fixed in Code Base
- 4 Sep 2026
- Medium
- Build: 5.4-dev
- # 48372
- Diff
- richard67:5.4-dev-composer-update-joomla-registry-3.0.3
User tests: Successful: Unsuccessful:
- I read the Generative AI policy and my contribution is either not created with the help of AI or is compatible with the policy and GNU/GPL 2 or later.
Summary of Changes
This pull request (PR) updates the composer dependency "joomla/registry" from version 3.0.2 to version 3.0.3.
Changes see https://github.com/joomla-framework/registry/releases/tag/3.0.3 .
For 6.x see the equivalent PR #48339 for 6.1-dev.
Similar to that PR, this PR here also changes the version requirement in the composer.json file to require at least the new version.
Testing Instructions
(Partly taken from PR #48339 )
- Add a new site menu item of
Article > Category List
- Set
Filter FieldtoMonth
- Visit menu item in frontend
Actual result BEFORE applying this Pull Request
PHP Deprecated: ArrayIterator::__construct(): Using an object as a backing array for ArrayIterator is deprecated, as it allows violating class constraints and invariants in [ROOT]\vendor\joomla\registry\src\Registry.php on line 256
Expected result AFTER applying this Pull Request
Select field is available
Link to documentations
Please select:
-
Documentation link for guide.joomla.org:
-
No documentation changes for guide.joomla.org needed
-
Pull Request link for manual.joomla.org:
-
No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | External Library Composer Change |
| Labels |
Added:
Composer Dependency Changed
PR-5.4-dev
|
||
it works correctly i just dont see the need for the change to composer.json
why did you update the composer.json the current setting of ~3.0 Include everything greater than a particular version in the same minor range so just a composer update and the updated comnposer.lock would have sufficed
@brianteeman I know. I just wanted to be consistent with what we do e.g. after security updates for the framework and to how PR #48339 proposes it for 6.1-dev. It is not necessary, but it does no harm.
ok - you're the maintainer
I have tested this item ✅ successfully on db184d5
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48372.
I have tested this item ✅ successfully on db184d5
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48372.
I have tested this item ✅ successfully on db184d5
The issue #46354 is not relevant for 5.4-dev.
This PR fixes a PHP deprecation message when using the month filter field:
PHP Deprecated: ArrayIterator::__construct(): Using an object as a backing array for ArrayIterator is deprecated, as it allows violating class constraints and invariants in [ROOT]\vendor\joomla\registry\src\Registry.php on line 256
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48372.
I have tested this item ✅ successfully on db184d5
The issue #46354 is not relevant for 5.4-dev.
This PR fixes a PHP deprecation message when using the month filter field:
PHP Deprecated: ArrayIterator::__construct(): Using an object as a backing array for ArrayIterator is deprecated, as it allows violating class constraints and invariants in [ROOT]\vendor\joomla\registry\src\Registry.php on line 256
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48372.
The issue #46354 is not relevant for 5.4-dev. This PR fixes a PHP deprecation message when using the month filter field:
PHP Deprecated: ArrayIterator::__construct(): Using an object as a backing array for ArrayIterator is deprecated, as it allows violating class constraints and invariants in [ROOT]\vendor\joomla\registry\src\Registry.php on line 256
@heelc29 Thanks. I've updated the PR description and testing instructions.
| Status | Pending | ⇒ | Ready to Commit |
RTC
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48372.
RTC
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48372.
| Title |
|
||||||
| Labels |
Added:
RTC
|
||
✅ Final test before merge with JBT using PHP 8.5
- Source code change is only
"joomla/registry": "^3.0.3"incomposer.jsonandcomposer.lockcontains only related modifications - Seen deprecation
ArrayIterator ... Registry.php on line 256with each site visit of category list - Applied PR with Patch Tester and running
composer i- No deprecation anymore
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-09-04 15:21:50 |
| Closed_By | ⇒ | muhme |
Thank you very much @richard67 for your contribution. Thanks to @heelc29 and @brianteeman for support and testing.
why did you update the composer.json the current setting of ~3.0 Include everything greater than a particular version in the same minor range so just a composer update and the updated comnposer.lock would have sufficed