I'm using spaces_og for a project and am running into a problem with this conceptually.

When a user creates a group, they have a required entry provided by PURL for a url. However, what it I don't want the user to define this, and instead want the path to their group to be created by my pathauto rules? These work concurrently, but it's needless, especially if I don't want the user to have the option that PURL currently gives them.

Recommendations?

Comments

redben’s picture

redben commented

Bump
+1

redben’s picture

redben commented
Component: User interface » Documentation
mikemccaffrey’s picture

mikemccaffrey
he/him
commented

Why the change to Documentation? Does that mean there is currently a way to do it?

nicks’s picture

nicks commented

subscribe

redben’s picture

redben commented
Component: Documentation » User interface

Sorry i inadvertently switched to Documentation... :s

kyle_mathews’s picture

kyle_mathews commented

From my experience -- this isn't a problem. I've been running an og/purl on my site for several months now and people have created quite a few new groups without any problem it seems creating a good purl prefix. All of the prefixes have been very good and perfectly acceptable.

But if you really want pathauto-style purl urls, a simple solution would be to borrow the JS library from, I think, features that auto-creates machine readable names from the feature name people enter. Rewrite that so it takes the group name and turns it into a purl name. You could adjust the JS code to format the purl name how you like. This might be a good candidate actually to add to purl as a default.

jmiccolis’s picture

jmiccolis commented
Status: Active » Closed (won't fix)

The 2.x branch is no longer supported; setting this to "won't fix".