Browse: Home / wordpress
Roll Your Own Lifestream With WordPress

Roll Your Own Lifestream With WordPress

By Jeffro on October 2, 2009

lifestreamwithwordpressEver wanted to know how to stream your life using WordPress? Matt Mullenweg does it with his blog, Adii does it with his and now you can to. The idea is to publish snippets along with the usual long form content. The problem is, the snippets and the long form content look the same unless you use some CSS along with a few other techniques. While there are a few different plugins and themes that accomplish this use of WordPress, Jestro explains how to roll your own.

However, Jestro talks about modifying a themes index.php and single.php something that may be a problem for those using a child theme based on a framework. If you follow through with this technique for your own blog, send me a link to take a look at it in the comments.

Posted in | Tagged , , , | 5 Responses

Guide To Installing WordPress Locally With WampServer

Guide To Installing WordPress Locally With WampServer

By Jeffro on October 1, 2009

wampserverlogoSparun, who is a member of the WPTavern community sent me a note the other day that he had published his first free ebook which goes into detail on how to install WordPress locally on Windows XP using WampServer. The guide contains 20 pages, each with there own screenshot to aid readers in the entire process.

What’s cool about this guide is you can either browse through it in a browser or download the PDF for viewing offline. I have an instance of WampServer installed on my own Windows XP desktop machine that I use to test the latest nightly builds of WordPress. I also have a mirrored instance of my live site on my local server to test the dev builds of WordPress with plugins I use everyday here on the Tavern. Download the guide and save it to your resources bin.

Posted in | Tagged , , , | 4 Responses

Clear Policies Related To Mod Validation For phpBB3

Is A Plugin Validation Team A Pipe Dream?

By Jeffro on September 30, 2009

wordpresslogoNow that the WordPress plugin competition for 2009 is complete, Ozh has published his reviews of each plugin that was entered into the competition. Some of his reviews mention particular security issues that were discovered along with some shoddy coding. Once I read his reviews, it occurred to me that if the plugins in the competition had these issues, just imagine the state of plugins being hosted in the repository. If every plugin in the repository was reviewed as closely as the competitions were by someone like Ozh, I’m afraid of what the results would be.

This leads me back to the idea that the WordPress plugin repository needs a plugin validation team. This team would be a group of individuals of Ozh’s caliber that would review each line of code for any plugin that was initially submitted to the repository. They would make sure that the coding guidelines were met, bad code was corrected, and would not approve of a plugin until all checks were passed. Unfortunately, it’s too late for the repository to have such a team/process. In order for it to be truly effective, the plugin repository would need to be wiped out to start fresh with these new guidelines/practices in place. Something I don’t see happening anytime soon.

Currently, WordPress plugins are encouraged to be built around these WordPress Coding Standards. There is also documentation on how to write a plugin for WordPress. When a plugin is submitted to the repository for inclusion, the plugin is manually checked by someone to make sure that the submission came from a human rather than an automated process. I’m not sure if each line of code is checked or if it’s just a once over but once the plugin is approved, the author then has SVN access to that plugin which is an automated process. There in lies another problem. These revisions are not checked because there are hundreds to thousands of them each day.  So the other risk here is  a popular plugin authors account gets hacked, that person publishes malicious code into the plugin to trigger an upgrade notice and now potentially hundreds of blogs are compromised. Thankfully, this hasn’t happened yet but I wonder if it’s a matter of when, not if.

That's A Lot Of Plugins

That's A Lot Of Plugins

So even if there was a plugin validation team, there is no second line of defense unless you consider that to be the countless number of eyeballs reviewing the code as they install plugins onto their blogs. However, this raises another point.

