Template revisions are not saved in EE3
How Do I?
I’ve searched high and low for an answer to this to no avail, so I have to post a new topic.
I have EE v 3.0.5 installed and under Template Settings I have set “Save Template Revisions” radio button to “Yes,” but my template revisions are not being saved. When I click the Revisions tab for a particular template it lists the revisions and times as if they are being saved (see attached screenshot) but when I view any of them they have the same content as the “current” revision. Does anyone know why this is the case? Is it a bug and is there a fix? Thanks for any help offered!
Tried it after reading this, and it’s the same in 3.0.6 Core version. It shows the current version of the template.
Tried it after reading this, and it’s the same in 3.0.6 Core version. It shows the current version of the template.
Thank you for confirming that the problem isn’t just me. Looks like someone needs to address this.
If i look in the database, the revisions are saved to the database. This part seems to work. I searched the bug tracker but didn’t found a related bug. So the problem is only to get the right version loaded back / displayed.
Can you please look in your db if the revisions are saved?
Look under ” Utlities -> SQL manager -> exp_revision_tracker “
I could fill a bug report after this…
If i look in the database, the revisions are saved to the database. This part seems to work. I searched the bug tracker but didn’t found a related bug. So the problem is only to get the right version loaded back / displayed. Can you please look in your db if the revisions are saved? Look under ” Utlities -> SQL manager -> exp_revision_tracker ” I could fill a bug report after this…
Yes, I show that revisions are saved in the database too. Thank you for volunteering to submit the bug report.
Reported. https://support.ellislab.com/bugs/detail/21482
Thanks for catching this guys. I’ve got a fix in for the next release and updated the bug report with the solution.
I just now updated to EE 3.1 a few minutes ago and it appears that this problem still exists. Was the fix not intended for 3.1 ?
Upgraded after reading this and it’s working for me, no problem…
Upon closer examination, yes it does work. Sorry for the rush to judgement. 😊