I’ve finally gotten around to solving an interesting problem. For security purposes our primary webserver is read-only which makes some normally trivial tasks extremely difficult. Originally the system was design to push static files to the front end cluster so the web server could deliver.
I’m excited to announce I’ll be presenting at HighEdWeb this year in Austin, TX. I’ll have more information as the event nears but for now I’ll post the link to the talk. If you haven’t heard of this conference before, look it up. The content is diverse, the people are friendly and the presentations always helpful.
We had a problem where we needed two different varnish configuration files between our staging and production plone environments. Generating two files that do similar things is just too much work and unnecessary. However, there is a solution.
Finally, the CMS is migrated to the latest version of Plone and on to new hardware. The actual transition happened two weeks ago Friday but it’s been several days of testing. Anyone visiting the site should notice a huge speed improvement and a generally large increase in reliability.
This was originally posted on Chris Heiland’s staff blog while he was a member of the Web Team. Chris migrated this post to the Web Team blog before he left because we thought the content still had value to the UW community. I can’t imagine why this would ever be useful but I wanted to… Read More
I was updating a test due to a recent migration for a content type. The previous was based on an ATBTreeFolder while the new inherits from an ATFolder. I was getting a test failure and couldn’t narrow it down to what was going on. I’m still unsure if this is a bug and where to even report it. Also, since Plone 4 has completely changed the folder implementation it’s probably not something to worry about.
This will be a short post but hopefully useful for someone running Plone. First a bit of background. We have a custom content type we use for what we call a ‘Portal’. Basically it’s inherits from an ATFolder and has a few extra fields. It also has a custom viewlet that is registered specifically for it’s interface.
In collaboration with the Department of Atmospheric Sciences, we are now providing local weather data on the UW home page. Two standout features: The temperature is taken directly from the Atmospheric Sciences building rooftop, and an in-depth Seattle/UW forecast is available by clicking the weather tab (top right, just above the search box).
Here is a quick and dirty way to enable rolling dates on the UW Events Calendar. By default there are several date range options to choose from, however the best option to grab the next few weeks of events is the end of month option. The downside, of course, is on the last week or last day of the month, there are no or a limited amount of future events.
If you are using the code, we’re pleased to announce our first set of updates: updates that are mostly content-oriented, but a few XHTML and CSS validation fixes as well.