I believe that the expectation for end users to dive into the code for plugins and themes they install onto their site is unrealistic. Essentially, everyone who uses WordPress would need to have a good understanding of PHP including the security aspects of it in order to make good decisions on whether a theme or plugin would be safe to install on their site. Matt Mullenweg and the WordPress project can not control end users blogs to make sure they are upgraded, they can’t control plugins or themes to ensure they are upgraded, they can’t control end user decisions but what they do control are the repositories. I think these repositories are a huge responsibility for the WordPress project and that in the beginning, more should have been done to ensure quality code would only be accepted into the repository. This is the way it’s worked for phpBB3 and so far, seems to be working well for them. Sure, if something like this were put into place, there wouldn’t be as many plugins or themes on the repositories but in this case, the end justifies the means. Good code and less insecure plugins and themes more than trump the amount of choices that would be available.

Clear Policies Related To Mod Validation For phpBB3

Clear Policies Related To Mod Validation For phpBB3

Now that a validation team simply wouldn’t work because the repository is in full swing, I think the potential is high that it is a ticking time bomb filled with insecure or improperly coded material. But, I don’t know PHP from ABC so I can’t confirm or deny my suspicion. The worst case scenario is that a new line of thinking takes place regarding the repository. Great place to pick from a large variety of plugins that fill a need but if you don’t know PHP to check how they were created, you may be installing the demise of your site. Of course, it would take some popular plugins to be compromised or, some popular sites to be compromised due to a plugin installed from the repository for this line of thought to gain any steam but considering how easy it is now to install plugins from the repository, it could certainly happen.

I see this entire issue as one of the big problems facing WordPress. Thankfully, nothing drastic has taken place so far but as more plugins are added to the repository, old ones are not pruned off (yes I know that some WordPress 1.5 plugins work on 2.8), and the bar to entry to use WordPress is lowered even more, the ingredients are slowly coming together to increase the risk for all who use the software.

As far as solutions to the problem, I can’t think of any off the top of my head that would not require the plugin repository to just start over. I suppose all end users of WordPress could read PHP For Dummies to be better educated on what is going on between plugins and their WordPress powered site but that would be expensive and some folks just want to publish content, not develop. Any solution that goes into place now which would make inclusion into the repository a more stringent process wouldn’t work because of the thousands of plugins submitted before them.

If the team is not going to make it harder to get into the repository then there should be clear warnings letting users know that while they host plugins, they can not be held responsible for any damage that may occur to their site from a plugin they installed from the repository. If I installed a plugin from the repository and it caused my site to be compromised, I would blame not only the plugin author, but much of the blame would be pushed onto the repository for hosting the plugin which made it easily available to millions of people.

Your Answers:

I find this subject to be a huge problem. You may not. Let me know in the comments what you think. Also, if you have any ideas on how this problem can be solved, particularly without requiring the plugin repository to start over, tell me about them.

Posted in | Tagged , , , | 16 Responses

Custom Install Profiles Sounds Like A Cool Idea

Custom Install Profiles Sounds Like A Cool Idea

By Jeffro on September 28, 2009

wordpressqilogoOn the WordPress Hackers Mailing list, Ptah Dunbar recently proposed an idea that I think is pretty cool and would be a time saver for developers and custom installers called Installation Profiles.

Installation profiles could automatically pre configure WordPress with a set of activated plugins, change the default activated theme and could also possibly change/add some default settings/content?–all during the install process. This could be beneficial to a lot of users/developers allowing them to jump right into content creation instead of site configuration.

Users could create a profile that contains all their settings and activated plugins they’d usually have to configure after installing WP. The profile that they create could also be used across all their blogs–saving a lot of time.

I’m thinking something along the lines of being able to export my blogs configuration into an XML file just like you can with blog content into a WordPress eXtended RSS file. I use the same settings for each WordPress install I do and since I occasionally reformat my WordPress powered sites, it would be an awesome time saver to just upload an XML file and have my site setup the way it was before the reformat took place. Of course, there are other uses for install profiles so implementing an extensible way of creating them would be a good idea. What do you think of the idea?

