Ron Fredericks

same problem in one more file: wiki_dashboard_widget.php

on line 12, add dummy 0 , as 2nd argument to $wpdb->prepare() like this:


$posts = $wpdb->get_results($wpdb->prepare("select * from $wpdb->posts where ID in (
select post_id from $wpdb->postmeta where
meta_key = 'wiki_page' and meta_value = 1)
or post_type in ('wiki') order by post_modified desc limit 5", 0)); // add dummy variable to satisfy argument 2 warning, RDF


Good point Keesiemeijer:

I am using the twentyten theme, I think that is the default.

Can you use a private post without it clobbering the category list display?

Best regards,

Ron

I discovered that my previous example of adding a paragraph tag around my ShareThis bookmark had a bad side effect… A new ShareThis button would show up above my page header making for a dumb looking blog.

I did come up with an improved way to solve this problem so I am sharing it here. Within the sharethis.php plugin file, make a simple modification like this:

if(!empty($widget)){  // <div>...</div> added  to $sharethis string, RDF
		$sharethis = '<div><script type="text/javascript">SHARETHIS.addEntry({ title: "'.str_replace('"', '\"', strip_tags(get_the_title())).'", url: "'.get_permalink($post->ID).'" });</script></div>';
	}

OK,

I solved this problem myself after reading other forum posts found by searching “permalink reset”. To fix this type of problem, I went to my admin permalink panel and changed the permalink format to some other format. I found that the new permalink structure worked fine. So then I went back to the admin permalink settings page and reset my parmalink structure back to my original format.

Permalinks restored.

BTW: I discovered that my admin panel blocks me from entering my name and password when a particular plugin is activated, followed by logging out. To log back in I normally rename that particular plugin directory to deactivate it, or the entire plugin directory to deactive all plugins. This trick failed this time, so I took the more drastic measure of reinstalling all the wordpress blog code. Neat that wordpress.org’s code and database structure is so rugged.

I hope this helps others when the time comes,

Ron

I have partially solved this problem – see post:
http://wordpress.org/support/topic/176358