even in 1.7.11?
That means that you have to manage the content of titles and avoid descriptive topic titles that that might be sensitive. That means no private HR topcs like "Planned reduction in benefits" or "Layoff plans for Q3" or anything of that sort.
My expectations were more inline with Dhrups comment - I would think that the topic inherits the group permissions and comments inherit the topic permissions.
Still, the fact that my "Friends only" group was still showing up in the Public topic list.
Bummer. That means more thinking.
Unfortunately the groups plugin is pretty convoluted and the victim of intense feature and scope creep. It's pending a rewrite, but we haven't had enough time.
It would be fairly easy to write a plugin that hides the access dropdown in the topic form, then overrides the action for create topic and reply and make those both inherit the access level of the group they're posted under. It's not out of the box, but should do what you want.
Yep, After "patching" Groups code for BrainTrainZ and for JedSite and momentariliy feeling warm and fuzzy about the (sic) achievement - going back over the 'Core' interlacings ;( I was 2/3 sorry for having dabbled in that sector.
The Access control cascade extensions though were (hack) coded (quite messy!) into the 'Clone' of Groups - calling it a different Groups PlugIn ;-O For a second shot I'd either code very differently (first cut was a rather long young time ago) or leave it well enuff alone.I think posted similar sentiments when Group's were first being discussed (to the point of getting it's own Group Topic). The slightly neater option seemed to be the the SuperGroups 'fork' by Zak.
An *alternative Groups PlugIn might be a better way to go if one does not want to delve into Groups and related Core code areas. Though I 1/2 wish I could find or 'make' the spare time needed to try a proper-like formal re-write.. Any volunteers to join or support lolz ?
( Within a few minutes of yr posting is pure coincidence ;)
Dhrup - I actually cited the link you posted in my original lead-in. The link: http://community.elgg.org/pg/groups/24849/external-pages-extended/ goes nowhere useful, sadly. The problem may have already been solved, but the link you refer to:
http://community.elgg.org/pg/groups/24849/external-pages-extended/
Give me the msg "The requested group either does not exist or you do not have access to it"
bummer
i dont understand well zhat is your probleme , but try to do this :
in views/default/page_elements add meta tag like this :
<link rel="stylesheet" href="<?php echo $vars['url']; ?>_css/YOUR_STYLESHEET.css" type="text/css" /> .
and creat your stylesheet , and save it in _css folder .
then use your classes created like this :
<div class="YOUR_CLASS">....</div> .
sorry for my bad english
If I understand you correctly, I would suggest following this logic:
1. Create a new plugin
2. Register url handlers to pick up a certain index/content page based on the url
3. Create views for different ads, and style them as you please
4. Use elgg_view_layout with say one_column
5. Render your pages using the views in point 3
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by Raül Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.