Upon restore of 2nd version, the Tag and Version Notes would be populated with the data entered in the tag and version notes fields as described above in Step 2.
Upon restore of 2nd version, the tag and version nots fields are blank.
Database Version 5.5.20
Database Collation utf8_general_ci
PHP Version 5.4.3
Web Server Apache
WebServer to PHP Interface apache2handler
Joomla! Version Joomla! 3.2.0 Stable [ Ember ] 6-November-2013 14:00 GMT
Joomla! Platform Version Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.57 Safari/537.36
Category | ⇒ | Tags |
Labels |
Added:
?
|
I actually found that regardless of the version restored, the tag field appears in blank after restoring.
System information:
Database Version 5.6.17
Database Collation latin1_swedish_ci
PHP Version 5.5.12
Web Server Apache/2.4.9 (Win64) PHP/5.5.12
WebServer to PHP Interface apache2handler
Joomla! Version Joomla! 3.3.7-dev Development [ Ember ] 01-October-2014 02:00 GMT
Joomla! Platform Version Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
User Agent Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.101 Safari/537.36
I notice the bug exactly as @jaimejjt mentions it.
However I can also see that @vdrover mentioned the version notes to be empty after restoring. I think this is the idea since (for them to be always empty) there is no current way to modify them - so if you load them, you would be creating a totally new version (i.e. version 3) with its own notes.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/2578.
Labels |
Removed:
?
|
Status | New | ⇒ | Confirmed |
Labels |
Added:
?
|
Version history acts on the 'base content' fields. As tags are an extension to the UCM base content fields they aren't tracked by user history. Whilst this is inconvenient given the current code structure this won't be changed in the foreseeable future.
The version note field is only used for showing the reason for changes in the comparison view and shouldn't be 'displayed' in the version note field (as you're now in edit mode and will want to write a new version note rather than seeing the existing one).
Status | Confirmed | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2015-09-20 09:16:59 |
Closed_By | ⇒ | wilsonge |
https://www.monosnap.com/image/aV825LeuWlL6Zdk2eTl0zNkcH
You may blame the J!Tracker Application for transmitting this comment.