Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

DietPress · Version history

DietPress changelog and version history

Latest version
3.7.3
Nov 2, 2026 (7 days ago)
Releases
67
since 2018
In the last year
29
about one every 12 days
Tested up to
WordPress 7.1.4
PHP 7.4 or later

Releases each year

  • 20187 releases
  • 20196 releases
  • 20208 releases
  • 20211 release
  • 20224 releases
  • 20232 releases
  • 20243 releases
  • 20259 releases
  • 202627 releases

202627 releases

  1. DietPress 3.7.3Latest

    • Fixes a fatal error when another plugin deletes or edits a term before WordPress has finished loading, as some WPML upgrade routines do. The page cache now empties itself completely after such a change.
    • Fix: With the page cache on, the site stopped with a fatal error (Call to a member function get_extra_permastruct() on null) when another plugin deleted or edited a category, a tag or any other term before WordPress had finished loading. WPML does this in some of its upgrade routines. Deleting a po…
    • Fix: Changing a term of a taxonomy with no public pages of its own, like the private ones WPML uses, no longer empties the cached home page. When a post changes, the archives it belongs to are chosen the same way: those of a taxonomy whose pages visitors can see, whether or not it is marked as publ…
    • Fix: Deleting a navigation menu now empties the whole cache, as saving one already did. Until now it emptied only the home page, and every other page kept showing the deleted menu.
  2. DietPress 3.7.2

    • The RSS feed of a logged in user, and a page that sets a cookie when a lifetime is chosen for HTML, no longer go out marked as public. Adds a Purge cache entry to the DietPress menu, marks the selective loading modules whose plugin is on the site and lists the scheduled tasks in Tools.
    • Improved: While the page cache is on, the DietPress menu has a Purge cache entry. It empties the cache from any screen of the dashboard and brings you back to it, with a note of how much was deleted.
    • Improved: In Selective loading, on the Strict tab, the modules that have something to act on come first and carry a “Detected on this site” label, so it is clear which ones are yours. The label follows what the module would do and not only whether its plugin is installed: Formidable Forms gets it w…
    • Improved: The site analyzer asks the same question as the module, so it no longer suggests the Formidable Forms module when Formidable already loads its styles only where a form is.
    • Improved: The Tools tab has a Scheduled tasks section that shows when the daily cleanup of transients and the cleanup of the page cache are due next. When one is late or missing it says so, with the likely reason and what it does and does not affect.
    • Improved: The site analyzer warns when the WooCommerce “Recently Viewed Products list” widget sits in a sidebar, even one the theme never shows. While it is there every product page sets a cookie, and no cache stores a page that sets a cookie: not this one, and not the one of the hosting.
    • Improved: The DNS prefetch hints for ajax.googleapis.com and stats.wp.com are printed only on pages that load a script or a style from them, or while Jetpack Stats is on. They were printed on every page of every site. The dietpress_dns_prefetch_domains filter still adds them back.
    • Fix: With Optimize RSS feeds on, which is the default, the RSS feed went out marked as public for an hour for everybody, logged in visitors included. For them it replaced the private, do not store answer WordPress gives, and the feed of somebody who can read private posts includes them, so a cache…
    • Fix: With a lifetime chosen for HTML pages under browser caching, a page that set a cookie went out marked as public, which lets a cache in front of the site keep it and hand that cookie to other visitors. It now goes out as private, with the same lifetime, so a cache in front that used to keep suc…
    • Fix: The answer the page cache gives a visitor who already has the current copy (a 304) was sent before declaring the type of the page, so on a site whose charset is not UTF-8 it could leave with the wrong one. Apache and PHP-FPM remove the type from that answer, so most sites never sent it.
  3. DietPress 3.7.1

    • Fixes the cache test behind a hosting cache, which kept the pages DietPress builds and served them ahead of it: purge that cache once after updating. The test now checks the page you choose, and the accelerator no longer switches on while the page cache is off.
    • Improved: “Test the cache now” tests the page in the field above it, typed or picked from the search, or the home page when the field is empty, and every result says which page it tested. Switching the accelerator on still tests the home page.
    • Improved: When a cache in front of the site answers the test instead of WordPress, the test says so and names the header that gave it away, instead of blaming the cache folder.
    • Improved: A page left out of the cache for setting a cookie now names the cookie, which usually tells which plugin sets it.
    • Improved: The confirmation for running on top of a hosting cache is now a tick box inside the page cache card, next to its warning, instead of a card of its own. Once ticked, the warning turns into a plain note there and no longer shows on the dashboard.
    • Fix: With the DietPress page cache on, the pages it builds go out telling the caches in front not to keep them, as the copies it serves already did. Since 3.7.0 they went out without saying anything, so a hosting cache could keep them and serve them ahead of DietPress, out of reach of its purges, a…
    • Fix: The accelerator could be switched on while the page cache was off, and showed as on while nothing ran. It now stays locked until the page cache is on, and unlocks as soon as that toggle is ticked.
    • Fix: Saving any setting without the confirmation for a second cache switched off, and emptied, a page cache that was already running when a hosting cache appeared. The confirmation is now asked only when switching the page cache on, and the message says what to tick.
    • Fix: With a hosting whose page cache is switched on from its own plugin, the warning and the confirmation it asks for showed while that cache was off. They now appear only while it is on. On LiteSpeed servers the note about LiteSpeed Cache no longer asks for the confirmation, since that cache only…
    • Fix: Two cache tests at the same time, by two administrators or by a save that tests the accelerator while someone presses the button, broke each other: the reasons went missing and the accelerator could refuse to switch on.
    • Fix: With a separate cache for mobile, the server rules of the accelerator took any character between Opera and Mini or Mobi as a phone, where WordPress takes only a space. On nginx the Cache tab asks to paste the rules again.
  4. DietPress 3.7.0

    • DietPress no longer tells browsers how long to keep your pages, so the cache of your hosting or your CDN can store them again. Also fixes a page cache that went on running after it had been blocked.
    • New: A new choice in “Let browsers keep the HTML for”, called “Send no rules for HTML”, and it is what a new install gets. With it DietPress says nothing at all about how long one of your pages may be kept. Sites that were on the old default, “Always revalidate”, are moved to it once when they upda…
    • Improved: However long you let browsers keep your pages, that is now decided in one place, when the page is built, instead of also being written into the .htaccess. The server rules could not know whether a visitor was logged in, whether the page was a cart or a checkout, or whether another plugin…
    • Improved: The compression rules no longer switch the compressor on for every response the server sends. The list of file types to compress is unchanged, so the same things are compressed, without the global filter that duplicated it and cost processor time on every dynamic page.
    • Improved: The Keep-alive connections option is gone. The header it wrote is forbidden in HTTP/2, which is what almost every site is served over today, and on HTTP/1.1 it is the server, not the page, that decides whether the connection stays open. Nothing else changes for your site.
    • Improved: The Vary header written for static files is merged instead of appended, so it is no longer sent twice on files the server also compressed, and it is written in the form every server understands.
    • Improved: SiteGround Speed Optimizer is recognised by name, so when its cache is the one in charge the Cache tab says so instead of describing it as an unknown drop-in, and the browser caching options warn when the value chosen would stop it from storing your pages.
    • Fix: With the default settings, every page left the site with a lifetime of zero seconds, which browsers read as “ask me again” and every cache in front of the site reads as “do not store this”. On hosting that caches pages for you, such as SiteGround, that meant the cache never stored anything and…
    • Fix: Feeds, robots.txt, ads.txt and any other plain text file were told they could be kept for a month, which is the lifetime of your images, because they had no rule of their own and inherited the default one. That inherited rule is gone: what is meant to be cached is now named one file type at a…
    • Fix: A Cache-Control header set by another plugin, or by a PHP session, straight with header() instead of through the WordPress filter was replaced without trace. DietPress now looks at the headers already sent and leaves the response alone when one is there. The cart, the checkout and the account…
    • Fix: The page cache went on serving and storing pages when another page cache had taken charge through an advanced-cache.php drop-in, which is what a hosting plugin installs when its own file cache is switched on. The Cache tab said the module was blocked while the engine answered every visit, so t…
    • Thanks to @webvillalba for the help and for testing this release on real sites.
    • For older changelog entries, please check the changelog.txt file.
  5. DietPress 3.6.0

  6. DietPress 3.5.6

  7. DietPress 3.5.5

  8. DietPress 3.5.4

  9. DietPress 3.5.3

  10. DietPress 3.5.2

  11. DietPress 3.5.1

  12. DietPress 3.5.0

  13. DietPress 3.4.1

  14. DietPress 3.4.0

  15. DietPress 3.3.1

  16. DietPress 3.3.0

  17. DietPress 3.2.1

  18. DietPress 3.2.0

  19. DietPress 3.1.0

  20. DietPress 3.0.1

  21. DietPress 3.0.0

  22. DietPress 2.3.2

  23. DietPress 2.3.1

  24. DietPress 2.3.0

  25. DietPress 2.2.2

  26. DietPress 2.2.1

  27. DietPress 2.2.0

