http://wordpress.org/support/ WordPress › Support Tag: clean-options en Thu, 26 Nov 2009 11:17:37 +0000 http://wordpress.org/support/topic/332029#post-1282200 Sun, 15 Nov 2009 17:15:52 +0000 MichaelH 1282200@http://wordpress.org/support/ <p>See <a href="http://codex.wordpress.org/Database_Description">Database Description</a>.</p> <p>Related:<br /> <a href="http://wordpress.org/extend/plugins/clean-options/" rel="nofollow">http://wordpress.org/extend/plugins/clean-options/</a> </p> http://wordpress.org/support/topic/332029#post-1282196 Sun, 15 Nov 2009 17:11:48 +0000 OscarGuy 1282196@http://wordpress.org/support/ <p>I was trying several different types of plugin calendars and ultimately I chose one, but there are some errors. I'm thinking that one of the other plugins created a DB entry that I didn't want.</p> <p>How do I know which MySQL Databases are native to Word Press and which ones are plugin-generated? I want to delete all the plugin-generated ones and see if that fixes my problem, but I need to know where to start. </p> http://wordpress.org/support/topic/263205#post-1102597 Sat, 13 Jun 2009 23:52:26 +0000 Mittineague 1102597@http://wordpress.org/support/ <p>Sorry for the delayed response. For more timely responses, please post any problems in the support forum (as indicated in the plugin) where I will be instantly notified rather than need to check here.</p> <p>@vesket, Just to be sure we're on the same page here, you are referring to the plugin by Alex Rabe, version 1.3.3 correct?<br /> The Clean Options plugin does not have a "fix automatically", what exactly are you referring to?</p> <p>It may be that there is an incompatability issue. I will look into it.</p> <p>However, note that this plugin does not list only orphaned options, but rather options that appear to be orphaned. That is, the plugin will find true orphaned options, but may also find options that, as looked for by the regex used in the plugin, will appear to be orphaned when in fact they are not.</p> <p>The Clean Options plugin is written so that as best as is possible, WordPress Core options can not be accidently deleted. However, it is impossible to take into account all possible options from all possible plugins and themes. Thus the need for blogmasters, that hopefully have knowledge of their blog's particular plugin history, to investigate options in the list of possible orphans before removing them.</p> <p>The plugin has several ways to help users in identifying true vs. false orphans. All measures should be taken <em>before</em> any option is removed. Only when when it is certain that an option is truly an orphan should it then be removed. </p> http://wordpress.org/support/topic/263205#post-1080107 Thu, 21 May 2009 19:47:32 +0000 Gene53 1080107@http://wordpress.org/support/ <p>Hmm, was going to use this plugin but due to the Author's lack of response (and looks like he decided to stop development), guess I'll stay away from it.</p> <p>Too bad, could have been a very useful plugin.</p> <p>Cheers,<br /> Gene </p> http://wordpress.org/support/topic/263205#post-1049429 Sat, 18 Apr 2009 17:45:34 +0000 vesket 1049429@http://wordpress.org/support/ <p>Had a blog that was originally upgraded from 2.0 - until i ran the "fix automatically" in this plugin. The problems did show after a few weeks, it was impossible to add ng-gallery images. Remove and install of the gallery did trigger other problems due to "cleaned" rarely used database options.</p> <p>Had to reinstall the entire blog and database from scratch to fix the problems. </p> http://wordpress.org/support/topic/215481#post-897585 Thu, 13 Nov 2008 06:58:11 +0000 Mittineague 897585@http://wordpress.org/support/ <p>I have heard of the "no name" problem before. The plugin uses the option_name value of the row instead of the id value. This is used to display next to the select box, and in subsequent handling. When I first wrote the plugin I assumed (I know, I know) that all options would have a name. I don't know how they would work without one. When I first heard of this problem, I thought it must only be a rare event (silly me), so I put in an error message to alert the plugin user so that the row could be deleted in another way (i.e. phpMyAdmin) if they wanted to, but still allow other rows to be deleted.</p> <p>When I get some time, Ill try to see if I can change the plugin to use the id values instead, and replace the error message with a warning, as it may be difficult for a user to determine what plugin/theme the row is associated with without a name belonging to it.</p> <p>As for the file failing to open, the plugin uses a recursive directory search to find PHP files and search them for "get_option" and "get_setting". the option_name values are put into an array, so that only orphaned options are listed. ATM, I don't see why this failed for you, although the "..//" looks suspect. At worst, what could happen is that some options that the unopened file uses may get displayed as orphans when in fact they aren't.</p> <p>As long as you are careful to not delete anything that you're uncertain of, you should be OK.</p> <p>As for the 10130 rows, I just put up the Release Candidate with a "Delete ALL 'rss' Options". Not the best solution to the "many rows" problem perhaps, but I figured it will do until I can come up with something better.</p> <p>Meanwhile, I'll try to figure out what happened and how to rectify the problem.</p> <p>Thanks for posting. </p> http://wordpress.org/support/topic/215481#post-892147 Thu, 06 Nov 2008 09:15:24 +0000 Ovidiu 892147@http://wordpress.org/support/ <p>btw: trying to also post in your forum...<br /> btw2: The Options table currently has 10130 rows :-( </p> http://wordpress.org/support/topic/215481#post-892146 Thu, 06 Nov 2008 09:11:09 +0000 Ovidiu 892146@http://wordpress.org/support/ <p>Hi there.<br /> when going to manage =&gt; clean options and click the button to start the plugin, I get these warnings on top of the page, then the plugin seems to work fine.</p> <pre><code>Warning: fopen(..//wp-content/cache/f20a0b3847983197b4e0c17532537c22/category_relationships/bea85e5b3109c267e9e558fc1b19a431.php) [function.fopen]: failed to open stream: No such file or directory in /var/www/web6/web/wordpress/wp-content/plugins/clean-options/cleanoptions.php on line 227 Warning: fopen(..//wp-content/cache/f20a0b3847983197b4e0c17532537c22/category_relationships/a202eb41473f7026bbc4e420072d7eb7.php) [function.fopen]: failed to open stream: No such file or directory in /var/www/web6/web/wordpress/wp-content/plugins/clean-options/cleanoptions.php on line 227 WARNING !! ERROR MESSAGE !! There is an autoload yes Option with No Name with the value: WARNING !! ERROR MESSAGE !! Could not open file ..//wp-content/cache/f20a0b3847983197b4e0c17532537c22/category_relationships/bea85e5b3109c267e9e558fc1b19a431.php Could not open file ..//wp-content/cache/f20a0b3847983197b4e0c17532537c22/category_relationships/a202eb41473f7026bbc4e420072d7eb7.php The following Options appear to be orphans. Non-selectable Options are known to have been created from files present during upgrade or backup, or are legitimate options that do not &quot;fit&quot; the search for get_option or get_settings. If you wish to remove them by other means, do so at your own risk.</code></pre> <p>any hints what could cause these problems?</p> <p><a href="http://wordpress.org/extend/plugins/clean-options/" rel="nofollow">http://wordpress.org/extend/plugins/clean-options/</a> </p>