Exception Thrown – not defined for ExtensibleObject – error

  • ARC1

    (@arc1)


    11 years, 8 months ago

    Exception Thrown – not defined for ExtensibleObject

    Can any one please help with this problem. I am unable to start WordPress from localhost (WordPress is currently installed only on my computer (Mac)prior to going live} but when I try to start WP I am now getting the following error ‘Exception Thrown – not defined for ExtensibleObject’ .

    I recently updated to WP 4 and noticed that page titles were missing in the address bar. Everything else seemed okay. So checked the permalinks settings in Dashboard and found they had been reset to default. So changed to ‘postname’ which was set previously prior to the WP 4 update. This then caused all pages to be redirected to the ‘home’ page when clicked.

    I searched for help on the Internet and it was suggested I deactivate all plugins and restore one at a time to find a possible problem plugin. The problem went away after all plugins were deactivated and the page links worked okay. I then re-activated each plugin in turn to find out if it was a plugin issue. Doing this I found that NextGen (the latest version) appeared to be causing the problem. So I deactivated NextGen and everything worked okay and I was able to use the PostName’ permalink option.

    I like NextGen so decided to download and install a fresh version thinking this might resolve things. NextGen would not update so tried to deactivate the plugin but it would not deactivate. So I tried to delete NextGen and then reinstall a completely fresh version of NextGen.

    On doing this WordPress crashed and when I tried to re-launch WordPress the ‘Exception Thrown – not defined for ExtensibleObject’ error was displayed on a completely blank page.

    I have access to the database PHPMySQL but do not have enough experience to know if the problem is in the DB or not. I am not able to restart WordPress to access either the frontend or backend.

    So would be very grateful if someone can suggest a solution.

    Many thanks.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter ARC1

    (@arc1)

    11 years, 8 months ago

    Since posting my request for help yesterday I have managed to start WordPress by going to the wp-content folder and renaming the plugins folder to plugins.old. This then made it possible to start WordPress.

    So this action seems to confirm the problem is associated within the plugins folder. So I then renamed the plugins folder back to the default and the problem reappeared. Because I had earlier deactivated and then reactivated each plugin in turn and discovered that NextGen was causing the conflict, I decided to temporarily rename the nextgen-gallery folder to temp.nextgen-gallery as a test.

    Everything now works including the permalink postname’ option.

    At least I can access the dashboard but I would like to be able to resolve the NextGen issue so I can continue to use the plugin. Would it be safe to simply delete the NextGen plugin via the dashboard or from the wp-content/plugins folder and then download and install a fresh NextGen plugin?

    Any ideas how I might best go about doing this would be very much appreciated.

    Thank you.

    joperami

    (@joperami)

    11 years, 4 months ago

    i have the same error, all pages are redirected to the ‘home’ page when clicked, and it fixed when i deactivate the nextgen plugin.

    but i want to use the nextgen gallery plugin..

    Do you still have this trouble ? or how did you fix it ?..

    Thanks for any help.

    WPyogi

    (@wpyogi)

    11 years, 4 months ago

    The best way to get help with NGG is to ask on their forum here:

    https://ww.wp.xz.cn/support/plugin/nextgen-gallery#postform

    directrosa

    (@directrosa)

    10 years, 11 months ago

    I had same issue and was able to get back to WP dashboard by following ARC1’s steps of renaming the plugins folder. Accessed WP dashboard and deleted Next Gen. All good.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Exception Thrown – not defined for ExtensibleObject – error’ is closed to new replies.