pSouper's Wish-Lish
pSouper's Wish-Lish
Hello Oliver [et al]
frontend user-group password WITH admin and guest
basically excatly the same as the backend but for the front end.
users only get access to the structure branches of thier usergroup as backend users do. usergroup admin have admin right simmilar to the backend admin but without any server configuration or the ability to change backend users etc.
superadmin able to view/edit anything by anyone. No arguments
When you are loged in your name is highlighted from the other users in the users logged in area.
whiche ever area of the backend you are in any users in that area too should have thier name highlighted too. mainly this is for chat so you know who you can talk live to.
the chat room automatically clears the information if:
there are no users logged in; if the content of a line is older than a set age; if admin clears it with a button. this would also seperate the overlap in uses between messages and chat a little further too.
the chat room could have a bad word filter on the text entered before posting.
i'm sure these plenty more too
frontend user-group password WITH admin and guest
basically excatly the same as the backend but for the front end.
users only get access to the structure branches of thier usergroup as backend users do. usergroup admin have admin right simmilar to the backend admin but without any server configuration or the ability to change backend users etc.
superadmin able to view/edit anything by anyone. No arguments
When you are loged in your name is highlighted from the other users in the users logged in area.
whiche ever area of the backend you are in any users in that area too should have thier name highlighted too. mainly this is for chat so you know who you can talk live to.
the chat room automatically clears the information if:
there are no users logged in; if the content of a line is older than a set age; if admin clears it with a button. this would also seperate the overlap in uses between messages and chat a little further too.
the chat room could have a bad word filter on the text entered before posting.
i'm sure these plenty more too
Last edited by pSouper on Wed 14. Jan 2004, 16:03, edited 1 time in total.
I think I would be usefull to include the setup pages 3,4&5 if not all of them in the ADMIN section of the phpwcms backend.
this sohuld help the Identifiying and fixing of almost ALL of the setup problems.
to fix most other problems a new field in setup &admin that compairs the necasery Database structure to the existing structure.
on a fresh install this would not be very helpfull but on subsequent Re-instalations or Upgrades/patches this may highlight errors that have been the cause of some trouble.
be able to use {REPLACEMENT_TAGS} in chat/messages to show links images and smilies etc
this sohuld help the Identifiying and fixing of almost ALL of the setup problems.
to fix most other problems a new field in setup &admin that compairs the necasery Database structure to the existing structure.
on a fresh install this would not be very helpfull but on subsequent Re-instalations or Upgrades/patches this may highlight errors that have been the cause of some trouble.
be able to use {REPLACEMENT_TAGS} in chat/messages to show links images and smilies etc
Last edited by pSouper on Wed 14. Jan 2004, 16:05, edited 1 time in total.
Admin Clean-up Button
I would love a 'Clean up' button that would iterate through BOTH the database trashing no longer used entries AND iterate through the folders trashing unused files.
I have noticed that deleting stuff from the trashcan doesn't really delete it from the folders at all and so over time whith a large site in developement and a limited filespace available there could be a lot of wasted drive space that would be a nightmare to reclaim by hand.
I have noticed that deleting stuff from the trashcan doesn't really delete it from the folders at all and so over time whith a large site in developement and a limited filespace available there could be a lot of wasted drive space that would be a nightmare to reclaim by hand.
Last edited by pSouper on Wed 14. Jan 2004, 16:05, edited 1 time in total.
hi pappanase, are you trying to poach me away from phpwcms?
the worst thing about phpwcms is it has put my plans to learn php back by months - still as an artist I just wanna have thing done for me while I draw
the worst thing about phpwcms is it has put my plans to learn php back by months - still as an artist I just wanna have thing done for me while I draw
Last edited by pSouper on Wed 14. Jan 2004, 16:06, edited 1 time in total.
Re: pSouper's Wish-Lish
Hello pSouperpSouper wrote:
admin>user_ section to include 'personal_data' within user_adminitration section so that the admin can view all personal dat regaurdless of it's public status and visivility.
granulated permitions - superadmin,admin, manager,staff,member,user
per page or per branch admition/restriction permitions.
superadmin able to view/edit anything posted by others [superadmin to set lowest level able to do this]
When you are loged in your name is highlighted from the other users in the users logged in area.
whiche ever area of the backend you are in any users in that area too should have thier name highlighted too. mainly this is for chat so you know who you can talk live to.
the chat room automatically clears the information if:
there are no users logged in; if the content of a line is older than a set age; if admin clears it with a button. this would also seperate the overlap in uses between messages and chat a little further too.
the chat room could have a bad word filter on the text entered before posting.
I think I would be usefull to include the setup pages 3,4&5 if not all of them in the ADMIN section of the phpwcms backend.
this sohuld help the Identifiying and fixing of almost ALL of the setup problems.
to fix most other problems a new field in setup &admin that compairs the necasery Database structure to the existing structure.
on a fresh install this would not be very helpfull but on subsequent Re-instalations or Upgrades/patches this may highlight errors that have been the cause of some trouble.
abiltiy to add, edit, modifiey, display, use and delete database information within the article counterpart area.
so that I could setup a new database seperate from the phpwcms database and within it store a photo of all users. then from the article/add counterpart I could insert a 'database list' of all users logged on or all members etc.
I realise this one could get big and messy.
be able to use Smilies and links in chat/messages.
i'm sure these plenty more too
no i don't wanna that you go*smile*
but a few wishes you had, sound like u wanna have a community system. an not a content system.
like the chatfunktion, rights manegement, chat function, user online feature.
an i think something like a chat you can solve with adding by change the pagelayout. with inserting an iframe or so! hope you understand what i mean.
i think the system is made for presenting content, and some people maintain differnt categories.
Greets
Pappnase
hi P,
I understand what you are saying and agree as regards to the permisions wish's, I hadn't quite got Idea of a wcms when I thought of those.
I guest I would like a flexible 'permisions content manager'. a way of placing whole directory structures behind a user/password wall. with session setting too .
As withthe chat stuff I guess I would like to see an MSN type chat room.
As it works at the moment it seems to cover the same ground as the message room but without the flashing notice to let you know someone wants to say something to you.
chatroom could be in a seperate window too - this way you can work and chat at the same time
I understand what you are saying and agree as regards to the permisions wish's, I hadn't quite got Idea of a wcms when I thought of those.
I guest I would like a flexible 'permisions content manager'. a way of placing whole directory structures behind a user/password wall. with session setting too .
As withthe chat stuff I guess I would like to see an MSN type chat room.
As it works at the moment it seems to cover the same ground as the message room but without the flashing notice to let you know someone wants to say something to you.
chatroom could be in a seperate window too - this way you can work and chat at the same time
lots more GD2 stuff
I would love to be able to watermark / overlay text and other images over the top of an image for copyrighting etc.
also, kind of related...
a checkbox to disable 'right mouse click' over images AND disable the 'Alt' or 'Printscreen' keys too.
I know this is not fool proof but deters the regular browser from stealing Images that maybe copyright protected: it's nice for us artists anyway
I would love to be able to watermark / overlay text and other images over the top of an image for copyrighting etc.
also, kind of related...
a checkbox to disable 'right mouse click' over images AND disable the 'Alt' or 'Printscreen' keys too.
I know this is not fool proof but deters the regular browser from stealing Images that maybe copyright protected: it's nice for us artists anyway
A Menu template option. so that we can use all sorts of .css/html/dhtml/javascript menus such as those found on http://css.maxdesign.com.au/listamatic/ and projectseven.com etc.
Copy article in addition to cut/paste. If an extra icon is undesireable then maybe as we can existingly move an artcle on the paste action phpwcms could display a 'cut, copy, cancel' querybox.
this would be very useful for creating tutorials may be based on the same page with additional information.
this would be very useful for creating tutorials may be based on the same page with additional information.
Another thing missing:
A standard-site (with an easy template - like the one that comes in Oli´s ZIP-Files) using all (or the most important) functions that should be turned on in the installer (but should be switchable), so that the people have something to start and play with... That site should also hold some content describing the features, links to the Login and the documentation...
This site (and the templates) should also be used as reference inside the hopefully soon coming documentation and howtos...
Next step could be a collection of standard-templates (with wizards), like Oli promised to do some weeks ago... ( Don´t kill me for that though )
A standard-site (with an easy template - like the one that comes in Oli´s ZIP-Files) using all (or the most important) functions that should be turned on in the installer (but should be switchable), so that the people have something to start and play with... That site should also hold some content describing the features, links to the Login and the documentation...
This site (and the templates) should also be used as reference inside the hopefully soon coming documentation and howtos...
Next step could be a collection of standard-templates (with wizards), like Oli promised to do some weeks ago... ( Don´t kill me for that though )
Think about that:
The following statement is true!
The last statement is false!
The following statement is true!
The last statement is false!
hello all
Copy article in addition to cut/paste >>yes it is really necessary, to keep the structure of a page.
possibility of hiding a title with the public but not in the area of administration.
copy template of course
A standard-site (with an easy template - like the one that comes in Oli´s ZIP-Files) using all (or the most important) functions >> yes
bon courage
Copy article in addition to cut/paste >>yes it is really necessary, to keep the structure of a page.
possibility of hiding a title with the public but not in the area of administration.
copy template of course
A standard-site (with an easy template - like the one that comes in Oli´s ZIP-Files) using all (or the most important) functions >> yes
bon courage
more menu features
Many good suggestions above already, but I would also like to see more features for the menu. For example some easy way to insert a menu seperator or blank item. Or different behaviors and actions that you can assign to it. For my websites I often use Sothinks's DHTML Menu: http://www.sothink.com/webtools/dhtmlmenu/index.htm
Now I don't expect some equivalent of that in phpwcms, but some extra easy to use features would be nice.
Now I don't expect some equivalent of that in phpwcms, but some extra easy to use features would be nice.