No Code Attached Yet
avatar JohnVesey
JohnVesey
3 Nov 2025

It would appear that using “drag and drop” ordering of featured articles isn’t “sticking”…

Expected behaviour:
"Drag and drop" ordering of featured articles should “fix” and be replicated on the frontend.

What happens:
Article order can be changed on admin by “drag and drop” and looks okay, but it reverts to the original order when navigating away.

To replicate the the issue:
In /administrator:

  1. Order your Featured Articles using the “drag and drop” interface.
  2. Navigate away from the page and then navigate back.

The article order will have reverted to its previous state.

Please note:
This is an upgraded site, i.e. J5.4.0 —> J6.0.0

Confirmed by another user on Joomla Forums:
https://forum.joomla.org/viewtopic.php?f=860&t=1021040

Votes

# of Users Experiencing Issue
1/1
Average Importance Score
5.00

avatar JohnVesey JohnVesey - open - 3 Nov 2025
avatar JohnVesey JohnVesey - change - 3 Nov 2025
Labels Removed: ?
avatar joomla-cms-bot joomla-cms-bot - change - 3 Nov 2025
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 3 Nov 2025
avatar brianteeman
brianteeman - comment - 3 Nov 2025

This is a known issue and already fixed for 6.0.1

avatar JohnVesey
JohnVesey - comment - 3 Nov 2025

Sorry Brian,

Looked but couldn’t see it on here. Closest thing I could find is this:
https://issues.joomla.org/tracker/joomla-cms/46374

Not the same thing, I’m afraid. However, if you say it’s fixed in 6.0.1 then I’m happy to hear it :-)


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46399.

avatar brianteeman
brianteeman - comment - 3 Nov 2025
avatar JohnVesey
JohnVesey - comment - 3 Nov 2025

Thank you :-)

avatar richard67 richard67 - change - 4 Nov 2025
Status New Closed
Closed_Date 0000-00-00 00:00:00 2025-11-04 10:26:46
Closed_By richard67
avatar richard67 richard67 - close - 4 Nov 2025
avatar richard67
richard67 - comment - 4 Nov 2025

Closing as being fixed with #46342 . The fix will be included in the next release 6.0.1.

Add a Comment

Login with GitHub to post a comment