So far, the closest thing we have to installation profiles is DD32′s newest project, WordPressQI or WordPress Quick Install which provides options to change the pre-installed plugins that are installed along with WordPress as well as configuring permalink settings up front.

Posted in | Tagged , , , | 16 Responses

WordPress RSS Parser SimplePie Ceases Development

WordPress RSS Parser SimplePie Ceases Development

By Jeffro on September 28, 2009

simplepielogo Over the weekend, some big news was published on the SimplePie development blog where it was announced that development for the RSS Parser would cease effective immediately. While the first version of SimplePie was built ontop of MagpieRSS, it quickly became the de-facto RSS/Atom parsing software for PHP. WordPress uses SimplePie to parse the RSS feed for the dashboard widgets such as Other WordPress News, WordPress News, etc.

Beginning in WordPress 2.8, MagpieRSS was beginning to be phased out in exchange for SimplePie due to the lack of development taking place around Magpie. Unfortunately, the same thing has happened to SimplePie leaving WordPress with a few options. First, hope that a fork of SimplePie is created which WordPress can then use. Second, continue the development of SimplePie to fit the needs of WordPress only or third, look for another actively developed RSS parser for PHP. It’s worth noting that in WordPress 2.9, SimplePie has been upgraded to version 1.3.

This doesn’t mean that dashboard feeds in WordPress will fail to be parsed as SimplePie is not a third party service. However, there are a ton of plugins in the repository that were built with the default RSS parser in WordPress both when it was Magpie and then SimplePie so this development affects those as well.

The WordPress development team is well aware of this announcement and it looks like it may be a topic of discussion for this weeks WordPress development meeting.

Posted in | Tagged , , , | 10 Responses

The Lowdown On WPCoop With Jayson Cote

The Lowdown On WPCoop With Jayson Cote

By Jeffro on September 24, 2009

I wanted to write about this new site called WPCoop.org but was unsure how to go about it. Instead, I’ve pestered Jayson with a bunch of questions and decided to go the interview route. Enjoy.

What inspired you to create WPCOOP.org?

I am a raving fan of WordPress.  As a developer, designer, business owner and entrepreneur I saw a need for WP professionals to be able to align themselves with fellow designers and developers to collaborate on projects and establish a network of contractors with various styles and skill sets. WPCOOP members have the availability to build out a team to win larger projects.

wpcoop

There is a high demand for WP services today from small and medium business. It can be a rather enduring and lengthy process to evaluate and interview web design and development firms for a project.  A business wants to work with a firm that understands their industry and business development methodologies.  WPCOOP allows businesses to learn about our members and select individuals that they want to work with.  Kind of a one-stop-shop to help companies find the right designer, developer and project manager based on their given criteria.

How will this site be any different than the WordPress consultants list?

The WP consultants list is just that “a list“.  You still have to go to each individual site to learn about the company, their expertise and services. WPCOOP members have their own profile page listing specific information about them, their company and their work.  Any visitor to WPCOOP can learn about several different designers and developers from one location.  They can read articles, view videos and hear podcasts contributed by WPCOOP members and gain a firm understanding to make an educated decision on selecting a pre-screened professional for their project.

What are the benefits of joining the coop?

There are many benefits to joining WPCOOP.

  • Association with the world’s most prominent group of WP professionals.
  • Exclusive access to all members for joint ventures and project collaboration.
  • Post and apply to job opportunities from your trusted network.
  • Bring projects to the table and maximize your time and effort to completion.
  • Establish a network of friends and colleagues that will support you in all your endeavors.
  • Build your business with dependable subcontractors and consultants.
  • Utilize your membership base to review, criticize and develop innovative ideas.
  • Be a part of a team designing and developing the world’s most impressive websites, applications and business solutions.

Is there a price tag on the coop?
In the true spirit of open source, WPCOOP is free to join. The future of WPCOOP lies within the participation of its members.  We are an autonomous community united voluntarily to meet common economic, social, and cultural inspirations through a democratically controlled enterprise.

