No Code Attached Yet
avatar hytsch
hytsch
3 Aug 2022

Steps to reproduce the issue

I use the versioning function and set a post from date Y to an earlier version back to a date X.

Expected result

The content of the post should then correspond to the version as of date X.

Actual result

However, I get a mixture: contents in core and standard fields are actually reset to the status as of date X. Contents in custom fields, on the other hand, are not reset but simply taken over from the version as of date Y. => This results in sheer chaos in the output...

System information (as much as possible)

J4.1.5

Additional comments

Joomla is a brilliant system, but such weaknesses are very unsettling for customers and content managers: There is no reason to call this behaviour desired and correct. Unfortunately, the custom fields function is simply not fully developed.

avatar hytsch hytsch - open - 3 Aug 2022
avatar hytsch hytsch - change - 3 Aug 2022
Labels Removed: ?
avatar joomla-cms-bot joomla-cms-bot - change - 3 Aug 2022
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 3 Aug 2022
avatar ReLater
ReLater - comment - 3 Aug 2022

There is no reason to call this behaviour desired and correct.

Just to say it: From my point of view it's a 50:50 decision if it's correct to reset the custom fields also. Sometimes welcome, sometimes not.

avatar coolcat-creations
coolcat-creations - comment - 6 Oct 2022

Versioning should absolutely work for custom fields as well. Its a huge flaw that it does not work.

avatar crystalenka crystalenka - change - 15 Nov 2022
Status New Closed
Closed_Date 0000-00-00 00:00:00 2022-11-15 07:47:49
Closed_By crystalenka
avatar crystalenka crystalenka - close - 15 Nov 2022
avatar crystalenka
crystalenka - comment - 15 Nov 2022

Collecting a few issues into a bigger discussion on versioning and preview in custom fields, so I'm closing this as duplicate. Join the discussion here if you would like: #39217

Add a Comment

Login with GitHub to post a comment