After update all collections empty

[navtsi]

I updated all my websites on different servers from 3.6 to 3.7. (MODx 2.7.1). Now I have a lot of problems. Most of my customers says that the lists of collections are empty. In some I can see the items but some are deffinetally empty.

In most cases I created some of own collection templates. And this seams the problem. If I go to the the collection templates the list is empty, but if I wan't to create a new template and use a name of a previous template, it says this template still exists.

If I Unistall the plugin and reinstall it I got the same message.

If I create a new template with different name, I got the error: collections.template_err_save.

In some installations I change the renderer, but I cannot say if I did it in the installations with errors, because these old files seams gone.

[Spheerys]

I get the same error when I tried to create a new template : collections.template_err_save

[theboxer]

Try and clear your browsers cache. If it won't help check error logs.

[navtsi]

Doesn't help. I uninstalled the plugin completely and reinstall with basic configurations. Than creating my templates again. I belive that something in the configuration was wrong and the new version cannot work with it. It appears just in two of my 22 installations, so it was not a great problem.

[theboxer]

So what errors you got?

[sepiariver]

I got the same issue but it was due to CDN caching (Cloudflare). What is the effect of disabling all CDN/caches and aggressively clearing browser cache (hard reload)?

[smg6511]

I experienced this same problem after the 3.7.1 update (running on modx 2.7.2), where child documents no longer appeared for collections (both existing and newly created). However, I did not see any errors in the log. I can confirm that clearing browser cache (files and cookies) cleared up the issue and collections are now displaying as expected.

[52eins]

For me problem like @smg6511 : child documents disappear (visually) with Collections 3.7.1 on modx 2.7.2-pl, server with PHP 7.3.11. With web developer tools in Chrome I can see this JS error:

Uncaught TypeError: Cannot read property 'bind' of undefined
    at collections.grid.ContainerCollections.wrapRenderer (collections.grid.resources.js:151)
    at collections.grid.ContainerCollections.getColumns (collections.grid.resources.js:163)
    at new collections.grid.ContainerCollections (collections.grid.resources.js:32)
    at Object.create (ext-all.js:21)
    at S.createComponent (ext-all.js:21)
    at S.lookupComponent (ext-all.js:21)
    at S.add (ext-all.js:21)
    at S.<anonymous> (ext-all.js:21)
    at Object.each (ext-base.js:21)
    at S.add (ext-all.js:21)

Tried to deactivate addons, uninstalled TinyMCE RTE, cleared cache in core and browser … nothing helps. No entries in error logs.

[52eins]

I tried this now:

• an older installation of modx with version 2.6.5 and Collections 3.6.0: works fine
• updated modx to 2.7.1 and tried with Collections 3.6.0: works fine
• updated Collections to 3.7.1: works fine with modx 2.7.1
• updated modx to 2.7.2, tried it with Collections 3.7.1: works fine too!

What's the difference between a twice updated modx (2.6.5 -> 2.7.1 -> 2.7.2) with current version of Collections and a clean install of modx 2.7.2 where Collections doesn't work as expected?

Update: installed modx 2.7.1 over 2.7.2 (doesn't helped) and reinstalled 2.7.2: no changes. Collections doesn't work, right area empty, JS error in the console.

[52eins]

Now tried some back and forth changes.

Last I uninstalled collections, removed all files manually via FTP, cleared the cache in modx, in browser and cleared the core/cache manually via FTP on the server. After this I reinstalled collections and was wondering why I found my self defined collection view (maybe because it’s saved in database and will not deleted while uninstalling the addon).

Now (because I deleted the standard blog collection view after creating my own view) I exported the blog view from an other site and imported it in my troublesome site, then deleted my own view.

And now I can change a document resource to collection and can see the content, tabs and so on. And the JS error is gone too.

Next step will be creating a new self-defined collection view and I will see if this makes new trouble or not.

[52eins]

Of course it was not the solution I'd hoped for. Now I have the same problem like in this thread in modx forums: https://community.modx.com/t/collections-children-not-visible-for-account/1677/9

No childrens are visible, the collection says: This resource doesn’t have any children (respectively "Diese Ressource hat keine Unterressourcen." in German). It doesn't matter if I've created a news child or copied an existing resource into the collection's document. The document "disappears" and the collections seems empty. Changing the resource from collection to document shows the children in the tree.

In the chrome console are no errors or warnings.

[janice171]

I am getting this after an upgrade to 2.7.3. No errors in the log apart from the deprecated modAction support one.. ERROR in modMenu::getSubMenus @ /home/website/public_html/core/model/modx/modmenu.class.php : 148) Cleared browser and site caches but still nothing displaying for Collection pages.

I've rolled back to collections to 3.6.0 and changed the Parent resource to a Document and now i can see all the child pages below as resources. This will have to suffice for now. Errors following this change are as follows:

[2020-05-12 11:43:20] (ERROR @ /home/website/public_html/core/model/modx/rest/modrestclient.class.php : 240) PHP warning: simplexml_load_string(): {"status":500,"code":2,"message":"DOMDocument::createTextNode() expects paramete
[2020-05-12 11:43:20] (ERROR @ /home/website/public_html/core/model/modx/rest/modrestclient.class.php : 240) PHP warning: simplexml_load_string(): ^
[2020-05-12 11:43:20] (ERROR @ /home/website/public_html/core/model/modx/rest/modrestclient.class.php : 245) Could not connect to provider at: https://rest.modx.com/extras/