☆ A M B ☆
Hi,
I have a strange problem with two different websites running MODx Revo 2.0.4-pl2 and 2.0.5-pl: The start page (id=1) "forgets" the value of "[ [publishedon] ]" from time to time. The field is just empty. I have not checked the actual MySQL value, because the problem does not occur so often (but often enough). This results in the disappearance of the whole website since MODx thinks, that the page has not yet been published and does not create any output. Just a white blank page. And this is funny, because ALL other pages work fine. It’s just the start pagee that are affected.
Clearing the cache usualy helps, but only if you know that the page is "down" and revive it manualy. Since there is nothing, not even a menu, to be found on the blank page, the visitor has no chance to go to one of the existing other pages and leaves, tries again tomorrow, only the get the white page again, and NEVER comes back. And that sucks a lot.
My two systems have on thing in common: the same webhoster. But why should that affect only the startpage (both id=1) and not the other pages? I am so confused.
Has anybody a hint for me? I googled no similar cases and that realy frustrated me. Am I the only one having this problem. This sucks even more. Perhaps there is someone with a good idea for me. Is there?
best
Hans
☆ A M B ☆
That was my first thought, too. But no, "publish date" and "unpublish date" are not set. They are empty.
Does that page have any publish or unpublish dates? That’s the only thing I know of that will make MODx change the published status.
Unfortunately, no. The problem stays until you clear the cache or fill in a reasonable value for "published". If I do not check the sites regularly they stay blank. And I look into angry faces. ;-(
Does the problem ever cure itself?
I am waiting for this to happen. But the error does appear on a regular basis. So I cannot dig into MySQL to search for any clues. Too bad, since I am not so much a patient guy. ;-) I want to fix this thing and see my customers happy again.
When it happens, have you looked in the DB in the modx_site_content table to see if the published field has actually changed?
☆ A M B ☆
This has happened to me twice already - on two distinct websites running 2.0.4-pl2. Clearing the cache remedied the problem on both cases, but I suspect it’s related to the same problem you’re describing in your thread.
☆ A M B ☆
MODX Staff
☆ A M B ☆
I cannot reproduce this on any sites that I have. I’m going to have to say this is related to a problematic Snippet or Plugin that is running on that Resource unless you can provide some other clue as to how this is happening.
