Errors after moving a site From Windows to Linux

Hi

I have a test Modx site on my Windows XP SP3 box and I decided to copy it over to my Linux  (Slackware 12.2) set up to test the scenario where a local site will be moved to a remote Linux Server. The database was exported from Windows and imported into Linux using phpMyAdmin and the entire modx installation was zipped up and unpacked in the Linux htdocs directory.

However browsing to the site ((http://localhost/modx/) produced the following errors:



On the other hand the manager section (http://localhost/modx/manager) works fine.

I have checked my URL and paths in Tools > Configuration:
"Interface & Features" and "File Manager", and I only had to update the "File Manager Path".
All other values were correct.

I searched through the forums for solutions and suggestions and tried a few.  This included

1. hardcoding the the following values in the confing.inc.php file

$base_url=’http://localhost/modx/’; (also tried "/" and "/modx")
$base_path=’/var/www/htdocs/’;
$site_url=’http://localhost/modx/’;

2. Clearing browser cache and cookies

However this only resuled in a blank home page and the manager page only displayed "Could not load DBAPI class."

Can anyone point out what the problem is and provide possible solutions?  Re-installation using the "upgrade" option may solve the problem but I would like to avoid this if possible.

Regards

As the error indicates, it looks like the AjaxSearch snippet cannot find the include it requires at /var/www/htdocs/modx/assets/snippets/ajaxSearch/includes/snippet.ajaxSearch.inc.php. Check to make sure that file exists and that the case of the directory/file names are correct (remember Windows boxes are not case sensitive, so these includes will work on Windows if the case is incorrect, but not on Linux).

Quote from: OpenGeek at Dec 22, 2008, 04:36 PM

As the error indicates, it looks like the AjaxSearch snippet cannot find the include it requires at /var/www/htdocs/modx/assets/snippets/ajaxSearch/includes/snippet.ajaxSearch.inc.php.  Check to make sure that file exists and that the case of the directory/file names are correct (remember Windows boxes are not case sensitive, so these includes will work on Windows if the case is incorrect, but not on Linux).

No wonder you are the Geek  !!! Oddly enough, one of the first things I did upon viewing the error message was to check whether the "snippet.ajaxSearch.inc.php" file was present in location indicated.  It  was indeed present but the location was not quite what it should be.  Maybe it was symptomatic of glazed eyes syndrome from spending too long compiling packages, configuring things, etc on my new Slack 12.2 setup and learning Modx, that I missed the fact that the the leading "a" in "ajax" in both the path and file names, where transferred from Windows in uppercase.

Thus editing /var/www/htdocs/modx/assets/snippets/AjaxSearch/includes/snippet.AjaxSearch.inc.php
to
/var/www/htdocs/modx/assets/snippets/ajaxSearch/includes/snippet.ajaxSearch.inc.php

solved the problem and now the site loads as expected.  Now no self respecting geek (glazed eyes or not) would have missed the case mismatches and of course OpenGeek was onto it like a flash  .

Top stuff M8  .

Cheers

Edit: On another note, after testing the site out for a while, I discovered that the "Search" feature does not work.  Hovering over the search button changes the cursor but clicking on it produces no effect.  Any ideas?

Ok seemed to have solved the Search problem . Once again, the leading "A" in ajaxSearch.js and ajaxSearch.php in the /var/www/htdocs/modx/assets/snippets/ajaxSearch directory were changed from uppercase to lowercase.

I will continue to test things and hopefully no further issues will crop up

My rule for stuff that will exist on both Windows and Linux boxes is: all filenames, all lowercase, always.

Quote from: BobRay at Dec 22, 2008, 11:59 PM

My rule for stuff that will exist on both Windows and Linux boxes is: all filenames, all lowercase, always.

Amen BobRay! And this will be a project coding standard established for reference components as we release Evolution and Revolution (1.0 and 2.0 respectively).

Yes indeed BobRay, this is what I practice, only lowercases for file and directory names. For composite names, I use the underscore "_" the separate individual words.