I think the way that Vincent is doing this is to use a wrap class to include
Nuke into the MHonarc HTML. Another way is to use an include statement to
put the the MHonarc code into Nuke, ie tackle it the other way around.
An example of this is at http://demo.wildgooses.com and click on the
"Experimental Diary By EMail" link. This dynamically reads the users mail
files and if there is a sub-dir called "Diary", it uses the contents to
create the web page. Works rather nicely, I can show you the batch files I
used (pretty simple), and Earl Hood wrote the resource file.
The main problem is really that there is no MHonarc control of how the links
should be created. And also there is excessive need to use mod_include.
However, it all seems to give exactly the right results! Very impressive
(thanks Earl)
Ed W
----- Original Message -----
From: "Earl Hood" <earl(_at_)earlhood(_dot_)com>
To: <mhonarc-users(_at_)mhonarc(_dot_)org>
Sent: Tuesday, June 25, 2002 5:13 PM
Subject: Re: MhonArc/PHP
On June 24, 2002 at 23:10, Vincent M wrote:
But... how do I prevent the MhonArc version comment
and the X-Headers from appearing?? That is what I've
been asking.
The only way to do it at this time is to modify the code.
I dont want them in the messaage pages.. or are the
absolutely nesisary?
The X-Headers are beneficial for archive recovering options. The
mha-dbrecover program uses them to reconstruct and archive database.
The comments can also be useful for those you want to do some
post-processing of archive pages.
The MHonArc version comment exists since it was a problem providing
help to users in the past by not knowing what version of MHonArc was
used to generate a page. This way, if a URL was provided, I
can verify for sure what version of MHonArc was used to create
a given archive page.
Technically, they are not absolutely necessary for regular
archive operations. They are useful in diagnostic and recovering
operations.
BTW, what version of PHP are you using? Looking at JC's work,
he does not even bother defining SSMARKUP and leaves the
X-Headers as-is, and he has things working okay with PHP.
Is it possible that this PostNuke that you mention is doing something
more than regular mod_php that is causing the conflict? Maybe there
is some configuration parameters you can set to fix it.
Note, the MHonArc version comment does show up on the index pages,
at it seems you are having no problems with them. Maybe the PostNuke
environment (note, I have no clue how PostNuke is setup or works)
is actually reading the X-Header comments.
It seems you could use SSMARKUP along with *PgBegin resources
to wrap the initial comment declarations within a PHP comment block.
Have you tried this?
--ewh
P.S. Please trim reply text that is not needed. Thanks.
---------------------------------------------------------------------
To sign-off this list, send email to majordomo(_at_)mhonarc(_dot_)org with the
message text UNSUBSCRIBE MHONARC-USERS
---------------------------------------------------------------------
To sign-off this list, send email to majordomo(_at_)mhonarc(_dot_)org with the
message text UNSUBSCRIBE MHONARC-USERS
