It would be cool if one of the experts took the time to take the latest release, patch it up, and put on all the popular mods...
Stats
Rewrite
Rewrite Alias
Alias Breadcrumb
Fancy Fonts
etc
etc
The made a single zip, that was kept up to date....
I noticed that FCK has a new release with some nice feature... would be nice to get that hacked in to get by till the next release as well....
My 2 cents...
Deluxe Build/Bundle of phpWCMS
I don´t like the idea of a fully moded phpwcms..... I would like to fit phpwcms to my needs....
For the phpBB you can find a fully moded version of phpBB at phpbb2.de and the result is that many hack not works properly and for every release more and more hacks a added and it gets more and more over killed..
I only support this idea if you there was a control panel where you can turn the mods off and on..
For the phpBB you can find a fully moded version of phpBB at phpbb2.de and the result is that many hack not works properly and for every release more and more hacks a added and it gets more and more over killed..
I only support this idea if you there was a control panel where you can turn the mods off and on..
http://www.studmed.dk Portal for doctors and medical students in Denmark
i think this sounds to be a goood idea but in reallity will proove to no good to anyone..
- you will never learn the anything about the inside of phpwcms or it's mods
- you will never learn the anything about the inside of phpwcms or it's mods
- you will never learn the anything about the inside of phpwcms or it's mods
- there are a few other reasons too
- you will gnot know what phpwcms is and what someone else thinks it is. because of this you will find giving and getting help in this forum confusing.
- considering an UBERphpwcms as just another mod that requires the COMBINED maintainance of ALL the included mods
ouch!
true ...frold wrote:I don´t like the idea of a fully moded phpwcms..... I would like to fit phpwcms to my needs....
For the phpBB you can find a fully moded version of phpBB at phpbb2.de and the result is that many hack not works properly and for every release more and more hacks a added and it gets more and more over killed..
what change that ?frold wrote:I only support this idea if you there was a control panel where you can turn the mods off and on..
felix - proud member of los locos
"Never argue with an idiot. They drag you down to their level, then beat you with experience."
"Never argue with an idiot. They drag you down to their level, then beat you with experience."
I would love a installer that incuded all of them as options... checkboxes maybe..
I would also want to have control over the mods in the backend.
perhaps a formal method of writing mods needs to be put in place, and the sourse code could have documented hook points.
What is the current plan for the MODULES panel in the back end...???
I would also want to have control over the mods in the backend.
perhaps a formal method of writing mods needs to be put in place, and the sourse code could have documented hook points.
What is the current plan for the MODULES panel in the back end...???
======
DX
======
DX
======
-
GreenNuggs
- Posts: 34
- Joined: Fri 9. Apr 2004, 01:14
- Location: Boston, MA. USA
Actually, I like the core as it is.
My biggest fear however is that I either hack the code or use someone else's hack, but a new version of the core is released and I have to worry about overwriting my previous hacks. I like the way mods work, but what I don't care for is having to put an include inside the frontend files for each hack.
As in the news mod hack for example, you must include:
"require_once ('./include/inc_module/mod_news/inc_front/news.func.inc.php');" in file content.func.inc.php.
It would be easier if the core included in all relevant files that would require hacks mostly specifically for replacement tags, a file (e.g. content.func.inc.mod.php or something to that effect) that was never touched by the core at any point down the line.
But know I'm probably throwing out a suggestion and I'll stop right there.
My biggest fear however is that I either hack the code or use someone else's hack, but a new version of the core is released and I have to worry about overwriting my previous hacks. I like the way mods work, but what I don't care for is having to put an include inside the frontend files for each hack.
As in the news mod hack for example, you must include:
"require_once ('./include/inc_module/mod_news/inc_front/news.func.inc.php');" in file content.func.inc.php.
It would be easier if the core included in all relevant files that would require hacks mostly specifically for replacement tags, a file (e.g. content.func.inc.mod.php or something to that effect) that was never touched by the core at any point down the line.
But know I'm probably throwing out a suggestion and I'll stop right there.