Pull Request for Issue #45782

Summary of Changes

When restoring an article from version history, the ordering field may be null if the version was saved during the initial creation of the item. This caused issues restoring that first version since the ordering column in the database is non-nullable and required.

This PR adds a safeguard in the restore process to explicitly set ordering = 0 if it is null in the versioned data. This prevents database errors or broken record state during restore. It also goes ahead and patches version saves to ensure a null ordering value cannot be saved.

Testing Instructions

1. Create a new article and save it for the first time.
2. Open the article again and save it a second time (creates a version).
3. Restore the first version via the Versions interface.
4. Ensure the article is restored correctly without errors and appears in the list with ordering value 0.
5. Optionally, verify that manually reordered articles are unaffected.

Actual result BEFORE applying this Pull Request

• Restoring the very first version of an article (before it had a valid ordering value) fails or causes an invalid NULL ordering to be saved.
• Article may not appear in the frontend or backend list correctly, depending on DB settings.

Expected result AFTER applying this Pull Request

• Restoring any version of an article works without error.
• If ordering was null, it is now safely set to 0.
• Article is visible and ordered safely in lists.

Link to documentations

Please select:

• Documentation link for docs.joomla.org:

• No documentation changes for docs.joomla.org needed

• Pull Request link for manual.joomla.org:

• No documentation changes for manual.joomla.org needed