20259 releases

  1. DietPress 2.1.3

  2. DietPress 2.1.2

  3. DietPress 2.1.1

  4. DietPress 2.1.0

  5. DietPress 2.0.3

  6. DietPress 2.0.2

  7. DietPress 2.0.1

  8. DietPress 2.0

  9. DietPress 0.9.30

20243 releases

  1. DietPress 1.0.7

  2. DietPress 1.0.6

  3. DietPress 1.0.5

20232 releases

  1. DietPress 1.0.4

  2. DietPress 1.0.3

20224 releases

  1. DietPress 1.0.2

  2. DietPress 1.0.1

  3. DietPress 1.0

  4. DietPress 0.9.31

20211 release

  1. DietPress 0.9.29

20208 releases

  1. DietPress 0.9.28

  2. DietPress 0.9.27

  3. DietPress 0.9.26

  4. DietPress 0.9.25

  5. DietPress 0.9.24

  6. DietPress 0.9.23

  7. DietPress 0.9.22

  8. DietPress 0.9.21

20196 releases

  1. DietPress 0.9.20

  2. DietPress 0.9.19

  3. DietPress 0.9.18

  4. DietPress 0.9.17

  5. DietPress 0.9.16

  6. DietPress 0.9.15

20187 releases

  1. DietPress 0.9.14

  2. DietPress 0.9.13

  3. DietPress 0.9.12

  4. DietPress 0.9.11

  5. DietPress 0.9.10

  6. DietPress 0.9.9

  7. DietPress 0.9.8

Questions about DietPress’s releases

What is the latest version of DietPress?

3.7.3, released on Nov 2, 2026 (1 week ago). It’s tested up to WordPress 7.1.4 and needs PHP 7.4 or later.

How often is DietPress updated?

29 releases in the last year, about one every 12 days. Its first release on WordPress.org dates from May 2018.

Know when your rivals ship

Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.

Start free

Release dates come from the day each version’s folder was made in DietPress’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.