cms or not?

[ravingcommie]

I'm looking for a way of making my site dynamic, with an admin bit and different users, but I don't think a content management system can do this, I have tried quite a few.

A friend that owns ICO Designs gave me a copy of MXCMS, which tbh isn't very good.

All I need is to be able to update, edit and insert into databases, add, change and delete users and upload images, through a like mini password protected admin panel. More like an add-in for my site, rather than a full cms.

Does anyone know how I could do this, or know of anything that does exactly that? A good chunk of code would be nice too

ravingcomme

[steadyguy]

They're not so hard to build with a bit of effort. Making it object-oriented will make your job a great deal easier.

As a general overview of what I did when I encountered this problem ... I decided to make a basic manager class, with mainly just create, update, delete, and view methods, in addition to a few utitility methods. Then I made a subclasses for each type of 'item' (ie., collections of photos, members, newsletters, subscribers, etc ...) that needed to be managed, overloading the aforementioned methods. This is working quite well, with the added benefit of being very extensible.

[ravingcommie]

would that be done just by making a few "function"s or something else?

[ravingcommie]

i read up on the class function, seems a good idea.
if anyone has done anything like this, would it be possible to look a like snippets of their code.... im a bit baffled

thanks alot

ravingcommie

[cyclops]

I suggest you use phpMyAdmin, this way you can handle the DB stuff, like updating texts etc. and using a simple script to retrieve the data.

Only thing missing is a way to upload an image with phpMyAdmin, but there are tons of premade-scripts who can help you.

HTH

[steadyguy]

The classes I described earlier look roughly like this:

class Manager {
    function Manager() {
        //constructor function
        //automatically set a bunch of variables like query strings, etc, whenever the class is instantiated
    }
    function connect() {
        //utility function
        //connect to the db, and return a result
    }
    // other utility functions, like input validators, and session managers...
}

class Newsletters extends Manager {
    function Newsletters() {
        /constructor function
        //again, automatically do a bunch of stuff whenever this class is instantiated
        //be sure to call the parent class constructor function:
        parent::Manager();
    }
    function view() {
        //view all the newsletters, or one individually, based on user input
    }
    function create() {
        //create a new newsletter
    }
    function update() {
        //update an exisiting newsletter
    }
    function remove() {
        //delete a newsletter
    }
}

These are missing a few functions like sending messages, and the logic for deciding which function is run. But I think you get the basic picture.