Despite their strong presence in the local and medical communities, their old site was nowhere to be found on search engines, and the user interface was not only ugly but difficult to navigate.

OACT contacted Soleer looking for a new image and more effective website.  Check it out at oactdocs.com.

We worked with D2Derm to provide an informational site that integrated with their PayPal shopping cart, allowing online shopping for their customer base, and simplifying their sales and fulfillment processes.

We have been working with the parent company of Onion Creek to update and overhaul their websites, as well as provide custom content management capabilities to enable in-house website management and cost savings.

Along with Twin Creeks, River Place, and The Dominion, Onion Creek is the fourth website we have completed in partnership with The Dominion Golf Group.

Features for the Austin Community College website include seperate portals for eight programs and seven campuses with unique news updates, video streams, and other content. We also integrated their existing calendar system and social networks.

While this is definitely not a timeline we recommend, Soleer worked with the Student Life folks at ACC and completed the full project from design and development to content entry and debugging in less than 15 business days.

The new site has led to significantly improved search engine rankings as well as 200% increase in traffic and a reduced bounce rate.

You can view the latest happenings at ACC and Student Life here: http://accstudentlife.info/.

We noticed, however, as we were setting up the module in Drupal, that our beloved media button was gone. Here’s how we got it back in there:

First, you need to install and setup the module & tinyMCE as detailed in the readme file.  Next, open ‘…modules\wysiwyg\editors\tinymce.inc’

All you have to do is add a few lines of code (around line 472):

‘layer’ => array(
‘path’ => $editor['library path'] .’/plugins/layer’,
‘buttons’ => array(’insertlayer’ => t(’Insert layer’), ‘moveforward’ => t(’Move forward’), ‘movebackward’ => t(’Move backward’), ‘absolute’ => t(’Absolute’)),
‘url’ => ‘http://wiki.moxiecode.com/index.php/TinyMCE:Plugins/layer’,
‘internal’ => TRUE,
‘load’ => TRUE,
),

/*Begin Inserted Lines*/

‘media’ => array(
‘path’ => $editor['library path'] .’/plugins/meda’,
‘buttons’ => array(’media’ => t(’Insert Media’)),
‘url’ => ‘http://wiki.moxiecode.com/index.php/TinyMCE:Plugins/media’,
‘internal’ => TRUE,
‘load’ => TRUE,
),

/*End Inserted Lines*/

‘paste’ => array(
‘path’ => $editor['library path'] .’/plugins/paste’,
‘buttons’ => array(’pastetext’ => t(’Paste text’), ‘pasteword’ => t(’Paste from Word’), ’selectall’ => t(’Select all’)),
‘url’ => ‘http://wiki.moxiecode.com/index.php/TinyMCE:Plugins/paste’,
‘internal’ => TRUE,
‘load’ => TRUE,
),

Now the media button will be available to be selected as an option from your TinyMCE administrator page within drupal.

We experienced a problem when attempting to move one of our codeigniter (CI) websites from one server to another.  We performed the transfer of the files, database setup, and necessary config file changes.  Then came time to test, and… Nothing.  FireFox and IE7 both rendered a blank page.

Debugging 

We tracked down the problem, by setting up test points within the php code.  Basically we’d put a ‘print “test” ‘ command in various places, and if it was successfully displayed, then the code was breaking after that point.

Starting with the index.php file, the breaking points were as follows:

<base_path>/index.php (approx. line 117)
require_once BASEPATH.’codeigniter/CodeIgniter’.EXT;

<base_path>/system/codeigniter/CodeIgniter.php (approx. line 80)
$EXT =& load_class(’Hooks’);

<base_path>/system/libraries/Hooks.php (approx. line 43)
log_message(’debug’, “Hooks Class Initialized”);

Okay, so the “log_message” was causing the problem.  After searching the CI user guide, we found the Error Handling page.  At the bottom, it states:

Note: In order for the log file to actually be written, the “logs” folder must be writable. In addition, you must set the “threshold” for logging. You might, for example, only want error messages to be logged, and not the other two types. If you set it to zero logging will be disabled.

So, possibly this was a permissions issue on the logs folder. 

The Solution 

To solve the problem, we navigated to our server, and changed the permissions to 777 (read/write/execute across the board) for the logs folder (<base_path>/system/logs).  

[localhost]$ chmod 777 system/logs

We did this via ssh, but you could also use some other file manager or possibly ftp on some servers. 

…And voila!  Our site threw us a database error. 

We had never been so happy about a database error before!  With the problem isolated, we quickly solved the issue, and got the website rolling.

1. Find the module on Drupal.org
2. Wait for the Module to Upload
3. Unzip the contents
4. Connect to your FTP server
5. Browse to the module directory
6. Wait for the module to upload

Using CVS installation, all you have to do is:

1. Enter one command into your ssh program. (The files are downloaded and installed directly from server to server in lightning-fast fashion)

Even more impressive, is the fact that if you install the module using CVS, you can also upgrade using a very short command in your ssh program.

Now that your excitement is palpable, let’s get into the how.  Here are the prerequisites:

• SSH/Shell access to your server.
• Some sort of SSH client.  (I use putty on windows)
• Hopefully some understanding of unix commands