Is membership open to anyone or is this invite only?

All WordPress professionals are welcome to apply.  We do have an evaluation process, basically just to ensure the applicant has significant experience and talent that will benefit the WPCOOP membership.  I don’t want to exclude anyone, but initially we are being somewhat selective.  I hope to have a Junior membership where less experienced designers and developers can join and have the opportunity to work with mentors.

wpcoop2

If someone is already established, do you think they could still find value in being a member of the coop?

Most definitely.  Its always valuable to have a network of professionals directly related to your field, whether its to share ideas, be a sounding board, get work feedback or collaborate on larger scale projects.  Many established developers and designers turn down projects because of their current work load and shy away from referrals because they want to ensure the clients satisfaction.  WPCOOP can be a huge asset to help members keep more clients and attract more work.

What is the end goal of WPCoop?

Initially our goal is to be the most definitive resource for Worpdress design and development for the individual and business communities and establish the world’s most prominent group of creative and dedicated WP professionals to continue the evolution of web content publishing.  From there its up to the members to decide.

This is Jeff of WPTavern.com. I want to write about WPCoop but not sure how
to go about it but I have a few questions regarding to site so I figure an
interview would be the way to go.

What inspired you to create WPCOOP.org?

I am a raving fan of WordPress.  As a developer, designer, business owner
and entrepreneur I saw a need for WP professionals to be able to align
themselves with fellow designers and developers to collaborate on projects
and establish a network of contractors with various styles and skill sets.
WPCOOP members have the availability to build out a team to win larger
projects.

There is a high demand for WP services today from small and medium business.
It can be a rather enduring and lengthy process to evaluate and interview
web design and development firms for a project.  A business wants to work
with a firm that understands their industry and business development
methodologies.  WPCOOP allows businesses to learn about our members and
select individuals that they want to work with.  Kind of a one-stop-shop to
help companies find the right designer, developer and project manager based
on their given criteria.

How will this site be any different than the WordPress consultants list?

The WP consultants list is just that "a list".  You still have to go to each
individual site to learn about the company, their expertise and services.
WPCOOP members have their own profile page listing specific information
about them, their company and their work.  Any visitor to WPCOOP can learn
about several different designers and developers from one location.  They
can read articles, view videos and hear podcasts contributed by WPCOOP
members and gain a firm understanding to make an educated decision on
selecting a pre-screened professional for their project.

What are the benefits of joining the coop?

There are many benefits to joining WPCOOP.
    * Association with the world's most prominent group of WP professionals.
    * Exclusive access to all members for joint ventures and project
collaboration.
    * Post and apply to job opportunities from your trusted network.
    * Bring projects to the table and maximize your time and effort to
completion.
    * Establish a network of friends and colleagues that will support you in
all your endeavors.
    * Build your business with dependable subcontractors and consultants.
    * Utilize your membership base to review, criticize and develop
innovative ideas.
    * Be a part of a team designing and developing the world's most
impressive websites, applications and business solutions.

Is there a price tag on the coop?

In the true spirit of open source, WPCOOP is free to join. The future of
WPCOOP lies within the participation of its members.  We are an autonomous
community united voluntarily to meet common economic, social, and cultural
aspirations through a democratically controlled enterprise.

Is membership open to anyone or is this invite only?

All WordPress professionals are welcome to apply.  We do have an evaluation
process, basically just to ensure the applicant has significant experience
and talent that will benefit the WPCOOP membership.  I don't want to exclude
anyone, but initially we are being somewhat selective.  I hope to have a
Junior membership where less experienced designers and developers can join
and have the opportunity to work with mentors.

If someone is already established, do you think they could still find value
in being a member of the coop?

Most definitely.  Its always valuable to have a network of professionals
directly related to your field, whether its to share ideas, be a sounding
board, get work feedback or collaborate on larger scale projects.  Many
established developers and designers turn down projects because of their
current work load and shy away from referrals because they want to ensure
the clients satisfaction.  WPCOOP can be a huge asset to help members keep
more clients and attract more work.

