Wrong order after upgrading to version 1.1.6

Check the issue, will release a new version with some modification.

@javiergonzalezotero version 1.1.7 released with the fixes.
Please let me know if you are still facing the issue?

Please note the, released no/id is not same as the dashboard display index, in dashboard the number you see #XX is the release id auto generated , it will not be the same as display index in dashboard. As in dashboard you can sort the display index by drag and drop sort, you can up down the release. So, release no/id is fixed, index changes. is sorting order is default then default index based order by is used. you can use date, new order by added ‘id’ which means you can order by release no.

@manchumahara We have tried the new version, and now the order is correct when changing to sort by date. But in the dashboard, in version 1.1.5 entries were displayed in descending order (by ID) and now are displayed in ascending order. The thing is that it looks like in the upgrade process, the autogenerated IDs have changed, because as you can see in the picture below, lower IDs were added later. For example, #1 was added later than #2. Besides, when clicking in “Add new release” the new block is added at the end of the list, so we have to do a long scroll to complete te information of the new release.

Ignore the id number, it’s unique number to each changelog. you can order as need by drag and drop sort. we will add a new feature in next release to reset the order ids to fresh as per current index.

By default now the dashboard changelogs loaded as hidden or closed mode. so scrolling will not be much.

2nd. I will not recommend to store more than 10 changelogs . Better if more than 10 then delete the oldest and add a new every time. People mostly focus on new changelog.

We have almost a 100 changelogs in some of our systems. We release quite often and some of our customers need to see all these changes. That’s why it’s a bit annoying to scroll all the way down in order to add a new release, unlike version 1.1.5 where the “add new release” block was on top

We added a new option to add top or bottom version 1.1.9. From now on this type issue will not happen any more as we finally fixed the sorting issue and also added unique id

Hi,

We tried the new version but now it has deleted all our entries after getting the following error when using the button “Add new release (Top)”. The other button, “Add new release (Bottom)” works as expected

2025/01/14 13:52:58 [error] 8350#8350: *1532338 FastCGI sent in stderr: “PHP message: PHP Fatal error: Uncaught InvalidArgumentException: Primary key 1 already exists. in /var/www/html/manuales.XXXXX.es/wp-content/plugins/cbxchangelog/includes/CBXChangelogMetaAsArray.php:70
Stack trace: 0 /var/www/html/manuales.XXXXX.es/wp-content/plugins/cbxchangelog/includes/CBXChangelogAdmin.php(391): CBXChangelogMetaAsArray->insert() 1 /var/www/html/manuales.XXXX.es/wp-includes/class-wp-hook.php(324): cbxchangelog\includes\CBXChangelogAdmin->metabox_save() 2 /var/www/html/manuales.XXXXX.es/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 3 /var/www/html/manuales.XXXXX.es/wp-includes/plugin.php(517): WP_Hook->do_action() 4 /var/www/html/manuales.XXXXX.es/wp-includes/post.php(5060): do_action() 5 /var/www/html/manuales.XXXXX.es/wp-includes/post.php(5162): wp_insert_post() 6 /var/www/html/manuales.XXXXX.es/wp-admin/includes/post.php(453): wp_update_post() 7 /var/www/html/manuales.XXXXX.es/wp-admin/post.php(227): edit_post() 8 {main}

Hi,

Please have patience, let me debug the issue.

Released a fix in version 1.1.10. Please check

Hi Sabuj,

It seems that it’s working fine now.

Thank you for your quick support

Hi,

after the update the option of the display order “ascending/descending” doesn’t have any effect on the displayed order in the frontend. Now, the oldest entries are on top. It doesn’t matter, which option I choose.

Could you please check this?

Best,

Ralf

Hi,

Check the latest update. We had some drawback how we stored. now we resolved it. from on. you add new changelogs at top or bottom based on dashboard display it will be stored perfectly, in frontend you can set order using shortcode as needed.

Thank you.

Best,

Ralf

• This reply was modified 1 month, 1 week ago by icarusmanifest.

Hello,

“Order” doesnt work for page with shortcode.
On default page “site.com/cbxchangelog/pagatitle” order works normally.

Best,