After using the “To look for option_name(s):” box below the list of orphans, it gives me a list where the search query was found.
There isn’t an option to delete these results, where can I do this?
I’ve added a screenshot below to help explain – I wanted to remove the results listed:
It works on WP Multisite.
I have a 171 MB database and it took a good minute or two for it to caugh up all the options it thinks are orphaned.
Now being a multisite, there is no telling if the changed affect one blog or the entire network, so I won’t be using it myself.
For anyone else using it try to set the PHP timeout limit higher and the memory limit higher so it doesn’t time out.
I am using a crazy Dedicated server and I don’t think this plugin will play ball with shared environments such as GoDaddy.
Hope this helps others out there, and I really hope either the WP team takes this one in or the plugin author does some more work or releases a premium version. Would be very helpful in a production environment.
]]>It started doing it last week.
Any help with this issue would be appreciated.
]]>Attempting to use (clicking Find Orphans) just takes you to a blank page.
]]>Hi everyone!
I’m getting this when i try to clean options (which i was able to do weeks ago): Error 500 – Internal server error
Does anyone know what may be causing it?
Thanks for your help!
]]>There is a message in the plugin for an upcoming 2.0 which will support multisite but I guess it never made it…
]]>After clicking “find orphaned packages” it loads for a long time and finally shows a page, where is the title “Clean options” but only white below it.
Does not work on my installation.
]]>Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 213 bytes) in /u1/home/ameliwdp/public_html/blog/wp-includes/plugin.php on line 569
i get this error after installing clean options
cant get into plugins to remove it
any ideas
After installing and activating this plugin for WP3.3-beta3, the dashboard is blank page. Login attempt works but dashboard remains blank. The site (home) page does render properly.
]]>Hi!
Just happened to know about this plugin while reading some comments somewhere…
So I tried “Clean Options” and it worked perfect. I was able to get rid of 1,5mb (!) of crap remaining from uninstalled and already deleted plugins.
I like your links to Google. Very convenient if we are not too sure of what the tag is about. To preview the elements before deleting them is also a great idea.
Yes! your plugin “Clean Options” is VERY useful and you should keep updating and promoting it.
I’m sure quite a few guys out there still don’t know about it. I will spread the word when I can in some comments…For the moment I already rated with 5 star ??
THANK YOU for your great contribution to the community!
Lucy
Fresh install of WordPress 3.1.3 and installed Clean Options Version 1.3.2. Activation went fine.
But I received the following error when going to Tools > CleanOptions (cleanoptions.php):
Notice: wp_specialchars is deprecated since version 2.8! Use esc_html() instead. in /home/test/public_html/wp-includes/functions.php on line 3303
Notice: wp_specialchars is deprecated since version 2.8! Use esc_html() instead. in /home/test/public_html/wp-includes/functions.php on line 3303
Notice: wp_specialchars is deprecated since version 2.8! Use esc_html() instead. in /home/test/public_html/wp-includes/functions.php on line 3303
]]>This plugin still lists options after they have been removed via phpMyAdmin. This should not occur. Maybe the plugin is caching it’s results?
To reiterate, I ran a search for orphaned items, and saw the message:
“The Options table currently has 1676 found rows.”
After the report, I used phpMyAdmin to remove orphaned entries. I then logged back into wp-admin and ran the orphan search again. This time I saw the message:
“The Options table currently has 1257 found rows.”
But… It still displayed the items I deleted. Both phpMyAdmin searches and MySQL queries indicate that those items are not in the database.
Also, the three “Search files by” text fields are not accepting text entry. Meaning I cannot type text into those fields.
]]>