Plone Sitemap Excellence

Plone Sitemap Excellence by pendragon David Whelan I don’t know anyone at or anything about Ingeniweb except that I love their Plone products. Talk about a company to put some $$ into! I’ve installed a number of their products, mostly just to fool around with but the latest one I’ve installed is their Sitemap. Having used some Perl-based folder-oriented site maps, this was harder to configure but once in place, it’s a great utility. A bit more documentation would be helpful but for those who are familiar with Plone and Zope, it’s probably not a big deal.  The biggest stumbling blocks I ran into related to the “root value” that you need to set for the map, and the metatypes.

The first item I looked for was how to create the sitemap.  Unlike many other Plone products, you don’t create a separate instance of a sitemap, but instead there is a portal_property sheet with all of the information that applies to the sitemap.  Installation creates a portal_action so that the site map can be accessed from the top navigation bar.

I’m not sure I still have the root value down, as I’ve got a Plone site hanging off the root of my Plone installation, so I used that site name as the root.  When I used other names for the value, nothing seemed to change the sitemap unless it was to break it.  Any root value with an odd character (like a backslash) broke the site map.

The metatypes took me a bit as well, as the Portal Types are in some cases the same as the Metatypes, but not always.  This was easily remedied, though.  Click on any Portal Type and you’ll see the “Product Meta Type” information on the page.  So “Document” equals “Document” but “Event” equals “CMF Event” and “Topic” equals “Portal Topic”.  Probably the most important one is the “Portal Image”, to eliminate graphic files showing up and littering the site map (unless you want them, of course!).  I am only “digging” into Plone Folder and Large Plone Folder.  This created another hitch, as I hadn’t made the folders themselves visible in some cases, so folders in which content was published were not appearing to the site map function.  Once the folders themselves in the tree I wanted to include were published, the site map looked down into them. 

I did find some “visible” files appearing in the sitemap, which I didn’t want and haven’t figured out (yet) why.  But I changed their state to “private” and they disappeared from the listing.

I never got to the other style sheet support it offers because it picked up the global styles I was already using.

Another excellent tool from Ingeniweb.  Lots of flexibility and very easy to install and use.

Document Actions