Alexandre Pereira

I know, the recommendation is 7.2 but it wouldn’t show up on the cPanel. I decided to request an upgrade on the shared hosting plan, as I think it will probably upgrade the PHP version and a lot of other things.

But it was nice to know that I could fix it temporarily without having to delete the plugin. I had all but forgotten that I could just change the PHP version on cPanel.

My hosting was using PHP 5.3.29 so I changed it to 5.5.13 on the CPanel and it works fine now.

Whatever is going on at simple-payments.php line 220 seems to be a compatibility issue with PHP versions below 5.4 so it should solve the issue for now.

That’s how I did.

But it doesn’t matter. Editing the wp_options table to seek for twentyeleven instead didn’t fixed it either.

By the way, I’ve downloaded WordPress again and uploaded it to the server, replacing every WordPress file that was there when the problem appeared. It didn’t helped. :/

Yes, I’ve tried repairing with phpMyAdmin.
Yes, I’ve tried deleting all the plugins through FTP.
Yes, I’ve tried disabling all the plugins through phpMyAdmin.
No, I can’t change themes since the Admin Panel doesn’t work and the theme is the Twenty Eleven with custom CSS so it shouldn’t matter.

The offending rule on the CSS for the top border is this one:

/* =Header
----------------------------------------------- */

#branding {
	border-top: 2px solid #bbb;
	padding-bottom: 10px;
	position: relative;
	z-index: 2;
}

See that first command? It creates the freaking border. It shouldn’t be there when we’re using the image without showing the title.

I’m having the same problem. Everytime I try to access the admin panel with Jetpack activated, the site becomes unresponsive. It keeps loading the page and don’t stop.

It makes sense. When you have a newer version, he’ll only offer you to update to the next stable which comes after the installation you have.

Just use it until you hear the stable was launched and deactivate it. The update will install the stable version then.

I have the exact same problem. I want to be able to update to WordPress 3.2 Beta, RC, etc and not the nighties. I had trouble with these some times.

This plugin doesn’t really works as advertised. :/

May I make a suggestion? Could you put in there an option to not use a URL shortener?

I’ve edited my permalinks to be extremely short (i.e. “https://mysite.com/p/1234”) so even though it’s not as short as bit.ly it’s not very big and could fit on a tweet message.

You even could put in there a message warning about having a long url in permalink or something.

There’s always the option of not using permalinks (i.e. “https://mysite.com?p=1234”) so you may consider allowing that to be selected too.

What’s the format for CSV to use?

Anything related to taxonomy is giving this error. Maybe the edit-tags.php is not telling WordPress that it was called from WordPress?

I can confirm this. The Redirection plugin version 2.1.25, the current one, doesn’t play well with WordPress 3.0-beta-14792.

If you use a GMail account, you can try to put dot inside the username:

[email protected]
[email protected]
[email protected]

GMail corrects it to your default account, but sites tends to interpret them as different addresses.

Maybe you can use the plus trick too.

[email protected]
[email protected]

I’ve never tested it but yes, you can!

Sorry. I don’t think such tool exists. He’ll have to move each one of his arts mannually.

But I know the site Artician allows you to import your deviantART portifolio into theirs systems. It’s very similar so, if he’s just angry with dA, he can use this one instead.