Hello -- I'm not sure I'm posting in the right place here so apologies if that is the case. I am having an issue with the OG and OG_FORUM navigation URLs. When viewing an organic group and selecting "Group Forums" in the navigation, the URL is off by +/- 1 or 2 for each group.

For example, If the forum URL is
- http://.../3

when in the organic group and selecting "Group Forums" the URL is
- http://.../2 or it could be http://.../5

This occurs for each group. Any assistance you could give would be very much appreciated. Thanks!!

Take care
Tim

Comments

rconstantine’s picture

Are the correct pages not showing?

I suspect you are confused about the URL. In some cases, the group ID will be showing, in other cases, only the term ID will. In other cases, both will show. So if you click on a forum item titled "groovy forum" and you do get to that page just fine, then there is no problem. SO if your term IDs are close numerically to your group IDs, then that would be what is happening.

I haven't had problems getting to the right spots and it looks like nobody else has either.

rconstantine’s picture

Status: Active » Closed (fixed)

It would seem maciagt has not come back to respond. Closing the issue. He can reactivate it if needed.

AAV’s picture

Status: Closed (fixed) » Active

I was noticing this same issue today on my new install. With a normal user login I was getting "access denied" when clicking on "Group Forums" in the group navigation. If I would change the trailing number in the URL(in my case from 4 to 3) and load that page.....the correct group forum came up correctly.

I figured out something that "fixes" it, but im not sure if it should or not. I posted this thread regarding what I set that eliminated the issue:

http://drupal.org/node/205218

No idea if ACCESS CONTROL>FORUM MODULE>ADMINISTER FORUMS is suppose to be checked for OG forums to work or not.

rconstantine’s picture

Some questions for you:

1) did you install this into an existing site, or is it all fresh?
2a) if an old site, did you already have forums using the standard Drupal module?
2b) if an old site, at what point did you add groups?
3a) if a new site, did you setup the standard forum module per the README?
3b) if a new site, in what order did you install modules?
4) either way, did you modify OG per the README so that entries are properly made into the og_ancestry table?
5) what access control modules are you using?
6a) are you using the access control built into OG?
6b) if so, have you tried to rebuild node permissions?
7) are you using any taxonomy modules other than the core taxonomy module? [I'm pretty sure the Category (or is it categories?) module won't work with this]
8) list versions of installed software (OS, PHP, MySQL, etc.) [this module only works with PHP 5 out of the box; PHP 4 patches are lying around in the issue queue if that's the issue.]
9) any other installation details will be helpful.

I have this installed in a dozen instances with no problem whatsoever. Very strange. I we can get to the bottom of this one, it may prove to be very interesting.

BTW, you should NOT be giving regular users administration rights to your forums! They could screw it all up worse! Still, I suppose that is a clue - which is why I asked about PHP version and the OG mod; those wouldn't be used by admins, only regular users.

AAV’s picture

Some questions for you:

1) did you install this into an existing site, or is it all fresh?
FRESH

3a) if a new site, did you setup the standard forum module per the README?
YES, I HAD ALREADY SETUP THE STANDARD FORUM BEFORE

3b) if a new site, in what order did you install modules?
CLOSE TO THIS >> THEMESETTINGSAPI; EVENT; FORUM_ACCESS; ACL; MESSENGER; BBCODE; QUICKTAGS; QOUTE; OG; OG_FORUM; OG_MENU(LATER UNINSTALLED); OG_CALENDAR.

4) either way, did you modify OG per the README so that entries are properly made into the og_ancestry table?
I ONLY DID THIS WHEN TRYING THE DEV VERSION. I HAD FIRST INSTALLED THE 5.X-2.1, THEN THE DEV, THEN BACK TO 2.1 BUT USED THE MYSQL4 PATCH, BACK TO DEV NOW.

5) what access control modules are you using?
ACL

6a) are you using the access control built into OG?
NOT 100% SURE(IM NEW TO DRUPAL), USING USER MANAGEMENT>>ACCESS CONTROL

6b) if so, have you tried to rebuild node permissions?
NO IDEA HOW TO DO SO

7) are you using any taxonomy modules other than the core taxonomy module? [I'm pretty sure the Category (or is it categories?) module won't work with this]
NO

8) list versions of installed software (OS, PHP, MySQL, etc.) [this module only works with PHP 5 out of the box; PHP 4 patches are lying around in the issue queue if that's the issue.]
PHP4.4.7; mysql4.1.22. I HAVE SEEN THE PATCH FOR MYSQL4(TRIED IT HAD HAD MORE ERRORS THAN WITHOUT. READ THAT SOME ARE RUNNING ON MYSQL4 OK SO I WENT BACK TO THE DEV VERSION). I DO NOT SEE A FIX FOR PHP4, CAN YOU POINT ME IN THE RIGHT DIRECTION?

9) any other installation details will be helpful.
POSTED MY CURRENT SITUATION HERE: http://drupal.org/node/205218

Not sure what my problem is over here, im guessing related to php4/mysql4? The mysql4 fix made things worse.....looking forward to trying the php4 fix.

AAV’s picture

Status: Active » Fixed

My above issue fixed. Was caused by forum access module.

Only remaining issue im having is that when I try to create a forum topic, no forums are listed in the dropdown menu. Any help appreciated. Thanks

rconstantine’s picture

After reading your post at #5, I was going to suggest trying to disable forum_access. I think there is a thread in the queue that says it doesn't work. Since og_forum naturally uses OG's own group access, I think that forum_access is redundant. If someone can come up with some significant use cases for combining OG and forum_access with this module and/or is willing to find out why they don't work together well (changing URLs is certainly strange), then I might consider supporting forum_access. Otherwise, I won't be.

BTW, forum_access should have been included in your list for item 5. As should have OG if you have the first section of the OG admin page turned ON.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.