Web Development

December 13, 2009

Web Services Content Management System

Filed under: Content Management — Tags: , — Tim @ 6:04 pm

Laubacher Multimedia’s Content Management System is in it’s third year of production and is gaining popularity. The system is incredibly easy to implement for designers and very flexible for developers.

Take our basic Web Page Content Management. Users edit parts of their web pages using an HTML editor. They can create versions and publish when they are ready. To implement it the designer or developer spends about 5 minutes setting up the page in the back end. Then the system provides copy/paste code for inserting the system into their page.

The nice thing is that, because it’s a service-based system, the client side can be PHP, Cold Fusion, ASP, or .NET. It doesn’t matter. Just copy and paste the code of your choice. Here is an example of a .NET implementation.

Place this code somewhere on the page. This sets up the connection to the XML source.

<asp:XmlDataSource runat='server' EnableCaching='False' id='PageContent1' DataFile='' XPath='responseXML'></asp:XmlDataSource>

Code for Title and META tags (inside of head)

<asp:Repeater runat='server' id='DataList1' DataSourceID='PageContent1'>
<meta name='keywords' content='<%#XPath("page/keywords")%>' />
<meta name='description' content='<%#XPath("page/description")%>' />
<meta name='Author' content='<%#XPath("page/author")%>' />

Code for Content – How do I get to Content Management? – Put this whereever you want the content to appear on your page.

<asp:DataList runat='server' id='DataList2' DataSourceID='PageContent1'>

This is just one example of an implementation for just one of our modules. We have a calendar system, a membership management system, email marketing, blog, FAQ manager, photo gallery manager, and much more.

Call us for a free demo and walkthrough.

December 1, 2009

Redirecting non www to www for SEO and Certificates

Filed under: SEO, Technical, Webserver — Rob @ 4:58 pm

You might have noticed, in most cases the “www” is not a necessary part of a url anymore.  It used to be, but that all changed some time ago. This created a bit of a problem for website admins when it comes to SEO.

Take this scenario – Bob has a site called “cans.com”   and you can view it both at http://cans.com     and at    http://www.cans.com

Google goes out to index the site and ends up indexing it basically as two pages, some links are here – some are there.

For SEO purposes you could see why this is less than ideal – your site will suffer in page rank and placement as it is essentially being looked at as two separate sites.

Take this scenario as well, Bob’s site “cans.com” sells cans (I know, crazy huh?) and Bob went out and got himself an SSL certificate to make that secure. He went and bought a cert for  http://www.cans.com

Still with me? Good.  Now a potential customer goes to Google to search for cans – ends up finding http://cans.com – clicks the link to the site – and tries to make a purchase.

Except the link he followed is http://cans.com and the SSL certificate was issued to http://www.cans.com……   so the user gets a HUGE security warning that the certificate was not issued to this site and leaves.


(would YOU continue?)

Multiply that by all  the potential customers that come by in a typical month and you’re losing some serious business.

So, follow the instructions below for either IIS or Apache and in 30 seconds problem avoided.


Create your website (http://www.cans.com) – verify it works, upload content, install cert if you need one.

Create another website from scratch – set it’s host header to cans.com

  1. In the Home Directory tab, change the option button “When connecting to this resource the content should come from” to “A redirection to a URL”.
  2. Specify the URL as http://www.cans.com
  3. Check the checkbox that says “A permanent redirection for this resource.”



For those of you using Apache the steps are somewhat easier, you need to edit your root htaccess file (or create one if you don’t have one) and your server needs to have mod_rewrite installed (most do)

Options +FollowSymlinks
RewriteEngine on
rewritecond %{http_host} ^domain.com [nc]
rewriterule ^(.*)$ http://www.domain.com/$1 [r=301,nc]

** Authors note, there’s no reason you HAVE to go with the “www” as your main site – redirecting to a non www address is perfectly acceptable – I just picked the www as the standard as that’s what most of the big guys are doing still.