Hi,

I'm not clear if this needs to be a support request or a feature request. It i need to solve my issue, but it feels important for the development path as well.

I also want to be honest, up front, I am currently using OG 5.x-7.2. I am posting here because this issue has been active for over 6 months with no reply. Posted again a month ago as a seperate (new) issue. No reply. Even a simple "too busy will respond in 6 months" would help. I think that I've been pretty polite and find myself wondering if I've been banned? I'm posting here out of desperation hoping that this (or the v6 port) is where people's attention is focused. I apologize in advance.

*******

I've been working with organic groups including OG-panels and OG-collections on a site with very satisfying success. The capability offered by Organic Groups and its integration with various modules is valuable and impressive and a testimate to the vision and hard work of this group.

However, I am trying to make sub-tabs on panels and having troubles.

As an example, I have made a panel ...Shared Resources with sub panels Books, Music, Movies, Links, Photos.

The directory hierarchy looks like this (ignoring the "dash" before the subdirectory examples):

Shared_Resources
- Shared_Resources/Books
- Shared_Resources/Music
- Shared_Resources/Movies
- Shared_Resources/Links
- Shared_Resources/Photos

This works very well (single panel tab shows up at Shared_Resources with sub tabs as expected) when I use og collections and preconfigured panels to make the panels and subpanels.

The panels and subpanels show up in my organic groups and work perfectly (as far as I can tell ) until I try to edit the panel page ( using edit page functionality). If I attempt to change anything on the page name or path, the og-panels edit functionality tells me that I can only use alphanumeric characters and dashes. My paths use underscores and slashes to denote subdirectories.

Since the panels and subpanels created with og collections using underscores and slashes work beautifully, is there a reason that the OG Panels module uses the more restrictive dashes and alphanumeric paths? Is this necessary?

Is there any workaround possible to include editable panels and subpanels (tabs and subtabs) inside an OG group?

Or can the OG Collections functionality be extended to be consistant within OG Panels?

thankyou.

Comments

moshe weitzman’s picture

Status: Active » Closed (duplicate)

You have not been banned. Folks can't answer your question or are busy or not reading other people's issues or not running same modules or the question is unclear or any number of reasons why questions go unanswered.

jackspiv’s picture

Moshe,

Thankyou so much for responding. I understand peoples limitations and the nature of this process. Especially yours.

For anyone:

Busy ... of course there is no solution but time and priorities.

If the question is unclear or in the wrong place ... I can solve that but not alone.

1) Is this the right place for this question?
2) Is it most correctly a bug, support request, or feature request?
3) Is the question clear enough to work with?
4) Is more info required?

If this is operator error (ie support request) anytime anyone gets to respond, I would be eternally grateful.
If this is a bugfix or feature request, it seems important to get it on someone's list for future version.

Does anyone else see this as an important or valuable issue for their usecases?

Thankyou everyone for listening.
Thankyou Moshe for being the first to respond in 6+ months and letting me know I'm not banned (major plus ... ;)

jackspiv’s picture

Status: Closed (duplicate) » Active

I have swapped the status on this thread and the old one.

issue of same name OG 5.x-7.2 --> duplicate
this issue ..............OG 5.x-8.0 rc1 --> active

I just realized that the duplicate threads don't show up on the default issue display (active)

leaving this as support request here because it seems valuable/relevant to the development of the 8.0rc1 version.

the primary support i need right now is to determine if this issue is most appropriately/valuably a

bug report
support request
feature request

so that it might most beneficially and clearly serve the community and fit most correctly into peoples priorities.

thanks