You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an issue I have noticed when working on the issue raised about restoring revisions and testing it with different types of fields. It must be only related on how the changes to "Repeater" fields are shown in the admin revision history tab. The changes are properly recorded in the "version_control__data" and "version_control__revisions" tables and can also be restored from their.
The text was updated successfully, but these errors were encountered:
This is true for "Repeater Matrix" changes, too. My website heavily relies on Repeater Matrix sections. In facts, it’s almost all our clients can do :-) It would be perfect if they could see and revert the changes that are indeed stored in the database.
This is an issue I have noticed when working on the issue raised about restoring revisions and testing it with different types of fields. It must be only related on how the changes to "Repeater" fields are shown in the admin revision history tab. The changes are properly recorded in the "version_control__data" and "version_control__revisions" tables and can also be restored from their.
The text was updated successfully, but these errors were encountered: