#32 lost PostNuke / PHP-Nuke module ability

open
nobody
None
5
2006-07-03
2006-07-03
cRazY_c0d3r
No

Some of the documentation and past posts refer to the
ability of PhpMyLibrary to function as a module in
PHP-Nuke and PostNuke. There is little/no documentation
on how to install it, but from piecing the information
together, I got the module installed as well as is
possible. After trying for many hours to get the module
working, I started reading the source code and server
errors the module is causing. Just about every URL
PhpMyLibrary refers to when functioning as a module is
wrong. Maybe this problem was introduced with the
directory restructuring?

Specifically, index.php always refers to
installation/install.php because PostNuke can't find
the polerio directory. header.php refers to files that
should be in PostNuke's themes directory (?) but aren't
because the themes or theme names are all different.
content.php should point to phpmylibrary's themes
folder, but doesn't. The URI and URL functions in the
Polerio class seem broken. The themes included seem to
have the same problem as content.php. Searching with
the webopac box takes you to index.php?(query) instead
of modules.php?(query) ... That's about where I gave
up. These problems exist under both PostNuke 0.762 and
PHP-Nuke 7.9

Polerio, I suggest you try a fresh module installation
under PostNuke to see what I'm talking about.

Discussion


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks