• I have tried many many many different permutations of fresh installations, installations with old configs, with or without plugins, anything I could think of but to no avail.

    I now installed WP fresh from the latest .tar.gz file.
    I ran the install script succefully.
    Blog created successfully.
    When I login with admin it gives me a page with just this error on it:
    Fatal error: Call to undefined function wp_dashboard_setup() in /home/sites/blog.bakabt.com/web/wp-admin/index.php on line 15

    Up to this point I have already tried many many many many many, I can not overexpress, many many many things to get this working.

    Chown apache * -R, chmod 775 * -R both have no effect.
    Yes all files exist.

    The only solution that I know is to disable APC (why? no idea).
    Adding wp- to apc.filters does not work.

    One peculiarity that I find useful to mention is the following.
    The above error occurs on wp-admin/index.php
    When I alter the require_once on line 13 to a require. Then duplicate that same line. I now expect a function-name clash, but no. It just gives me a white page (wtf?).
    Then if I enable error_reporting(E_ALL&E_STRICT) I get this error instead:
    Fatal error: Call to undefined function wp_cache_init() in /home/sites/blog.bakabt.com/web/wp-settings.php on line 299

    Can someone please tell me how to fix this?
    I will repeat myself if I have been unclear:
    THIS IS A FRESH INSTALL. Yes, all files are present (checked with file_exists). No, require_once does not seem to do it’s job. Yes, disabling APC works but is not an option for me.

    I must add that I am an experienced professional PHP programmer and I simply can not explain the above behaviour. It seems like somehow the cache is interfering. But the errors only appear when using require_once, when using require the behaviour changes radically.

    Help!

Viewing 8 replies - 16 through 23 (of 23 total)
  • limitless86, did you notice though that the Widgets can’t be accessed even with reyespoint’s fix?

    I’m with A2Hosting too.

    First of all, i rarely have any issues with them so it’s not a big deal that this came up. I was still able to access my admin page by going to a post and clicking on “edit” then navigating to where i wanted.

    A2 Hosting upgraded their servers yesterday to allow a choice of php versions. Evidently the new default PHP version is not entirely compatible with WordPress.

    The new default PHP Version is 5.2.9 Cached, which is what caused the error message. After changing it to the second option: 5.2.9 Zend Optimizer” the error went away.

    To change your version, go here: CPanel -> Software/Services -> PHP Version -> 5.2.9 Zend Optimizer

    @lmagnif, Yeah I have the same issue, Looks like it’s to do with “ABSPATH” If you go to the top of widgets.php and make a similar mod:

    /** WordPress Administration Widgets API */
    //require_once(ABSPATH . ‘wp-admin/includes/widgets.php’);
    require_once(‘includes/widgets.php’);

    It will display the page.

    Not an ideal solution but it works.

    I followed Neilcm1450‘s steps and switched to “the second option: 5.2.9 Zend Optimizer” and backed out all my changes Everything running fine now. Thanks man!

    Do you guys know how long term switching to 5.2.9 Zend will be a viable option? When will support for that be discontinued by our host? Will WordPress upgrade to support the more current version of php?

    I am also on A2Hosting. I tried to switch PHP versions to the “5.2.9 Zend Optimizer” but then ALL of my sites stopped working with an “Internal Server Error”.

    I opened a ticket on A2Hosting pointing to this thread. Hopefully they are on it.

    Hi all,

    We wanted to stop by and let everyone know that we’ve received all of the tickets, and the links to this thread. Thank you for pointing our attention here. This is top priority right now.

    The team is currently crowded around our office meeting room attempting to resolve this precise issue.

    I’ll try to provide updates here, while they continue to work. We’ll be responding to individual tickets once the larger issue is resolved. Please keep in mind that you’ll likely see a public update here before a responses to individual tickets.

    Again, many thanks to those who pointed here. We appreciate the opportunity to resolve these with a single fix.

    -Kylebot

    A2Hosting, THANK YOU for acknowledging the issue and working on it – so many hosting companies just say “Well, that’s WordPress – we don’t support it.” THANK YOU for being customer-focused!

Viewing 8 replies - 16 through 23 (of 23 total)
  • The topic ‘WP 2.8 fresh install Fatal error: Call to undefined function wp_dashboard_setu’ is closed to new replies.