Simple, Affordable, Effective.  These are the principles of the D2Derm Skin Care line, and they came to us needing a website with the same characteristics.

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.

Today we launched the new website for the Onion Creek Club, a genuine Texas treasure steeped in family tradition, friendliness, camaraderie and good fun! Onion Creek Club is Austin’s most historic golf club, founded in 1974 by three-time Masters Champion, Jimmy Demaret. There is no other golf club in the Austin area that provides the history steeped in tradition and quality, the convenience to downtown and surrounding neighborhoods, and most importantly the opportunity to make new friends!

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.

When one of the largest and fastest growing community colleges in the nation needed a fully functional Drupal CMS website ready for new student registration (in under 3 weeks), they turned to Soleer.

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’re implementing the new WYSIWYG Module in Drupal 6, and really digging it.  We are using it with our WYSIWYG Editor of choice: TinyMCE (3.2.1.1).

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.

The Problem 

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.