Problem with templates in Manager after Server change

Hello from Germany,

I hope my English is good enough to describe my Problem.

We have reinstalled nginx on our Server. After this, we put our websites back and everything worked fine with the other sites. Just the ModX Manager (Plugins: archivist, Articles, Babel, Breadcrumbs, Captcha, getpage, getresources, quip, SPForm, taglister) of ONE site causes problems. When I try to open the Templates (Elements -> Templates) there is no content on the right site - just on the top of the Page. I add a screenshot below:



We figured out, that the <!Doctype> tag is the problem. When I try to add a chunk with this tag, it's the same problem when I try to reopen the chunk. When we delete the content in the database, the page on the right site shows up as long as we retype the doctype tag, save and reopen it again...I am no IT-expert so I hope somebody is able to help me with this problem.

We also have another site set up with ModX and everything works fine so I think one of the listed plugins above might cause this problem.

I used 2.2.9. for the site which cause the problem. If any other information is needed to help me solving this problem, please let me know.

Thanks a lot in advance,
Plemmi

It looks like one of the files got corrupted during the moving process. I would be inclined to try an upgrade to 2.2.10, thus replacing all of the /manager/ and /core/ files and running setup in upgrade mode.

Thanks sottwell for the fast reply. I was afraid that this answer might come - Do you know if updating the ModX Version affects the already installed Plugins or anything else?

I am glad that I got this all working and am afraid that the update might destroy settings or something else :/ When I follow the official 'How to move to another Server'-Tutorial, are there other things which are important to backup before updating than just the database?

Thanks

Are you using ckeditor? Try uninstalling that add-on and see what happens. Or perhaps if you can access the Plugins just disable the editor plugin to see if that's what is causing the problem.

Hello sottwell,
first of all thank you that you try to help me out. We dont use ckeditor. We had TinyMCE but also the uninstall of it hasn't fix the problem.

I give you a complete list of the plugins I use:



I got closer to the problem:

It's just the <! which causes the problem that the right site doesn't show up and instead there is the error (the textline) at the top of the page. Don't know it that helps you. Could it be a chmod problem with something? (I think at least now you realize, that I am just a Designer and far away of an IT-expert)

I think I used to suffer from something similar a while ago - and if I remember ok it was permissions on folders. Try checking the permissions on 'core' and 'components' etc

Hmm, thanks Phil - I set all folder & files in core to 777 to check that but no difference. Do you know which folders in "manager" must have "777" or which files?

I still think you should replace the /manager/ files. That's fairly obviously part of one of your templates being displayed at the top of the page. The $ck- tags at first made me think you were using the CKEditor, but on closer look those look like your own tags in a template. It's not unusual for all of those finicky Javascript and Smarty files to get corrupted when they're being move around. Nothing ever gets changed in the /manager/directory during site development, so it's safe enough to replace the /manager/ with the same files from the same version of MODX.

Oh thank you both - the replacement of the /manager/ files worked! Thank you soooo much

Another Question: I have MODX Revolution 2.2.9-pl (traditional) at the moment but 2.2.11 is the latest version. When I plan to update, will there something to be careful with? Running the setup in "Update-Mode" will replace the database not? That would not be good. And when I do the update will I have to run setup of 2.2.10 first in "Update-Mode" and then the 2.2.11 or can I just run the 2.2.11 without updating to 2.2.10 first?

No, it will not replace your existing database. It will update it with any fields that the new version has that the old one didn't, but no database content will be touched, just the structure. You can just straight to 2.2.11, although I'd wait for the next patch release, as 2.2.11 has a couple of minor problems.