System Administration

According to the recent research, 64% of dissatisfied online shoppers said they were less likely to visit a slow retailer again, 62% were less likely to purchase from the site again and 48% would purchase from a competitor.

Such statistics always makes developers puzzle – from one hand, the website owner wants the application to be multifunctional and universal, from the other – it shouldn’t be slow. And the problem is always to make a solid extension work as fast as possible.

Performance optimization is a good way out in such situation. Optimizing a website, you should consider providing two factors:

Organizations deal with a lot of confidential information every day, information that is typically managed using business applications, like SharePoint. That means that properly implemented and managed security is critical to these applications.

With SharePoint, you can implement effective security, but managing it with the tools you get out of the box isn’t the easiest. Here we look at the challenges you will face managing security and permissions within SharePoint and discuss why you should make it a key element of your Information Architecture plan.

As expected, this week the Drupal development team released Drupal 7.3 and Drupal 7.4. 

Drupal 7.3, a maintenance release which fixes security vulnerabilities is now available for download.

Drupal 7.4 also fixes other issues reported through the bug tracking system.

Upgrading your existing Drupal 7 sites is strongly recommended. There are no new features in these releases. For more information about the Drupal 7.x release series, consult the Drupal 7.0 release announcement.

Andrew Lynch posted a fantastic list of 32 Web Frameworks over at memeburn.com. He starts off that list with Ruby on Rails, Django, Drupal, CakePHP...well you get the idea.

Frameworks are built on top of programming languages and provide methods of streamlining some of the more mundane and common tasks associated with web development. In essence, they allow developers to achieve more with less coding, saving both time and money. They provide a range of simple methods that help you connect to a database, authenticate users and build an admin backend, all with a few lines of code.

Be sure to read the complete story so you can see Andrew's review of 32 web frameworks that you have to choose from for your next project.

Lots of changes are starting to take place here at CMS Report. We're now running on a new version of the Drupal content management system!

Over the weekend, I decided to pull the trigger and upgrade CMSReport.com from Drupal 6 to Drupal 7. It's hard for me to believe that it has been almost half a year since Drupal 7 was released. This was a frustrating upgrade for me as I've traditionally upgraded CMS Report shortly after any new release of Drupal is out. In fact, I have sometimes upgraded a site before the release is official. As a content management system, my five-year hate-love relationship with Drupal is still going on strong.

Despite the usual learning curve associated with a major Drupal upgrade, I ran into two additional problems I've never had to face with this site. First, the CMSReport.com of today is a much more complex site to run, maintain, and upgrade then it was in 2008. With the number of readers and sponsors this site now sees, I just don't have the luxury of blowing up the site and say "oh well" lets start again. Secondly, the selection of premium or contributed themes available for Drupal 7 just plain sucks (there, I said it). I must have spent half of my upgrade time just searching for and then tweaking a Drupal 7 theme. People often complain about the lag time between a Drupal release and the availability of third-party modules. In my opinion, it is the lack of theme development going on with Drupal that is the real problem with Drupal upgrades.

It was five years ago that I posted in programmer tradition at CMS Report, "hello world". At the time, I expected CMSReport.com to be around for only a couple years which was more than enough time for it to fulfill my purpose. At the time, I had an academic interest in information systems and found that Web-based content management systems were a nice way to put theoretical ideas into practical know-how. This site focused on content management systems in hopes of meeting the few other people out there that shared my interests in CMS.

In that first post, I actually wrote more than "hello world". The full title of the article was "Hello World, New Version". The phrase "new version" was in reference to CMSReport.com not being the first site I created to focus on the CMS.  A couple years earlier, I had tried to start up a website called WebCMS Forum. The online forum was intended to be a "place for those with a passion for web-based applications such as portals, blogs, and forums". I spent a lot of time and money on that site, but in the end few visitors joined in as members to talk about content management systems with me. If Twitter had existed back then I would have easily tweeted "WebCMS Forum RIP #failed".

Looking back at it now, I'm convinced CMS Report is a success because of my experience from failing so miserably with WebCMS Forum. Previously, I had tried to build a site for others to express their passion and obsession for their favorite content management systems. Here at CMSReport.com, I took the opposite approach and built the site for the sole purpose to talk about my passion for content management systems. It was a crazy idea to put my opinions at the center of CMS discussions as even now I do not consider myself an expert in content management systems. It was only by circumstance that I later realized people are attracted to other passionate people that ask questions and are willing to go at great lengths to find the answers. If you're looking for the facts you go to Wikipedia but if you're also looking for great discussion from people asking the same questions as you are; it is the blogs you seek.

You have just completed all the website development work and are ready to take it online. You started to search for a hosting plan that will suit your website and budget. You know the system requirements for Bitrix websites are: Apache 2, MySQL 5, PHP 5 etc. And you see that there a lot hosting plan that meet these requirements. But is it enough to check the system requirements only?

The real answer is – “no”.

Here are several things you should care about:

Main system requirements

Sure, your hosting tariff should meet all the system requirements.

This means that Apache, PHP and MySQL should be installed on the server in appropriate versions.

Sometimes the PHP version can be changed directly in server settings. You need to use either the hosting control panel or edit the .htaccess file. This can be tricky but you can always check it and fix it before the installation.

Specific server settings

• Be sure that you have safe_mode turned off.
• Safe mode may interfere with file and image uploads.
• You need to check the open_basedir settings in your php.ini file and disable it.
  

Slowly but surely, CMSReport.com has turned into a nice side business for me. The problem is that this site has grown to a point that it demands more of my time than I can currently offer it. The future of CMS Report is now sitting at crossroad. I plan to be spending the next few months deciding where this site should go from here.

Some of the options I am considering for this site include:

Like most website administrators, I have a long history of fighting spammers and protecting my sites from unwanted content. Over the years I've used a lot of tools and services to block spam from reaching the pages of my sites. In recent years, the service I've relied on most heavily is Mollom.  Mollom is a web service that helps you identify content quality and, more importantly, helps you stop spam on your blog, social network or community website

Overall I've been very happy with the spam filterering Mollom provides for my sites. However, occasionally Mollom can be too aggressive and remove legitimate story and comment submissions. And when I say "remove" I most definately intend to use the word in the literal way. You see, up to now, Mollom had an "all or none" approach to rejecting or accepting spam. When your stories or comments were rejected, the content submission was simply discarded without review by a human.

If you've ever submitted good clean content to CMSReport.com or another site only to only have it identified and discarded as spam, you have every right to be upset with spam filters. Over the past couple months, I've had a number of people upset that the spam filtering CMS Report has been using rejected their story submission. This may not be all the fault of Mollom either as I was also using the Bad Behavior module too. My apologies to everyone that has gone through this experience when they've submitted legitimate comments and stories to this site. Unfortunately, without spam filtering the content on this site would not be good to view. Spam filtering is a necessary part of maintaining a site open to the public.

Luckily, there has been some improvements in the Mollom for Drupal module that should keep your posts and comments from getting discarded while continuing to protect this site from spam. The module has now been improved to to retain spam comments as unpublished posts in a site's moderation queue. So we're giving the new module a try. I won't promise that your content will not be identified as spam, but I do promise you that every intent is being made to review your comments and stories for publication.

Jay Gilmore wrote to us the other day. Jay wanted to make sure we were aware that MODx 2.0.2 was released last Friday. Lots of bug fixes and improvements in this one that you might just notice a performance improvement. You can check out Jay's announcement below or at the MODx site.

MODx Revolution 2.0.2 Brings a Little More Speed and Lots of Little Fixes