Answered Manager Screens not displayed correctly in Development Site

Hi Comp_nerd
I hadn't tried running setup as an upgrade. I have been using the advanced option.
So I did. It didn't change much that I could see.
The $modx_manager_url was just as I left it.
$modx_manager_url = '';

I changed it back to the '/' and the Managers screens completely broke again.
So I took the / back out to do some more testing.

When I compare the manager screens in my dev site to the managers screen in my production site there is actually a lot missing.

My Dev site doesn't have the pretty tabs named Resources, Elements, Files and tree view underneath it.
The Site name is "Undefined" Most of the options in the drop down menus just leave the menu's at the time and a blank white screen underneath.

I'm getting no where fast with this. I'm not getting any where near actually developing some new web pages which is supposed to be the point of this mission.

I'm going to try starting a new/fresh install with no imported web pages and see what that does.
If that doesn't work I don't have much hope.
David

I think you may be confusing paths and URLs in your config files (I do it all the time). Anything that's called a path should be a physical path to the directory.



URLs, otoh, should be paths from the web root of the server.



All should end in a trailing slash.

I'd also recommend turning off the friendly_urls System Setting in the DB and renaming .htaccess until you get the site working.

I try not to push this on people here, but I think you're an excellent candidate for SiteCheck. It will test all the paths and URLs for you and tell you which ones are invalid, but you'll probably have to run it outside of MODX. See this: http://bobsguides.com/sitecheck-tutorial.html.

Hello Again,
I'm not sure how this got marked as answered.
Following the advice above I have completed the following steps.

So this is just a list of the steps I have performed. Not really a question at this stage.

• Downloaded the version of MODX that matches the version in production 2.2.6-pl
  Unpacked the install files in the /var/www/
  Run the setup and did a new install and created a new database.

As expected this has created a completely blank site and everything appears to work.
The config.inc.php looks the same as what I have tried originally. I guess that means that something else was wrong with my previous attempts. Never mind lets press forward

From the instructions above if I understand correctly I should copy any missing files from the prod www folders to development site then restore my dev database from the production SQL backup.


Copy static files from Production to Dev.

1) Production has a assets/components folder with lots of sub folders like codemirror, coolcaptch, cronmanager, phpthumbof etc
Nothing exists in the assets/components folder in dev so that won't overwrite anything if I copy it across.
2) Production has an assets/files folder. Nothing much it in except what looks like old test files. I'll create the folder and leave it empty.
3) Production has an assets/images folder which contains lots of graphics so I'm gong to need that in dev.
My dev site currently has no assets/images folder so again can't break anything to copy them across.
4) Production has an assets/template folder with lots of sub folders. No assets/template in dev so I copy that across as well.
5) Production has a /cgi-bin folder but doesn't contain anything. I can probably ignore that folder.
6) Connectors Appears to be populated in the dev folders so I'll just leave that alone
7) Core I'll also leave alone
8) Production has a /html folder with files and sub folders. Nothing in dev so I'll copy that folder as well.
9) /Manager folder I will leave alone.
10) Production has an /xml folder My site has an upload feature. I'm sure this is to do with that. All files copied.
11) Various other files in the var/www folder. Replaced nothing that already existed.

Restarted the Apache2 service just for fun and reloaded the Manager page. So far so good.

Now I should be able to restore my production SQL database.
I only have a SQL dump so I can't pick and choose tables to restore.
I'll leave my new "created today" database alone and restore to one that uses names matching production.
Restored database no problem using MySQL Workbench.

Modify core/config/config.inc.php to point to restored production database
Changed only these three variables
$dbase =
$table_prefix =
$database_dsn =

Now the Dev Manager screens still work and seem to match Production.
Except the Manager Screen is Named "MODX Revolution" instead of my Company Name.
My public web page doesn't load and I still get the "Hello World" page I created during the clean install of Modox.
The var/www/index.php page is identical dev <-> to production.

I checked the "site_start" setting and it had the value of "4" which is the ID of my home page.
And it does appear to be published. I can't open the home page from within the manager console either.

I know Frogabog said that I should do an Upgrade install at some point and use the same Modx version as before.
I took the bull by the horns and did the upgrade install.
My home page partially loads now with some error messages and things missing.
Lots of broken links etc.

So I'll start looking into what they are.
The first one I spot is "error: Wayfinder class not found"

So at this stage there are no real questions.
The best part is I have made some progress.

Thanks
David

ohhhhhkayy...

Are you running this on localhost? WAMPP or XAMPP? There are configuration settings for local that you should check. This could help: http://bobsguides.com/xampp.html

Wayfinder is a component, so in this case I'd check in the manager and see that the package is installed. Whatever the case, I'd uninstall it removing all previous versions till it's gone and then reinstall Wayfinder. This extra powers your menus.

You will likely find more that aren't working. They may all need uninstalling and reinstalling.

Without seeing the innards of this site, it's hard to know why some things are missing on the home page. Not all MODX sites are built with the standards that make it fully transfer-able, some things such as absolute links could break a site easily.

The good news is that your site is working, and it appears that you've got it installed correctly now. I would not update right now, you have some work to do. Look at the templates, the chunks, and the head for the site. This will all affect your front end display and will likely contain a myriad of links that you'll have to adjust for your server.

The error log is your friend. Clearing the files in the core/cache folder is your friend. We at the forum are here to help, friendly like and all :~}

I think most of your extras will need to be uninstalled till all versions are gone, and then reinstalled. This will not be the only extra work you'll have to do, but a good start.

Update
I found some more folders that should exist in Dev and copied them from Prod
core/components contained 15 sub folders in prod that didn't exist in my dev site so I copied them over

core/packages also had a stack of folders and zip files. From what I read these are installers and their original downloaded archives. Won't hurt to copy them across for consistency.

(Cleared the cache and loaded again)

Still lots of broken links but at least my home page looks complete now.

David

Quote from: frogabog at Feb 06, 2015, 01:55 AM

ohhhhhkayy...

Are you running this on localhost? WAMPP or XAMPP? There are configuration settings for local that you should check. This could help: http://bobsguides.com/xampp.html

Wayfinder is a component, so in this case I'd check in the manager and see that the package is installed. Whatever the case, I'd uninstall it removing all previous versions till it's gone and then reinstall Wayfinder. This extra powers your menus.

You will likely find more that aren't working. They may all need uninstalling and reinstalling.

Without seeing the innards of this site, it's hard to know why some things are missing on the home page. Not all MODX sites are built with the standards that make it fully transfer-able, some things such as absolute links could break a site easily.

The good news is that your site is working, and it appears that you've got it installed correctly now. I would not update right now, you have some work to do. Look at the templates, the chunks, and the head for the site. This will all affect your front end display and will likely contain a myriad of links that you'll have to adjust for your server.

The error log is your friend. Clearing the files in the core/cache folder is your friend. We at the forum are here to help, friendly like and all :~}

I think most of your extras will need to be uninstalled till all versions are gone, and then reinstalled. This will not be the only extra work you'll have to do, but a good start.

I have the dev stuff running on a Debian server that I connect to via ssh.
I don't know WAMPP or XAMPP so I'd say localhost
Too late about the update, I have already run it but it didn't seem to break anything

The guys that built the site seem to know what they are doing and it is fairly complex.
I have been in IT 25 years and am Jack of all trades master of some

I think I'm over the hump on this one. At least I have solved the problem this thread is based on.

You (Frogabob) and BobRay seem quite active on these forums.
It seems it is time to close this thread as Fixed and if I run into more problems I'll post a new question and link back to this thread for background information. I sure you will spot my new posts.

Thanks Very Much for your input.

Hey it is already the week end here
David.