@spaceshiptrooper wrote:
Yeah, I would really love to make it so that it can operate in a manner like that.
In these kind of situations, I really want to know how most frameworks do it. How do they allow their users to add new elements without touching the core files. Like SMF, they allow you to make your own text fields of random stuff you can put on profile pages. I know I'm taking the wrong approach and I'm not sure what to expect.See that's the thing. I'm not sure if the audience I'm going to be getting is tech savvy or if they're just beginners. In all honesty, I know that they are going to be beginners, but I would have to assume that they know a little bit about PHP. This way, I know that they will be modifying the core files themselves.
Discussions aside, what I have done is allow my clients to create their own custom codes. They can place these custom codes in a folder named "custom". The core files are separated from the custom code, but the core files are being called before the custom codes. If a user tries to create a PHP file with a core file name, the custom file will be ignored. However, the main problem from the start of the discussion up until this point where I'm trying to battle for is that my theory is that a few of my audience might go and modify the core files. The whole point I was trying to make with the few couple of posts was that what I truly want is to overwrite the core files so that even if someone is smart enough to bypass and modify some core files, it will revert back to the default core files.
That was the main point of my first couple of posts. The customization of files however will not be affected because the custom folder will not be overwritten with any new updates. Only the core files will. That was what I was trying to argue and point out, but I couldn't put it in more meaningful words.
Sorry if my topic shifted some how.