Trouble diagnosing plugin problems

Doug Ransom <[email protected]>
Newsgroups gmane.comp.web.pyblosxom.user
Message-ID <[email protected]>
I am fairly sure I have the plug-in directory set correctly and that the
httpconditionalresponse plugin is working, but the diagnostics don't
show that any plug ins are loaded.  I report the lack of a list of
plugins in the diagnostic report and the lack of version of which
pyblosxom is running in the report as a possible defect in version 0.9.


I am trying to get the archives and categories plugins working, but no
joy.   Any tips on where to start debugging appreciated.

Below are the diaganostic output (which doesn't show any plugins loaded,
maybe it doesn't work when loading all plugins in a directory <the
default>?),  the foot.html, and the config.py

---- diagnostic output.  No version of pyblsxom printed nor $Id$, no
list of plugins. no list of variables actually set.

[[email protected] cgi-bin]$ python pyblosxom.cgi
Welcome to PyBlosxom's installation verification system.
------
]] printing diagnostics [[
sys.version: 2.3.3 (#1, Jan 17 2004, 09:32:26)  [GCC 3.3.2 20031022 (Red
Hat Linux 3.3.2-1)]
os.name:     posix
codebase:    --default--
------
]] checking config file [[
config has 12 properties set.

   missing optional property: 'blosxom_custom_flavours'
   missing optional property: 'base_url'
   missing optional property: 'renderer'
   missing optional property: 'cacheDriver'
   missing optional property: 'cacheConfig'
   missing optional property: 'load_plugins'

Refer to the documentation for what properties are available
and what they do.
PASS: config file is fine.
------
]] checking datadir [[
PASS: datadir is fine.
------
Now we're going to verify your plugin configuration.
You have chosen not to load any plugins.
---- foot.html

</div> <!-- class=stories -->
<div id="navsection">
<div id="categoryindex">
<p>Categories:</p>
<div id="categories">
$categorylinks::display
</div> <!-- categories-->
</div> <!-- category index -->
<div id="archives">
$archivelinks::display
</div><!-- archives -->
<!--

<a rel="validate" id="validatehtml"
href="http://validator.w3.org/check/referer">

<img
        src="http://www.w3.org/Icons/valid-xhtml10" height="31" width="88"
        alt="Valid XHTML 1.0!" /></a>-->
</div> <!-- navsection-->
</body>
</html>
---- config.py
py = {}

###############
# Start Below #
###############
# If your PyBlosxom installation is in a funky place, uncomment
# this next line and point it to your PyBlosxom installation
# directory.
#py["codebase"] = "/path/to/pyblosxom/installation"

# What's this blog's title?
py['blog_title'] = "Doug Ransom's web log"

# What's this blog's description (for outgoing RSS feed)?
py['blog_description'] = "Doug Ransom's weblog"

# What's this blog's author name and email?
py['blog_author'] = "doug ransom [email protected]"

# What's this blog's primary language (for outgoing RSS feed)?
py['blog_language'] = "en"

# Encoding for output. Default is iso-8859-1.
py['blog_encoding'] = "UTF-8"

# Where are this blog's entries kept?
py['datadir'] = "/home/doug/wwwroot/doug/blosxom"

# Should I stick only to the datadir for items or travel down the directory
# hierarchy looking for items?  If so, to what depth?
# 0 = infinite depth (aka grab everything), 1 = datadir only, n = n
levels down
py['depth'] = 0

# How many entries should I show on the home page?
py['num_entries'] = 40


###########################
# Optional Configurations #
###########################

# What should this blog use as its base url?
# py['base_url'] = "http://www.some.host/weblog"

# Default parser/preformatter. Defaults to plain (does nothing)
#py['parser'] = 'plain'

# Using Caching? Caching speeds up rendering the page that is going to be
# shown. Even if you are not using pyblosxom special features, caching can
# improve rendering speed of certain flavours that can show a large
number of
# files at one time. Choose a cache mechanism you'd like, see the
# Pyblosxom/cache/ directory, and read the source on how to enable
caching with
# the particular cache driver, you need to set two variables:
#py['cacheDriver'] = 'xxxx'
#py['cacheConfig'] = ''

# Plugin directories:
# You can now specify where you plugins all lives, there are two types
# of plugindirectories, the standard pyblosxom plugins, and the xmlrpc
# plugins.  You can list out as many directories you want, but they
# should only contain the related plugins.
# Example: py['load_plugins'] = ['/opt', '/usr/bin']
#py['plugin_dirs'] = ['/path/to/my/plugins']
py['plugin_dirs'] = ['/home/doug/wwwroot/doug/pyblosxom-plugins']

# There are two ways for PyBlosxom to load plugins.  The first is the
# default way which involves loading all the plugins in the lib/plugins
# directory in alphanumeric order.  The second is by specifying a
# "load_plugins" key here.  Doing so will cause us to load only the
# plugins you name and we will load them in the order you name them.
# The "load_plugins" key is a list of strings where each string is
# the name of a plugin module (i.e. the filename without the .py at
# the end).
# ex: py['load_plugins'] = ["pycalendar", "pyfortune", "pyarchives"]
#py['load_plugins'] = []


###########################
# Nothing to modify below #
###########################
__author__ = 'Wari Wahab <wari at wari dot per dot sg>'
__version__ = "CVS"
__date__ = "$Date: 2004/02/19 16:42:19 $"
__revision__ = "$Revision: 1.6 $"
__copyright__ = "Copyright (c) 2003-2004 Wari Wahab"
__license__ = "MIT License"
py['pyblosxom_version'] = __version__
py['pyblosxom_name'] = 'pyblosxom'
py['archive_template'] = '<li><a
href="%(base_url)s/%(Y)s/%(b)s">%(m)s/%(y)s</a></li>'





-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.