Hopefully somebody will benefit from this. I got 1.3.10 to setup and work on an NT platform running Apache and mysql by performing the following steps:
In config.ini, include the statement:
Set INCLUDE_PATH=".;lib/pear"
Remove the following files from ./pgsrc:
OldMarkupTestPage
OldStyleTablePlugin
OldTextFormattingRules
PgsrcRefactoring
PgsrcTranslation
Zap the database tables and hit the root url.
Does anybody see any pitfalls to my approach? Does anybody know why removing the pgsrc files would allow this to work. My approach was completely trial and error and with more time, I could have narrowed the presumed bad file list further.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hopefully somebody will benefit from this. I got 1.3.10 to setup and work on an NT platform running Apache and mysql by performing the following steps:
In config.ini, include the statement:
Set INCLUDE_PATH=".;lib/pear"
Remove the following files from ./pgsrc:
OldMarkupTestPage
OldStyleTablePlugin
OldTextFormattingRules
PgsrcRefactoring
PgsrcTranslation
Zap the database tables and hit the root url.
Does anybody see any pitfalls to my approach? Does anybody know why removing the pgsrc files would allow this to work. My approach was completely trial and error and with more time, I could have narrowed the presumed bad file list further.
BTW, the error I kept getting was immediately following the virgin setup process, I got a "File Not Found" error in my web browser.
PHP Error trapping and Apache logging couldn't point me to the problem.
These are the pages which hit us with the 1.3.10 memory problem. This was fixed during the last months.
PgsrcRefactoring is ok.
See http://phpwiki.org/PhpMemoryExhausted