Version 1.3 with fatal error

  • iuato

    (@iuato)


    8 years ago

    Hi,

    I updated the version from 1.2 to 1.3 and got a blank screen, both administrative page and public page.

    Deleted the plugin from file system and install again version 1.3, but when I try to activate the plugin, I got this message:

    Plugin could not be activated because it triggered a fatal error.

    Please, what could be wrong? Version 1.2 was working fine.

    Thanks

Viewing 14 replies - 1 through 14 (of 14 total)
  • insert-post-ads

    (@insertpostads)

    8 years ago

    Hi @iuato,
    Could you please try to temporarily switch to a default theme and disable other plugins? Possibly there is some conflict.
    Did you try on different browsers?

    ahillmortons

    (@ahillmortons)

    8 years ago

    We’ve had the same issue. Had to roll back to the old version.

    insert-post-ads

    (@insertpostads)

    8 years ago

    We do NOT recommend to roll back to previous versions. We’ve published a hotfix today. Could you please try to delete the plugin and install the latest version?

    mikepetersonwi

    (@mikepetersonwi)

    8 years ago

    I received the same fatal error. I deactivated all plugins, manually removed the plugin directory from the plugins directory (as it failed to uninstall,) reinstalled the plugin, and still receive the error.

    ahillmortons

    (@ahillmortons)

    8 years ago

    Hi,

    Thanks for your reply, the new files appear to be exactly the same which would cause the same errors, are there some new files elsewhere with the hotfix?

    Thanks

    insert-post-ads

    (@insertpostads)

    8 years ago

    Thanks a lot for notifying us.
    We’ve just fixed this. Please, try to install the latest update – 1.3.1
    If you can’t delete or update the previous version, just remove the folder “insert-post-ads” which is located on your webserver at “<your website path>/wp-content/plugins” folder.

    Please, let us know if you still have problems with the plugin.
    If there are still some errors after updating to 1.3.1, please, send us exact error messages or screenshots.

    mikepetersonwi

    (@mikepetersonwi)

    8 years ago

    I’ve uninstalled and reinstalled 1.3.1 without error and I am still having issues with Content Aware Sidebars.

    insert-post-ads

    (@insertpostads)

    8 years ago

    Content Aware Sidebars compatibility is a separate topic. We see that Content Aware Sidebars developer can’t reproduce the issue with our plugin: https://wordpress.org/support/topic/sidebar-conditions-arent-working/ It may be caused by other plugins or a theme. Please, try to temporarily switch to the default theme and check if the problem appears.

    Lucian R.

    (@rlucian)

    8 years ago

    Have the same issue after update to 1.3 and the last verssion 1.3.1 not fixed the problem. I get fatal error on …/wp-content/plugins/insert-post-ads/insert-post-ads.php on line 669. Theme is Blognews v2.6 and WP is the latest 4.9.4. Until verssion 3.0 was 100% ok.

    insert-post-ads

    (@insertpostads)

    8 years ago

    Hi, do you have the same problem on the default WP theme?

    Lucian R.

    (@rlucian)

    8 years ago

    Yes.

    Thread Starter iuato

    (@iuato)

    7 years, 11 months ago

    Hi,

    Today I tryed to update from version 1.2 to 1.3.1 and got a blank screen. Had to delete 1.3.1 and rollback to 1.2.

    Thanks

    Lucian R.

    (@rlucian)

    7 years, 11 months ago

    Where i can get 1.2 ?

    insert-post-ads

    (@insertpostads)

    7 years, 11 months ago

    Hi,
    Just try to go to the “Installed plugins” menu. Deactivate the plugin. Refresh the page. Activate the plugin again.
    If it doesn’t help – just delete the plugin, clear cache, install it again via wp-admin/plugin-install.php page.
    Also, please, check if the WP DEBUG mode is disabled.
    We do not recommend to use older versions.

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

The topic ‘Version 1.3 with fatal error’ is closed to new replies.