AMO: Difference between revisions
(creating page) |
(Off the top of my head) |
||
| Line 1: | Line 1: | ||
File Mirrors | |||
Use bouncer | |||
Don't store full path in db | |||
Admin pages | |||
Prevent non-admins from seeing Theme, Extension, and User Managers | |||
Change the theme, extension, and user managers to be a simple search instead of big lists. Need to edit the Pinball theme? Type it into a box and click search. This would let us combine the theme and extension managers. We just search on Main.Name. User Manager would search on name and email address. | |||
Approval Queue | |||
Yes, we need accountability of users. We have that with the approval history log | |||
Trusted Users | |||
I think we need to ditch this. It allows someone to bypass the approval queue. If something is being listd on the site, even if its official, it would be easy enough to get an Admin or Editor to approve it. | |||
Coding | |||
Use templates | |||
User PEAR:DB | |||
Use subselects (requires mySQL 4.1) | |||
Use more variables, such as $imagepath and $siteroot. | |||
Use more funtions | |||
Revision as of 02:00, 20 January 2005
File Mirrors Use bouncer Don't store full path in db
Admin pages Prevent non-admins from seeing Theme, Extension, and User Managers Change the theme, extension, and user managers to be a simple search instead of big lists. Need to edit the Pinball theme? Type it into a box and click search. This would let us combine the theme and extension managers. We just search on Main.Name. User Manager would search on name and email address.
Approval Queue Yes, we need accountability of users. We have that with the approval history log
Trusted Users I think we need to ditch this. It allows someone to bypass the approval queue. If something is being listd on the site, even if its official, it would be easy enough to get an Admin or Editor to approve it.
Coding Use templates User PEAR:DB Use subselects (requires mySQL 4.1) Use more variables, such as $imagepath and $siteroot. Use more funtions