Support » Fixing WordPress » What are the _transient options for in the db

  • In the Database there are a bunch or _transient_…. options that are accounting for a large portion of the size of my database. If I delete them they come back, but in other blogs I have they do not exist can anyone tell me:

    a) What are they?

    b) How do I permanently get rid of them?

Viewing 6 replies - 1 through 6 (of 6 total)
  • those are objects stored in cache.

    quoting Ryan B:

    We’re experimenting with having
    transient data such as update_plugins stored in the cache whenever a
    persistent object cache backend is installed so that we can avoid
    cluttering up the options table. See

    Transients have transient_* filters that behave the same as option_*.

    Thread Starter Derek Herman


    Still a little hazy on what a transient object is or how it come to exist. Is it not possible to delete these or do they keep coming back due to my use of wp-super-cache?

    Please help us remove RSS feed cache out of options table DB and also allow us to flush it clean. (Clean Options plugin allows removing only the OLD storage of pre 2.8 RSS feed.)

    What site owner would want to cache or store news “feeds for the WP planet & stuff” in their options table DB? It seems to store them just in case I turn on the dashboard Blog news option.

    If it really is a dashboard option then surely turning it off:
    OFF – WordPress Development Blog / OFF – Other WordPress News
    could flush transient NEWS cache and leave us free from storing it.

    Anyway, the option table DB should store the option only not the actual RSS feed.

    it is dozens of copies of the same “tell me something I don’t already know” stuff. I don’t want it cluttering up my database, my cache, or anything else. Please!

    These entries are actually causing some of my blogs to crash. I get memory errors when trying to access the site. (This host does not allow increasing the memory above 32M through the WP functions, but that is a different issue.)

    Even removing all plugins was not letting me access either the live blog or the admin pages. Using phpMyAdmin, I deleted from wp_options only those entries beginning with _transient_ and the blog was immediately accessible.

    I also cleaned out a bunch of records with option_name beginning with rss_. They contained the full content of individual feeds, some of the same feeds from different dates.

    Between the two record purges, I removed over 300 entries, leaving only 315.

    Not being a programmer, I am unsure of the problem. Any suggestions on automatically cleaning these out every so often would be appreciated. I manage three dozen blogs for myself and others.

    As you say, there is about 1/2 meg (more or less) of “_transient_feed_” (aka magpie) data in the options table of the wordpress database.

    I am sure there is a good reason for storing so much text in the options table (or in a cache, or where-ever), but its purpose seems to boil down to a few paragraphs in the Dashboard, displaying popular wordpress plugins, wordpress news, and the wordpress development blog (and my most recent incomming links). For me, the incoming links is nice, but there could be an option to, instead, simply have links to the appropriate areas of the wordpress website for the rest. When we want to see wordpress plugins, news, the dev. blog, etc., we can just go there.

    For now, I know one solution is to comment out lines 49,50,73, and 85 of the wp-admin/includes/dashboard.php file (in ver. 2.9 anyway),
    which stops the fetching of the data, the storing of it, and the display of it on the admin’s Dashboard page, but I admit I like seeing the ‘incoming links’ (line 46) which are actually unique to my site, as opposed to the wordpress links which are not.

    I would not mind as much if the data was strictly ascii, but it is not.
    So, my question is, for line 46 [“wp_add_dashboard_widget( ‘dashboard_incoming_links’, …”] Is there a way to filter the non-ascii information to restrict it (or to convert it to utf8? – but that seems to be problematic as of yet. – I have even had troubles getting my database fully defined as utf8 — because of the non ascii data in the _transient_ records of course)

    lines 46,49,50,73,85 of the wp-admin/includes/dashboard.php file
    commented out with an #:
    46 #wp_add_dashboard_widget( ‘dashboard_incoming_links’, …
    49 #if ( current_user_can( ‘activate_plugins’ ) ) …
    50 #wp_add_dashboard_widget( ‘dashboard_plugins’, __(‘Plugins’) …
    73 #wp_add_dashboard_widget( ‘dashboard_primary’, $widget_options …
    85 #wp_add_dashboard_widget( ‘dashboard_secondary’, $widget_options …

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘What are the _transient options for in the db’ is closed to new replies.