Vladimir Prelovac

No frames removes the browser frames sometimes imposed on your site.
It has become a trend for top sites especially news and content aggregrators to show your site inside a frame (if you see a site toolbar on the top of the page it’s usually using a frame).
Basically the visitor never leaves the site using the frame although they are viewing content created by you. This is done for multiple reasons and one is to improve the metrics of the site using the frame as ‘visitor time on site’ will improve only for the site using the frame and not you.
Purpose of No Frames plugin is to detect these cases and break your site free from the shackles of the frame, thus presenting the user with your full page.
This not only improves your visitor experience but your site metrics as well.
Changelog:
v0.2 
– Disabled it for admin panel
v0.1: 
– Released first version
Plugin by <a href="http://www.prelovac.com/vladimir" rel="nofollow ugc">Vladimir Prelovac</a>. Looking for <a href="http://www.prelovac.com/vladimir/services" rel="nofollow ugc">WordPress Consultant</a>?
<h3>License</h3>
This file is part of No Frames.
No Frames is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
No Frames is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with No Frames. If not, see <a href="http://www.gnu.org/licenses/" rel="nofollow ugc">http://www.gnu.org/licenses/</a>.

No Frames

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.

No Frames vs PHP Everywhere