Mark McKibben

I don’t know of any official documentation for child themes. However I have found by editing the nr_load_template function (found in now-reading-reloaded/now-reading.php) so it uses STYLESHEETPATH instead of TEMPLATEPATH; then my custom templates get loaded from my child theme’s directory.

When tested with a self-hosted WordPress blog on WordPress v2.7.1 with PollDaddy 2.5 and PollDaddy Polls 0.9, I no longer get the error listed above, however I continually get the message that I need to enter my PollDaddy details and when I try to enter them it does not save them.

When tested with a self-hosted WordPress blog on WordPress v2.7.1 with PollDaddy 2.5 and PollDaddy Polls 0.9, I no longer get the error listed above, however I continually get the message that I need to enter my PollDaddy details and when I try to enter them it does not save them.

@danielsands: I’m wasn’t blaming you, just reporting it in case others run across the same issue. And it wasn’t likely that you’d find the old plugin as it’s not hosted with WordPress Plugin directory (which I find makes it kind of odd that the updater assumes the 2 are the same).

Like arikontiainen, I had read that both plugins were no-longer needed. However when I try entering my PollDaddy account info into WordPress with both plugins enabled, I get the following error.
Catchable fatal error: Object of class WP_Error could not be converted to string in /wp-content/plugins/polldaddy/polldaddy-xml.php on line 57

Same problem here also on 2.7 official release, additional server details available upon request.

Thanks for the plugin and the quick fix. Just so you know, I experienced the problem on both WP 2.6.3 & WP 2.7-beta2-9718.

This bug appears to have been fixed in WP 2.6.

According to the plugin directory the plugin was last updated on April 13, 2008. I’d say it’s likely still under development.

If you’re using any other plugins on your blogs –particularly plugins that alter the post page– try deactivating them to see if one of them is causing a conflict. For example, the ancient WP-Amazon plugin causes problems with Simple Tags and if both are activated then neither works.

@ivovic: Nope, the only site I work at keeping the latest/greatest version is my test blog on my home server. All my production sites tend to stay on a version until I’m sure the plugins/themes I’m using are fully upgraded and I know things will work correctly. The site I upgraded and got caught with this bug was kind of an exception as I hadn’t upgraded it for a while and wanted to get caught up a bit (e.g. was still on 2.2.x).

Sure am, missed that bug when looking through the bugtracker. I hope they release the fix for that quick, the blog mostly affected by this uses custom fields extensively.

Thanks!

The first thing I would try is disabling ALL plugins you have on your site and resetting it to one of the default WP themes. From the little information you’ve provided, I don’t think that’ll fix it; but eliminating possible sources of the problem is always a good first step. Assuming that doesn’t work, try turning registration back off. Again from the info you’ve given, I find it unlikely this will help but another good troubleshooting step is to reverse any changes you’ve made.

Before we move on to more interesting stuff, if my above suggestions seem trite or too simple; let me just say after doing helpdesk for 6 years I’ve learned to always, always, always check the easy stuff first. ??

I don’t know what OS/PHP/MySQL your website runs under and you don’t say which part of the dashboard is showing the wrong info (e.g. is it the count of posts or the list of recent posts or both?). However I can tell you on my home/test server, I’m running Ubuntu Linux 6.06, Apache2, MySQL 5.0.22 and PHP 5.1.2 (your basic LAMP setup). I upgraded my test site to WP 2.0.4 as soon as it was released. I also was not automagically redirected to the upgrade page, went to it manually and my site has been working fine. I tried turning on “Anyone can register” and “Users must be registered and logged in to comment”. Clicking the update options button dropped me at wp-admin/options.php. Only the page was blank except for WP’s logo, a link to the codex, a link to these support forums, the version number (2.0.4) and the # of seconds it took to generate the page (1.78 seconds). I tried adding posts after changing those optoins but cannot recreate your problems.

Since other have mentioned using phoMyAdmin in this thread, I threw my test server’s data into phpMyAdmin and ran ANALYSE TABLE wp_posts;. It came back with these 2 error messages on wp_posts: “Key in wrong position at page 3072” and “Corrupt”. Then I used phpMyAdmin to run CHECK TABLE wp_posts EXTENDED and got back the same 2 errors plus 1 warning saying “Table is marked as crashed”. So then I tried REPAIR TABLE wp_posts; which phpMyAdmin says ran OK. I checked my dev blog again and it was still up & running fine for me. Maybe you should also try running at least ANALYSE TABLE wp_posts; via phpMyAdmin and see what happens?

You should take a look at this article in the Codex

All I was saying is that it could be legal, but it depends on where in the world you’re at. Also I’m not a lawyer; what I wrote above is just my opinion and I could be wrong. If you’re really concerned about this; then you should:
1. Check with a lawyer.
2. Maybe check with the sites you want to copy from.

Try going into the theme and editing it to point to the port you’re using.