Amir Helzer

jozik

<a href="http://wp-types.com/home/custom-fields-shortcodes/" rel="nofollow ugc">Custom Fields Shortcodes</a> lets you insert custom fields that you created using Advanced Custom Fields, Custom Field Template and More Fields or manually, into the WordPress visual editor. You’ll get a new popup, next to the media buttons. There, you can select which custom fields to insert, anywhere in the content.
You will see the custom fields that you’ve defined, neatly arranged by meta-boxes. Choose the field to insert and you’ll get its shortcode. You can insert custom fields from either Visual or HTML editing modes.
When inserting custom fields that were created by other plugins, they display using the plugin’s API. For instance, if you use ‘Advanced Custom Fields’ and you insert a ‘radio’ field, you get the current value. If you insert a WYSIWYG field, you get the full HTML content.
This allows inserting custom fields to your content without having to read them using PHP.
<h4>Adding Custom Fields to WordPress Templates</h4>
Custom Fields Shortcodes integrates seamlessly with <a href="http://wp-types.com/home/views-create-elegant-displays-for-your-content/" rel="nofollow ugc">Views</a>. You will be able to create <a href="http://wp-types.com/documentation/user-guides/view-templates/" rel="nofollow ugc">dynamic templates</a> that include any field you want. Then, apply these templates to different content types, right from within the WordPress GUI.

Custom Fields Shortcodes

Lets you insert custom fields in the visual editor without coding in PHP.

scribu

Jotschi

Front-end Editor is a plugin that lets you make changes to your content directly from your site. No need to load the admin backend just to correct a typo.
It makes the same <a href="https://codex.wordpress.org/Roles_and_Capabilities" rel="nofollow ugc">capability</a> checks, so that if a user isn’t allowed to edit something in wp-admin, they aren’t allowed to edit it in the front-end either.
You can edit posts, pages, custom post types, comments, widgets and many <a href="http://github.com/scribu/wp-front-end-editor/wiki/List-of-editable-elements" rel="nofollow ugc">more elements</a>.
Goals:
<ul>
<li>save as many trips to the backend as possible</li>
<li>compatible with any theme, out of the box</li>
<li>light and fast</li>
</ul>
Support and development:
<a href="https://wordpress.org/support/plugin/front-end-editor" rel="ugc">Support</a> is handled by the lovely <a href="https://wordpress.org/support/profile/designsimply" rel="ugc">designsimply</a>.
I am not developing the plugin anymore; only applying the patches that other people send via <a href="https://github.com/scribu/wp-front-end-editor/" rel="nofollow ugc">Github</a>.
Credits:
<ul>
<li><a href="http://aloha-editor.org" rel="nofollow ugc">Aloha Editor</a> for the fantastic WYSIWYG editing component</li>
</ul>
Links: <a href="http://github.com/scribu/wp-front-end-editor/wiki" rel="nofollow ugc">Documentation</a> | <a href="http://scribu.net/wordpress/front-end-editor" rel="nofollow ugc">Plugin News</a> | <a href="http://scribu.net" rel="nofollow ugc">Author’s Site</a>

Front-end Editor

Edit content inline, without going to the admin area.

Custom Fields Shortcodes vs Front-end Editor