The case against Singletons in WordPress

ByBrady Vercher Posted on Updated on
Mike Toppa makes a case against Singletons in the ongoing discussion regarding best practices for object oriented WordPress development.

Similar Posts

Shoppable Pins, WooCommerce 6.4, and the Blockified Road Ahead
| | | |

Shoppable Pins, WooCommerce 6.4, and the Blockified Road Ahead

ByBob Dunn
WooCommerce Partners with Pinterest 📌 WooCommerce 6.4 and Blocks Roadmap Released 🗺️ Blockify all the things! ✂️ DevLife Snippets
Advanced Phone Fields for Gravity Forms
|

Advanced Phone Fields for Gravity Forms

ByDan Knauss
Phone number fields in Gravity Forms can be tough. You may have resorted to building your own custom fields and doing some coding to accommodate numbers outside the North American Numbering Plan (NANP) — or even within it. You may have had to match a precise numbering format for syncing a form field with a…
Editor blocks design is underway

Editor blocks design is underway

ByBrian Krogsgard
The editor blocks concept is being designed. An extremely healthy conversation is happening on Make Design around what the behavior should be, and how people may interact with a block-style editor. I’m really liking the general UI concepts, and most of the shortcut ideas, like using a / for quick-command access. Note that the image…

Replace the WordPress the default category metabox with radio buttons

ByBrian Krogsgard
Justin Sternberg posted on the WebDevStudios blog a code example for changing the default hierarchical taxonomy metabox (like for categories) into a radio button select box. This is very handy for limiting end users to choosing only one taxonomy term.