Lots of error code if I update to latest version in WP 3.8.3 & 39

Hi xprt007,

I’m not sure that the error is actually coming from AWPCP. All of the errors above show the problem is coming from wp-content/plugins/bp-forum-notifier, which is not us.

What happens if you upgrade to AWPCP 3.2.2 and temporarily disable that plugin?

If that works, then BP Forum Notifier may have some issues with 3.9 that our 3.2.1 version of AWPCP manages to hide from you. I suspect that is the case here, since we’re not seeing those errors on other sites.

I too have masses of warning messages when i upgrade to the latest version on WP3.9 – and whilst the warnings are pointing to other plugins – they only started appearing when the upgrade of this plugin was done:

Notice: load_plugin_textdomain was called with an argument that is deprecated since version 2.7 with no alternative available. in /var/sites/s/slade-tonbridge.co.uk/public_html/wp-includes/functions.php on line 3195

Notice: Undefined index: cptch_login_form in /var/sites/s/slade-tonbridge.co.uk/public_html/wp-content/plugins/captcha/captcha.php on line 197

Notice: Undefined index: cptch_comments_form in /var/sites/s/slade-tonbridge.co.uk/public_html/wp-content/plugins/captcha/captcha.php on line 202

Notice: Undefined index: cptch_register_form in /var/sites/s/slade-tonbridge.co.uk/public_html/wp-content/plugins/captcha/captcha.php on line 213

Notice: Undefined index: cptch_lost_password_form in /var/sites/s/slade-tonbridge.co.uk/public_html/wp-content/plugins/captcha/captcha.php on line 220

Notice: Undefined index: action in /var/sites/s/slade-tonbridge.co.uk/public_html/wp-content/plugins/wp-filemanager/wp-filemanager.php on line 65

Notice: bbp_setup_current_user was called incorrectly. The current user is being initialized without using $wp->init(). Please see Debugging in WordPress for more information. (This message was added in version 2.3.) in /var/sites/s/slade-tonbridge.co.uk/public_html/wp-includes/functions.php on line 3245

Notice: bp_setup_current_user was called incorrectly. The current user is being initialized without using $wp->init(). Please see Debugging in WordPress for more information. (This message was added in version 1.7.) in /var/sites/s/slade-tonbridge.co.uk/public_html/wp-includes/functions.php on line 3245

Notice: register_sidebar_widget is deprecated since version 2.8! Use wp_register_sidebar_widget() instead. in /var/sites/s/slade-tonbridge.co.uk/public_html/wp-includes/functions.php on line 3078

Notice: wpdb::prepare was called incorrectly. The query argument of wpdb::prepare() must have a placeholder. Please see Debugging in WordPress for more information. (This message was added in version 3.9.) in /var/sites/s/slade-tonbridge.co.uk/public_html/wp-includes/functions.php on line 3245

Notice: Undefined offset: 1 in /var/sites/s/slade-tonbridge.co.uk/public_html/wp-content/plugins/cookie-opt-in/wp_cookie_opt_in.php on line 399

Notice: Constant WP_MEMORY_LIMIT already defined in /var/sites/s/slade-tonbridge.co.uk/public_html/wp-config.php on line 117

Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /var/sites/s/slade-tonbridge.co.uk/public_html/wp-includes/functions.php on line 3193

Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /var/sites/s/slade-tonbridge.co.uk/public_html/wp-includes/functions.php on line 3193

Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /var/sites/s/slade-tonbridge.co.uk/public_html/wp-includes/functions.php on line 3193

Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /var/sites/s/slade-tonbridge.co.uk/public_html/wp-includes/functions.php on line 3193

Notice: Undefined index: wop_name_6 in /var/sites/s/slade-tonbridge.co.uk/public_html/wp-content/plugins/widgets-on-pages/widgets_on_pages.php on line 248

Notice: Undefined index: wop_name_7 in /var/sites/s/slade-tonbridge.co.uk/public_html/wp-content/plugins/widgets-on-pages/widgets_on_pages.php on line 248
=======

Unfortunately I found that even deactivating it & then removing it left all the warning messages there (despite clearing cache) – and the only way I could get the site back up and running was to revert to a back up I’d taken just before upgrading (fortunately!)

I’m guessing it’s a conflict somewhere – but obviously Im not going to attempt another upgrade of this any time soon.

