Fatal Error

  • Fatal error: Uncaught Error: Call to a member function get_page_permastruct() on null in /home3/waferswi/public_html/wp-includes/link-template.php:435 Stack trace: #0 /home3/waferswi/public_html/wp-includes/link-template.php(397): _get_page_link(Object(WP_Post), false, false) #1 /home3/waferswi/public_html/wp-includes/link-template.php(197): get_page_link(Object(WP_Post), false, false) #2 /home3/waferswi/public_html/wp-content/plugins/ecwid-shopping-cart/includes/class-ecwid-store-page.php(108): get_permalink(Object(WP_Post)) #3 /home3/waferswi/public_html/wp-content/plugins/ecwid-shopping-cart/includes/class-ecwid-store-page.php(497): Ecwid_Store_Page::get_store_url() #4 /home3/waferswi/public_html/wp-includes/class-wp-hook.php(312): Ecwid_Store_Page::set_store_url(Array) #5 /home3/waferswi/public_html/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters(”, Array) #6 /home3/waferswi/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #7 /home3/waferswi/public_html/wp-includes/option.php(581): do_act in /home3/waferswi/public_html/wp-includes/link-template.php on line 435

    I’m getting this error. i have no idea about the error.

    It happens when I try to see installed plugins from the left panel. I cannot access plugins nor can I deactivate them from the menu. It looks like some plugin is giving an error after the update. Please help.

    • This topic was modified 1 year, 1 month ago by wajiyaz.
    • This topic was modified 1 year, 1 month ago by wajiyaz.

    The page I need help with: [log in to see the link]

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

  • The error seems to be triggered by the plugin “Ecwid Ecommerce Shopping Cart”. I would recommend deactivating this.

    Since you can’t access the plugin list in the backend, the best way to do this is via FTP. Log in via FTP and remove the directory /wp-content/plugins/ecwid-shopping-cart (if necessary, you can also download it beforehand to save it). The support of your hoster can help you to connect via FTP.

    If you can then call up the plugin list again, you can try to install the plugin again. If the problem occurs again, remove it again and contact their support: https://www.ads-software.com/support/plugin/ecwid-shopping-cart/

    Hello,
    This is Joanna from the Ecwid Customer Care team.

    I’m sorry that you encountered this issue! Please, send us the following details at [email protected]:

    • Your store ID (Where is my Store ID?);
    • Link to your site;
    • Ecwid plugin log: open your WordPress admin panel and navigate to wp-admin/admin.php?page=ec_debug (add this path to your site URL), then click “Download log file” and send us the generated file.

    We will investigate what caused the issue and check how it can be fixed. Thank you!

    Thread Starter wajiyaz

    (@wajiyaz)

    @threadi I tried to figure out the problematic plugin using “Plugin Detective”. I tried disabling or rolling back plugin updates, but nothing worked. Then I rolled back the update to the theme “Personalblogily, ” which fixed the problem. So, it concludes that the update of the theme was not compatible with the plugin or was erroneous.
    However, when I log in to WordPress I get the following error which again seems to be theme-related.

    Errors:

    92 bytes failed with errno=21 Is a directory in /home3/waferswi/public_html/wp-includes/pomo/streams.php on line 189

    Warning: Cannot modify header information – headers already sent by (output started at /home3/waferswi/public_html/wp-includes/pomo/streams.php:189) in /home3/waferswi/public_html/wp-admin/admin-header.php on line 9

    threadi

    (@threadi)

    These are only consequential errors because something else is output before them. If you suspect the theme to be the cause, change it. If you can no longer access the backend, you can also delete the directory of the theme via FTP. WordPress should then automatically use a standard theme that is hopefully still in parallel.

    Thread Starter wajiyaz

    (@wajiyaz)

    Thanks for the advice. Yes it happened once before too. At that time, I changed the theme as u suggested. This time I rolled back. Because, making interface adjustments and configuring plug ins is an added overhead.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Fatal Error’ is closed to new replies.