wp_deregister_script('jquery'); before wp_head(); is
run, where the scripts are usually printed out from the queue.
Category: this way
-
My little experience with the queue of scripts
Published: On Monday, February 16, 2009
– Sometimes you might be surprised, that WordPress/eventually a plugin (from an unknown reason) enqueued jQuery (not speaking about administration but public template!). De-queuing is simple: Call -
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):
-
How did I vote in “Prioritizing Features” survey
Published: On Friday, December 26, 2008
Who had read anything here before, would probably answer „predictably“. :-) WP.org team is collecting users' opinions of most wanted features. This is how I'd like to see the next big version of WordPress.
-
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). -
Plugin development tip: Sign your code via HTML comments
Published: On Monday, January 7, 2008
I wanna suggest some rules for plugins development: making HTML code. Well, probably not rules, but something like good practices. Or so. -
Theme folder clean up: story continues
Published: On Saturday, August 4, 2007
I know I have written on this topic twice before, I know it must be annoying! :-) But I feel that the moment of perfection is coming closer and closer and at the end I will have in my hand the final vision of ideal theme directory structure. -
Mastering the feeds’ problem
Published: On Tuesday, July 10, 2007
You probably noticed that some time ago i cried about “how silly WordPress works with feeds”:/wordpress/wp-feeds-miserable-performance/, now I come with a solution. First thing I tried before I could be lost in infinite list of wp-plug-ins was that I **signed up into “FeedBurner”:http://feedburner.com/**. If you didn’t hear about Feedburner yet (what I really doubt about), it’s a web service which offers you much things, everything is of course related to *feeding* and it’s nicely “written down here”:http://www.FeedBurner.com/fb/a/about by FeedBurner people themselves.
