Hi, and excuse for my english...
I read and followed all the steps of the readme inside the folder of the domain taxonomy and applied the patch but the functionality "Rewrite all URLs to point to a single source" that I checked did not seem to work ...
In fact I have a portal with domain access with all primary domain ( no subdomain) and if I create a term and assigns it to the domain (for example) "x" when I go to see the domain "y", path is not http://www.dominioX .com / taxonomy / term but http://www.dominioY.com/raxonomy/term. If i go into same term within the domain "z" I see the path http://www.dominioZ.com/taxonomy/term ...
So I assume it don't work !!! because the patch is right for rewrite url in absolute and not relative.
I did various tests , but without success: I uninstalled the module url alter, I applied the patch before the function is as stated in the readme and, later, after the function outbund rewrite, but nothing. I tried to uninstall any modules as path redirects or global redirect but nothing to do ..
How do I fix this?
Thank you in advance.
Comments
Comment #1
giacinlui80 commentedNobody can help me for this problem? Or perhaps I should explain the problem better?
Comment #2
IckZ commentedsubscribe! I have the same bug!
//this is also in dev!
Comment #3
IckZ commentedhm.. anyone looked at this actually? I cant find the error
this function is called right but nothing appears.
domain_taxonomy_url_rewrite_outbound($path, $options, $original_path); -> placed in the domain module file: settings_custom_url.inc
Comment #4
optimusprime619 commentedI've had the same problem where my term is affiliated to all contents, but on a different domain instead of pointing to the source domain the URL points to the domain from which its being viewed. And this is despite enabling URL Rewriting to a single source, after reading the instructions provided in the readme.txt of the module i patched the domain access
custom_url_rewrite_outboundI got the error message call to undefined function domain_taxonomy_url_rewrite_outbound. This seemed to be a bit unsurprising as the rewrite function is included through settings.php at a very early phase and the other module methods might not be registered. So I tried the following to ensure the function is already visible to drupal in domain's settings_custom_url and it worked:Though the module_load_include is used for inc and other help files for modules based on the inner working I believed that it would be suited for my necessity. It would be great if someone could validate this as many people seem affected by the same.
Comment #5
kenorb commentedClosed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.