Better signature limiting options

[why-not]

Hi All

I keep adding stuff that makes it take longer to release this! I think I will stop that now! A few have emailed me asking when will it be done! Well, it is almost done. The only thing I need to do is finishes the phrases (100 to go!)! I hate that part because I never know what to write and it's boring! Give me notepad and some code to write and I am happy :ermm: !

I have some questions if people want to answer them! If you do it will help me figure what way of doing things will people like best! Anyway here are my questions!

The database layout!

The signature control adds (2) tables...

1. table (signature)

This holds each groups settings...

groupid = group the configuration belongs to
permissions = the form data for the admin panel
editor = the compiled permissions used for editing signatures
admin = the configurations (cron, monitor, mass manage users)
run = the signal that tells the cron to run
cron = a time field to track the next run time
users = holds the list of users being processed by the cron task manager
warn = holds a list of users that have more than once violated the sig perms...

2. table ( monitor )

this table keeps a list of users by userid and all the image urls that are in each users signature!

usergroupid = the user is a member of this group
userid = the id of the user
images = a serialized array of images that are in this users signature, including (date, size, type, last time checked)

We use this table for the monitor, so we don't have to do any script processing on a signature to validate images that are contained in a users signature that has already been validated! This table is updated every time the user updates their signature, if it has images the user is added to the monitor table, if they don't have images in their signature they are not added to the monitor!

The reason for adding the first (1) table, is that forum permissions are global, so adding big array that the signature control uses to the global permissions would be a waste because the only time the signature control permissions are needed is during a edit of a signature!

Having said that!

My question!

1. I can remove the first table and just add the permissions to the usergroup table, removing the one extra query that is needed when a editing request is made. But like I said the array is carried around the forum taking up memory!

2. I can leave it just the way it is, and just live with one extra query for a signature edit! But be happy because memory of a big array would not be wasted!

So what do you think, (1) or (2)

Before I go, here are two screens standard editor, advanced editor with the signature control reporting the errors it has found!

I will be taking requests in a few days for people wanting to test it on their forums, I will also put a demo up so others can try it!

One thing I will say, some of your members will not like that you add this to your forums, because they can not get by this control no matter what they do! Let me tell you some will get very mean, I am telling you this from experience!

C, ya...

Sonia