Its pretty easy to add a loop to a page template but having pagination will … Read More »
March 04
It’s been a long time since I worked on a JSP project and I’m now … Read More »
March 02
One of the very first things I had to do to start using the … Read More »
August 26
This morning I needed to use the the_category tag but I needed to exclude a … Read More »
December 15
Cut from my post on this “Page Searching examples” thread on the wp-hacker’s list and a continuation of Jared and my conversation on a previous post.
Here’s what I propose, knowing it’s most likely not going to happen
but it will alleviate: user expectation, not bloat the core with
“unnecessary” options and more importantly the patch [I assume] will
only be a few lines of code:Let’s have Wordpress’ default search include:
* Posts
* Pages
* Tags
* Meta fields
* Attachment Fields (title and description)
…this is what I strongly believe the author expects search results
are pulled from.THEN,
Have the community (maybe me) create a plugin that will provide
options for the user to exclude, limit or include more from the core
search.All this without requiring the any new options panel.
Pretty much the exact opposite of what’s being done now, except it
will help the average non-plugin wordpress user and the wordpress user
that doesn’t know how the default search works. Whom are the people
I’m thinking about when I make these suggestions or comments, not the
wp-hackers who can write a plugin or the above average .org user
swamped with plugins.Then again, what about the wordpress.com user?
[These are only suggestions and should not be taken as a directive nor
was any of it meant to be condescending or rude to anyone on this
list. Thanks]–Dan Cameron
http://dancameron.org
[Updated 10/5]
Version 2.0 was just released.
Version 2.0 – multiple mobile browsers supported
After a week and a half of hard work Jared and I committed Version 1.0.2 to Wordpress Extend. we lapsed and forgot to test the plugin on the 2.2 branch and now we’ll need to pull it back for a later release when we get everything straightened out for the majority of users.
Mobile Admin started it’s development shortly after Matt requested on the [wp-hackers] mailing for the community to create an iPhone Admin theme in response to the MovableType iPhone beta theme released just a days prior.
Jared did the majority of hard core coding and I centered around the interface and CSS. Since I was the one with the iPhone I was the lucky one to exhaustingly check in and test new CSS changes for testing on the phone, since there aren’t any good development tools for iPhone devs; iPhoney is phony before anyone suggests it.
Here’s the current trac project home for bugs and management.
Here’s the support and suggestion forums. If you have an iPhone we really need your suggestions so please throw them out to us there.
Or if you have any contributions or changes you’d like to make directly just contact us.
Created with Admarket’s flickrSLiDR.
Details:
iPhone / Mobile Admin UI for WordPress?
The plugin home page is on WordPress Extend.
Contributors
Jared Bangs and Dan Cameron
Gives a mobile-friendly admin UI to browsers by User Agent. The iPhone is the primary supported device for the first release.
Description
Mobile Admin adapts the WordPress? admin UI to be more friendly to mobile devices, specifically phones. The iPhone is the primary target (and only supported device) for version 1, with more to come in the future.
Most common WordPress admin features are supported:
… with more to come in later revisions.
Other resources
Please submit all usage questions to the support forums
The Trac server can be used for viewing changes and submitting tickets
SPECIAL NOTE – Testing and bug reporting is especially encouraged, as only one of us currently owns an iPhone.
I just got a call from Joswiak who wanted to make clear: “not hate” doesn’t mean “like” or “support.” I think I made that clear further down, but they said that some people may not be reading all the way down this piece. So to summarize: Apple will neither forbid nor support native code on the iPhone/Touch. They will not … Read More »
September 11
After finally setting up Trac and SVN on my new server I’ve moved all my projects off Google Code hosting. But instead of checking in all of the code to the new repositories I updated all of the theme and plugin pages. So the problem, you’ll not be able to download anything until tonight when I get around to updating the repositories. Unless you just want to head over to GCode (link above) where all the latest versions are, plugins don’t count.
Currently I’m planning to keep all of my plugins on extend but if it’s a major plugin like Search Everything I’m making a trac project to make it easier to manage. I’ll be able to do betas there too. Linking plugins to wordpress.org’s extend is almost a requirement now if you want any kind of good exposure or you want to be involved with automatic plugin updates whenever wordpress roles that feature out.
All of my themes will have it’s very own trac project, e.g. iScattered. I had thought Google Code was going to work best but after all the work of getting trac and svn installed and thinking about manageability of two project homes I deleted had to break off of GC.
This whole week I wanted to post about each theme; describing what changed or didn’t change, a showcase almost while updating their project homes and pages at the same time but it didn’t work out since I had to migrate servers Tuesday. I’m going to push it off, hopefully next week will work out but either way the code will be up soon and if you can’t wait just go here.
I’d recommend reading this illogical post from Duncan at Techcrunch and then rally around Matt in the comments section.
After reading all of Duncan’s and Matt’s comments I had to throw my two-cents in,
Duncan: I don’t see your point. You mention that Matt can’t have it both ways but by writing this article and placing *your* issues into a “gray area” you’re rewarding your terms with two-ways to lean; neither for or against, making you’re actually opinion irrelevant. And isn’t this just an opinion piece? I don’t see any facts–that are correct–, it’s all lambasting for self-promotion, similar to your friends at Vallywag.
No matter how many times you’ll be told that your statements are false and irrational you’ll always be clinging to that “gray area” message.
In your response to the question you pose to Matt, “WTF did someone do to you BTW? Where did this hatred come from?”. What exactly made you criticize Matt–and by association the entire wordpress community of developers and supporters–? All without one ounce of research of how to properly run a business through OSS, the business model of automattic and how Matt runs it, the history of wordpress or even get to know how spam works? Instead of reporting you glued your self-important thoughts together and lambasted the very person AND the community that built the infrastructure for you to get paid from.
I find this post so disturbing as D’s trying to associate taking advantage users by placing paid text ads on released code is the same as Matt providing a service through Wordpress.com and Akismet. He really needs to step back and learn a few things, specifically:
The Blogroll: it’s there as an example for users, is easily managable and provides a credit to the hard 
working developer community. Since Matt works very hard at wordpress.org he deserves it like the others. Lastly how does he make money off of those links again?
Akismet: Is entirely a service. Yes the free Akismet users contribute to the whole but they also benefit is the entire community. Matt is not holding back the perfect solution to stop all spam for every wordpress user, he’s just providing an added value to the paid users of Akismet because it includes a service level that the free addition could not support.
Wordpress.com: Charging for an extra service level through Wordpress.com doesn’t leverage the community nor the code-base. It’s a service level agreement that you’re paying for, similar to Akismet.
Update: Another comment.
I just finished updating all of my classic and K2 themes, what a chore. I’m looking to release them this week; hopefully tomorrow. The reason for not releasing them now: I need to post about the changes, get the word out through some posts and setup repos.
I’m going to have to decide tomorrow if I want to continue with Google code for all of my themes (I already have a few there now) or wait until I get my new server up and running. Either way I’ll zip them up if I plan to wait.
One thing I will be doing is depracating Sca4ered.2, I like the theme but it’s a mess of code. I saw a lot of code that wasn’t clean in all of my themes, remnants of the early years, but this theme stood out like a sore thumb. Don’t look it’s bad, and instead of cleaning it up I’m just going to let it die, maybe Google code could salvage it if anyone wanted to contribute–but I highly doubt it–.
It looks like it will be 1.5 week, since I’ve versioned all of my themes to 1.5 and it turns out a few of my plugins last week reached the 1.5 milestone too.
