Most pages in co-munity take between 1-2 seconds to load. Some views even longer.
Some caching mechanisms and strategies might help to boost the performance of co-munity. These include:
- caching database queries via Memcached/Redis
- pre-compiling PHP code through APC/Zend Optimizer Plus
- caching anonymous pages through Varnish (alternative, Boost module)
- enabling cache in all (relevant) views (Views Cache Bully can help here)
Using uif + uif_plus modules, it is possible to allow certain roles to import users and even assign them directly to the groups.
A basic implementation of this functionality would allow administrators and a potential additional role (to be given to users based on some criteria) to add new users to the platform and their communities.
Suggestions for criteria on who should be given these privileges are welcome.
When a content with a custom URL alias is edited by a user without permissions to manually set the URL, the path is reset to the default pattern, probably by pathauto.
This is urgent, since many people are now editing their conference papers (to add presentations, or new versions) and the links from the external program get obviously broken.
Working groups are section types that can be used for group-assembly processes, open spaces or other short-term, intensive group processes that are open for all space users.
These sections, however, do not allow for membership (and therefore automatic notification to all working group members), which is a necessary future for a continued follow-up of these working groups.
The module node_convert might allow setting up the needed functionality for transforming sections into spaces.
Allow users to send private messages to other users in the platform.
Users should then receive an e-mail notification.
The privatemsg module serves the purpose. There's also a nice module extension, pmgrowl, which allows for a kind of instant messaging system with ajax popups. Might be worth trying out as well.
- 63648 Aufrufe