The Saga Continues…
WordPressWordPress was borne of initial idea seeding via B2 (Cafelog) in 2001, which was launched by Michael Valdrighi. In 2003, cofounders Matt Mullenweg and Mike Little forked B2 and created WordPress, an Open Source blogging and now content management system estimated to power the largest number of websites of any individual product (20%). Through the largest thriving community of any website management system, WordPress has grown to include theme designers, plugin developers, webmasters and site developers. With the power of participants, WP now can power anything from small individual blogs to large multi-user social communities to business websites. Core contributing developers include Ryan Boren, Mark Jaquith, Matt Mullenweg, Andrew Ozz, Peter Westwood and Andrew Nacin. WordPress has just recently celebrated its 10 year anniversary.
WPCommunityWPCommunity.com was started as an extension of Web Developer Tom Ford who found WordPress in the early days looking for a solution to power a group of large websites that had outgrown their flat HTML infrastructure. Needing more features, WordPress was chosen based on another user who was kind enough to put together a comparison chart of several platforms, with detailed information. The way this individual was able to present this side by side comparison using WordPress ultimately led to giving it a shot...which led to massive experimentation to the different things it could do. The heavy and growing demand for assistance led to offering such, bringing us to today. Tom Ford has contributed to various other development agencies including TC Websites, WPMU.org and WPML. (as well as solving countless technical issues and working through many full website builds).
WordPress 3.9 “Smith” Available!
- RECENT WORDPRESS NEWS ON THE WEB
Post editor not have option to choose more color in color picker.
Media uploder header not show properly in mobile and tablet view.
Dominik, Overtaken by events, when I updated the nightly build this morning, I was surprised to find WordPress 4.0-alpha runn
- APR 16, 2014
WORDPRESS.TV: INTRODUCING WORDPRESS 3.9 “SMITH”
APR 16, 2014
WPTAVERN: HOW TO SET UP 1 OR 2 COLUMNS FOR WORDPRESS DASHBOARD WIDGETS
One of the improvements in WordPress 3.8 was the responsive dashboard. Thanks to this improvement, the option to select the number of columns to display dashboard widgets was removed. The dashboard now shows the appropriate number of columns using the available screen real estate. Unfortunately, for those using wide-screen monitors, this usually means 4-5 skinny columns. In the screenshot below, you can see that even if a column doesn’t have a widget assigned to it, the column remains in place.
The issue was brought up by Chris Jenkins shortly after the release of WordPress 3.8. WordPress core developer Mark Jaquith agreed that “dashboard widgets should be able to specify a min-width, such that they span multiple columns if WordPress tries to make them smaller than that.” Jaquith created a ticket suggesting a fix but so far, a patch has not been created.
Since the ticket was created, Jenkins has developed and released a plugin called Two Column Admin. When activated, the plugin restores the ability to select 1 or 2 columns to the screen options tab. The downside to using this plugin is that selecting two columns will disable the responsiveness of the dashboard widgets. Instead of merging into one column when the screen size gets smaller, the two columns will crash into each other.
Matt Beck responded to the ticket with a good suggestion in lieu of the column option returning:
Best case scenario would be for the number/width of columns to adjust to the number of active dashboard widgets instead of displaying the empty drag/drop areas. In lieu of that, some mechanism to specify either column-count of a widget intended to be wide and/or better yet – maximum number of columns to display on the dashboard would be great.
After being stuck with four columns since the release of 3.8, I’ve forgotten how nice it is to have wide dashboard widgets. I’m hopeful that in the future, the ability to specify the number of columns in the dashboard returns as I prefer three, not four columns.
How many of you would like to be able to specify a specific amount of columns versus the current implementation?