Upgraded to MODx Revo 2.0.2 and Blog is broken now

Are you using TinyMCE by chance?

Yes, I have disabled TinyMCE and used codemirror and still it keeps doing this

I made a backup of my DB and made a new DB with it and a new MODx 2.0.2 install and it still has the same problem, I will try downgrading back to 2.0.1 and see if my site goes back to normal.

Any other ideas or suggestions on what could be causing this issue?

Thanks.

Don’t downgrade to 2.0.1, that wont fix your issue.

I’m planning on restoring my site back before I did the upgrade since I made a full backup of the files and the DB, and keep the 2.0.2 version running in another directory until I figure out what the problem is.

Ok even more crazyness now.

Now my homepage that was giving me the problems about the code not being properly rendered is not displaying at all.

I haven’t done anything, I can log into the manager and the other sections of the site work fine.

Has my site been hacked? Is it a MODx bug or something?

I am really stumped here.

Here’s the homepage which is a nice big white square now for some odd reason.

And here is a section of the website that works perfectly fine.

Individual blog entries display correctly but the blog itself now has vanished.

Update:

I made a new document and put my blog call on it and changed my site start to this new resource and it’s working again but it still has that html rendering error.

Ok so I uploaded my old files from Revo 2.0.1 and my site is working as it should again.

Here is my site on Revo 2.0.1 and here it is using Revo 2.0.2.

They are both using the same database but as you can see the Revo 2.0.2 install is not rendering the HTML of my Blog correctly, the 2.0.1 install is perfectly fine.

I guess I will have to stay on 2.0.1 for the time being.

You need to move to 2.0.2. 2.0.1 has a major bug with saving, and other than that, the differences are minor. The problem you’re experiencing on 2.0.2 should occur on 2.0.1 - you must have not completed the install fully or uploaded all the files for 2.0.2.

I want to urge you *strongly* to update to 2.0.2. Otherwise we wont be able to provide you any kind of help, minus saying, "Upgrade to 2.0.2.".

Here’s the changelog for 2.0.2: http://bugs.modx.com/browse/MODX/fixforversion/10231

As you can see, there’s no related issues fixed in 2.0.2 that aren’t changed as well in 2.0.1.

Quote from: splittingred at Sep 23, 2010, 08:07 AM

You need to move to 2.0.2. 2.0.1 has a major bug with saving, and other than that, the differences are minor. The problem you’re experiencing on 2.0.2 should occur on 2.0.1 - you must have not completed the install fully or uploaded all the files for 2.0.2.

I want to urge you *strongly* to update to 2.0.2. Otherwise we wont be able to provide you any kind of help, minus saying, "Upgrade to 2.0.2.".

Here’s the changelog for 2.0.2: http://bugs.modx.com/browse/MODX/fixforversion/10231

As you can see, there’s no related issues fixed in 2.0.2 that aren’t changed as well in 2.0.1.

I’ll try a new 2.0.2 install using my old database and pass my chunks and other stuff manually hope that fixes the problem.

Will post again results.

Thanks.

So I installed a new copy of 2.0.2 with a new DB and manually copied all my themes, chunks snippets etc. and I am still having the same error.

Has my host been hacked or something?

The only thing that seems strange is the



I see in my source I don’t know if this is a TinyMCE issue in MODx or something else.

This is only affecting anything with getPage or getResources, everything else works fine which is really weird.

Confused