Answered Manager - undefined - resource-tree not showing

I know this has been a topic many times and I read through all (most?) of the regarding threads.

Following situation:

MODX install 2.5.2-pl
PHP 7 on a shared hosting (Hosteurope) - I do have quite a few MODX installs with this hoster (evo & revo for many years) and no technical problems so far.
MODX is hardened: core-folder outside the root and manager-folder renamed
My page is a 3-language install using BABEL

I am just trying to move the whole page to another folder on the same webspace to do some content-modifying on a non-accessible install. So, no subfolder and no subdomain - using a spare domain for the testing.

what did I do?
- First I installed a clean MODX (same version of course) in the new folder-structure (paralell to the productive install)
- then I installed all the same plugins I am using in the productive install
- I checked the productive install for errors with BobRay´s SiteCheck-Plugin
- I cleared all the caches, sessions, and so on before the DB-export
- I exported the DB and imported it in the new install (after logging out of course)
- I rerunn the setup on the new install (disabled JS-compress and CSS-compress)
- I rerunn SiteCheck on the new install (outside MODX) -> no errors whatsoever
- I cleared the browser-cache, cookies, and so on.
- of course I checked manually all the paths and also the rewrite-part in the .htaccess

Tried to login in the manager with diferent browsers and with and without "www" with the same result: no resource-tree and the "Undefined"-Error

As I did have issues in the past with BABEL I first uninstalled BABEL on the productive page befor the DB-export, without improvement
I even tried to deactivate all the installed plugins via phpmyadmin without success

So here you find me, after spending hours reading and searching for hints...

Any ideas?
I would grant access to the install for some MODX-Crack here in the forums ;-)

MODX is great, but sometimes you just want to, well... go and change the Job. Maybe plant tomatos in the garden or become a shepherd

Thanks in advance,

The frogge

Have you tried visiting the Manager with your browser in private or incognito mode? Sometimes a leftover cookie will mess up the Manager.

Quote from: BobRay at May 09, 2017, 04:04 AM

Have you tried visiting the Manager with your browser in private or incognito mode? Sometimes a leftover cookie will mess up the Manager.

Yes, I tried that. With Chrome and Firefox - same result - "undefined"
And I also noticed in the frontend that the charset obviously got messed up while copying the DB.

I don't think you mentioned the compress_js and compress_css System Settings. If you haven't already, try turning them off.

Do you have anything running that injects JS? (Lots of extras do.) Possibly there's a JS conflict between MODX and one of your extras.

compress_js and compress_css is turned off - yes, I had problems with that in the past already ;-)

The extras I have installed:

• Google Analytics Dashboard Widget
• Babel
• Breadcrumbs
• CodeMirror
• fastField
• FirstChildRedirect
• getFeed
• getPage
• getResourceField
• getResources
• Redirector
• SimpleSearch
• sitecheck
• TinyMCE
• Wayfinder

Well, of course I could uninstall all of the extras before migrating the DB. But, well... it´s an productive project. I would have to take the site offline for that time. And have the risk of crashing something while reinstalling all of the extras. You think it´s worth a try?

It might be worth removing TinyMCE before migrating.

And you can disable any plugins (in the modx_site_plugins table in the DB, if necessary) after you move things.

Be sure to manually clear the cache after disabling them. You might also poke around looking for leftover pieces of Babel.

I´m starting to believe that the problem has to do with the core-folder that I moved out of the domain-reach on the webspace as suggested here:
https://docs.modx.com/revolution/2.x/administering-your-site/security/hardening-modx-revolution

Why do I assume this?
Next project, next problem:
This time with an MODX install 2.5.1-pl with another provider.
Also hardened MODX as indicated in the link above
Also tried to move MODX to another folder just to do some content and template modifications out of sight of the visitors
This time a simple install, one context, one language, no BABEL-Plugin

So, nearly the same steps:
- installed 2.5.1-pl in the new folder using a spare domain
- installed all of the plugins used in the productive page
- deactivated js_compress and css_compress
- exported DB of the productive page
- imported in the new install via phpmyadmin
- checked all the paths

Result: the resource-tree is showing, but without showing the resources
Rerun install after deleting the cache manually and ended up with the following error:


So, the first problem is not solved, the second problem at hand.
To tell the truth: after 8 years of MODX just getting tired of it because I always end up having issues while moving a page from one place to another. This should not be that troublesome.

And if you do not harden modx and hide the core-folder you can be sure to get hacked sooner or later, even with the newest version of MODX. Had this quite a few times on different server and different providers.

Sorry, just a bit of a bad mood here at the moment...

nontheless happy for any suggestion on both the problems

I was moving a couple of sites the other day and made a mistake in the database part of the config.inc.php file

I think that I forgot to enter the $database_dsn and this caused Manager problems, but because I had entered the $dbase line correctly the site displayed correctly in the front end.



I always dread moving sites. I seem to make a mistake or encounter a problem every time.

I think it is one of those things that I do often enough to think I know how to do it, but not often enough to be correct in that assumption!