I have a 70+ microsite Drupal install which is making good use of the family of Domain modules. They have been great for the most part, however a bug popped up recently which I can't seem to get down to the bottom of. On a few CCK types on certain sub-domians, when I go to add a new node the path for the new node it defaults to http://foo.domain.com/Array.
I am assuming this has something to do with tokens and the domain path module interfering with the pathauto module. The interesting thing is that there is still an alias created in pathauto. If I add a path into the domain path area on the node it overwrites /Array.
Any ideas on how I can make sure an admin doesn't get /Array as a path or any ideas of what could be causing this?
Thanks for your help, you're modules are a great contribution to the community.
Comment | File | Size | Author |
---|---|---|---|
#13 | domain_path_array_bug.diff | 453 bytes | bryanzera |
#9 | Screen shot 2012-05-22 at 1.31.25 PM.png | 45.71 KB | HelloStephanie |
#9 | Screen shot 2012-05-22 at 1.32.18 PM.png | 56.59 KB | HelloStephanie |
#9 | Screen shot 2012-05-22 at 1.33.37 PM.png | 13.85 KB | HelloStephanie |
Comments
Comment #0.0
HelloStephanie CreditAttribution: HelloStephanie commentedgrammar correction
Comment #1
agentrickardNot sure. What path gets saved in {url_alias}? What token(s) are you using?
Comment #2
agentrickardComment #3
HelloStephanie CreditAttribution: HelloStephanie commentedI'm still having an issue with this /Array issue.
When a microsite admin makes a new page, usually the pathauto alias is saved. Sometimes, however, Drupal skips the pathauto alias and defaults to what is in Domain Path (which might be empty) creating the /Array path issue. At least this is my understanding of what's going on.
This issue has been truly perplexing so any hunches you might have about it would be greatly appreciated. Most paths are in the format name/[title] under pathauto settings.
Comment #4
HelloStephanie CreditAttribution: HelloStephanie commentedComment #5
agentrickardPlease answer the questions in comment 1.
Comment #6
HelloStephanie CreditAttribution: HelloStephanie commentedIn {url_alias} the node/12440 is program/test-program
In {domain_path} node/12440 is empty
node/12440 defaults to /Array when you try to visit the page.
Comment #7
agentrickardWHAT TOKENS ARE YOU USING?
Please include a screen capture of the Domain Path settings for node 12440.
Please provide the information requested so that I can try to help you.
Comment #8
agentrickardFurther, is there an empty entry in {domain_path} for this node, or _no_ entry? Those are two very different things.
Comment #9
HelloStephanie CreditAttribution: HelloStephanie commentedAs I said before, the only token I'm using is [title].
There is no entry for the node in {domain_path} -- sorry, I should have been more descriptive about that.
I've attached some screenshots of the settings on the node edit page for 12440. There is no Domain-specific path set so they are all empty.
Comment #10
agentrickardSorry. I'm a little grumpy.
Comment #11
agentrickardI can't seem to replicate the error. I'm not sure that it's coming from Domain Path.
You might try disabling the module -- or just disabling the functions domain_path_domainpath() and domain_url_alter() -- to see what happens.
Comment #12
grndlvl CreditAttribution: grndlvl commentedOver a month, closing for now. if it's still an issue feel free to re-open.
Comment #13
bryanzera CreditAttribution: bryanzera commentedAfter an exhaustive night of debugging with @stevector, we found the issue with the following code in domain_path_domainpath()
$paths contains an array of domain-specific paths keyed by nid. What ends up getting returned is the value of the $paths array keyed by the domain id, which gets translated by url() to /Array.
This only occurs when:
- you have a domain whose id is the same as an existing nid AND
- the node referenced by that nid has a domain_specific path.
Attached is a small patch to fix this. Caveat: No unit testing has been performed on this patch.
Comment #14
agentrickardWhy is this marked "to be ported"? What version is the patch really for?
Comment #14.0
agentrickardgrammar fix
Comment #15
i-trokhanenkoClosing a Drupal 6 issue. It's time. Thanks!