storyday

cos-html-cache is an extremely efficient WordPress page caching plugin designed to make your WordPress site much faster and more responsive. Based on URL rewriting, the plugin will automatically generate real html files for posts when they are loaded for the first time, and automatically renew the html files if their associated posts are modified. 
cos-html-cache. Current version, cos-html-cache2.6, is a huge improvement over previous versions of cos-html-cache.
**** Installation ****
1.Upload to your plugins folder, usually <code>wp-content/plugins/</code> and unzip the file, it will create a <code>wp-content/plugins/cos-html-cache/</code> directory.
2.Activate the plugin on the plugin screen.
3.Make that your perm link looks like a real html file : http://storyday.com/post/xxx.html 
4.create a file named “index.bak” under the root of your web directory
3.done 
**** Uninstallation ****
1.go into admin->options->cos-html-cache 
2.delete all cache files (very important) 
3.go into admin->plugins ,disable cos-html-cache 
4.done.
**** Frequently Asked Questions ****
** Do I really need to use this plugin? **
<ul>
<li>If your site gets Slashdotted</li>
<li>If you’re on a very slow server</li>
<li>If you’ve had a complaint from your host about performance</li>
<li>If you just want to blog rather than testing new plugins and functions of wordpress</li>
</ul>
** How can I tell if it’s working? **
cos-html-cache adds some stats to the very end of a page in the HTML, so you can view source to see if there any codes like ““
** Do you cache other pages such as cat ? **
No,this plugin only cache posts and pages.
**** More Info ****
For more info, please visit http://www.storyday.com/cos-html-cache

****** cos-html-cache ******

cos-html-cache is an extremely efficient WordPress page caching plugin designed to make your WordPress site much faster and more responsive.

Alex

Attention: The update to version 3.0.0 of this plugin is a breaking change that removes the [php_everywhere] shortcode and widget. Run the upgrade wizard from the plugin’s settings page to migrate your old code to Gutenberg blocks.

 This plugin enables PHP code everywhere in your WordPress instalation.


 Using this plugin you can use PHP in:

<ul>
<li>
 Pages
 </li>
<li>
 Posts
 </li>
<li>
 Sidebar
 </li>
<li>
 Everywhere you can place a Gutenberg block
 </li>
</ul>

 The plugin also supports different user restrictions and multiple PHP instances.


 So feel free to just insert PHP in every part of your WordPress site.

 Examples of use:
<ul>
<li>
 Create custom contact forms and process any kind of data or upload.
 </li>
<li>
 Generate user optimized content.
 </li>
<li>
 Customize every little detail of your WordPress installation.
 </li>
</ul>
Design
Icon & Wallpaper Design : <a href="https://gigateam.net/" rel="nofollow ugc">GiGATEAM Ltd.</a>
Translation
English and German : <a href="https://www.alexander-fuchs.net" rel="nofollow ugc">Alexander Fuchs</a> 
Spanish : <a href="https://www.ibidemgroup.com/" rel="nofollow ugc">IBIDEM GROUP</a> 
Portuguese : <a href="http://inforarte.com/" rel="nofollow ugc">Luis Reis</a> 
Serbian : <a href="http://www.webhostinghub.com" rel="nofollow ugc">Borisa Djuraskovic</a> 
Italian : Andrea Rosenthal Manetti

PHP Everywhere

How dare you just kill the classic editor? 

And not even a decent interim solution is offered, only a list of which pages no longer work. 

This is really terrible. Everyone who was happy about a great connection to Digistore or something similar is suddenly faced with a problem - OR DON'T KNOW THAT THEY HAVE ONE! 

Really, weak and with that, everything by this author died for me.

PS: Over 1 million users use the classic editor. Shutting out a million users isn't a brilliant move.

kill websites with stupid blocks


For my ACF Pro projects that use meta boxes, I use FSE themes just because it is so much easier to create and edit custom templates for the project. However, Because FSE themes can only use blocks + HTML and CSS, this plugin is invaluable to me for some custom php coding.



One suggestion that I have and I would love to see for extra security, is to have the option for this plugin's block to show up only in the templates, and not in posts, pages and CPTs. Of course I can only use TinyMCE and with ACF Pro disable the editor all together for the corresponding CPT, or simply remove the Post Content block from the appropriate templates, but having an option to limit this plugin to just the templates will be a more elegant solution.



Nevertheless, this is a very important plugin for me.


God Sent for FSE Themes.

This plugin enables PHP code everywhere in your WordPress instalation.

Using this plugin you can use PHP in the sidebar, pages and posts.

****** cos-html-cache ****** vs PHP Everywhere

cos-html-cache vs PHP Everywhere