Skeleton CRU's Blogs
Hello World! and welcome to the Computing Resources Unit blogs' of the College of Agricultural and Environmental Sciences at the University of California, Davis (http://computing.caes.ucdavis.edu/). We are currently hosting two different blogs: a programmer's blog and a web blog. Please take a look around!
May day, may day.
We launched a new website recently, however a glitch with the blog set up has been found. We're running two Plone products in tandem, Products.QuillsEnabled and Products.Scrawl, as per the cleverness found at Jon Stahl's blog.
On its own, Scrawl provides a simple content type Blog Entry that allows comments by default, and includes a 'blog_view' for collections and folders. QuillsEnabled, on the other hand, allows you to convert any folder into a blog using any content type. It appends a number of functional portlets that you might find on other blog services, such as a tag cloud, archives, recent entries, etc.
The problem we've run into is that attempting to access any of the auto-generated structure on the Quills end throws traversal errors like no other. That means, no clicking on any of the 'topics', no access to the archives, or authors. Sure, it's not interrupting with consuming the blog in a normal fashion, but all those extras are crippled in the meantime.
No solutions yet. I found someone who ran into the same errors with QuillsEnabledRemoteBlogging, however the ticket was closed with no resolution as the makers were unable to reproduce the problem. I added my notes their, but wanted to document (aha!) here as well, to keep track of what I've tested thus far. And as a note, I'm fairly certain this worked on the site sometime before, while I was initially testing the site before it launched.
Anyway, haven't tried much so far but:
- Creating a blog on the same server (.28) with just QuillsEnabled, Scrawl, and qPloneComments installed produces no errors.
- Creating a blog in a folder lower than the root level does not produce errors.
- Creating a blog on the same server with all the same products installed as the ASI site produces no errors.
- Creating a blog on the same server with the same products, and then creating folders within the 'Blog' folder (named 'test' and then '2010' and '2009') doesn't create errors, although the year folders have odd properties.
And in the meantime, I've:
- Hidden the archives portlet and authors portlet.
- Adjusted the tagcloud.pt in portal_view_customizations so that the topics still appear in their weighted formats, but aren't links.
Rawr! Little help, anyone?
We at the UC Davis CA&ES Dean's Office are embarking on a brave new voyage through the interwebs! This little blog will be our home from here on out, chronicling our trials, tribulations, and victories over the beast known as Plone, as well as a variety of our design exploits. Stay frosty, kids.
Hi, I'm web developer Trish Ang! You might remember me from such web locales as @feesh on Twitter, the Davis Finer Things Club, and flavors.me/feesh. Today, with my good pal Mr. Tyler Randles, I'll be bringing you updates on our web adventures and design practices.
Currently at the Dean's Office, we herd cats like nobody's business, in the form of thirty-odd websites for all sorts of departments, institutes, and centers. We run Plone 3.3.1 primarily, maintained by hockey pro Tom Pomroy, and also add some style to the business web applications that come from our oh-so-talented programming group including the good sir, Scott Kirkland.
So keep a weather eye on this spot! We'll bring you juicy insider info on all the good stuff we're developing.
My name is Tyler Randles and I am a web designer for UC Davis College of Agricultural and Environmental Sciences. This blog is meant to catalogue and document my journey into the land of Plone, Zope, CSS, jQuery, .net, and some HTML every now and then. I have been creating websites for close to ten years now, but only using Plone in the last year. I hope to share with the community what I have learned, usually through trial and error, and perhaps get some feedback from the community too.
Thanks for listening to my ramblings!