WordPress just released version 3.1.4. Overall, it’s a solid release but if you’re working with a theme that has support for multiple custom menus, then you may notice a regression with custom menus after you upgrade the application. Specifically, all custom menu locations that do not contain a menu actually display all pages on […]
Search: “support” (Page 21 of 68)
We found 336 results for your search.
[…] the problem of needing to introduce a fallback. The standard embed player when the audio element or MP3’s are not supported. Since not not all browser yet support the audio element, the plugin does the best it can to determine if it should fall back to a normal `embed` element. If so, it will […]
Lately, one of the questions that I find myself wrestling with is what’s considered respectful and acceptable for charging for support or accepting donations for open source plugins? Or, more simply, what’s an ideal model for open source profit sharing when you’ve received contributions to open source plugins? A Disclaimer (For The Paranoid!) To […]
[…] to releasing a free plugin, there are several obligations that I believe the developer has: The plugin should work with whatever version(s) of WordPress it claims to support The developer should be responsive to both users and customers alike but is not obligated to build custom features for users Unfortunately, there’s a type of […]
[…] ability to change that? This is where additional block attributes come into play. ⌨️ Update the Block Attributes First, we’re going to update the attributes to add support for color of text and background. Locate the area of index.js that looks like the following: attributes: { content: { type: ‘string’, source: ‘text’, selector: ‘input’ […]