WordPress.org

Ready to get started?Download WordPress

Forums

Missing theme directory (4 posts)

  1. Anointed
    Member
    Posted 1 year ago #

    Actually running svn nightly 3.5alpha (upgraded each night).

    Problem:
    When I add a new network site, and visit the dashboard, it says:

    Error: the themes directory is either empty or doesn't exist. Please check your installation.

    screenshot of error

    WP-Config Setup:

    /* Custom Paths */
    define( 'WP_CONTENT_DIR', $_SERVER['DOCUMENT_ROOT'] . '/extensions' );
    define( 'WP_CONTENT_URL', 'http://mysite.net/extensions');
    define( 'WP_PLUGIN_DIR', $_SERVER['DOCUMENT_ROOT'] . '/extensions/addons' );
    define( 'WP_PLUGIN_URL', 'http://mysite.net/extensions/addons');
    define( 'PLUGINDIR', $_SERVER['DOCUMENT_ROOT'] . '/extensions/addons' );

    Now, if I go into the appearance -> themes, I can see my default theme and I can activate it just fine.

    The error on the dashboard goes away.

    Question:
    How do I remove this error in the first place?
    As I am offering sites to customers, the last thing I want them to see is an error code showing up on their first visit.

    I'm sure it has something to do with renaming the wp-content folder, but other than that one symptom, I am having no other issues with this setup.

    Is there possibly another setting for wp-config that I can add to help?

  2. Re-run SVN up, first of all and make sure they didn't already fix it :)

    As I am offering sites to customers, the last thing I want them to see is an error code showing up on their first visit.

    Don't offer sites running trunk/beta to customers! Yikes.

  3. Anointed
    Member
    Posted 1 year ago #

    yeah I know better than to run trunk for live sites. I just got so used to them being so reliable that sometimes you forget they're beta.

    I do an hourly svn up on the cron tab.

    If I remove all the custom directory settings, and just do a default install with wp-content etc, then it works as advertised, no errors. It only seems to happen because I am defining a custom wp-content dir as 'extensions'.

  4. Oh no, I think it's fine for live sites, but not for customers (they're special peoples).

    That's trac worthy, I think, then.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.