|
Stephen Milley
|
Saturday 21 August 2010 12:32:22 pm
I've recently read some reviews on Ez Publish and one of them mentioned that according to his research, the CMS is missing a community based system, such as one like Drupal. So, I was wondering, do they have any of this currently, or do they even have plans to add more community like features? I know that they have a forum and a blog system, currently. Thanks for any responses. :)
|
|
Steven E. Bailey
|
Sunday 22 August 2010 1:33:49 am
IMHO the off-the-shelf community features aren't really sufficient for a community based site... but, it is possible to make a nice community based site if you put a lot of time into it - take a look at the community site we've developed at: http://www.labforculture.org/en/labforculture/browse And of course this site share.ez.no is also a good example - but it took a lot of custom work too.
Certified eZPublish developer
http://ez.no/certification/verify/396111
Available for ezpublish troubleshooting, hosting and custom extension development: http://www.leidentech.com
|
|
*- pike
|
Wednesday 25 August 2010 2:00:58 am
.. but if you're going to give it a shot anyway, here's a few things to consider:
- a community site usually has a lot more edits then a noninteractive site. ezpublish tries to keep a history of each edit, which a regular webuser wouldnt care about, but they can hog your database quickly. in a site with 5 languages, if a user does 5 edits on a node with 20 attributes, thats 500 records in the attribute table. so turn it down or try to avoid it at all. also reconsider if you want to give users ezp's concept of 'stored drafts' (like the button 'store and continue' below this message).
- there will also be a lot more moving/renaming stuff than usual. ezpublish keeps a record of all previous locations of all nodes (so it can redirect to the new location if someone looks for the old one). that table (the urlalias table) may get a pain in the b*t - grow to big - get corrupted - slow things down. you may want to (try to) disable it. also consider if you really want to have multilingual urls, as this doubles/triples that table as well.
- you really want to use caching if the site grows, but caching a community site is not so easy. while setting up the system, outline what can be cached and which updates should trigger what other updates where. you can have caching (blocks) based on classes/locations, and triggers up and down the node tree, so it can be done.
- you can have nested user groups in ezp. any subgroup inherits permissions from the parent group, so there is a way to set up different levels of user profiles quite neatly.
- this is probably not so ez specific, but if you have a multilingual community, you cant really be sure what language people are typing on the front end - it might not be one of the x languages of your site. so start of with a base language 'webspeak' or something, and add your sites language on top of that. that way, you'll never accidently show the french flag above user-added romanian content.
$2c, *-pike
---------------
The class eZContentObjectTreeNode does.
|
