Previously the asterisk (*) domain was an option and a part of the description on "manage hostnames". It could be assigned and the use the dictionary items.. mostly when working locally.. perhaps it was from an earlier version before I upgraded Umbraco.. but I actually haven't any domains assigned to node with ID 1054, in my case it is the root node.. only the two domains on the child node (da-node) with ID 1059.
But I think I had assigned the asterisk (*) domain in early state when working locally.. perhaps Umbraco doesn't delete the row after removing the hostname?
It didn't solve the issue.. the stack trace from above throws an error at CalculatedOldUrl, so I think it might be something about the old url's?
In the OldUrl column I think it has catch some odd url's like scripts/).html(n.highlighter(r)),t[0]}),t.first().addClass( ,scripts/)[this.options.html? and some other url's including scripts
No it's definitely a hostnames issue, because it fails inside the CalculatedOldUrlWithDomain property accessor.
I think the issue is, that your hostnames are starting with 'http://', which is the scheme and not part of the hostname. Could you edit your hostnames to the format 'd25283583.u359.surftown.dk' and 'www.lightair.dk'?
Invalid URI: The hostname could not be parsed
Hi..
after upgrading from v. 2.2.6 to v. 2.4.5 and migration of the data I get the following error in the dashboard:
Invalid URI: The hostname could not be parsed.
Stack Trace:
I can send the data from the database table, it might be some of the values in the OldUrl column that fails?
I am using Umbraco v. 6.1.6
/Bjarne
Please let me know the contents of your umbracoDomains table :-) Sounds like an invalid hostname.
The umbracoDomains table contains the following:
Then the asterisk (*) domain is the problem because it's not a valid hostname, is that supported by umbraco anyway??
Previously the asterisk (*) domain was an option and a part of the description on "manage hostnames". It could be assigned and the use the dictionary items.. mostly when working locally.. perhaps it was from an earlier version before I upgraded Umbraco.. but I actually haven't any domains assigned to node with ID 1054, in my case it is the root node.. only the two domains on the child node (da-node) with ID 1059.
But I think I had assigned the asterisk (*) domain in early state when working locally.. perhaps Umbraco doesn't delete the row after removing the hostname?
Could be, have you tried to remove the entry with the asterisk? Please let me know if that helps.
It didn't solve the issue.. the stack trace from above throws an error at CalculatedOldUrl, so I think it might be something about the old url's?
In the OldUrl column I think it has catch some odd url's like scripts/).html(n.highlighter(r)),t[0]}),t.first().addClass( , scripts/)[this.options.html? and some other url's including scripts
No it's definitely a hostnames issue, because it fails inside the CalculatedOldUrlWithDomain property accessor.
I think the issue is, that your hostnames are starting with 'http://', which is the scheme and not part of the hostname. Could you edit your hostnames to the format 'd25283583.u359.surftown.dk' and 'www.lightair.dk'?
Okay it solved the issue to remove http:// from the hostnames...
but I think it conflicts Umbracos with the manage hostnames as you might want to specify http:// (default) or https://
and that Umbraco specify valid domains as:
Valid domain names are: "example.com", "www.example.com", "example.com:8080" or "https://www.example.com/".
True, I'll add support for the scheme too :-) Thanks for reporting.
Have the same issue, this is in my umbracoDomains table :
613307*3307
721078*1078
811077*1077
Think it happens when just setting languages on nodes & no hostnames. (v6.1.6)
Well it should be fixed in v2.5.1 thanks to Gerty!
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.