Gwyneth Llewelyn

Wow, thanks for the quick update! I upgraded it, got the same error, but deleting the plugin and installing 4.8.2.2 worked flawlessly for me. Many thanks!

Thanks for the very, very thorough reply, Matt! I sincerely hope that the extreme edge case I found actually never happens any more.

And I do apologise for taking so much of your time just to figure out that deleting pingfm_options was really a bad, bad idea…

Here is how I do my upgrades from WP 2.9.2 (or WP MU 2.9.2) to WP 3.0 Beta 2:

1. Log in to WP 2.9.2
2. Go to Plugins, Add New, search for “WordPress Beta Tester” and install it
3. Under Tools, you have now a new submenu: “Beta Testing”. Click on it.
4. Select “Bleeding edge nightlies” and save changes
5. Under Tools, now go to “Upgrade”
6. You should get something like:

   There is a new version of WordPress available for upgrade
   
   You are using a development version of WordPress. You can upgrade to the latest nightly build automatically or download the nightly build and install it manually:

7. Select “Upgrade Automatically”

That’s it ?? This should always do the trick. My last update (just tested now) brought it to 3.0-beta2-14822 (as shown on the Dashboard).

I would love to hear about that, too ?? I like the plugin a lot.

Apparently the problem is with the way options are passed in the form.

This forum post gives a clue on how to fix it, but I really don’t want to mess with the PingPressFM plugin; it looks like PingPressFM echoes the whole HTML+JavaScript to the screen, and adding PHP in the middle of it might not be a good idea…

Thanks, @feedmeastraycat ! I had the same problem with SimplePie on the Accessible News Ticker (ANT) plugin, which uses a copy of its own SimplePie (which has the same problem). Changing the included line as per your suggestion fixed ANT for me!

I’m having the exact problem myself (strangely, only in a 2.8 install that hasn’t English as a default language; other installs, even with the same language, don’t have any problems) but apparently it has no effect whatsoever on the output of the theme… it’s just annoying!

Thank you very much, creatov! It worked quite well for me too. Now I just need Gears to work with Safari 4/WebKit too hehe… at least in WordPress, Gears says it’s installed properly… but the “Turbo” button says otherwise.

Anyway, my major worry was really the problem with the links. I’m glad it’s all Apple’s fault *grins* and not WordPress’ or TinyMCE’s.

I have sadly the very same issue. Bummer! Thankfully, if I waited a bit, at least the post auto-saved to draft, so I didn’t lose everything.

I’m glad to see that it’s a TinyMCE issue and not a WordPress one, but still, I can imagine that there won’t be a quick fix to this ?? Hmm a pity that Apple’s Safari writes the Beta over the last version. Ironically, I have been beta-testing Safari 4 for quite a long time now, and only the last “public” release has this issue with TinyMCE; the one available for the closed Beta worked flawlessly, and since the first release, it was always 100% Acid3 Test compatible.

One wonders if someone knows of a workaround to this?… The TinyMCE forums only lists it and the TinyMCE is being aware of the issue and promising to fix it in an upcoming patched version…

Hi! I keep forgetting to do this on my own blog; I have a category “Homepage” with which I like to “flag” all posts that actually go on the front page, instead of showing all categories.

The simplest way to do this seems to be:

<?php query_posts("cat=1"); ?>
Your loop stuff goes here

It certainly works for me!

Try the tips at https://www.ads-software.com/support/topic/118278?replies=12#post-671605 — they worked for me.

Note that there is a include_once('widgets.php'); on line 562 too; removing it as well seems to make the plugin work fine for me under 2.3.2.

After reading the other entries, I did something similar to GrillSgt…

functions.php:

<?php
if ( function_exists('register_sidebar') ) {
	register_sidebar(array(
		'name' => 'Sidebar_1',
		'before_widget' => '',
		'after_widget' => '',
		'before_title' => '<h3>',
		'after_title' => '</h3>'
		));
	register_sidebar(array(
		'name' => 'Sidebar_2',
		'before_widget' => '',
		'after_widget' => '',
		'before_title' => '<h3>',
		'after_title' => '</h3>'
		));
}

?>

sidebar.php:

Replace

dynamic_sidebar('Sidebar_1') with dynamic_sidebar(1) and

dynamic_sidebar('Sidebar_2') with dynamic_sidebar(2)

I don’t know if this is a changed behaviour in WP 2.3.2, it’s the first time I get widgets working, and I love the jd-nebula-3c-10 theme ??

Oops. Please disregard the above comment. Actually, it was all my fault, really — I had two different versions of an OpenID authentication plugin installed, and both competing for “taking over” the comments section. No wonder I got weird errors when trying to call a modified template for the old (uninstalled) plugin :-/

If you’re keen on OpenID authentication — and these days you should be! — use this plugin instead. So far, it’s the easiest I’ve found out, it works properly, and only does minimal changes to your comments.php (in most cases, it’ll even manage to add everything it needs without manual configuration) and leaves all the rest of your WordPress installation untouched. Also, it allows tying your manually-created users to OpenIDs, so people who have already registered can now assign OpenIDs to them…

And really — there are 4 or 5 different plugins for OpenID around — make sure you delete them completely before installing a new one. The older plugins are rather hard to install properly and require lots of files to be changed or added — delete them all ??

My apologies to VincentChow, my case most definitely is not related to yours (or to Dreamhost…), but is just a silly user mangling a perfectly good WP installation ??

Interesting, I’m in the same situation right now (using Dreamhost as well with the latest release). The comments stopped working on one of my blogs, and the only clue I got was those errors. I was pointed to take a look at the suexec.log (ie. probably php5.cgi was being called with the wrong permissions or something) but that doesn’t provide any errors, just a confirmation that it is being called.