What is the end goal of WPCoop?

Initially our goal is to be the most definitive resource for Worpdress
design and development for the individual and business communities and
establish the world's most prominent group of creative and dedicated WP
professionals to continue the evolution of web content publishing.  From
there its up to the members to decide.

I thank you for your interest and this opportunity to share about WPCOOP.

Posted in | Tagged , , | 8 Responses

Supported Legacy Branches For WordPress.org?

Supported Legacy Branches For WordPress.org?

By Jeffro on September 23, 2009

Randy HoytThis is a guest blog post written by Randy Hoyt, author of the blog, RandyHoyt.com. He’s also the founder of Web development firm Amesbury Web.

The recent attacks on older versions of WordPress have made security a hot topic in the community. There has been finger-pointing and mud-slinging from many different directions, but there has also been some good discussion about how to move the project forward. I agree with Jeff, David, and others that responsibility ultimately lies with web site owners. While the official WordPress development blog states that the WordPress team is doing everything they can, others have been wondering if more could be done. I would like to get a discussion going here at the tavern about something that I think would help: a supported legacy branch.

What’s A Legacy Branch?

Newer versions of WordPress currently come with security fixes, but also with added functionality, database changes, and redesigned interfaces. Many users are quite happy with the functionality of their existing version of WordPress, but there is currently no way for them to get only the security fixes without also getting all the other changes. According to the existing WordPress release strategy, only the current branch is supported. When a security issue was found in WordPress 2.8.2 this summer, the new version 2.8.3 was released to fix it. Older versions like WordPress 2.6.5 were also vulnerable to this issue, but no fix was released for them because they were no longer supported. Many software companies and projects do choose to support older versions, and I would like to suggest that the WordPress team supported one legacy branch for around 18 months.

How Might It Work?

Looking back through WordPress’s release history, WordPress 2.2.x and 2.6.x could have been supported legacy branches. Imagine a site built on WordPress 2.2 in June 2007. Under my suggested system, the site owner would have applied only security fixes (2.2.x) for the next eighteen months — not needing to upgrade to 2.3 in September 2007, to 2.5 in March 2008, or to 2.6 in July 2008. When WordPress 2.7 was released in December 2008, the 2.2.x legacy branch could have been deprecated and 2.6.x could have then become the supported legacy branch: the site owner would only then need to upgrade to 2.6.5.

Under my suggested system, someone building a new WordPress site would have the choice between installing the most recent branch (e.g., 2.8.4) or the legacy branch (e.g., 2.6.x). The most recent branch would have all the latest features, but it would also need to be upgraded every three or four months. The legacy branch would not have all these new features, but it would need only security fixes applied until it was deprecated: it would not need to be upgraded to the next supported legacy branch (e.g., 3.0.x) until the version after it (e.g., 3.1) was released.

Objections

Many patrons here at the tavern no doubt remember that WordPress used to support the legacy branch 2.0.x. The branch was supported for almost four years, but the WordPress team abandoned it in back in July. I have talked with WordPress team members about this in the past, at WordCamps and over email, and I have received the following objections to such a system:

1. It’s too much work to maintain.

There is no way for me to deny it: it’s definitely more work to support a legacy branch than not to support one. But it is a known quantity of work. How much work does it take to recover from the negative press generated from large attacks? If a supported legacy branch increases the number of users who keep their WordPress installations secure, the project team could spend less time responding to the latest round of “WordPress is Insecure!” blog posts and more time working on the software.

2. There’s no demand for one.

I certainly believe that there was no demand for the 2.0.x legacy branch. WordPress then had a fairly limited set of features compared to WordPress today. Since the web is constantly evolving, I wouldn’t expect there to be a demand for software three or four years old. But WordPress today is a very mature product, and the current version will be more than adequate for many web site owners for another eighteen months. In fact, WordPress 2.6 was a very good product: many users would have preferred to stay on a secure WordPress 2.6.x instead of upgrading so quickly to a completely new interface.

