Posted 1 year ago #
Fatal error: Cannot redeclare aioseop_mrt_fix_meta() (previously declared in /home/yodelay/public_html/wp-content/plugins/all-in-one-seo-pack/all_in_one_seo_pack.php:1095) in /home/yodelay/public_html/wp-content/plugins/all-in-one-seo-pack/all_in_one_seo_pack.php on line 1109
This error message appears after new blog creation in place of: 'Congratulations! Your %s website is now ready...' click to login etc.
We are using:
Wordpress 3.0 - All in one SEO Pack 1.6.1.2
Posted 1 year ago #
Upgrade to the latest version of All in One SEO Pack.
Posted 1 year ago #
We are using latest versions
Posted 1 year ago #
You said you're using 1.6.1.2. The latest version is 1.6.12.1.
Posted 1 year ago #
Sorry, we have tried updating the plugin, the error still occurs.
Posted 1 year ago #
Maybe you require further information about any other plugins we are using or any particular settings...
I am thinking the issue is something to do with aioseop hooking into the page header and then running similar code when a new blog is created. Maybe someone knows where the add_action() for this new blog hook is located within the aioseop plugin?
The aioseop plugin that we have installed is activated for the main blog only and not network activated.
Posted 1 year ago #
So you're using multi-site? That would have been helpful to know.
Upgrade to the latest version of AIOSEOP. You can't be getting that error if it's been successfully upgraded. Those line numbers don't exist.
What is the URL of your site?
Posted 1 year ago #
Yes it was originally WPMU 2.9, we then upgraded to 3.0 and enabled multi-site. The error occurs when you create a new blog as a new user or existing user. The aioseop plugin is definately the latest version.
Posted 1 year ago #
have just found out that if you disable aioseop, it will cause basically the same error message (Fatal Error: Cannot redeclare...) but with a different plugin function.
Maybe this thread should be moved to the multi-site forums, sorry for any inconvenience.
Posted 1 year ago #
SOLVED
Was the supporter plugin from WPMUDEV causing the issue.
Posted 1 year ago #
What plugin is that?
This topic has been closed to new replies.