Hi Rich,

Looking at the paths of those error messages, none of them are actually coming out of AWPCP. Your errors are from other plugins and possibly your theme. I can’t say why it specifically happened at the time you upgraded AWPCP, it could have been a coincidence, depending on cache flush times, etc. The source of the errors doesn’t seem to have anything to do with AWPCP.

This is why “even deactivating it & then removing it left all the warning messages there (despite clearing cache)”. Those errors are the results of these plugins not working well with WP 3.9:
– widgets-on-pages
– wp-filemanager
– captcha
– cookie-opt-in

Hi

Thank you for the response.

I tried this out:

Deactivated BP notifier, then went ahead to update the classifieds plugin & immediately got the following errors:

Notice: Undefined property: stdClass::$id in /home2/as/public_html/wp-content/plugins/bp-gallery/includes/bpa.core.php on line 1781

Notice: Undefined property: stdClass::$image_slug in /home2/as/public_html/wp-content/plugins/bp-gallery/includes/bpa.core.php on line 173

Notice: Undefined property: stdClass::$id in /home2/as/public_html/wp-content/plugins/bp-gallery/includes/bpa.core.php on line 181

Notice: Undefined index: display-page in /home2/as/public_html/wp-content/plugins/recipe-press/classes/initialize.php on line 219

Notice: wpdb::prepare wurde fehlerhaft aufgerufen. Der Abfrage-Parameter wpdb::prepare() ben?tigt einen Platzhalter. Schau Dir Debugging in WordPress an, um mehr darüber zu erfahren. (Diese Meldung wurde in Version 3.9 hinzugefügt.) in /home2/as/public_html/wp-includes/functions.php on line 3245

Notice: has_cap wurde mit einem Parameter oder Argument aufgerufen, der seit Version 2.0 veraltet ist! Die Benutzung von user_level in Plugins und Themes ist veraltet. Nutze stattdessen das Abfragen von roles oder capabilities. in /home2/as/public_html/wp-includes/functions.php on line 3193

Das Plugin wurde erfolgreich reaktiviert.

<= Means plugin was successfully reactivated

#####

At the frontend is this what I have:

Notice: bbp_setup_current_user was called incorrectly. The current user is being initialized without using $wp->init(). Please see Debugging in WordPress for more information. (This message was added in version 2.3.) in /home2/as/public_html/wp-includes/functions.php on line 3245

Notice: bp_setup_current_user was called incorrectly. The current user is being initialized without using $wp->init(). Please see Debugging in WordPress for more information. (This message was added in version 1.7.) in /home2/as/public_html/wp-includes/functions.php on line 3245

Notice: Undefined property: stdClass::$id in /home2/as/public_html/wp-content/plugins/bp-gallery/includes/bpa.core.php on line 1781

Notice: Undefined property: stdClass::$image_slug in /home2/as/public_html/wp-content/plugins/bp-gallery/includes/bpa.core.php on line 173

Notice: Undefined property: stdClass::$id in /home2/as/public_html/wp-content/plugins/bp-gallery/includes/bpa.core.php on line 181

Notice: Undefined property: stdClass::$id in /home2/as/public_html/wp-content/plugins/bp-gallery/includes/bpa.core.php on line 207

Notice: Undefined index: display-page in /home2/as/public_html/wp-content/plugins/recipe-press/classes/initialize.php on line 219

###

The only thing leaving me with no errors was reverting to 3.2.1 & restoring DB.

So quite confounded.

Hi xprt007,

In your case, it looks as if you have different plugins that are not compatible with WP 3.9 and they don’t appear to be related to AWPCP either.

Looking at the path of the file in the error message:
/home2/as/public_html/wp-content/plugins/bp-gallery/includes/bpa.core.php

The last entry is the filename. The entry after “plugins” indicates the name of the plugin that is failing. In your case, that’s:
– bp-gallery
– recipe-press

The other errors coming out indicate that these plugins are calling API methods that have changed as of WP 3.9. AWPCP did some updating for this release and the messages are not coming out of it.

If they were, you would see:
/home2/as/public_html/wp-content/plugins/another-wordpress-classifieds-plugin/ as the path. But that’s not what we see above.

I would suggest deactivating these plugins and see what happens to the errors. I believe they will disappear.