Limited Editor role

Just to let y’all know, we have fixed MODX-1321, MODX-1329, and MODX-1343 in SVN and they will be available in the Evo 1.0.2 patch release.

and they will be available in the Evo 1.0.2 patch release.

any ideas on when that will be? ( ~ roughly )

having the same problem here.

Luckily this only happened with 1 document on my system, so if you need to get the document working again:

Bring up the database and edit the modx_site_content table

Find the row for the document that is not working and edit the "type" and "contentType" fields back to what they should be.

The document will then be editable from in the Modx Manager

This doesn’t cure the cause but in my case was enough of a fix for now. I then changed the users role to administrator to avoid this problem.
I know that won’t be possible for everyone, but it might help some.

Thanks for sorting this out. I’ve been having the same problem since upgrading only with 12-15 users and several pages knocked out - luckily I’ve got some DB backups and I can salvage most of what was lost.

Please keep us posted on updates, patches, etc.

For now, I’m reverting to 1.0.0.

After upgrade 1.0 -> 1.0.1 I have the same problem. When user edit any document and save it, tree document icon and content editor disappear. When I login on administrator and save it - it works again. But problem back when common user change document and save it again. It is big problem, should I back to 1.0 (is it possible to downgrade?) or should I wait for any quick fix?

should I wait for any quick fix?

Well, the options are attempt a downgrade, wait for 1.0.2 (not sure on the exact timescales for this release yet) or apply the patch manually.

To apply the patch manually, view the changeset here: http://svn.modxcms.com/crucible/changelog/modx/branches?cs=5998

Aside from fixing the codebase to stop this bug from occurring, we’re planning to add to the install/upgrade script so that it will fix any corrupted records in the db, so that users can go right from 1.0.1 to 1.0.2.

If anyone with affected content cares to share a dump of their {prefix}site_content table with me, it could help us to make sure that this fix covers as many scenarios as possible. Just go to Tools > Backup in your Manager, check off the (prefix)site_content table, then click the link at the top to download the backup. Then just PM me with it. Thanks!

Thank You, patched and it works now!

is there a better explanation on how to fix this bug. I am not a programmer and I need to get this site working asap.

thanks