Now that you have all of the necessary tools, let’s install a module! 

1. Use your SSH client to connect to your server
2. In your client, navigate to your modules directory
3. Browse to: http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/ (This is the CVS repository for modules)
4. Click on the link for your desired module (We’ll use the pathauto module for our example)
   
5. Go the the Sticky Tag Selection, and make note of the latest stable version of the module for your drupal release.  In this example, I’m running Drupal 6.x.  So, the latest release for pathauto at the time of this writing is “DRUPAL-6–1-1″.  Take note of this; we’ll call this {latest_stable_version}.  Also note how the module is listed in the directory structure at the top of this page (contributions/modules/pathauto), in this case, the name is listed as “pathauto”.  Take note of this; we’ll call this {module_name}.
6. Type the following command:
   

   cvs -z6 -d:pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal-contrib checkout -r {latest_stable_version} -d {module_name} contributions/modules/{module_name}

   So, for our example, the code would look like this:

   cvs -z6 -d:pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal-contrib checkout -r DRUPAL-6–1-1 -d pathauto contributions/modules/pathauto

7. Voila!  It’s installed.  All you have to do is enable it in your drupal admin section.

Stay tuned for a post on how to update via CVS…

Almost 7 out of 10 individuals surveyed clicked on a first-page search result.  Only 8% of respondents were willing to click results beyond the third page.  This continues a recent trend of search engine users refusing to dig into deeper search-result pages.

Instead of progressing into deeper search results, most users (over 9/10) simply altered their search terms or switched search engines.

eMarketer forecasts these dramatic trends to influence SEO spending in the next few years.  Companies are not only realizing the importance of quality search engine rankings, but also the relative cost efficiency of SEO investment.  By 2011, they forecast SEO spending to total 23% of search-marketing spending. 

For more information on SEO, including how your company can benefit, please contact Soleer.

 Here is an example of what we’re looking to accomplish:

• Bullet-List Item 1
• Bullet-List Item 2
• Bullet-List Item 3
• Bullet-List Item 4
• Bullet-List Item 5

Note how the bullets are red and the list-item text is blue.  Now, let’s take a look at the code:

Standard code:

<ul id=”ex_list”>
      <li>Bullet-List Item 1</li>
      <li>Bullet-List Item 2</li>
      <li>Bullet-List Item 3</li>
      <li>Bullet-List Item 4</li>
      <li>Bullet-List Item 5</li>
</ul>

In order to style the bullets and text seperately, we must enclose the <li> text within <span> tags:

<ul id=”ex_list”>
      <li><span>Bullet-List Item 1</span></li>
      <li><span>Bullet-List Item 2</span></li>
      <li><span>Bullet-List Item 3</span></li>
      <li><span>Bullet-List Item 4</span></li>
      <li><span>Bullet-List Item 5</span></li>
</ul>

Now that we have the xhtml setup correctly, all we have to do is perform some minor CSS changes:

#ex_list li{
          color: blue;       /* The color you want the bullets to be */
}
#ex_list li span{
          color: red;      /* The color you want the bullets to be */
}

1. Pre-requisits: You’ll need an instance of CiviCRM running on Drupal, (we’re using Drupal 5.5 with CiviCRM 1.9) with CiviEvents Enabled.
2. Download & Install the following Drupal modules:
   1. Calendar: http://drupal.org/project/calendar
   2. Views (required by Calendar): http://drupal.org/project/views
   3. Date (required by Calendar): http://drupal.org/project/date
3. Go to your Module management screen ( Administer >> Site Building >> Modules )
   
   1. Enable Calendar View
   2. Enable Calendar iCal
   3. Enable all other modules required by these
4. Go to the “Administer Views” screen ( Administer >> Site Building >> Views)
   
   1. Set ‘calender’ view status to ‘enabled’
   2. Click on the ‘add’ link next to calendar

   

   3. On the “Add a View” Screen, under Access, select all the roles you want to be able to view this calendar.
   4. Go to the bottom of the page and click save
   5. You will now see ‘calendar’ listed under ‘existing views’
   6. Click on the ‘calendar’ link listed in that same row or go to the calendar url, which should be http://www.yoursite.com/calendar (if you have drupal installed in the base directory) or http://www.yoursite.com/drupal/calendar (if you have drupal in it’s own directory).
5. Go to your “Access Control” page. (Administer >> User Management >> Access Control)
   1. Under CiviCRM, make sure “register for events” is enabled for your anonymous role, and any other roles you are going to want to register for events.
6. From the Calendar page, you should see the following:
   
   1. Click on the “iCal” tab, and insert the following information:

   

   2. Under “Expire iCal cache:” I recommend setting this to ‘0 sec’ for debugging purposes, and then scale back based on your traffic and update timing requirements.
   3. Set the Name as anything, I went with “civi” to keep it simple.
   4. Set the Url to your civi iCal feed.  Should be something like:  http://www.yoursite.com/civicrm/event/ical?reset=1&page=1  or http://www.yoursite.com/drupal/civicrm/event/ical?reset=1&page=1 .
7. And that should be it!  Set up a test event, and make sure it shows up on your calendar page.