Thanks Bob:
I'll review the links you sent. I've just uploaded my zip containing the old site with the changes made to the .php files in regard to paths. Even that is a bit confusing to me and to goDaddy. My cPanel has a full path of /home/mydomain1/public_html/. So, I assume that's what I enter into those PATH locations in the various php files. At least that what the tech support guy earlier tonight was doing when he was able to get a few items to display in the manager. So I'm rolling with the more absolute path even though tech support just told me I didn't even need to put public_html, I could just put the folder name.
I guess I am a bit confused about the database. I have a backup of the schema and the mySQL. I don't know whether I need to import the schema or not...Guess I'll find out. I'd use the database they migrated for me, but I'm nervous that it has new changes from any of the work tech support was doing, and then it may or may not work with my site.
It's a toss up. Could try running the setup with the current database and see what happens. If need be, I could then just delete everything and give it another go. Importing the database at this point is giving me the most anxiety.
I'm beginning to suspect that nobody ran Setup after moving the site to the cPanel server. That would explain most of the trouble. The Setup directory contains a config.core.php file with a relative path to the MODX root directory, which contains the core directory, so Setup should be able to find everything with no trouble.
All the important paths and URLs are in the core/config/config.inc.php file (which can be empty on a new install) and Setup should set all of them correctly when you run it.
It's almost never necessary to set them all by hand on a remote site.
One last thing, if you are setting them by hand, be sure to check the path in the modx_workspaces directory in the DB.
Do you think I might be safe making an attempt with the database they imported? I can double check the path to the path in the modx_workspaces directory.
Just occurred to me too. Would just running the setup be kind of like an update and I should delete the contents of the core cache folder?
It's worth a try, but don't proceed unless the "Upgrade" checkbox is checked during Setup. If MODX thinks it's a new install, you'll lose all the existing content.
Setup should set the workspaces path correctly for you.
Deleting all the files in the core/cache folder never hurts and can often help.
I'm going to see if their database import will work. All the specs, name, user name etc seem to be fine.
Not sure how to update path for workspaces. I found the entry and it looks like this:
Edit Edit
Copy Copy
Delete Delete
1
Default MODX workspace
{core_path}
2013-06-17 23:48:20
1
NULL
I assume that they created a database, or moved the old one over. I don't see anything that looks like an old path anywhere
I found friendly URLs in the database and changed the 1 to 0.
Question. Should I be able to see .htaccess file icon in the cPanel file manager?
I did a search of the file manager earlier, and it said there was a file named .htaccess but I could not see an icon. Thus, the filemanager would not allow me to change the name of the one I had uploaded from ht.access to .htaccess.
Ok. Just did the setup, and Upgrade option was checked, but when I hit the next button, I got the dreaded Error 500 Internal Server Error.
I assume that I leave my old config.core.php in the root. Or would I have deleted that an moved the new one from an install folder out to the root?
I doubled checked some of the permissions. Connectors is 0755. Core is 0755. Manager is 0755. And my config.core.php is 0755
What about the path to the database? I don't think I changed that anywhere.
I checked the database settings. Collation is the utf8_general_ci
MySQL version is 5.5.36-cll-lve
Server charset: UTF-8 Unicode (utf8)
Yikes though! In phpMyAdmin, there is mention of a user, and the user name is different that what I had on the old site.
