stupid_moron

Yes, I can confirm, changing the Table Prefixes does destroy your install with WP Lockup. I tried it on a site that I didn’t mind killing and there was no way back. This forum seems to have no answers either I’m afraid. Best is to re-install WordPress and always have a backup available (I did, but couldn’t be bothered ??

N.B. The sites that I have it working on only take advantage of the CAPTCHA aspect of it and that seems to be perfectly fine, even with the latest version of WordPress (3.8.1). Just don’t use “Lockup Database” or it will. I guess I won’t have any more buyers for this plugin now ??

Unrelated, but it’s the end of an era; Expert WordPress closes 1 May ??

Yes, ‘mahsandeep’ we might all benefit from exactly HOW you did this “after i created new database in phpmyadmin” trick.

I messed up mine on a live site (as Xampp won’t run with my AV).

Who says the is “[resolved]”, it is not! One user just said they fixed it, but didn’t elaborate. Hardly “[resolved]”!

I have a Developer license and I’ve come unstuck – the guy’s domains are all up for sale! He’s left no way of ‘leaving the door open on the way out’ either, so I guess we’re all screwed ??

Yes, it was a great plugin, but I’m afraid now it’s gone. It does seem to still be working on those sites I did activate it on, but new ones are gone. I still had 90 odd activations left, but if the guy is unreachable, that it. Let’s just hope he reads this and has a conscience – it’s O.K., I’ve exhaled already.

Yeah, it splattered red text all over my site too. Reading your comments, I went to my “Share This” plugin and switched off the Facebook like button in the plugin’s control panel and it went away.
Looks like some French hacker has found a way to compromise Facebook in some way ?? Or is it the plugin code?

Hi,

I hope someone can help. I just tried to upgrade to the latest version of WordPress and it hung.
Now all I can get is;

“Fatal error: Call to undefined function wp() in /home/CPANEL_USERNAME/public_html/wp-blog-header.php on line 14”

Is there anything I can do to get back to where I was before I tried to upgrade?

I was just about to install a backup plugin – please tell me that my work is not gone forever.

I know I’m really dumb for asking this, but why can’t the WordPress install system first look to see if there is enough space, stop if there isn’t and otherwise make a backup of anything needed to get the site back up again? I’m sure WordPress’ tech people are sick of dealing with this issue, so what is so hard about implementing what I just suggested?

Thank you Master Ipstenu.
Knowledge is power!
It fixed the complete crash problem.
On looking at the contents of that folder, I saw three plugins that had been updated. The first one I chose was “What Would Seth Godin Do” so I removed it, renamed the dir to its original state and everything is fine again.
Whatever Seth might have done, I don’t want him to do it to my blog again!

My user name is appropriate – I trusted my host’s instructions. They say to set the permissions to 755 in their “Installing WordPress” help article. When I changed /wp-content/ to 777 it started working.

Yes, I seem to have attempted the impossible here too, but from Fantastico.
What I want is “www.sitename.com/directory/blog” but it will seemingly allow only “www.sitename.com/blog” because all attempts to specify another subdirectory; “/directory/blog/” or “directory/blog” etc will not work.
With systems such as servers, which have fastidious requirements for syntax, it never fails to amaze me why people who write these installation instructions cannot simply provide a “Like this; ‘abc’ (without the quotes).” example.