evolution-cms/evolution

v3 Missing Elements from the main RHS area after updating from 1.4.15

nick0 opened this issue · 3 comments

nick0 commented

(edit: I misread the version as 3.1.17 instead of 3.1.7)

Hello,

I recently updated an Evolution site from 1.4.15 to 3.1.7 with the Migration plugin.
Then I ran manual ftp updates using the "old-new update method" (uploading the new folders as assets-new, core-new, install, manager-new / renaming the older folders assets-old, core-old, manager-old / then renaming the new folders as assets, core, manager / then running the install manually).... I also ran the update manually again multiple times,
This resolved a number of issues but this puzzling one remains and I am wondering if any of the devs can please help me with a solution...

There are many missing Elements > Templates / Template Variables / Chunks / Snippets and Plugins from the main RHS area.

However in the LHS tree (via the ElementsInTree plugin), all Elements show as expected and can be accessed.

See screencap below showing the differences between the Elements in the LHS tree and the RHS content area.

evo3 1 17 - elements missing

Any idea on how to fix this issue so I can see all Elements in the RHS?

Many thanks.

fourroses666 commented

This is not normal behaviour. Did you updated ElementsInTree and re-installed EVO 3.1.7 just to be sure?
Cleared cache or checked other browser to confirm?

nick0 commented

Agreed. Not normal at all.
Yes to the above - noting though the issue is not the ElementsInTree plugin... that is the only thing showing all Elements. Updating / Disabling that makes no difference.
Firefox and Chrome have the same issue - Elements are missing in the RHS

nick0 commented

BBloke solved the issue for me...
The existing locks on the Elements (templates, template variables, chunks, snippets, plugins) was the problem.
He wrote a small plugin that clears the locks against the resources in the tables that you see in ElementsInTree.
The plugin and details are located here at the Evo forum .
I think this could potentially affect other users when they update from 1.4.x to 3.1.x and should still be addressed by the devs as there is a backward compatability issue highlighted here.
Cheers