Tuesday, February 23rd, 2010
We are constantly trying to find easier and better ways to create manageable blocks of content for clients.
Widgets
Widgets are only helpful up to a certain point since there isn’t a great plugin for a WYSIWYG visual editor that I’m aware of. The Rich Text Widget and WYSIWYG Text Widget are buggy and aren’t compatible with 2.9.2. Rich Widget is ok but requires too many clicks and is not so user friendly.
Custom Fields
Custom fields are only helpful up to a certain point – since once again there is no visual editor. Coding in your own add_meta_box to the functions.php to add customized, user-friendly custom fields takes a fair amount of time and quite a bit of PHP know-how. Also, explaining to clients the concept of custom fields is not a super joy.
So, what is the solution for expanding WordPress CMS functionality?
Content Blocks
I investigated a few CMS content block plugins, and here’s what I have to say:
1. Page.ly MultiEdit Excited to try out a new plugin that would help with editable content, I installed the MultiEdit plugin with instructions here. MultEdit lets you flip between tabs to edit multiple areas of content! So exciting, but no matter what I did, I couldn’t get the content in each tab to save properly. It only saved the content in the last tab called “Right”. Sigh.
2. Multiple Content Blocks This plugin is insanely easy to use. All you have to do is add one snippet of code <?php the_block (‘newarea’); ?> to a page template and voila! you have another WYSIWYG text editor in the admin area. Whatever you enter into this new content area will show up on the page where the snippet is. Amazing. BUT, I couldn’t figure out how to use this code in the sidebar since the sidebar isn’t a page. Sad.
3. Page blocks I followed the instructions for how to use the plugin like a good girl, but I still couldn’t get it to work the way I wanted with additional editors in the editing page area. 
4. Custom field template Bring out the champagne peoples! We have a winner! This plugin is the daddy of all custom field plugins. It lets you add whatever customization you want to the custom field and then add code into your template as if it were a regular custom field.
Here’s how to use it.
- Install and activate the plugin. Obviously.
- Go to the new tab in the admin area called Custom Field Template.
- Modify the example they have. Here’s the one that I created:[ContentAreaName]
type = textarea
rows = 4
cols = 40
tinyMCE = true
htmlEditor = true
mediaButton = true
This means that the custom field I created has a WYSIWYG TinyMCE text editor, an HTML view, and a media button so that the client can upload an image. There are tons more options explained in the settings page.
- Add this code to wherever you want in your template files:
<?php if(get_post_meta($post->ID, “ContentAreaName”, true)) { ?>
<?php echo get_post_meta($post->ID, “ContentAreaName”, $single = true); ?>
<?php } ?>
or if you want to add it as a shortcode, use [ContentAreaName]
That’s all for now. If you have another content block CMS tip, please share!
![[Slashdot]](http://slashdot.org/favicon.ico)
![[Digg]](http://digg.com/favicon.ico)
![[Reddit]](http://reddit.com/favicon.ico)
![[del.icio.us]](http://images.del.icio.us/static/img/delicious.small.gif)
![[Facebook]](http://www.facebook.com/favicon.ico)
![[Technorati]](http://technorati.com/favicon.ico)
![[Google]](http://www.google.com/favicon.ico)
![[StumbleUpon]](http://www.stumbleupon.com/favicon.ico)
Posted in WordPress as CMS | Tags: CMS, content blocks, custom fields, wordpress | 5 Comments »
Friday, February 22nd, 2008
Today, WordPress Garage turns one year old. Hasn’t our little baby grown up fast? Blow out the candles…
It is exactly one year ago today that I wrote my first post here. It was about Jerome’s Keywords Plugin, which was a popular plugin for creating tags in WordPress before they became a built-in feature.
The reason I started this blog is because at that time, I was building web sites for clients, but felt that I could not justify creating static sites anymore. I was searching desperately for a solution that would enable me to create sites with a content management system that wouldn’t break the bank, and that I could manipulate and customize without being a programming wizard.
I looked into many open source options, and found that WordPress was easiest to use from the designer/developer’s point-of-view, and from the user’s point-of-view. So my company started building sites on WordPress. As we built, we learned a lot and I felt like we really need a good way to organize the information we were gathering about good plugins and how to use them, themes, and code hacks.
And thus WordPress Garage was born. Between WordPress’ categories, tags, and the search function, I figured we’d always be able to locate the information we need within minutes.
Apparently, others also were looking for this information, and readership grew as well, which is good because it’s a lot more fun to write when you know people are listening.
Birthday presents
In honor of WordPress Garage’s birthday, I have two new presents:
- A WordPress Garage facebook page! If you like this blog, please come on over to this page and become a fan. I’d really like to get to know my readers a bit more.
- The WordPress Garage YahooGroup – I’m on the WordPress Pro mailing list, which is about the most dry and boring list on earth. I suggested that the list become more active, and while people said it wasn’t appropriate for that list, they liked the idea. So, this email list’s goal is to be a place where people can help other people with their WordPress issues. Looking for that perfect plugin? Can’t figure out why your blog is breaking? Join the list and ask!
Statistics and summary
It’s fun to compare my first month on WPG to this last month. Site visits have gone up 1,424%, and pageviews have gone up 841%. Now I get almost 8000 visitors a month according to Google Analytics, and over 14,000 page views. Most of my visitors come from Google Search, with the rest coming from StumbleUpon and other sites. My top referring sites in order of traffic are:
Most popular posts
The most popular posts on WPG at the moment are:
Best WP Garage tips
These posts aren’t necessarily the most visited, but the tips in them are pretty useful:
Most controversial posts
A little bit of controversy adds color to an otherwise boring monologue about loops and plugins. I don’t like to create conflict, but getting people to participate in an active discussion is just fun.
Consumer evangelists vs. lawyers: using “WordPress” in domain names – this is the post where Matt Mullenwegg commented three times. In this post, I argued that WordPress shouldn’t shun blogs (like mine) that use the word WordPress in their domain name, and should rather embrace these consumer “evangelists” who love the product so much that they volunteer their own time to talk or blog about it. After I wrote this post I finished Meatball Sundae by Seth Godin, and he also talks about this idea.
Anyways, Matt and Lorelle didn’t like my opinion, and accused me, or those like me, of “blatant[ly] disregard[ing]…a core tenet of our community,” of being like a scraper, and of legal violations. In the end Matt kind of softened up and he said he’s “thrilled about [me] or anyone who blogs about WordPress.” He said if I want clarification about their policies I should feel free to email or call him. So, mustering up some good ol’ Israeli chutzpah, I called him and left him a message. Despite his generosity, I think this blog is still shunned by the WordPress powers-that-be. Oh well.
Would we use WordPress if there were no plugins? – I just threw out this question to make us think about how valuable WordPress would be on its own. I think it’s value lies in the fact that it supports plugins.
ZDNet says WordPress not clunky, but also not CMS – I referred to an article by ZDNet about whether WordPress is a CMS and sparked a lively discussion.
WordPressGarage is being scraped! I want to stop them…now! – I realized that one particular site was scraping all of my content and republishing it. I threw the issue out to my readers, and got some interesting responses in the comments.
Is WordPress’ security vulnerable at its core? – WordPress is being upgraded all the time because of security issues. Plugins also have constant security vulnerabilities. Is this standard, or is there a problem with WordPress? BlogSecurity.net said there’s a problem with WordPress. Read the post to find out more.
Milestones
- Someone told me that I’m one of the coolest people in the WordPress community! Can you believe it? (No, it wasn’t my mother.) While in the real world I am far from being considered cool (mother with lots of kids who works hard to pay the bills with little time for play), I guess that in the WP community my geekiness is…cool…or something.
- WordPressGarage listed as one of Top 40 Blogs About WordPress!
- I’m sure there was something else I got excited about over this past year, but I can’t remember.
So happy birthday WordPress Garage, and may we enjoy another fun year of WordPress blogging together!
Posted in News & Views | Tags: backup, blogging, CMS, security | 16 Comments »
Monday, January 14th, 2008
Recently I posted about why I think WordPress is a CMS. This led to a pretty interesting discussion in the comments on the topic, but it was unresolved.
Here’s some more fuel for the fire: I just came across Josh Byers’ blog, thanks to his amazing Custom Admin Branding Plugin. He has a post there that lists the plugins he uses to transform WordPress into a full-fledged content management system (CMS). Aside from the fact that it’s good to know about the plugins he mentions, it’s interesting to note that by adding a few plugins, Josh feels that his WordPress sites can be considered CMSs, as opposed to just blogs.
Here are some of the plugins that he says he uses to make WordPress into a CMS. Visit his blog to see the rest of them, and read his concise descriptions of each one, and why he uses them:
Here are a few more tweaks and plugins that I think help make WordPress into a great CMS:
- The WordPress static home page option – obviously. The fact that the home page of your blog can be a static Page by selecting a single option in the admin changes WordPress from a blog into a CMS. I don’t know why people always ignore this.
- Page Links To Plugin: gives more flexibility to WordPress Pages by allowing you to link them to other pages, like category pages.
- Role Manager Plugin: better and more precise role management in WordPress
- Future Posts Calendar Plugin: this plugin is a savior. It gives me an overview of the days when posts are scheduled to be published, so I can make sure that posts are spread out evenly across the week, instead of all of them ending up on Tuesday (for example).
- Admin Drop-down Menus Plugin: also a life saver (not the candy). Can you imagine getting to the Write Post page with just one click, instead of clicking on Manage, waiting, and then clicking on Post? Will, this plugin turns everything into drop-down menus, so submenus are just one click away.
- All in One SEO pack, Google Sitemaps Generator Plugin and Meta Robots WordPress plugin: just upload and activate these WordPress plugins, and you’ll have a serious SEO advantage over so many other sites.
I think that the whole argument over whether WordPress is a CMS boils down to the lack of an exact definition of what a CMS is. So, according to my definition of a CMS, which holds no weight whatsoever, WordPress meets the criteria.
Posted in WordPress as CMS | Tags: CMS | 29 Comments »
Friday, December 21st, 2007
Larry Dignan over at ZDNet writes about the media’s relationship with CMS systems, particularly his own past experiences with custom-built CMS systems. He says that “when it comes to ease of use, a blog platform beats or [sic] average CMS hands down.” So he asks why it is that he’s always getting stuck with some clunky, Frankenstein-like CMS system when he could happily and easily use something like WordPress. And he basically asks if people in the media industry will ever figure out that they don’t have to reinvent the wheel, since it already exists.
But what struck me the most about this article was the Update at the end, where he says that he was corrected by Dennis Howlett, who pointed out that WordPress isn’t actually a CMS.
This is something that I really don’t get. WordPress manages content, does it not? Then why isn’t it a CMS? How come I can call the awful, clunky systems that I used before WordPress CMS systems, even though they don’t have even half of the functionality and features of WordPress.
Posted in Themes, WordPress as CMS | Tags: CMS | 19 Comments »
Wednesday, December 5th, 2007
Sorry for the confusing title, but there is an issue that we face over and over when using WordPress as a CMS, and have not been able to solve. When we are using WordPress as a CMS, our Blog page doesn’t pick up the current_page_item class and therefore its link on the nav bar isn’t highlighted like the other pages are. How can we get it to change?
I know that the above might not make sense, so here is a detailed description of the problem:
If you use WordPress as a CMS, you generally create the Pages you want to appear on your nav bar under Write > Write Page. One of those Pages is the Home page, for example, and you create another Page for your blog posts called Blog. Then, you go to Options > Reading, and select one of those pages for your front page from the drop-down list, in this case you would select the Home page, and another page for your blog posts, in this case the Blog page.
You create a style in your style sheet called current_page_item which causes the current page that the viewer is on to appear differently in the nav bar or list of pages. For example, you want the background color of that page on the nav bar to change from green to purple.
Now, here’s where the problem lies: all pages on the nav bar change from green to purple when the user is on that page…except the Blog page! For some reason, that Blog page does not pick up the current_page_item class.
So my question is: does anyone know of a solution to this problem?
Thanks!
Posted in WordPress as CMS | Tags: CMS, navigation, Pages | 18 Comments »
Thursday, June 21st, 2007
Since I discovered the Page Links To plugin, it’s become one of the plugins that I use most on my sites, particularly those where I’m using WordPress to create a CMS. I’ve reviewed it already (see the review here), but it seems that they have added a great features which was lacking in the previous version.
First, let’s just review what this plugin does: it allows you to create a Page, and then have that page link to any URL anywhere on the web. I mostly use it to link Pages in my navigation bar to Categories, or posts, but you could theoretically link a Page to any other page on the web.
It seems that in the new version, Pages links in the navigation are now highlighted when you click on them, even if they are linking using the plugin. This means that if you set a CSS style so that the current page you are on looks different in the navigation, this will apply also when the Page links using this plugin.
I highly recommend checking out this plugin…
Page Links To>>
Posted in Plugins, WordPress as CMS | Tags: CMS, Pages | 7 Comments »
Tuesday, March 13th, 2007
This is something I’m definitely going to use on client sites.
This plugin allows you to add whatever you want to the Dashboard through PHP and HTML and allows you to even add Sidebar Widgets. You may also wipe the entire dashboard or individually remove some of the more irritating sections like the Dev news, Planet Wordpress and the getting started section.
That part about getting rid of the Dev news is great. I’m sure it’s confusing for clients to get to a Dashboard filled with all sorts of stuff that they probably will never read.
Compatible with WP 2.1.
Wordpress Dashboard Editor>>
Posted in Plugins | Tags: admin, CMS | No Comments »
Thursday, February 22nd, 2007
Christian Montoya over at the Montoya Herald says he understands why many web developers use WordPress as a CMS system instead of the many other systems that are not blogging platforms, but CMS systems themselves.
All of these CMS’s have rather complicated administration interfaces, tend to be difficult to theme, and usually don’t put as much emphasis on syndicated publishing as blogging software. It’s really interesting when you think about it; after all, on a typical website you might publish a couple handfuls of static pages, whereas you might have a fresh news posting every week. Doesn’t it make sense for a platform to emphasize news/blog content over static pages? Moreover, if you are going to hand something over to a client, it’s natural to opt for something that non-technical people can use (and do every day). When I tell people “updating this site is just like updating your Livejournal/Xanga,” that’s one of the great things about Wordpress. It’s the combination of the simple admin interface and the focus on blogging (even when the end result is not a blog) that makes Wordpress ideal for most simple sites that I would build for a client.
He does point out that WordPress has its limitations, which makes sense since it’s goal is to be a good blogging platform. But he sums up with a good point:
…content management systems shouldn’t just be about offering more features and functionality for the developer, but being user-friendly for the client too.
I have started to use WordPress as a CMS system because it is relatively easy to theme and customize, and web site owners can easily update their content.
Posted in WordPress as CMS | Tags: CMS | No Comments »
