[2.3.1] Multiple ArticlesContainers alongside modDocument in the tree makes modDocuments disappear

[ReSpawN]

Running the latest MODX, upgraded from 2.1.5 and I've got resources disappearing when using multiple Articles.

In the first screenshot (http://pbrd.co/1n3m5qO), "Referenties", "Nieuws" and "FAQ" are ArticleContainers. Now, by looking at the second screenshot (http://pbrd.co/1n3mglK), you'll see "Over ons hardnekkig" rearing it's head and "FAQ" sporadically jumping under "Contact".

At first, I started debugging by changing the ArticlesContainer in the database (_site_content) 'class_key' to modDocument. Suddenly, all was fine, the resources reappeared in the right order but when I switched 'em back, "Over ons hardnekkig" was gone.

Next, I debugged the articlescontainer.class.php and traced it to line 220, isLazy:

    /**
     * Prevent isLazy error since Articles types have extra DB fields
     * @param string $key
     * @return bool
     */
      public function isLazy($key = '') {
          return false;
      }

When I commented that out, I got what was shown in screenshot 2.

Might be an xPDO problem.
I tried duplicating, deleting... everything,... but no cigar.

[ReSpawN]

Kind of a priority issue with 2.3.1 and Articles...

We just tested it with 2.1.5, same problem!

[opengeek]

What version of Articles is this using?

[ReSpawN]

That would be 1.7.8-pl! :)

Clean 2.3.1 installation with 1.7.8-pl yielded the same incorrect behavior. First I created 4 modDocuments with 2 of them having a child, all published and not hidden from menu.
Next, I created 3 subsequent ArticlesContainers and all worked fine. When I started dragging and reordering, after pressing the reload button or refreshing the page, 2-3 modResources disappeared. When I reordered the resources back to the last 3 being ArticlesContainers, I got them back.

[ReSpawN]

Any resolution yet? The problem still pops up on multiple websites at this time. We're running 3 Article Containers, indexed separately in the tree, sometimes separated by a modResource or modWeblink...