Mick Levin

Workaround:

ALTER TABLE wp_awpcp_payments CHANGE user_id user_id INT( 10 ) NULL

I wonder if that had to be accounted for before doing a DB manipulation?

Thanks! ??

Thanks!

Looks like most of the configuration parameters are available only in the commercial version of this plugin.

FYI: When changing the URL of the WordPress site, one always has to rewrite the content of the posts/pages to update the URL of all embedded images too.

It’s not just a click-and-forget easy action, changing your domain name…

Mark, thanks a lot!

Details:

That’s a problem with compatibility with one of few plugins. Try to deactivate them all, then activate one at a time, and see which one breaks the site.

There are many ways to deactivate all plugins, my preferred one is to update the MySQL database, the table wp_options, record active_plugins. Save it’s old value somewhere, and replace with this:

a:0:{}

In my case the guilty plugin calls the function “current_user_can” at improper time.

Your case could be the same – most likely, it calls current_user_can() right from the constructor, rather than from a method, which has to be called via add_action (‘init’, …).

It might be something new to WP 3.8 – at the time the plugin is being constructed, the wp-include\pluggable.php had not been called yet, and the function wp_get_current_user is not being defined yet.

So it’s up to the plugin’s author to fix that.

Details:

In my case the guilty plugin calls the function “current_user_can” at improper time.

You case could be the same – most likely, it calls current_user_can() right from the constructor, rather than from a method, which has to be called via add_action (‘init’, …).

It might be something new to WP 3.8 – at the time the plugin is being constructed, the wp-include\pluggable.php had not been called yet, and the function wp_get_current_user is not being defined yet.

So it’s up to the plugin’s author to fix that.

Details:

In my case the guilty plugin calls the function “current_user_can” at improper time.

You case could be the same – most likely, it calls current_user_can() right from the constructor, rather than from a method, which has to be called via add_action (‘init’, …).

It might be something new to WP 3.8 – at the time the plugin is being constructed, the wp-include\pluggable.php had not been called yet, and the function wp_get_current_user is not being defined yet.

So it’s up to the plugin’s author to fix that.

That’s a problem with compatibility with one of few plugins. Try to deactivate them all, then activate one at a time, and see which one breaks the site.

There are many ways to deactivate all plugins, my preferred one is to update the MySQL database, the table wp_options, record active_plugins. Save it’s old value somewhere, and replace with this:

a:0:{}

—
Видимо есть проблема с одним или несколькими плагинами. Попробуйте деактивировать их все, и затем активировать по одному, пока сайт не сломается опять.

The problem is that the plugin changed the name during the update – it HAS to be deactivated, then activated again.

Thanks GF!