Paths and Pathauto

I've just run into the same problem though the problem is actually with spaces_og not purl. I get an infinite redirect when this happens though. Disabling spaces_og did the trick for me but I haven't got a patch to fix it. I'm still not entirely sure why spaces_og requires this prefix.

+1

Hi there,

I have the same problems and questions as nickbits. Also trying to use the magic combination of Context, Features and Spaces and stumbled across the Pathauto <-> PURL issue and at the end came up with an "The page isn't redirecting properly" - Failure ... I am using the beta12 version.

Greets,
Nikolay

Same problem here: I made my groups before install PURL, and every groups already had thier automatic path with pathauto.

Now, enabling PURL, I can't save the same path as pathauto, because I'm receiving the error "There was an error registering the value "groups/my-particular-group". It is either invalid or is already taken. Please choose another"

What can we do to have PURL and pathauto sharing the same base path?

Thank you very much

MXT

Sorry for not responding sooner. Here's what I can tell you about path alias and PURL first:

• Path aliasing and PURL can be used together but PURL will not read modifier components from it. For example, if you have a group with a PURL modifier fruits and a blog post in that group with path alias bananas, you can get to that blog post at bananas or fruits/bananas, just as you could get to the same blog post using node/5 or fruits/node/5.

• Currently there is no way to have the PURL modifier automatically generated from a node title, token, etc. This would be a nice feature.

I see the right fix to this being a combination of a few things:

• Correct pathauto settings for any nodes that will be posted to groups. As described above, they should not include the group path.
• Changes to spaces_og and purl that allow PURL modifiers to be automatically generated via token or pathauto-like mechanism.

Does this sound like it would address your issues?

I am wondering what version of Spaces everyone that has this issue is using, maybe it is version specific.

or if anyone has come up with a fix / patch / workaround?

I have run into the exact same problem. Did some poking, turning things on and off, I was finally able to get a path entered and have the system accept it, with all modules turned on. Then resulting page came up for editing the newly created group node, and the module Spaces was throwing errors all over the screen. Turning off OG Spaces then did take care of the problem, and was then able to access the group.

So....

@nickbits I found one of my problems with at least being able to enter in a path was making sure I had the latest beta versions of everything. I was using context release version but using the beta of spaces. This caused the invalid errors when entering in a path, anywhere.

Was about to type something else.. then just tested my current setup again, and it is working(mostly)...
this is what I did:

completely uninstalled context. make sure to delete the dir since from some versions of spaces it leaves some "breadcrumbs" there.
cp the context dir in appropriate modules dir.
then I turned on the context module first, let it do its thing, then the context_ui module and let it do its thing.
then off to group creation
the specifics here for the Path field I just simply put in the name of the group.
then for URL path settings - I unchecked automatic alias. then typed in group_type/group_name so it looks nice and kinda keep things in order.

Will say this... I think that there is something similar to another post though. I am able to get to that page via:

mysite.com/group_type/group_name

at the same time it also resides at:

mysite.com/group_name/group_type/group_name

this link rarely comes up and with my settings am able to suppress it. I have found that if I follow the later link, then all links will become that format, following the former link keeps the links in that format.

There is the only real bug I can now find with the setup. I know what is happening there also, it is basically doing this from all the paths being filled out taking the Path field and then appending the manually entered automatic alias field to it.
thus two URLS get created from those fields.
site.com/-whatever_is_filled_out_for_automatic_alias and
site.com/pathfield/what_ever_is_filled_out_for_automatic_alias

I have not been able to find any content whatsoever at mysite.com/pathfield.

I hope any of this helps.

My question is then where does the bug I found actually preside itself.

I'm having similar problems (with the page redirects, etc) that seems to be solved either by disabling og_spaces or following @murias' suggestions (which seemed to only fix the problem temporarily). I'm working in a clean install with only og, spaces, context, context_og (plus dependencies, ie: no pathauto). There are also a lot of "Infinite redirect prevented." errors in the log with a type of "purl."

Digging a little deeper, it seems that this query creates the redirect error:

SELECT object_id AS id, value FROM spaces_overrides WHERE type = 'og' AND id = '7' AND object_type = 'variable

While this query runs ok:

SELECT object_id AS id, value FROM spaces_overrides WHERE type = 'og' AND id = '7' AND object_type = 'variable' AND object_id = 'spaces_preset_og'

Hope that helps someone.

I had the same problem. By removing the initial tag and allowing all pathauto group content to be just [title-raw] it seems to work ok.