As the WordPress community grows, many users are not as technically savvy or as anxious to get upgraded features every few months as in the earlier days of the project. They simply want their sites to work, and they rightly fear that an upgrade may break custom themes or plugins. A supported legacy branch would not let them completely off the hook — they would still eventually need to upgrade — but it would greatly ease the burden of maintaining a WordPress web site.

I build business web sites for clients in WordPress. If the WordPress team adopted a system like the one I am suggesting, I would build new web sites on the most recent branch. I would then upgrade my clients every few months until they reached what would become a supported legacy branch. After that, I would be able to upgrade them every eighteen months. I think many WordPress users would be thrilled to have something like this upgrade plan available to them: it would be great if it could be available starting with WordPress 3.0.x.

3. It’s too confusing for users.

This is a legitimate concern, but I have no doubt that a system like this could be adequately explained — and I’m more than willing to help the project team in designing this user experience. Here are my initials thoughts about what could be done:

  1. Two buttons would be needed on the “Download” page, with descriptive text beneath them something like the following:

    [Download WordPress 3.2]
    Contains the newest features but requires more frequent upgrades:
    security patches only available until 3.3 release

    [Download WordPress 3.0.x]
    Legacy branch: security patches available until 3.5 release

  2. The upgrade notifications in the administrative interface could be modified for users on a supported legacy branch. They might see something like this:

    [Red] WordPress 3.0.3 fixes a security issue found in this version of WordPress. Update Now

    … or this:

    [Yellow] WordPress 3.1 adds new features to this version of WordPress. Learn More | Update Now

    … or this:

    [Red] This version of WordPress is no longer supported. You must update to WordPress 3.4.2 to remain secure. Update Now

Discuss

This is a tavern, and I have already monopolized the conversation for far too long. I want to hear from the other patrons: What do you think? Would you be interested in a legacy branch for your own sites? For your clients’ sites? How many users do you think would use such legacy branches? Would existing users feel less upgrade fatigue? Would more people be comfortable staying on or switching to WordPress? Could this help WordPress overcome the recent negative press about security?

Posted in | Tagged , , , , | 12 Responses

WordPress Dev Chat For 9-17-09

WordPress Dev Chat For 9-17-09

By Jeffro on September 18, 2009

wordpresslogoThis weeks meeting covered basic image editing which is being worked on by Andrew Ozz, Gallery improvements, embeds, and the possibility of a new supported legacy branch of WordPress. The chat heavily focused on the topic of handling gallery improvements along with the use of photo albums. This is a topic that has been discussed in great length in previous meetings.

WordPress IRC Channel Ops – Back in March of this year, a poll was conducted for individuals to vote on who should be added as channel operators for WordPress on IRC. Sometimes in IRC, it turns into the wild west and it becomes frustrating very quickly when there is a troll or spammer which can’t be dealt with thanks to the lack of operator presence. Hopefully, that will no longer be the case as Matt has added Vipder007bond and Sivel to the ops list.

Basic image editing –
azaozz - sure, image editor has been in for few days, no much comments on it for now..
azaozz - at the moment it keeps all old files, so when editing an image many times, files accumulate
azaozz – perhaps needs a way to check which (old) sizes have been used in posts and delete the rest
junsuijin - post meta?
azaozz - may need to separate the attachments meta into 3 fields, old meta, sizes and exif
azaozz - any questions/wishes/complains about it?
sivel - azaozz: honestly haven’t had time to look at the code or play with it
azaozz - ok, if there are any, add them to the ticket :)

I have no idea what the ticket number is. A search in trac for image editor or image editing didn’t provide me with any clear answers.

