webdevstudios

Michael Beckwith

pluginize

modemlooper

Brad Williams

John Hawkins

<p>Custom Post Type UI provides an easy-to-use interface for registering and managing custom post types and taxonomies for your website.</p>
<h4>Custom Post Type UI Extended</h4>
<p>CPTUI helps create custom content types, but displaying that content can be a whole new challenge. <a href="https://pluginize.com/plugins/custom-post-type-ui-extended/?utm_source=cptui-desription&utm_medium=text&utm_campaign=wporg" rel="nofollow ugc">Custom Post Type UI Extended</a> was created to help with displaying your crafted content. <a href="https://pluginize.com/cpt-ui-extended-features/?utm_source=cptui-description-examples&utm_medium=text&utm_campaign=wporg" rel="nofollow ugc">View our Layouts page</a> to see available layout examples with Custom Post Type UI Extended.</p>
<h4>Plugin development</h4>
<p>Custom Post Type UI development is managed on GitHub, with official releases published on WordPress.org. The GitHub repo can be found at <a href="https://github.com/WebDevStudios/custom-post-type-ui" rel="nofollow ugc">https://github.com/WebDevStudios/custom-post-type-ui</a>. Please use the WordPress.org support tab for potential bugs, issues, or enhancement ideas.</p>


Custom Post Type UI

Works well, but it's missing a number of CPT options: rest_namespace, capabilities, map_meta_cap, register_meta_box_cb, rewrite[feeds, pages, ep_mask], template, and template_lock. I realize these are not common, but it's a drag when you go to create your third CPT and realize you need to find a different solution that will accommodate one of the missing options. It's no good to have a few registered in CPTUI and a few by hand.

Good, but missing a bunch of options.


There is no documentation. In plugin description there is just a link to so called documentation that is just bunch of tutorial of doing specific stuff that are very scarce and targeted to people who already know how to use it. Nothing for first time users, to learn how to actually begin with plugin, or at least nothing that can be easily found.


One of the worst documented plugins I saw


Thank you very much for this amazing Plugin that serves us since years!


Amazing Plugin


speeds up development and has nice user-friendly UI. It was a nice experience working with this plugin.


really useful


Plugins like these make wordpress worthwile


Great piece of software

Admin UI for creating custom content types like post types and taxonomies

mormat

<p><strong>[mormat_scheduler]</strong> is a shortcode that render an event scheduler component. The purpose was to provide an alternative to Google’s scheduler.</p>
<p>The scheduler offers three calendar views : <code>day</code>, <code>week</code> or <code>month</code>.</p>
<p>Events can be created, edited and deleted directly from the scheduler (which can be done by logged in users only).</p>
<p>Drag and drop is also available.</p>
<h4>Shortcode parameters</h4>
<ul>
<li><strong>height</strong> : Define the height of the scheduler. It must be a css compatible value (for instance “640px” or “70vh”). </li>
<li><strong>initial_date</strong> : A date from which the scheduler will start displaying the events. If not provided, the current date system will be used. A string formatted as “yyyy-mm-dd” can be provided or any value compatible with the <code>Date</code> javascript object. </li>
<li><strong>default_view</strong>: The default view used for displaying events. Allowed values are “day”, “week” or “month”. Default value is “week”</li>
<li><strong>events_namespace</strong>: Useful only if you need to display and manage a specific set of events. The default value is “”.</li>
<li><strong>locale</strong> : i18n locale used for displaying dates (For instances <code>en</code>, <code>en_US</code> or <code>en_GB</code>). Default value is the website’s current locale.</li>
</ul>


Mormat Scheduler

Add a Google-like scheduler to your WordPress site

Custom Post Type UI vs Mormat Scheduler