Skip to content

fix(url-rewrite): prevent ArgumentCountError on empty spread in array_merge#40665

Open
lbajsarowicz wants to merge 2 commits intomagento:2.4-developfrom
lbajsarowicz:fix/39579-array-merge-empty-spread
Open

fix(url-rewrite): prevent ArgumentCountError on empty spread in array_merge#40665
lbajsarowicz wants to merge 2 commits intomagento:2.4-developfrom
lbajsarowicz:fix/39579-array-merge-empty-spread

Conversation

@lbajsarowicz
Copy link
Copy Markdown
Contributor

Description

DbStorage::deleteOldUrls() and DbStorage::checkDuplicates() use array_merge(...$entities) to flatten the entity request paths. In PHP 8, when $entities is empty, the spread operator passes zero arguments to array_merge(), causing:

ArgumentCountError: array_merge() does not accept unknown named parameters

This occurs when calling StorageInterface::replace() with URL rewrites that don't exist in the database yet.

Fix

Prepend an empty array as the first argument: array_merge([], ...$entities). This ensures array_merge always receives at least one argument, returning an empty array when $entities is empty.

Both occurrences (lines 223 and 276) are fixed.

Fixes #39579

Files Changed

  • app/code/Magento/UrlRewrite/Model/Storage/DbStorage.php — 2 lines changed

Manual Testing Scenarios

  1. Call StorageInterface::replace() with a URL rewrite for a non-existing entity
  2. Expected: Method completes without error
  3. Before fix: ArgumentCountError thrown from array_merge()

⭐ Support my work

Do you like the fix? Remember to react with "👍🏻" to get it merged faster,
Then Sponsor me on Github so I can spend more time on fixing issues like this one.

Learn more at https://github.com/sponsors/lbajsarowicz

…_merge

In PHP 8, array_merge() requires at least one argument. When
$entities is empty, the spread operator (...$entities) passes
zero arguments, causing ArgumentCountError.

Prepend an empty array as the first argument to array_merge()
so it always receives at least one argument regardless of
whether $entities has values.

Fixes magento#39579
@m2-assistant
Copy link
Copy Markdown

m2-assistant bot commented Apr 9, 2026

Hi @lbajsarowicz. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:
  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests
  13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.


For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

@lbajsarowicz
Copy link
Copy Markdown
Contributor Author

@magento run all tests

Two tests verifying array_merge([], ...$entities) handles edge cases:
- testReplaceWithEmptyUrlsArray: empty input returns empty result
- testReplaceWithEmptyRequestPathDoesNotThrowError: URL rewrite with
  empty request path processes without ArgumentCountError

Relates to magento#39579
@lbajsarowicz
Copy link
Copy Markdown
Contributor Author

@magento run all tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

PHP8 compatibility issue with array_merge

1 participant