Error causes site not to show.

I did a clean install today with some addons that worked without problems.

Now I only get an error and the site is not shown at all:

[2014-01-24 23:24:24] (ERROR @ /index.php) Instantiated a derived class modDocument that is not a subclass of the requested class ArticlesContainer

When I uninstall Articles the problem is gone.

Anyone any idea what is causing this error?

Thanks!
[ed. note: mewolari last edited this post 12 years, 8 months ago.]

What other add-ons are you using (especially ones that might be creating a resource)?

@Bob, thanks for your reaction.
I'm using Ace, Advsearch, Articles, Formit, getResources, MIGX with getImagelist, Notify404, pThumb, sitemapFriend, VersionX, Wayfinder and xFPC.

Everything worked together without a single error in the error.log.
I made a new template with some chunks, still no errors.
I made a portfolio-tv with MIGX and a portfolio-tv with pic, to put together a portfolio.
A map is created called portfolio. It has sub-maps that have the names of the separate projects. I added some new projects and everything still worked.
Retested the site and the error appeared. Only added pics.
Rebuild the complete site. Exact same error after adding the pics.
Using MODX 2.2.11

A similar site is already online with MODX 2.2.10. I'm building a new one with MODX 2.2.9 and see if the problem also occurs with that version and MODX 2.2.10.

[ed. note: mewolari last edited this post 12 years, 8 months ago.]

Articles was called in footer and container didn't exist anymore.

Problem solved.

Thank you Bert Oost!

Quote from: mewolari at Jan 25, 2014, 05:04 AM

Articles was called in footer and container didn't exist anymore.

Problem solved.

Thank you Bert Oost!

@mewolari can you share how to found that Articles was called in a footer? We're having the same issue and need to track down where Articles are being called that they shouldn't be. Thanks!

Quote from: fairmam at Jan 31, 2015, 12:29 PM

Quote from: mewolari at Jan 25, 2014, 05:04 AM

Articles was called in footer and container didn't exist anymore.

Problem solved.

Thank you Bert Oost!

@mewolari can you share how to found that Articles was called in a footer? We're having the same issue and need to track down where Articles are being called that they shouldn't be. Thanks!

@fairmam I remember that Bert could find out by looking in the database which resource was called by getResources in the footer. The id of that resource did not exist anymore. That was also the cause of the black screen. When I pointed to the correct id everything was working again.

Maybe you should look for your getResources calls and check their id's or temporarily disable getResources to check if that is causing the problem.

Example:

Nevermind, figured it out. Articles was also being called in our footer outside of the container.

Thanks!