For me, it's pretty much OK that the new version was released immediately after fixing the issue. „The problem“ of new release are the implications. Which means:
- „new version available“ announcement method
- upgrade distribution method
Category: wrong way
-
Too many upgrades these days? Not really a problem.
Published: On Wednesday, August 12, 2009
Another minor WP version is out and guys in (WP)Tavern are discussing whether it's O.K. or it isn't and how they feel about it and so on. I will prefer pin my humble opinion here, so that it will seem like this site is still alive :-). -
Who owns the function? [from Plugins development series]
Published: On Thursday, February 12, 2009
Once again, I find useful torecommendremind one important practice, when writing a plugin.Be sure, that user will notice, he's using functions of your plugin.
Life example: In the first project, user did use the
get_metafunction and expected, it's a core function. It didn't do anything specific. Why should he ever expect, it's part of a plugin? But once he tried to use this function elsewhere, it surprisingly failed, function wasn't found. The (in other ways great) plugin called More fields was missing.Two ways how to emphasize function's owner:
- prefix function-name with your unique signature (will also
lower the risk of name-collision):
get_meta⇒mf_get_meta - use a bundling class:
get_meta⇒MoreFields::get_meta
Actually, WordPress itself should practise this habit too – since any function is in fact a part of a bigger unit.
- prefix function-name with your unique signature (will also
lower the risk of name-collision):
-
Please, don’t force us to download plugins’ screenshots
Published: On Sunday, December 14, 2008
Can anybody tell me what is the sense in including plugin's screenshots into its main ZIP archive? Does anybody need this, has anybody ever appreciated it?My opinion is directly the oposite. Not only that I have never appreciated this feature yet, but also it's quite uncomfortable to me – regularly.
- more files in plugin's directory make it less clear
- these screenshots can mean hundrets of kilobytes to download/upload
Until managers of WordPress official plugin repository decide to fix these unnecessary inclusions, I'd like to please plugins' authors to spend a minute with optimizing size of screenshots. Remember. JPG is better for photos, PNG/GIF (8-bit) is great for screenshots. Wrong. Wrong.
Right(too hard to find). -
On 2.7 and growing in general
Published: On Monday, December 1, 2008
New major Worpress' version is going to be released any moment and I must react with „WTF“ again. Again – because a few months ago when 2.5 was fresh and hot yet, I wrote down some similar impressions. That time, the most unpleasant thing were not-too-smart feature additions, if I do remember correctly. Today it's about the same thing, adding features or possibilities conflicting with my personal (WP) development philosophy:It's no reason to code something hard, when there's the way to do it as a plugin.
-
Will the old dog ever change?
Published: On Monday, March 24, 2008
Reading a resume of db changes in WP 2.5 I found out, that WordPress will probably never change.Changed 'comment_approved' to varchar(20) NOT NULL default '1'Changed 'link_visible' to varchar(20) NOT NULL default 'Y'Changed 'autoload' to varchar(20) NOT NULL default 'yes'Changed 'ping_status' to varchar(20) NOT NULL default 'open'
I think it's a bit overvarchared here…
Update: funny thing I have found right now in the code of WeblogToolsCollection:
<!-- Gorgeous design by Michael Heilemann - http://binarybonsai.com/kubrick/ -->:-)
-
Widgets integration – how good step was that?
Published: On Sunday, August 26, 2007
It seem like this is gonna be another article from the “wrong way” “category .(yes, categories are invisible for now)”. I’m sorry, but what can I do? I just must think about these bad things and another urge forces me to transcript my minds… here!
My mindset to *Wordpress widgets* is really simple. Although it’s an interesting concept, I don’t like them and don’t use them because **they do not provide enough flexibility which I unconditionally require**.
And secondly, I think that sidebars (like any other site’s design element) should be made in a way that is correspondent to designer’s aims and giving the customer an opportunity to change the design is not in interest of anybody.
And even if the designer and the content-master are one and same person, even in this case are assets of widgets disputatious, in my opinion, from the same reason: opportunity to change the design easily is also opportunity to change design imprudently.
-
Theme folder needs cleaning, right?
Published: On Friday, July 20, 2007
Today I want to say a few words about the files located in typical theme folder. Before all I think that after opening this folder, you will see just a mess, mass of non-ordered files, the pile of randomly sorted files. The more often I work in template folder (what's actually almost always if I work with WP), the more I don't like this view. -
WP feeds performance? Miserable!
Published: On Friday, June 22, 2007
Today I get an interesting idea: to explore WordPress’ **power demands while feeds content generation**. That means I probed how much time it takes to generate a XML file (either RSS or Atom, either with posts or with comments). I *hoped* that WP developers *presumed* – that feed pages are going to be the most hit pages, pages creating most of the traffic (sure, not measured in data volume in bytes but for example in DB queries). Obviously, they didn’t do so.