Getting MODx site working on remote server

I’m still trying to get my site (MODx 1.0.2) successfully uploaded.
I believe I’m down to two problems:
First, my home page is live on the internet (huge progress) but when I click any of the menu options, it is trying to find them on my local development environment. I’m not aware of anything specifically referencing my local installation - where is this coming from?
Second (and possibly related... ): when I edit the File Base Path, File Browser URL, and File Manager Path to what I think they should be, I get dozens of messages like this:

Warning: Missing argument 16 for Qm::Qm(), called in /home/hostusername/public_html/manager/includes/document.parser.class.inc.php(746) : eval()’d code on line 2 and defined in /home/hostusername/public_html/assets/plugins/qm/qm.inc.php on line 16

Here is what I have set these paths to:
File Manager Path: /home/hostusername/public_html/
File Base Path: /home/hostusername/public_html/
File Browser URL: http://www.mydomain.com/assets/

Any ideas on what I should be doing?

At least I know a bit more about the problem now...
My site on the internet seems to be working but in fact is still pulling everything in from localhost:8888. The fantasy disappears when I quit MAMP. I have changed the System Configuration for the File Base Path, the File Browser URL, and the File Manager path. Am I missing something else that has to be changed? Where is it getting its path back to localhost:8888?

On the remote server did you clear the MODx cache in the manager?

Thank you for that! No I did not clear the cache. Clearing the cache changes things, unfortunately exposing some underlying problems...

I now get this error when I go to the home page:

« MODx Parse Error »
MODx encountered the following error while attempting to parse the requested resource:
« PHP Parse Error »

PHP error debug
Error: Missing argument 13 for Qm::Qm(), called in /home/hostusername/public_html/manager/includes/document.parser.class.inc.php(746) : eval()’d code on line 2 and defined
Error type/ Nr.: Warning - 2
File: /home/hostusername/public_html/assets/plugins/qm/qm.inc.php
Line: 16
Line 16 source: function Qm(&$modx, $jqpath, $loadmanagerjq, $loadfrontendjq, $noconflictjq, $loadtb, $tbwidth, $tbheight, $hidefields, $hidetabs, $hidesections, $addbutton, $tpltype, $tplid, $custombutton, $managerbutton, $logout) {

Parser timing
MySQL: 0.0080 s (3 Requests)
PHP: 0.0597 s
Total: 0.0677 s

But, this is progress ...

Regrettably, progress is slow...
Going to my home page gives the above error message.
My MODx Manager page is covered with warning messages like:

Warning: Missing argument 14 for Qm::Qm(), called in /home/hostuesername/public_html/manager/includes/document.parser.class.inc.php(746) : eval()’d code on line 2 and defined in /home/hostusername/public_html/assets/plugins/qm/qm.inc.php on line 16

Has anyone run into this? Any ideas on what I should do? Thanks...

I’m just guessing, but it looks like it might be a version mismatch between the QM (Quick Manager) add-on and MODx, or between the different files in the QM add-on (or a bug in QM).

Thanks Bob,
It was likely the version mismatch at play, as I had gone from 1.0.0 to 1.0.2 (although I find it puzzling, since everything was working fine on the local installation, and I did the installation of 1.0.2 on the server before uploading... ). Anyway I reverted to 1.0.0, and the site is now uploaded and working. I can’t say definitively this was the cause because it didn’t work immediately after I reverted, it took a couple of attempts before a successful upload - but I’m going with the version mismatch theory. Lesson here I guess is don’t upgrade in midstream.

OK, now I’m seriously puzzled...
Here’s the scenario:
First website - uploaded and working on remote server.
On to 2nd website. Developed site in local environment. Uploaded 2nd website to remote server. Encountered same problems (parse errors etc) that I had initially with first site. Went into first website Tools–>Configuration to double check the paths I set. Found that on my last upload attempt I forgot to change the paths. Eg. File Manager Path is still set to /Applications/MAMP/htdocs/sitename/modx-1.0.0/, etc. So... I changed the paths on the second site to the paths from the local environment. Second site now working on remote server. Seems like my first site is working only because I screwed up and forgot to make the path changes. According to my (flawed?) understanding of these paths, neither website should be now working on the remote server, but both are. I’d like to know what’s going on with these paths (File Manager and File Base). If anyone can enlighten me I’d really appreciate it.

Did you do an upgrade install at the new site after moving the files and DB? That will usually straighten out the paths (unless it’s an IIS server). The upgrade install won’t affect your content as long as you don’t install the sample site.

Neither path affects the front end or most of the Manager. They’re for when you browse files in the Manager or in a rich-text editor.

I did not do an upgrade install. I have done that now for the first website (upgrading from 1.0.0 to 1.0.2). The paths didn’t get straightened out, but I’m ecstatic that the upgrade happened painlessly! Since everything seems to be working nicely can I just forget about the paths, or will it come back on me in some weird way later on?