In times of war, you may be asked what you can do for your country. In modern times, your country may be asking you to do your part by updating your WordPress plugins.
The United States' Federal Bureau of Investigation (FBI), through the Internet Crime Complaint Center (IC3), issued a public service announcement last week recommending website administrators to update their Wordpress sites. More specifically, the bureau wants you to update your third-party WordPress plugins.
This is the third year for the Now What? Conference which is held in one of the fastest growing modern communities in the region, Sioux Falls, SD. If you're within a half day's drive from this great city, I encourage you to register for the conference. The conference and various workshops will be held on April 29 - 30, 2015. Created by Blend Interactive, the conference will be bringing together web and marketing professionals from across North America. Something that rarely happens in our region, you have an opportunity to hear from today’s content management leaders as they come together and cover post-launch web maintenance, web analytics, content strategy, and talk shop with colleagues and speakers.
Over the years, I've talked about building a range of simple websites for personal use to implementing very complicated proprietary and open source enterprise content management systems. What I haven't talked about is the cost of building and maintaining those websites. Honestly, I've been too embarrassed for how little I spend and too stunned by the price tag for what the big companies pay for their websites. Who Is Hosting This? sent us a graphicthat we thought represented the typical costs small to medium size businesses can expect when building and hosting their new websites. So good was the infographic that we decided to post it here.
Much of the statistics came from Which Web Design Company. WWDC maintains a database of over 7000 web design agencies world-wide, and provided them with the average starting cost statistics for web development used in the graphic below. Whatever your costs and whatever you decide, assuming you're working with reputable companies, the bottom line is that you get what you pay for. That's not a threat, but just a reality of the market.
For the first time in 15 years, my family doesn't have a website to call their own. In January 2000, I registered the domain Bryansplace.com. This was the first website I ever built outside of work and it became a sandbox for me to express my interests as well as a way to seek personal growth. From handwritten HTML pages into Frontpage to a number of CMSs, the software and content at Bryansplace evolved as my life evolved.
Bryansplace.com was the website where my girlfriend and I announced our marriage to the world. As a married couple, we eventually publicly announced the birth of our son via the site. This domain was the site where I talked about camping, computers, and my latest beer recipes. It wasn't all about me either. My wife showcased her photography for the first time online via our family website. This was also the website my son learned how to navigate the Drupal content management system and talk about his gaming skills. Bryansplace.com was synonymous with "family news". Despite how much I valued the domain, last week I unceremoniously killed the website.
Last month, CMS Report celebrated eight years of providing stories to readers focused on content management systems. Over the years, I've told you how grateful and even surprised I am of the success CMS Report has seen. All true, but for fear of sounding ungrateful I've never acknowledged the negatives of blogging over such an extended period of time. Today, I'm acknowledging the costs and the need to take a break from my routine of waking up before sunrise and going to bed late to maintain this site. Starting today, I'm taking a three month sabbatical away from blogging here at CMS Report.
CMS Report will still be publishing articles from our contributors during my sabbatical, but you likely won't be seeing any articles written by me. I still plan on continuing working as editor but my office hours for the site will be reduced. I'm doing all this simply because I have responsibilities to the "day job" and myself that are begging for higher priority. In the draft for this article, I originally provided three reasons that I'm doing this sabbatical but deleted them from the published article. My reasons for taking such a break are not important but only the outcome. The end result is CMS Report will be fine without me and will likely be a better website as a result of my sabbatical.
This data is powerful. Even with the “unknown” visitors, I can start to aggregate information and see if patterns based on the content they engage with develops. If they do, I can start creating specific content for southern California visitors and deliver better experiences. Portals and web are one—it’s time to start treating every visitor as an individual.
This week, CMS Report celebrates our eight year anniversary. No one is more surprised than me. Now here we sit with thousands of articles posted by over 350 different contributing authors. I spent some time this week looking back at the most popular articles we posted here on CMS Report. Besides just a list providing the "reader's choice", I also provide my own list of favorite articles that has been posted here on CMSReport.com. When comparing the two lists, you will find the only article on both lists is the one comparing Drupal and Joomla. In 2006, it was one of the first articles that I had written which suggested CMSReport.com might stick around a little longer than I had expected.
Open-source PHP framework ImpressPages recently released a preview of its upcoming 4.0 version. Users can get their hands on the new website management tool with built-in content editor and get a hint of what’s really coming up. Let’s see what’s so new about it.
Well, this certainly wasn't on my radar. Gábor Hojtsy, Drupal 6 lead maintainer, announced that starting March 1, 2014 support for PHP 4 in Drupal 6 will end. I wasn't surprise to hear about Drupal developers dropping support for PHP 4. Instead, I was in shock to hear that Drupal didn't drop support for this ancient version of PHP sooner.
To put this announcement in perspective, the PHP project developers said their goodbyes to PHP 4 back in 2008 and I personally said my "see ya later" back in 2007. Needless to say, I don't think anyone with merit can complain Drupal is dropping PHP 4 support.
As with all WordPress updates, WordPress 3.8 adds some nice features for both users and administrators. There are also lots of bug fixes in this new version which over 188 open source contributors pitched in to fix. The following are the most significant features we found in WordPress 3.8.