We recently upgraded from 7.4.3 => 7.15.1 => 8.1.2 and mostly everything is working well. The only remaining issue is with the media picker.
We have a number of folders that existed before the upgrade to 8.1.1 and they still exist except they no longer appear in the left-hand nav. They also don't appear when selecting media for documents.
Is there anything I can do to get the folders to show in the nav other than recreating the entire structure and moving the media from the old folder to the new folder?
It's a problem with media folders created before 7.8, which left some details missing in the database. This only became a problem in 7.15 and 8.0, where the media tree expects those details to be present.
As a workaround until this is fixed, there's a SQL query here which adds the missing rows.
Media folders after 7.15.1 => 8.1.2 upgrade
We recently upgraded from 7.4.3 => 7.15.1 => 8.1.2 and mostly everything is working well. The only remaining issue is with the media picker.
We have a number of folders that existed before the upgrade to 8.1.1 and they still exist except they no longer appear in the left-hand nav. They also don't appear when selecting media for documents.
Is there anything I can do to get the folders to show in the nav other than recreating the entire structure and moving the media from the old folder to the new folder?
Hi Anthony,
It looks something related to cache as on the right side you can see the folders. I would suggest few troubleshooting approach:-
Hope that helps.
Cheers,
Shaishav
IIS restart didn't help.
The
GetApplicationTrees
call returnsIt only has the 2 nodes.
No errors in the Chrome Dev tools.
Saving the folder does not resolve the issue.
It's a problem with media folders created before 7.8, which left some details missing in the database. This only became a problem in 7.15 and 8.0, where the media tree expects those details to be present.
As a workaround until this is fixed, there's a SQL query here which adds the missing rows.
Thanks Steve - it worked perfectly
For the benefit of anyone reading this in the future, this is fixed in 8.1.4.
is working on a reply...