maybe I´m stupid and I don't get it, but I will ask...
Why are the template default settings stored in include/inc_conf/conf.template_default.inc.php?
I think most of phpwcms users are using the vertical menu with js-over effects. So, if you don't want your page look like the original phpwcms-websites menu, you will have to change these settings...
And, tell me if I'm wrong, with nearly every new release or patch, your settings will be overwritten and you always will have to change this file to your comforts. (or you have to look before which lines have been changed but this needs time of course).
So, if nearly every phpwcms user has to change these settings for his personal settlement of visual claims, it would be much better and easier to set these values (colours, pics, etc..) directly in the backend and then store in the database. so nobody would have to edit conf.template_default.inc.php in an editor program (after every patch/release).
Think about it. In my opinion it's now time to correct and improve all the existing functions phpwcms has to offer before more and more new functions are included.
Oliver, you did a very very great job. now it's time to concentrate on the important things to improve usability.
why not saving template default settings in db?
-
jmeyknecht
- Posts: 112
- Joined: Sun 11. Jan 2004, 23:13
- Location: Merseburg, Germany
- Contact:
I guess time is the keyword.... Oliver is busy man and phpwcms is a side-project and not a fulltime job eventhough he would like it 
http://www.studmed.dk Portal for doctors and medical students in Denmark
-
jmeyknecht
- Posts: 112
- Joined: Sun 11. Jan 2004, 23:13
- Location: Merseburg, Germany
- Contact:
I think you make a valid argument but I think adding some that needs to be flexible in the database provides too large of a solution for a problem that works pretty well using just flat files. Also when updating phpwcms you do not have to upload a new config file most of the time (only the files in the patch). Does that help? I might be missing something.
-
jmeyknecht
- Posts: 112
- Joined: Sun 11. Jan 2004, 23:13
- Location: Merseburg, Germany
- Contact:
sure, you are right, of course it takes a lot of time to fix that and of course it's also working with flat files.
but the cms is also working without one or even 3 wysiwyg-editors ;-)
that's why i posted this in the forum "feature request".
you are also right when saying, just install the newer changed files.
I just downloaded the patches since release of RC-1.2
and because of less time, i just copied all the included files on the server and got annoyed, when i had to fix my menu colours every time. ;-)
I don't wanna denigrate phpwcms or any developer. I just wanted to let you know, what a normal phpwcms user thinks about it and what could be improved for better working, usability and user interaction. so I thought, that could be a nice feature request.
Lucky you, if you are not installing every patch and not having this problem ;-)
but the cms is also working without one or even 3 wysiwyg-editors ;-)
that's why i posted this in the forum "feature request".
you are also right when saying, just install the newer changed files.
I just downloaded the patches since release of RC-1.2
and because of less time, i just copied all the included files on the server and got annoyed, when i had to fix my menu colours every time. ;-)
I don't wanna denigrate phpwcms or any developer. I just wanted to let you know, what a normal phpwcms user thinks about it and what could be improved for better working, usability and user interaction. so I thought, that could be a nice feature request.
Lucky you, if you are not installing every patch and not having this problem ;-)
I agree that individual "code changes" by different users for different reasons can be maddening to re-create, if overwritten by upgrades.
Immediately after modifying a file, create a simple backup copy of that updated file. Always backup those few other pivotal config files and your database.
This will go a long way, for now
Restore files from backups (if update adds no new options) as a part of the chmod permissions process. 
Immediately after modifying a file, create a simple backup copy of that updated file. Always backup those few other pivotal config files and your database.
This will go a long way, for now
Restore files from backups (if update adds no new options) as a part of the chmod permissions process. First of all, i agree to JM that it is hardcore boring to check each patch for changes in the conf.template_default.inc.php. And i also absolutly agree with him, that it would be a great _FEATURE_ if that would be replaced with database-based and from the backend handleable settings.
I can't understand - and that goes directly to frold (don't be sad about it) - that a feature-request is discussed in a way, that it is unmakeable coz of missing time. We all know, that Oliver is doing a hard an great job and also that is taking much time. But a feature-request is only something that could be taken in mind and maybe some more user and even Oliver think that the requested feature would be a great thing - even in closer look to the usability of the cms.
greetings
cguenther
I can't understand - and that goes directly to frold (don't be sad about it
) - that a feature-request is discussed in a way, that it is unmakeable coz of missing time. We all know, that Oliver is doing a hard an great job and also that is taking much time. But a feature-request is only something that could be taken in mind and maybe some more user and even Oliver think that the requested feature would be a great thing - even in closer look to the usability of the cms.greetings
cguenther
just a thought...
I was just thinking about this issue of where you keep your data such as defaults and similar information and the issues of keeping that in a database. The one thing that would be frustrating about it would be having to run a query in a database instead of just looking at a text file. This seems trivial but when you think about having some sort of system to add and change defaults the simplest and fastest is to just keep a list in a text file. From a developers perspective (which is first hand ) it just makes more sense to add a text file into the workflow than keeping track of information in a database. Just something to think about.
I do agree that looking how we can improve the functionality and not increase it is a good thing to work towards with phpwcms.
) it just makes more sense to add a text file into the workflow than keeping track of information in a database. Just something to think about. I do agree that looking how we can improve the functionality and not increase it is a good thing to work towards with phpwcms.