MarkJaquith – Galleries — this has been disappointing to me. We need to make some decisions. I feel like we’ve thrown a bunch of ideas around but we need to stop waffling.

This topic took up the bulk of time for the meeting. It looks unlikely that the code created through the GSoC project for Media in general will not be used. The general line of thought is to create an album taxonomy which would not be limited to the traditional ‘album’ displays. Considering the magnitude of this project, images will be the primary focus as first with other media types to follow. Last but not least, this project has a high possibility of being one of the first canonical plugins for core which just means one plugin but many contributors.

jeffr0 – Directed at Mark. Has their been any talk of a new supported legacy branch?

Considering the security stuff earlier this month, some folks have been suggesting that WordPress bring back a supported legacy branch of WordPress. I decided to ask if any talk of this has been ongoing in the inner dev circle and Mark replied that he wasn’t aware of any. In fact, Mark stated he would be extremely opposed to an LTS (Long Term Service) branch. Sivel doesn’t think it is something that they are ready to undertake.

MarkJaquith – I’d rather direct resources to making upgrades smoother and showcasing well-coded plugins that won’t break on upgrade.
westi - The only way a LTS branch is going to exist is if the person that wants it creates it. our resources are better directed elsewhere

Embeds – Viper007Bond has been cranking away on something called embeds which would make embedding video content easier. (Trac Ticket 10337) The talk was a bit too technical for me to understand but Mark Jaquith along with some others believe that the code will need an independent security review. If you want to read more about easier embeds, point your browser to here and scroll up.

How To Participate:

If you want to suggest a topic to be discussed at the next meeting, you can by visiting the WordPress development updates blog. If you would like to participate in the chat next week, install IRC or an IRC compatible client and connect to the following IRC server.

chat.freenode.net or any random server on the Freenode network and then join this channel at 5PM Eastern time or 9PM UTC Thursdays. The meeting day was changed to accommodate European users.#wordpress-dev.

Posted in | Tagged , , , , , | 3 Responses

CodePoet.com – New Home For WordPress Consultants

CodePoet.com – New Home For WordPress Consultants

By Jeffro on September 16, 2009

codepoetlogoIt used to be that if you needed to find a WordPress consultant, you would need to visit the consultants page hosted on Automattic.com. Today, that is no longer necessary. Instead, all of that information and more can be found on CodePoet.com which is running on P2. Thanks to an email I received from a tipster, here is what the site is going to be used for:

Over time we plan on adding new features like consultant profiles, better search, promo badges, etc to help direct the ever increasing demand for WP consulting services. For search, we’re considering ranking results by contributions made to WordPress.org (i.e. the more plugins/themes/core & forum credits a firm has to their name, the higher they rank).

Not too long ago, I reported on the fact that WordPress.org sitewide profiles were in public use. If you’ve created your sitewide profile, you’ll know that there is an option that enables you to have your account show up in the consultants list. Between that option, CodePoet, consultant profiles and such, things are starting to look as if they are coming together, one puzzle piece at a time.

Posted in | Tagged , , , | 10 Responses

Who’s Responsible For Keeping Your WordPress Site Up To Date?

Who’s Responsible For Keeping Your WordPress Site Up To Date?

By Jeffro on September 15, 2009

So who do you think is responsible for keeping WordPress updated? The New World Order? Matt Mullenweg? You tell me by voting in the poll. I am hoping that 100% of the votes will be for a particular answer but judging by the usual voting crowd, I have a feeling some of the voters will opt for one of the other choices.

Who’s Responsible For Keeping Your WordPress Site Up To Date?

  • The End User (68%, 50 Votes)
  • The New World Order (12%, 9 Votes)
  • Matt Mullenweg (9%, 7 Votes)
  • WordPress (8%, 6 Votes)
  • Automattic (3%, 2 Votes)

Total Voters: 74

Loading ... Loading ...

Posted in | Tagged , , , | 24 Responses

Page 24 of 36« First...510...232425...3035...Last »