Closed (duplicate)
Project:
Domain
Version:
7.x-3.x-dev
Component:
- Domain Alias
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 Jan 2012 at 15:43 UTC
Updated:
26 Dec 2012 at 20:26 UTC
Jump to comment: Most recent file
Comments
Comment #1
agentrickardCannot replicate.
Did you upgrade from 7.x.2?
Comment #2
josebrito commentedYes, but not directly because I had the same problem with 7.x-3.1.
Comment #3
agentrickardThat doesn't really help.
Do you have any items with domain_id of 0 (zero) in the {domain_alias} table? That would explain the problem and indicate an incomplete upgrade.
Comment #4
josebrito commentedNo. I don't have any item with domain_id of 0 (zero) in the {domain_alias} table.
Comment #5
agentrickardWell, I cannot reproduce the error.
Any idea why you are getting that empty value?
Comment #6
josebrito commentedNo idea. On my debug I only get to those conclusions. But I'll try to understand why domain["aliases"] is empty.
Thanks any way.
Comment #7
agentrickardWell, if you can give me steps to reproduce, I can help. Otherwise, there isn't anything I can do.
Comment #8
agentrickardIs it possible that the alias is wildcarded to a domain other than the one you think it is? The new server info block can help you debug that.
Comment #9
gasloff commentedsame thing happened
subscribe to topic
Comment #10
agentrickard@gasloff
Please include an ordered list of steps to replicate.
Inability to replicate the report has stalled this issue.
Comment #11
stevendeleus commentedI have the same problem. As best as I can describe these are the steps to replicate:
- I created two domains that need to serve different content
- all content was added
- when the second domain needed to go online, I changed the temporary domain name domain.tmp.tld to domain.tld
- to make sure the temp domain was still accessible for checking before DNS records were correctly found, I added the temp domain domain.tmp.tld as an alias of domain.tld
- at that time the aliases don't show up any more
The changes needed to be made from the first domain. Making changes on the second domain is not allowed because of domain module settings. Even though the aliases don't show up, they are added and they work.
Comment #12
agentrickardComment #13
agentrickardI cannot replicate this issue.
What _path_ are you trying to access that doesn't return anything? What does that page, in fact, return?
Screenshots and URLs are required.
Comment #14
stealthtech1 commentedI have this same issue.
Been developing a site with 5 domains for couple months now and this problem persisted from the start.
I cannot give you steps to reproduce as its been so long ago when i loaded the domains in the first place.
After added aliases to a domain the edit form just shows: "There are no aliases recorded for this domain."
Although the aliases work, they just not shown on the edit form and therefore i cannot make any changes to them.
The domain_alias sql table have all the aliases there that i loaded. It just doesnt show on the edit form. just gives the above message of no aliases recorded for this domain.
Could it be another module? perhaps if i list them here you can just tell "off the bat" if any of them could pose a risk at clashing with domain module:
ACL
Forum Access
User Permissions
Revisioning
Diff
Advanced Forum
Entity
Redirect
Support
Ubercart
Comment #15
agentrickardNo idea. I have never been able to reproduce this issue.
Comment #16
agentrickardWhat does this mean:
The domain_alias sql table have all the aliases there that i loadedLoaded HOW?
Comment #17
stealthtech1 commentedSorry with loaded i mean "added through the admin edit form" here: /admin/structure/domain/view/1/alias.
Example:
I enter name(s) in the "Add new aliases" form fields and tick redirect if needed. Then click "Save aliases".
These details i just entered and saved is correctly processed and inserted in the "domain_alias" table.
But just doesnt show previously added aliases on this page. See attachment. This domain has got couple aliases saved already for it.
Comment #18
agentrickardWhat's in the {domain_alias} table?
As you can see, the history of this issue has not been very good. That screen shot doesn't really tell me anything because I cannot replicate it.
Comment #19
stealthtech1 commentedSee attached
Comment #20
agentrickardI cannot replicate this issue. Perhaps some other module is interfering.
Comment #21
agentrickardIf you can come up with steps to reproduce, please reopen the issue.
Comment #22
agentrickardAnd magically, I just duplicated this issue, but I don't know how.
Comment #23
agentrickardIt is caused by #1140898: hook_domain_load does not register correctly for domain_alias and other 3rd party modules.