Online archive contains odd strings like "%(indexing_disable)s"
For some of our lists, the web interface for the archives are peppered with various strings like %(indexing_disable)s and %(htsearch)s. The lists were recently migrated from a Solaris 9 box to a RHEL6 box. Rebuilding the archives doesn't fix the problem. What do we need to do to fix it?
We are running Mailman v2.1.12 with htDig integration.
Larry M. Rosenbaum Oak Ridge National Laboratory
Rosenbaum, Larry M. wrote:
For some of our lists, the web interface for the archives are peppered with various strings like %(indexing_disable)s and %(htsearch)s. The lists were recently migrated from a Solaris 9 box to a RHEL6 box. Rebuilding the archives doesn't fix the problem. What do we need to do to fix it?
We are running Mailman v2.1.12 with htDig integration.
If rebuilding the archive doesn't fix it, something is wrong with your htDig integration.
Those replacements are in the htDig integration version of the archive templates and they should be properly replaced as messages are archived or as the archive is being rebuilt.
If you run bin/arch --wipe on a list's archive, it *should* fix it. If it doesn't, but newly archived posts are OK, I can't understand what would be wrong. If newly archived posts also have uninterpolated replacements, then something is missing from htDig integration.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
From: Mark Sapiro [mailto:mark@msapiro.net]
Rosenbaum, Larry M. wrote:
For some of our lists, the web interface for the archives are peppered with various strings like %(indexing_disable)s and %(htsearch)s. The lists were recently migrated from a Solaris 9 box to a RHEL6 box. Rebuilding the archives doesn't fix the problem. What do we need to do to fix it?
We are running Mailman v2.1.12 with htDig integration.
If rebuilding the archive doesn't fix it, something is wrong with your htDig integration.
Thank you for the help. It turns out that some of the files didn't get patched (or somehow got unpatched). I applied the patches and it is working properly now.
participants (2)
-
Mark Sapiro -
Rosenbaum, Larry M.