2020. 2. 7. 16:47ㆍ카테고리 없음
KeyGens, also known as 'key generators' or 'cracks,' are small utility programs used to generate product activation keys and serial numbers, specifically for. Sep 26, 2016 - Apple is currently rolling out macOS Sierra, a major update to the Mac. Some popular 'keygens', which help many pirate releases run, have.
Scene group ZWT released the lastest version of SuperSpeed SuperCache. If you want to further improve performace of your computer beyond its current power, here’s the perfect app for you: SuperSpeed SuperCache allows to make your PC even faster by utilizing patented caching mechanism. Description: SuperCache breaks the disk I/O bottleneck by using the computer’s RAM to hold or contain the most frequently used disk data. This ‘container’ is referred to as a cache. With SuperCache, as a program sends and receives disk data, the most frequently used data is read from and written to RAM – not the hard drive – thus accelerating the program’s performance. SuperCache implements our patented block-level cache technology to increase performance above that of the operating system’s file-level cache. Features:.
Overview of available storage drives in system. Caching graph showing 4 performance items. Configure SuperCache by right clicking a volume. Automatic configuration of boot drive (usually C:) during installation. Release name: SuperSpeed.SuperCache.v5.1.819.0.Incl.Patch.and.Keymaker-ZWT Size: 7.42 MB Links: – – Download.
LOL @ People who fall for this crap. Reminds me of software that was supposed to magically double your ram back in the 90′s. And yeah, what #15 said, win 7 already has superfetch, but I don’t agree about SSD yet, still too expensive, just get 16gb, defrag your drive using something like Ultimate Defrag and put your program files and windows directory close to the outer edge of the disk, have superfetch running, install jv16 powertools and turn on all the speed tweaks. Also you can increase your systems file cache using the command line but I 4get the exact command, it’s something you only do once, but I saw a huge boost after doing it.
Don’t EVER trust silly looking software that claims to boost system performance. Even Tune-up utils is somewhat of a joke, use what the pros use, use jv16. It doesn’t have a barbi-dollhouse GUI either, like Tune-up Utilities does, and it doesn’t stay in memory, hogging resources, claiming it’s speeding up your machine, LOL.
Description This plugin generates static html files from your dynamic WordPress blog. After a html file is generated your webserver will serve that file instead of processing the comparatively heavier and more expensive WordPress PHP scripts. The static html files will be served to the vast majority of your users:. Users who are not logged in. Users who have not left a comment on your blog.
Or users who have not viewed a password protected post. 99% of your visitors will be served static html files. One cached file can be served thousands of times. Other visitors will be served custom cached files tailored to their visit. If they are logged in, or have left comments those details will be displayed and cached for them.
The plugin serves cached files in 3 ways (ranked by speed):. Expert. The fastest method is by using Apache modrewrite (or whatever similar module your web server supports) to serve “supercached” static html files. This completely bypasses PHP and is extremely quick. If your server is hit by a deluge of traffic it is more likely to cope as the requests are “lighter”.
This does require the Apache modrewrite module (which is probably installed if you have custom permalinks) and a modification of your.htaccess file which is risky and may take down your site if modified incorrectly. Supercached static files can be served by PHP and this is the recommended way of using the plugin. The plugin will serve a “supercached” file if it exists and it’s almost as fast as the modrewrite method. It’s easier to configure as the.htaccess file doesn’t need to be changed.
You still need a custom permalink. You can keep portions of your page dynamic in this caching mode. WP-Cache caching.
This is mainly used to cache pages for known users, URLs with parameters and feeds. Known users are logged in users, visitors who leave comments or those who should be shown custom per-user data. It’s the most flexible caching method and slightly slower. WP-Cache caching will also cache visits by unknown users if supercaching is disabled. You can have dynamic parts to your page in this mode too. This mode is always enabled but you can disable caching for known users, URLs with parameters, or feeds separately.
Set the constant “DISABLESUPERCACHE” to 1 in your wp-config.php if you want to only use WP-Cache caching. If you’re not comfortable with editing PHP files then use simple mode. It’s easy to set up and very fast.
Recommended Settings. Simple caching. Compress pages. Don’t cache pages for known users. Cache rebuild. CDN support.
Extra homepage checks. Garbage collection is the act of cleaning up cache files that are out of date and stale. There’s no correct value for the expiry time but a good starting point is 1800 seconds. Consider deleting the contents of the “Rejected User Agents” text box and allow search engines to cache files for you. Preload as many posts as you can and enable “Preload Mode”.
Garbage collection of old cached files will be disabled. If you don’t care about sidebar widgets updating often set the preload interval to 2880 minutes (2 days) so all your posts aren’t recached very often. When the preload occurs the cache files for the post being refreshed is deleted and then regenerated.
Afterwards a garbage collection of all old files is performed to clean out stale cache files. Even with preload mode enabled cached files will still be deleted when posts are modified or comments made. Development.
Active development of this plugin is handled. Translation of the plugin into different languages is on the. Documentation If you need more information than the following, you can have a look at the. Preloading You can generate cached files for the posts, categories and tags of your site by preloading. Preloading will visit each page of your site generating a cached page as it goes along, just like any other visitor to the site. Due to the sequential nature of this function, it can take some time to preload a complete site if there are many posts.
To make preloading more effective it can be useful to disable garbage collection so that older cache files are not deleted. This is done by enabling “Preload Mode” in the settings.
Be aware however, that pages will go out of date eventually but that updates by submitting comments or editing posts will clear portions of the cache. Garbage Collection Your cache directory fills up over time, which takes up space on your server. If space is limited or billed by capacity, or if you worry that the cached pages of your site will go stale then garbage collection has to be done. Garbage collection happens on a regular basis and deletes old files in the cache directory.
On the advanced settings page you can specify: 1. Cache timeout. How long cache files are considered fresh for. After this time they are stale and can be deleted. Setup how often garbage collection should be done.
Notification emails. You can be informed on garbage collection job progress. There’s no right or wrong settings for garbage collection. It depends on your own site.
If your site gets regular updates, or comments then set the timeout to 1800 seconds, and set the timer to 600 seconds. If your site is mostly static you can disable garbage collection by entering 0 as the timeout, or use a really large timeout value. The cache directory, usually wp-content/cache/ is only for temporary files. Do not ever put important files or symlinks to important files or directories in that directory.
They will be deleted if the plugin has write access to them. CDN A Content Delivery Network (CDN) is usually a network of computers situated around the world that will serve the content of your website faster by using servers close to you. Static files like images, Javascript and CSS files can be served through these networks to speed up how fast your site loads. You can also create a “poor man’s CDN” by using a sub domain of your domain to serve static files too. Has been integrated into WP Super Cache to provide basic CDN support. It works by rewriting the URLs of files (excluding.php files) in wp-content and wp-includes on your server so they point at a different hostname.
Many CDNs support. This means the CDN will download the file automatically from your server when it’s first requested, and will continue to serve it for a configurable length of time before downloading it again from your server. Configure this on the “CDN” tab of the plugin settings page. This is an advanced technique and requires a basic understanding of how your webserver or CDNs work.
Please be sure to clear the file cache after you configure the CDN. REST API There are now REST API endpoints for accessing the settings of this plugin. You’ll need to be authenticated as an admin user with permission to view the settings page to use it. This has not been documented yet but you can find all the code that deals with this in the “rest” directory. Custom Caching It is now possible to hook into the caching process using the addcacheaction function. Three hooks are available:.
‘wpcachegetcookiesvalues’ – modify the key used by WP Cache. ‘addcacheaction’ – runs in phase2. Allows a plugin to add WordPress hooks. ‘cacheadminpage’ – runs in the admin page.
Use it to modify that page, perhaps by adding new configuration options. There is one regular WordPress filter too. Use the “docreatesupercache” filter to customize the checks made before caching. The filter accepts one parameter. The output of WP-Cache’s wpcachegetcookiesvalues function. WP Super Cache has it’s own plugin system.
This code is loaded when WP Super Cache loads and can be used to change how caching is done. This is before most of WordPress loads so some functionality will not be available. Plugins can be located anywhere that PHP can load them. Add your own plugin by calling wpscaddplugin( $name ) where $name is the full filename and path to the plugin.
You only need to call that function once to add it. Use wpscdeleteplugin( $name ) to remove it from the list of loaded plugins. The cookies WP Super Cache uses to identify “known users” can be modified now by adding the names of those cookies to a list in the plugin configuration. Use wpscaddcookie( $name ) to add a new cookie, and wpscdeletecookie( $name ) to remove it. The cookie names also modify the modrewrite rules used by the plugin but I recommend using Simple mode caching to avoid complications with updating the.htaccess file. The cookie name and value are used to differenciate users so you can have one cookie, but different values for each type of user on your site for example. They’ll be served different cache files.
See as an example I use for my plugin. Troubleshooting If things don’t work when you installed the plugin here are a few things to check:. Is wp-content writable by the web server?. Is there a wp-content/wp-cache-config.php? If not, copy the file wp-super-cache/wp-cache-config-sample.php to wp-content/wp-cache-config.php and make sure WPCACHEHOME points at the right place.
Is there a wp-content/advanced-cache.php? If not, then you must copy wp-super-cache/advanced-cache.php into wp-content/. You must edit the file and change the path so it points at the wp-super-cache folder.
If pages are not cached at all, remove wp-content/advanced-cache.php and recreate it, following the advice above. Make sure the following line is in wp-config.php and it is ABOVE the “requireonce(ABSPATH.’wp-settings.php’);” line: define( 'WPCACHE', true );. Try the Settings-WP Super Cache page again and enable cache. Look in wp-content/cache/supercache/.
Are there directories and files there?. Anything in your php errorlog?. If your browser keeps asking you to save the file after the super cache is installed you must disable Super Cache compression.
Go to the Settings-WP Super Cache page and disable it there. The plugin does not work very well when PHP’s safe mode is active. This must be disabled by your administrator. If pages are randomly super cached and sometimes not, your blog can probably be viewed with and without the “www” prefix on the URL. You should choose one way and install the plugin if you are using an old WordPress install. The latest versions redirect themselves (you should always be running the latest version of WordPress anyway!).
Private Server users at Dreamhost should edit wp-content/wp-cache-config.php and set the cache dir to “/tmp/” if they are getting errors about increasing CPU usage. See this for more.
File locking errors such as “failed to acquire key 0x152b: Permission denied in” or “Page not cached by WP Super Cache. Could not get mutex lock.” are a sign that you may have to use file locking. Edit wp-content/wp-cache-config.php and uncomment “$useflock = true” or set $semid to a different value. You can also disable file locking from the Admin screen as a last resort. Make sure cache/wpcachemutex.lock is writable by the web server if using coarse file locking. The cache folder cannot be put on an NFS or Samba or NAS share.
It has to be on a local disk. File locking and deleting expired files will not work properly unless the cache folder is on the local machine. Garbage collection of old cache files won’t work if WordPress can’t find wp-cron.php. If your hostname resolves to 127.0.0.1 it could be preventing the garbage collection from working. Check your accesslogs for wp-cron.php entries. Do they return a 404 (file not found) or 200 code?
If it’s 404 or you don’t see wp-cron.php anywhere WordPress may be looking for that script in the wrong place. You should speak to your server administator to correct this or edit /etc/hosts on Unix servers and remove the following line. Your hostname must resolve to the external IP address other servers on the network/Internet use.
See for more. A line like “127.0.0.1 localhost localhost.localdomain” is ok. 127.0.0.1 example.com. If old pages are being served to your visitors via the supercache, you may be missing Apache modules (or their equivalents if you don’t use Apache). 3 modules are required: modmime, modheaders and modexpires.
The last two are especially important for making sure browsers load new versions of existing pages on your site. The error message, “WP Super Cache is installed but broken.
The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed!” appears at the end of every page. Open the file wp-content/advanced-cache.php in your favourite editor. Is the path to wp-cache-phase1.php correct?
This file will normally be in wp-content/plugins/wp-super-cache/. If it is not correct the caching engine will not load. Caching doesn’t work. The timestamp on my blog keeps changing when I reload. Check that the path in your.htaccess rules matches where the supercache directory is.
You may have to hardcode it. Try disabling supercache mode. If supercache cache files are generated but not served, check the permissions on all your wp-content/cache/supercache folders (and each of wp-content cache and supercache folders) and wp-content/cache/.htaccess. If your PHP runs as a different user to Apache and permissions are strict Apache may not be able to read the PHP generated cache files. To fix you must add the following line to your wp-config.php (Add it above the WPCACHE define.) Then clear your cache. Umask( 0022 );. If you see garbage in your browser after enabling compression in the plugin, compression may already be enabled in your web server.
In Apache you must disable moddeflate, or in PHP zlib compression may be enabled. You can disable that in three ways. If you have root access, edit your php.ini and find the zlib.outputcompression setting and make sure it’s “Off” or add this line to your.htaccess: phpflag zlib.outputcompression off If that doesn’t work, add this line to your wp-config.php: iniset('zlib.outputcompression', 0);. The “white screen of death” or a blank page when you visit your site is almost always caused by a PHP error but.
Disable that PHP extension if you have trouble and replace with eAccelerator or Xcache. After uninstalling, your permalinks may break if you remove the WordPress modrewrite rules too. Regenerate those rules by visiting the Settings-Permalink page and saving that form again.
If your blog refuses to load make sure your wp-config.php is correct. Are you missing an opening or closing PHP tag?. Your front page is ok but posts and pages give a 404? Go to Settings-permalinks and click “Save” once you’ve selected a custom permalink structure. You may need to manually update your.htaccess file. If certain characters do not appear correctly on your website your server may not be configured correctly. You need to tell visitors what character set is used.
Go to Settings-Reading and copy the ‘Encoding for pages and feeds’ value. Edit the.htaccess file with all your Supercache and WordPress rewrite rules and add this at the top, replacing CHARSET with the copied value. (for example, ‘UTF-8’) AddDefaultCharset CHARSET. Use to help diagnose garbage collection and preload problems. Use the plugin to make sure jobs are scheduled and for what time.
Look for the wpcachegc and wpcachefullpreloadhook jobs. The error message, “WP Super Cache is installed but broken. The constant WPCACHEHOME must be set in the file wp-config.php and point at the WP Super Cache plugin directory.” appears at the end of every page. You can delete wp-content/advanced-cache.php and reload the plugin settings page or edit wp-config.php and look for WPCACHEHOME and make sure it points at the wp-super-cache folder. This will normally be wp-content/plugins/wp-super-cache/ but you’ll likely need the full path to that file (so it’s easier to let the settings page fix it). If it is not correct the caching engine will not load.
If your server is running into trouble because of the number of semaphores used by the plugin it’s because your users are using file locking which is not recommended (but is needed by a small number of users). You can globally disable file locking by defining the constant WPSCDISABLELOCKING, or defining the constant WPSCREMOVESEMAPHORE so that semremove is called after every page is cached but that seems to cause problems for other processes requesting the same semaphore.
Best to disable it. Set the variable $htaccesspath in wp-config.php or wp-cache-config.php to the path of your global.htaccess if the plugin is looking for that file in the wrong directory. This might happen if you have WordPress installed in an unusual way. Installation Install like any other plugin, directly from your plugins page but make sure you have custom permalinks enabled.
Go to the plugin settings page at Settings-WP Super Cache and enable caching. How to uninstall WP Super Cache Almost all you have to do is deactivate the plugin on the plugins page. The plugin should clean up most of the files it created and modified, but it doesn’t as yet remove the modrewrite rules from the.htaccess file. Look for the section in that file marked by SuperCache BEGIN and END tags. The plugin doesn’t remove those because some people add the WordPress rules in that block too. To manually uninstall:.
Turn off caching on the plugin settings page and clear the cache. Deactivate the plugin on the plugins page.
Remove the WPCACHE define from wp-config.php. It looks like define( 'WPCACHE', true );. Remove the Super Cache modrewrite rules from your.htaccess file. Remove the files wp-content/advanced-cache.php and wp-content/wp-cache-config.php. Remove the directory wp-content/cache/. Remove the directory wp-super-cache from your plugins directory. If all else fails and your site is broken.
Remove the WPCACHE define from wp-config.php. It looks like define( 'WPCACHE', true );. Remove the rules (see above) that the plugin wrote to the.htaccess file in your root directory. Delete the wp-super-cache folder in the plugins folder. Optionally delete advanced-cache.php, wp-cache-config.php and the cache folder in wp-content/.
Changelog 1.6.4. Changes between. Fixes for WP-CLI (#587) (#592).
Bumped the minimum WordPress version to 3.1 to use functions introduced then. (#591). Fixes to wpscposttransition to avoid a fatal error using getsamplepermalink. (#595). Fixed the admin bar “Delete Cache” link.
(#589). Fixed the headings used in the settings page. (#597) 1.6.3. Changes between. Added cookie helper functions (#580). Added plugin helper functions (#574). Added actions to modify cookie and plugin lists.
(#582). Really disable garbage collection when timeout = 0 (#571).
Added warnings about DISABLEWPCRON (#575). Don’t clean expired cache files after preload if garbage collection is disabled (#572). On preload, if deleting a post don’t delete the sub directories if it’s the homepage. (#573). Fix generation of semaphores when using WP CLI (#576). Fix deleting from the admin bar (#578). Avoid a strpos warning.
(#579). Improve deleting of cache in edit/delete/publish actions (#577). Fixes to headers code (#496) 1.6.2. Fixed serving expired supercache files (#562). Write directly to the config file to avoid permission problems with wp-content. (#563). Correctly set the.htaccess rules on the main site of a multisite.
(#557). Check if settransient exists before using it. (#565). Removed searchengine.php example plugin as it sets a cookie to track users. Still available. (#567).
For advanced users only. Change the vary and cache control headers.
See (#555) 1.6.1. Fix the name of the WP Crontrol plugin. (#549). Handle errors during deactivation/uninstall by email rather than exiting. (#551). Add a notice when settings can’t be updated.
(#552 and #553) 1.6.0. Fix issues in multisite plugin (#501). Fixes wp-cli plugin deactivate/activate (#499). Cleanup – change quotes. (#495). $htaccesspath defines the path to the global.htacess file. (#507).
Fix ‘cannot redeclare gzipaccepted’ (#511). Correct the renaming of tmpwpcachefilename (removed unnecessary slash in path) which caused renaming to fail. (#516). Add check for Jetpack mobile theme cookie (#515). Optimize wpcachephase2 and create wpscregisterposthooks (#508). WPCACHEHOME has a trailing slash (#513). Cleanup cache enable/disable and updatemodrewriterules (#500).
Post Update now clears category cache (#519). Various fixes for saving the debug page form (#542). Expert-caching and empty parameters, like?amp, should not serve cached page (#533).
Tiny Yslow description fix (#527). Add ipad to mobile list (#525). Hide opcacheinvalidate warnings since it’s disabled some places. (#543). Check that HTTPREFERER exists before checking it. (#544). Replace Cron View” with WP Crontrol because it’s still updated.
(#546). adding hook (wpcachecleared) for full cache purges (#537) 1.5.9.
Fixed fatal error if the debug log was deleted while debugging was enabled and a visitor came to the site. Fixed the dynamic caching test plugin because of PHP7 changes. Dynamic cache mode must be enabled now. Lots of WordPress coding style formatting fixes to the code. All changes: 1.5.8.
PHP 7 fixes. (#429). Fix debug comments checkbox. (#433). Only register uninstall function in admin pages to save queries.
(#430). Check that wp-cache-phase1.php is loaded before saving settings page. (#428). If a url has a “?” in it then don’t delete the associated cache.
It’ll delete the whole cache after stripping out? (#427 & #420). Allow static functions in classes to be used in cacheactions. (#425).
Don’t make AJAX requests anonymous. (#423). Fixed link to chmod explanation. (#421).
Add more escaping to the CDN settings page. (#416). Use SERVERPROTOCOL to determine http protocol.
(#412 & #413). If preload stalls only send one email per day, but do display an admin notice. (#432). Fixed more PHP warnings in #438 and #437.
Hide modrewrite warnings for Nginx users. #434 1.5.7.1. If the HTTP HOST is empty then don’t use it in strpos to avoid a PHP warning. (#408). Don’t preload posts with permalinks that contain rejected strings. (#407). Generate a list of archive feeds that can be deleted when the site is updated.
Also fixes corrupted config file issue and fatal error with older versions of WordPress. (#403) 1.5.7. Fix fatal error in plugins/searchengine.php (#398) 1.5.6. REST API: Added /plugins endpoint to handle the plugins settings page. (#382).
Minor changes to indentaion and spaces to tabs conversion (#371) (#395). Don’t set $wpsupercachecomments here as it’s not saved. (#379). realpath only works on directories.
The cachefile wasn’t set correctly. (#377).
Fix problem deleting cache from admin bar because of realpath (#381). Use triggererror instead of echoing to the screen if a config file isn’t writeable. (#394). Added the “wpscenablewpconfigedit” filter to disable editing the wp-config.php (#392). Fix some PHP notices when comments are edited/published/maintained. (#386).
Minor changes to description on plugins page. (#393) 1.5.5. Catch fatal errors so they’re not cached, improve code that catches unknown page types. (#367). Fix caching on older WP installs, and if the plugin is inactive on a blog, but still caching, give feeds a short TTL to ensure they’re fresh. (#366).
When preloading don’t delete sub-directories, or child pages, when caching pages. (#363). Avoid PHP warnings from the REST API for settings that are not yet defined. (#361). Added missing settings to the config file. (#360) 1.5.4. Fix messages related to creating advanced-cache.php (#355, #354).
Deleting the plugin doesn’t need to delete the cache directory as it’s already done on deactivation. (#323). Disable Jetpack mobile detection if Jetpack Beta is detected.
(#298). Add more checks on directories to make sure they exist before deleting them. (#324). Add siteurl setting to CDN page for users who have WordPress in it’s own directory.
(#332). Don’t enable and then not save debug comments when toggling logging. (#334). Show plugin activity html comments to users who disable caching for logged in users. (#335). Better notifications on Preload page, and redo sql to fetch posts.
Added “wpscpreloadposttypesargs” filter on post visibility, and wpscpreloadposttypes filter on post types used. (#336). Use a cached feed if it is newer than the last time a post was updated.
(#337). Better define a sitemap (#340) but when the content type is unknown add more checks to find out what it is. (#346). Save cache location correctly on the advanced settings page.
(#345). Make sure the debug log exists before toggling it on/off to ensure the http auth code is added to it. Return the correct cache type to the REST API. Ignore supercache enabled status. (#352). Fix cache contents in REST API showing double count of supercache files.
(#353). Move the nonce in the CDN page back into a function. (#346). Use realpath to compare directories when loading the sample config file to account for symlinked directories. (#342).
Other minor changes to html or typos (Numbers are on Github.) 1.5.3. Fix a critical bug that caused unlink to be run on null while deleting the plugin. 1.5.2. Add a trailing slash to home path.
Fixes problems with finding the.htaccess file. Delete WPCACHEHOME and WPCACHE from wp-config.php when plugin deactivated. Check that WPCACHEHOME is the right path on each load of the settings page. Load the REST API code without using WPCACHEHOME. Fixed mobile browser caching when using WP-Cache caching. Fixed directory checks on Windows machines. Reverted CDN changes in 1.5.0 as they caused problems in older “WordPress in a separate directory” installs.
Added note to CDN page when site url!= home url. Site owners can use a filter to adjust the URL used. Stop preload quicker when requested while preloading taxonomies. Added more information for when updating the.htaccess file fails. “Served by” header is now optional. Enable it by setting $wpscservedheader to true in the config file.
1.5.1. Don’t use anonymous functions in REST API. Check that REST API Controller is available before loading the REST API. Don’t use multibyte string functions because some sites don’t have it enabled.
1.5.0. REST API settings endpoints. Simplified settings page. WP-Cache files reorganised. Caching of more http headers. Lots of bug fixes.
1.4.9. Fixed bug when not running semremove after semrelease. See. Fixed a PHP error impacting PHP 7.1.
Fixed a bug where we cached PUT and DELETE requests. We’re treating them like POST requests now.
Delete supercache cache files, even when supercache is disabled, because modrewrite rules might still be active. Updated the settings page, moving things around. Make file locking less attractive on the settings page and fixed the WPSCDISABLELOCKING constant so it really disables file locking even if the user has enabled it already. Added a WPSCREMOVESEMAPHORE constant that must be defined if semremove is to be used as it may cause problems. Added a “wpscdeleterelatedpagesonedit” filter that on returning 0 will disable deletion of pages outside of page being edited. Fixed plugin deleting all cached pages when a site had a static homepage.
Make sure $cachepath has a trailing slash. Remove flush but also check if headers are empty and flush and get headers again. Add fix for customizer and don’t cache PUT AND DELETE requests. Check for superglobals before using them. 1.4.8. Removed malware URL in a code comment. (harmless to operation of plugin but gets flagged by A/V software).
Updated translation file. 1.4.7. Update the settings page for WordPress 4.4. Layout changes.
1.4.6. Generate the file cache/.htaccess even when one exists so gzip rules are created and gzipped pages are served correctly.
Props Tigertech. 1.4.5.
Enhancement: Only preload public post types. Props webaware. Added an uninstall function that deletes the config file. Deactivate function doesn’t delete it any more. Possible to deactivate the plugin without visiting the settings page now.
Fixed the cache rebuild system. Rebuild files now survive longer than the request that generate them. Minor optimisations: prunesupercache exits immediately if the file doesn’t exist.
The output of wpcachegetcookiesvalues is now cached. Added PHP pid to the debug log to aid debugging. Various small bug fixes. Fixed reset of expiry time and GC settings when updating advanced settings. Removed CacheMeta class to avoid APC errors.
It’s not used any more. Fixed reset of advanced settings when using “easy” settings page. Fixed XSS in settings page. Hide cache files when servers display directory indexes. Prevent PHP object injection through use of serialize. 1.4.4. Fixed fatal error in output handler if GET parameters present in query.
Supercache Keygen For Mac Pro
Props webaware. Fixed debug log. It wasn’t logging the right message. 1.4.3.
Security release fixing an XSS bug in the settings page. Props Marc Montpas from Sucuri. Added wpdebuglog. Props Jen Heilemann. Minor fixes. 1.4.2.
Fixed “acceptable file list”. Fixed “Don’t cache GET requests” feature. Maybe fixed “304 not modified” problem for some users. Fixed some PHP warnings. 1.4.1. Fixed XSS in settings page.
Props Simon Waters, Surevine Limited. Fix to object cache so entries may now be deleted when posts updated. (object cache still experimental).
Documentation updates and cleanup of settings page. 1.4. Replace legacy mfunc/mnclude/dynamic-cached-content functionality with a “wpsccachedata” cacheaction filter. Added dynamic-cache-test.php plugin example wpsccachedata filter plugin.
Delete post, tag and category cache when a post changes from draft to publish or vice versa. Props @Biranit. Update advanced-cache.php and wp-config.php if wp-cache-phase1.php doesn’t load, usually happening after migrating to a new hosting service. Misc bugfixes. 1.3.2. Any mfunc/mclude/dynamic-cached-content tags in comments are now removed. Dynamic cached content feature disabled by default and must be enabled on the Advanced Settings page.
Support for the mobile theme in Jetpack via helper plugin on script’s Plugins tab. 1.3.1. Minor updates to documentation. Fixed XSS in settings page.
1.3. mfunc tags could be executed in comments. More support for sites that use the LOGGEDINCOOKIE constant and custom cookies. 1.2. Garbage collection of old cache files is significantly improved. I added a scheduled job that keeps an eye on things and restarts the job if necessary. Also, if you enable caching from the Easy page garbage collection will be enabled too.
Editors can delete single cached files from the admin bar now. Fixed the cached page counter on the settings page. Some sites that updated to 1.0 experienced too much garbage collection.
There are still stragglers out there who haven’t upgraded but that’s fixed now!. Supercached mobile files are now used as there was a tiny little typo that needed fixing.
If your site is in a directory and you saw problems updating a page then that should be fixed now. The deactivate hook has been changed so your configuration isn.t hosed when you upgrade. Unfortunately this will only happen after you do this upgrade. Some sites use custom cookies with the LOGGEDINCOOKIE constant. Added support for that. Added support for WPTouch Pro, but it appears to be flaky still.
Anyone have time to work on that?. Some sites had problems with scheduled posts. For some reason the plugin thought the post was in draft mode and then because it only checked the same post once, when the post magically became published the cache wasn.t cleared. That.s fixed, thanks to the debug logging of several patient users. And more bug fixes and translation updates. 1.1. Use $SERVER ‘SERVERNAME’ to create cache directories.
Only create blogs cached directories if valid requests and blogs exist. Only clear current blog’s cache files if navigation menu is modified. Added cleanpostcache action to clear cache on post actions.
Removed garbage collection details on Contents tab. Added wpcachecheckmobile cacheaction filter to shortcircuit mobile device check. Don’t delete cache files for draft posts.
Added action on wptrashpost to clear the cache when trashed posts are deleted. Show a warning when 304 browser caching is disabled (because modrewrite caching is on). New check for safe mode if using less that PHP 5.3.0. Added wpsupercacheremovecookies filter to disable anonymous browsing mode. Fixed garbage collection schedule dropdown. Fixed preload problem clearing site’s cache on “page on front” sites.
Fix for PHP variable not defined warnings. Fixed problem refreshing cache when comments made as siteurl sometimes didn’t work. Preloading of taxonomies is now optional. Domain mapping fixes. Better support for https sites. Remove to get cache paths. Added AddDefaultCharset.htaccess rule back in and added an option to remove it if required.
Added multisite plugin that adds a “Cached” column to Network-Sites to disable caching on a per site basis. Added WPTouch plugin to modify browser and prefix list in mobile detection code.
Added support for that plugin’s exclude list. Fixed cache tester. Filter the tags that are used to detect end-of-page using the wpcacheeoftags filter. Removed debug level from logging as it wasn’t helpful. Removed mention of wp-minify.
1.0. Removed AddDefaultCharset.htaccess rule.
Fixed problem with blogs in a folder and don’t have a trailing slash. New scheduling of garbage collection. Added a “Delete cache” link to admin bar to delete cache of current page. Updated documentation. Sorry Digg, Stephen Fry power now!. Updated translations.
Preload taxonomies and all post types except revisionsand nav menu items. Fixed previews by logged in users. Added option to make logged in users anonymous. Use WP 3.0 variables to detect multisite installs. Hash filenames so files are served from the same CDNs 0.9.9.9. Fixed typo, isfrontpage.
Serve repeated static files from the same CDN hostname. Updated translations.
Make supercache dir lowercase to avoid problems with unicode URLs. Add option to skip https loaded static content. Remove 5 second check on age of existing cache files. Should help with posts that get lots of comments and traffic. Lots of bugs fixed.
0.9.9.8. CDN updates: can be switched off, multiple CNAMEs. Uninstall process improved. It removes generated files and fixes edited files. Cached dynamic pages can now be stored in Supercache files and compressed. 1and1 Webhosting fix (/kunden/). Remove log by email functionality as it caused problems for users who were inundated by email.
Many more minor fixes and changes. 0.9.9.6. Fixed problem serving cached files with PHP.
Added support for 304 “file not modified” header to help browser caching. (PHP caching only).
Added French & German translations, updated Italian translation and fixed translation strings. Sleep 4 seconds between preload urls to reduce load on the server. Updated docs and FAQs. 0.9.9.5. Disable compression on on easy setup page.
Still causes problems on some hosts. Remove footerlink on easy setup page. Don’t delete modrewrite rules when caching is disabled. Don’t stop users using settings page when in safe mode. 0.9.9.4. Settings page split into tabbed pages. Added new “Easy” settings page for new users.
New PHP caching mode to serve supercached files. Mobile support fixes.
Added Domain mapping support plugin. Added “awaiting moderation” plugin that removes that text from posts. Terminology change. Changed “half on” to “legacy caching”. Fixed cache tester on some installs of WordPress.
Updated documentation. Added $wpsupercachelockdown config variable to hide lockdown and directly cached pages admin items.
Preloaded checks if it has stalled and reschedules the job to continue. Serve the gzipped page when first cached if the client supports compression. Lots more bug fixes. 0.9.9.3. Fixed division by zero error in half on mode. Always show “delete cache” button.
Fixed “Update modrewrite rules” button. Minor text changes to admin page. 0.9.9.2. Forgot to change version number in wp-cache.php 0.9.9.1. Added preloading of static cache. Better mobile plugin support.htaccess rules can be updated now.
Added wpscupdatehtaccess. Fixed “page on front” cache clearing bug. Check for wordpressloggedin cookie so test cookie isn’t detected. Added clearpostsupercache to clear supercache for a single post. Put quotes around rewrite rules in case paths have spaces.
0.9.9. Added experimental object cache support. Added Chinese(Traditional) translation by Pseric.
Added FAQ on WP-Cache vs Supercache files. Use Supercache file if WP-Cache file not found. Useful if modrewrite rules are broken or not working. Get mobile browser list from WP Mobile Edition if found. Warn user if.htaccess out of date.
Make sure writer lock is unlocked after writing cache files. Added link to developer docs in readme. Added Ukranian translation by Vitaly Mylo. Added Upgrade Notice section to readme. Warn if zlib compression in PHP is enabled.
Added compression troubleshooting answer. Props Vladimir (. Added Japanese translation by Tai (. Updated Italian translation. Link to WP Mobile Edition from admin page for mobile support.
0.9.8. Added Spanish translation by Omi.
Added Italian translation by Gianni Diurno. Addded advanced debug code to check front page for category problem. Enable by setting $wpsupercacheadvanceddebug to 1 in the config file. Fixed wordpress vs wordpressloggedin cookie mismatch in cookie checking function. Correctly check if WPCACHE is set or not.
PHP is weird. Added wpcacheclearcache to clear out cache directory. Only show logged in message when debugging enabled. Added troubleshooting point 20.
PHP vs Apache user. Fixed problem deleting cache file. Don’t delete cache files when moderated comments are deleted. 0.9.7. Fixed problem with blogs in folders. Added cache file listing and delete links to admin page. Added “Newest Cached Pages” listing in sidebox.
Made admin page translatable. Added “How do I make certain parts of the page stay dynamic?” to FAQ.
Advanced: added “late init” feature so that plugin activates on “init”. Set $wpsupercachelateinit to true in config file to use. Disable supercaching when GET parameters present instead of disabling all caching. Disable on POST (as normal) and preview. Fixed problem with cron job and mutex filename. Warn users they must enable mobile device support if rewrite rules detected.
Better detection of when to warn that.htaccess rules must be updated (no need when rewrite rules not present). Advanced: Added “wpsupercache404” filter. Return true to cache 404 error pages. Use the wordpresstestcookie in the cache key. Show correct number of cache files when compression off.
Fixed problem with PHP safemode detection. Various bugfixes and documentation updates.
See Changelog.txt 0.9.6.1. Move “not logged in” message init below check for POST. Add isadmin check so plugin definitely can’t cache the backend. Add “do not cache” page type to admin page. 0.9.6.
Add uninstall.php uninstall script. Updated cache/.htaccess rules (option to upgrade that). Added FAQ about category and static homepage problem. Add wpcacheuseragentisrejected back to wp-cache-phase2.php. Show message for logged in users when caching disable for them. Check filemtime on correct supercache file 0.9.5.
Show next and last GC times in minutes, not local time. Don’t serve wpcache cache files to rejected user agents. Supercache files are still served to them. If enabled, mobile support now serves php cached files to mobile clients and static cached files to everyone else. Added checks for “WPSCDISABLECOMPRESSION” and “WPSCDISABLELOCKING” constants to disable compression and file locking. For hosting companies primarily.
Supercache Keygen For Mac Free
Added check for DONOTCACHEPAGE constant to avoid caching a page. Use PHPDOCUMENTROOT when creating.htaccess if necessary.
Supercache Keygen For Mac Mac
0.9.4.3. Added “Don’t cache for logged in users” option.
Display file size stats on admin page. Clear the cache when profile page is updated.
Don’t cache post previews. Added backslashes to rejected URI regex list.
Fixed problems with posts and comments not refreshing.