Sean Klein

Code to Widget Plugin uses PHP files from a specified directory, and (if the file has the proper template tags) adds a Widget.
<h3>Details</h3>
Code to Widget provides an easy way to create widgets, without having to deal with writing the widget class everytime
<h3>Configuration</h3>
The plugin provides an interface for selecting a specific folder to search for widgets in. The folder path entered into the settings page must be an absolute path. Then the widgets are easily configurable similar to all other widgets.
The files in the specified folder need to have specific template tags to be added as widgets. The following code will need to be added to the top of the files:
<pre><code><?php
/*
Widget Name: Test Widget 1
Widget Description: Test 1 widget
*/
?>
</code></pre>
A “Widget Title:” field can also be added. That title will be set as the default widget title when the file is selected on the widget settings screen.

Code to Widget

Code to Widget Plugin uses PHP files from a specified directory, and (if the file has the proper template tags) adds a Widget.

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.

Code to Widget vs PHP Everywhere