Troubleshooting Installation Problems

Overview

Some quick pointers that may help you overcome installation issues that have occured on some Exponent systems.

Installation Troubleshooting Guide

You are unable to send e-mail

In order for the email system to work, you MUST have correctly entered the mail server settings.  Information about this part of the Site Configuraion can be found here. ...

Installation was interrupted and now I can only 'Upgrade' the site

If you failed to finish an installation and the site doesn't work, but trying to reinstall brings you to the upgrade screen, you'll need to manipulate a few files. ...

I extracted the Exponent package, but now I only get the "Site is Down" message

In version 2.0.4, the installation process was changed to be less apt to be triggered by any user visiting your site.  You MUST now specifically envoke the installation/upgrade routine by browsing to www.mysite.org/install/index.php. ...

I moved my site out of a subfolder and it no longer works

If you installed your site within a subfolder, the system creates an 'overrides.php' file on some servers to help find the subfolder.  This must be updated to show the new system location. ...

I installed v2.2.0 and now my content has disappeared

Because v2.2.0 finally sheds all the old 1.0 style code the existing content can not be displayed until the site database is updated to the v2.2.0 format (you should have received a warning to this effect).  Because the 2.0 style code references the database consistently, it MANDATES an upgrade be performed. ...

I installed v2.2.0 and now see messages about such and such module is not found.

Because v2.2.0 finally sheds all the old 1.0 style code, the old 1.0 style modules no longer exist.  In some cases, Exponent is still able to display the module because the 2.0 module has the same name, but in this case, the referenced 'hard-coded' module in the theme template(s) (don't forget subthemes) still refers to the old module with the 'module' suffix'.  You'll need to update the hard-coded module entries in your theme templates.  This article explains how to update your custom theme template(s). ...

I installed v2.2.0 and now my site crashes all the time

Most likely your theme template(s) (don't forget the subthemes) was using some deprecated 1.0 style function calls.  All the 1.0 style code was removed from v2.2.0 and the failure to update the custom theme to remove all the obsolete functions (they were deprecated when v2.0.0 was released) has now been exposed.  This article explains how to update your custom theme template(s). ...

I installed v2.2.0 and now my site formatting is messed up

Most likely your theme template(s) (don't forget the subthemes) or custom views make reference to deprecated YUI 'reset' stylesheet names or constants.  The YUI 'reset' stylesheets still exist, but under a different name, and the YUI path constants were renamed for consistency with other 'path' constants.  This article explains how to update your custom theme template(s). ...

I upgraded to v2.3.0 and now my pages won't load correctly

In v2.3.0 we fixed/changed the javascript loading to the bottom of the page for good loading optimization.  Though this was always the design/intent, it wasn't properly implemented until v2.3.0.  If you have javascript code in your theme or subtheme template which requires the YUI or jQuery libraries be loaded, it MUST now be placed AFTER the expTheme::foot() call since that method where the javascript (library) loading code is output to the page.  The placement of javascript within a theme template previously didn't matter because the javascript (library) loading actually occured at the top of the page (which delayed initial display of the page). ...

I upgraded to v2.3.0 and now my page styling is different

In v2.3.0, we fixed the loading of framework library, Exponent CMS system, and theme styling to take place in the correct order so that style cascading is implemented correctly.  In previous versions, this was the intent, but in some cases didn't work that way.  Here is the sequence of stylesheet loading: ...