[…] in place all types of automated testing around the code, we can hire QA engineers to test all sorts of edge cases, and we can have entire support departments dedicated to handling user feedback, requests, bug reports, and so on. And still they persist. Rather see them as an enemy that has to be […]
Search: “support” (Page 39 of 69)
We found 345 results for your search.
[…] way to customize the look of their plugin without losing changes during upgrades. The feature’s easy enough to port from plugin to plugin and it provides a consist way for me to support users. Again, I’ve my own thoughts on custom stylesheets that I’ll discuss in another post. Ain’t No Body Got Time For That
[…] exist, then it will be left alone Simple enough, right? Other Updates In addition to this single new feature, I’ve also updated the following: Verifying WordPress 3.5 support Updating localization calls Updating calls to play nicely with newer versions of PHP Again, these are largely small updates to make sure the plugin is as […]
[…] that are tough to put into practice or aren’t always feasible to do so, that doesn’t mean some of it can’t be done. This doesn’t refute or support the statement in the original article though, does it? Specifically, said article claims: “Nobody gives a f*** about your clean code.” Is that true? Who Cares […]
[…] assets, then the block panel within the editor should yield something that looks like this: And that’s it. As mentioned earlier, you can see edit and save are simple. It’s possible to make them as elaborate as needed, but if you’re just building a container to support your custom blocks, this is all you need.
