scott-t / ssc Goto Github PK

Currently no way to delete anything from the db (eg, can't remove pages, photos, blog posts, etc)

Gallery mostly works, but would benefit from some fine tuning (formatting, possibly template, etc).

Slightly related, images in a blog post could use formatting too.

As title - allow for pages to be cached (in a /cache directory?) to reduce load on busier sites.

Possibly run on a per-module and allow the module to cache itself - higher overhead for more flexibility...

At some point, need an install/update framework set up (including SQL creation steps).

At the moment, while sites may share an install directory, things break badly for various modules for modules that change directory contents.

Example of this using gallery modules (set up for separate tables) would two try and store their two default galleries (the hidden ones) within the same sub-directory, along with any other galleries which share id. This may not be desired effect.

Possible solution is to create a "files" sort of subdirectory which all site-unique files should be contained in (within a folder to somehow split by site) yet somehow allow sharing when needed (eg, shared photo gallery).

Currently exists in a manual form. Would be nice to add ability to have auto-lock or auto-unlock after specified cooldown period.

When determing install url, it doesn't take into account port (eg, :81 or :8080).

Enable granular permission levels within a particular module (eg, add/delete posts for a particular news page but not others, only edit static pages (not add), and so on).

Would need co-op of module_login and all other modules - need to flesh out implementation details still...

In all teh .php files, fair bit of trailing whitespace present

Potentially controversial. (semi?)-auto in-lining of emoticons could be nice.

Changes would be made inside sscEdit::parseToHTML somewhere.

Allow widgets to be shown or hidden based on permissions for that user (eg, particular user groups may be able to see certain navigation widgets, etc)

As title.

Keep track of the current revision so when simultaneous changes are made, one set isn't unknowingly overwritten by the other.

Blog posts and other edits would suffer from similar problems but possibly less likely to be encountered.

Completely doesn't exist at the moment.