Needs review
Project:
Content Type Administration by Organic Group
Version:
6.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 Aug 2010 at 22:58 UTC
Updated:
13 May 2011 at 19:50 UTC
Comments
Comment #1
rhymeswithcamera commentedI am having the exact same issue as Evelyn. It seems that you cannot see any new content type in the "Create content" menu after this module is enabled. Disabling the module restores the menu items and access to the new Create [node] page.
Comment #2
Taxoman commentedSounds like a complete showstopper for using this module until fixed?
(I am looking into using it, haven't decided yet...)
Comment #3
nyleve101 commentedHas anyone else experienced this issue or is it just the three of us?
Hope all is well,
Evelyn
Comment #4
leeaustin24 commentedSame problem here.
Interestingly when this module is enabled it also appears to cause another 'access denied' issue with the 'add new forum topic' / 'new topic' on og forums.
Others are discussing this here: http://drupal.org/node/651672
Comment #5
christopherreay commentedI have this problem aswell
This is a problem with:
function og_content_type_admin_menu_access()
Given that ALL types are ALLOWED in SiteWide, then
else { // do normal processing plus 'allowed' check
$sql = "SELECT octa.types_allowed FROM {og_content_type_admin} octa WHERE octa.gid = -1";
$types = db_fetch_object(db_query($sql));
dsm_once("default Types", $types);
$allowed_types = unserialize($types->types_allowed);
if ($allowed_types[$type] && call_user_func_array($original_callback, $args)) {
return TRUE;
}
}
makes no sense at all
and should read:
else {
return call_user_func_array($original_callback, $args);
}
Comment #6
nyleve101 commentedHi,
thanks for looking into this christopherreay! Just to be clear where in the original code do we put your line?
Thanks again for your help!
Eve
Comment #7
christopherreay commentedSorry it took so long for me to notice this, I must have missed the email:
The issue is that og cta does an extraneous check for "ALLOWED" for sitewide. If you look at the admin page for og cta, you can see that all the allowed checkboxes are checked for sitewide, and they are all disabled.
In fact, the list created by og cta as to which types are "ALLOWED" sitewide is created on installation of the module, so clearly any types created after installation "break".
The code I detailed shows the if block which deals with the case "which types are allowed sitewide"... I tell you what, I will make a pastebin think for it and link it here.. hold on a sec...
Here you go, a link
http://pastebin.com/bNr9YCSd
Should be clear ( maybe too clear)
Comment #8
nyleve101 commentedHi,
thanks for the thorough explanation and code- it's very much appreciated. :-)
Hope you're well and taking care of yourself.
Thanks again!
Eve
Comment #9
Taxoman commentedComment #10
christopherreay commentedGlad I could help (if I have)
Id love to submit patches, but I dont know how to generate them
Comment #11
christopherreay commentedOh, and btw, I got some really good meta help on how to track down the origins of this issue on #drupal, from someone really good... name obviescant