I don't know how other users of phpwcms think about this but in my oppinion a better management of modules would make sense, if you have to update your phpwcms-installation (and this is done not seldom).
Maybe there's a better solution but i had some ideas how to handle this:
=>A "module-table" in the phpwcms-database, where paths, visibility, usage and other things are stored.
=>A "primary-module" in the backend, where you can register/(un)install modules and change the settings stored in the "module-table"
=>In combination with the PclZip-Library it would make sense to make a complete module-installer, with that you can upload, unzip and install a module, that is written in the usual way.
I guess once this is realized you don't have to edit phpwcms.php and the content.func.inc.php every time you update your system.
I would do this for my self and not report this to this forum, if it was'nt senseless as long as there is no solution like this in new phpwcms-releases. (because then i had to change the new release for my mod-needs
)Hope my idea of installing modules without editing/changing the core code makes sense for you.
