Ad Lagendijk

https://www.stringcat.com/company_blog/2012/09/09/brute-force-attack-on-a-wifi-network/

The problem is not solved.
When Google News is down or when the site using this plugin is temporarily ip-blocked by Google there is no news feed. Under these circumstances the widget shows the “Atypical …” error message. Quite embarrassing. A better error text seems something like “News service temporarily unavailable”

You can find all information here. It is a free opensource collection of php scripts with one convenient browser interface to manage MySQL databases.

I checked your site. It does seem top have a caching problem. However even without a caching plugin your site should not be that slow. The cache problem might well be with your hoster. I abandoned Bluehost for hosting my blogs for exactly that reason: slow site.

If your theme was well designed it should survive the upgrade.

Do you have a backup?
Manipulation with the database directly is best done using phpAdmin.

This issue has come up several times in the WordPress forums. The solution is usually a combination of changing folder and file protection settings and adding some changes to wp-config.php. Look at related problem and another one.

You have nested your php tags and you cannot do that.

I have also used BlueHost for WordPress without any problems.Su stands for single user. BlueHost uses a single-user environment.

It is in your javascript. If I disable that it seems to work.

When I run html tidy on your site I find
< li > problems. It might not be the solution, but you have to fix it anyway.

Install the plugin post-teaser.

Many people complain about WordPress whereas their problem lies with their webhoster. Or with a newly installed plugin. Webhosters typically change their file protection settings without telling you. Or they change the settings of their Apache server or their php.ini settings. You first have to rule all that out before you start blaming WordPress. And good luck with your finding a better blog platform. I couldn’t find one yet.

It could be a mysql version problem

Did you deactivate all your plugins?

Do you have a wp-content/upgrade folder? If not: create it. If yes, and it still does not work chmod the upgrade folder and anything in it. This is what did the job for me. The problem is usually the file protection settings by the server of the web hoster. Another problem might be that the folder exists but is owned by “nobody”. Any decent hoster has a facility to “chown” the nobody files to its rightful owner.

By the way even if the upgrade folder can be created, plugin upgrading might still not work. One error message could be “cannot delete old plugin files”. The solution described here worked for me.