Support » Installing WordPress » Fatal Error when accessing backend in v3.3

  • Resolved JonathanMcC

    (@jonathanmcc)


    Good evening,

    After auto upgrade to 3.3 I receive the following message when attempting to access the dashboard:

    Fatal error: Call to undefined function is_rtl() in /home/secrev/public_html/wp-includes/general-template.php on line 2102

    Please help… It looks like other had a similar problem and deleting a file worked for them. Would I need to do the same thing? Please name specific file.

    Thanks for the help,

    Jonathan

Viewing 6 replies - 1 through 6 (of 6 total)
  • If anyone else having this problem just rename popup domination plugin folder.

    Some reported that a blank admin board was fixed by removing the plugin Popup Domination. Do you use that plugin?

    Edit: While writing the above you already found out about it 🙂

    HA! I have popup domination and was getting this error, but I reverted back to 3.2.1 already.

    Maybe I’ll try again this weekend when I have more time; this already wasted my entire evening.

    Thanks for the tip about the Pop Up Domination plugin.

    I was able to resolve this problem using the following technique:

    1) Rename the Pop Up Domination plugin folder,

    2) Go to the “Installed Plugins” page and deleting files for the now
    inactive Pop Domination Plugin.

    Cheers.

    Hi,

    Does this mean that pop-up domination does not work with the new wordpress update?

    I am getting same error!

    Cheers

    yes.

    In my case, I had three blogs using the Pop Up Domination plugin which became inaccessible via the admin panel after upgrading to WP 3.3 .

    The problem was fixed using the technique of renaming the Pop Up Domination plugin folder and then deleting the plugin via the admin panel.

    I have a ticket open with the creators of Pop Up Domination regarding this problem but the plugin will remain uninstalled on my blogs until they provide a fix for this problem.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Fatal Error when accessing backend in v3.3’ is closed to new replies.