CCK
Technical Issues which Pop Up in the New Year
Nice post on Smashing Magazine reminding us not to forget the small stuff in the new year: http://www.smashingmagazine.com/2010/01/23/dont-forget-the-small-stuff-this-year/ . For example, did you change the copyright date on all your clients’ sites?
Here are two interesting client issues I had in after the New Year.
Expired Security Credentials
A client called to ask for help getting access to an old Content Management System they had for about four years. The site just stopped allowing them to log in. Turned out to be the site was on a Windows Server which authenticated via the Windows User Groups. After four years, the server reset the user account privileges.
The lesson: Watch server configs and security accounts in the new year. They often (correctly) expire after a certain period and this often occurs at the start of a new year.
CCK Date Fields Stopped Working
Here’s one for us Drupal CCK Date field users.
One of my clients has a content type which includes a publication date using a CCK Date field. Suddenly, they could no longer save changes to nodes in this content type.
This was the error message:
An illegal choice has been detected. Please contact the site administrator.
Here’s what happened:
The CCK Date field has a setting called, “Years back and forward.”
