[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sheflug] Content management with Plone



Bob Holland <bobholland [at] bradwell.net> wrote :

> On Monday 22 November 2004 18:05, you wrote:
> > I looked at Mambo a while ago too;
> > Didn't find it at all suitable, sadly.
> >
> > In general, the CMS scene is fairly poor. Each CMS out there has some
> > kind of major flaw (for my requirements) so I'm currently writing my own
> > system :(
> 
> Thanks for the usual considered & informative response Alex...
> 
> I think we could just about make Mambo work in this - but there seem to be 2
> 
> main problems...
> 
> 1) Whilst Mambo's 'authors' (any normal user with the relevant permissions) 
> can create and edit their own content from the front end, they can't upload 
> images etc. only the authorised backend users can do this. I can see some 
> very good reasons why this should be so, but I can also see an administrative
> 
> nightmare once the site content grows.

You *might* find legal requirements an issue here?
I'm thinking about people being able to upload pron and 
worse.  I guess this is a problem for all CMS systems that 
allow graphic (png, jpg, gif etc.) upload and I don't know
how any sites manage that issue.  If you allow people to 
upload this stuff then unfortunately you have to monitor
what they upload because of 'corporate responsibility'.

It's an overhead in running such systems.  

FYI: I know of one large communication company that employs
people to watch the URLs employees visit because of this
corporate responsibility issue.  I also know of a local
 government office that catches practically every key tap 
every employee makes, partially from a time keeping, work 
activity monitoring basis.  In there would be reasons to 
protect the council against the activities of it's 
employees.  (And no, I don't know if Sheffield Council also 
employs such software.)

> 
> 2) Authors can create pieces of content anywhere in the site. If this is not
> 
> the most appropriate place is seems impossible via the backend management 
> functions to move it somewhere else. This is also a problem if the site needs
> 
> to be reorganised for convenient use as it grows.

How would you manage changing the links to the existing 
pages that you are now moving around?  A redirect page,
 error page or leave it to 404?  

Regards

Lesley




___________________________________________________________________

Sheffield Linux User's Group -
http://www.sheflug.co.uk/mailfaq.html

  GNU the choice of a complete generation.