Auto-Nav links using absolute primary domain links instead of correct sub-domainBrowser Info Environment
Great add-on, got a little issue tho.
I've got a primary domain setup up x0.site.com
I'm loading 3 sub-domains to it: x1.site.com, x2.site.com, x3.site.com
On all sub-sites, the auto-nav is showing the main sub-domain page in the nav, despite having "Exclude from Nav" checked. Kinda like having a "home" button. Don't need it, not sure why it's not respecting the exclude from nav.
But the main issue is, in the auto-nav, the links are all absolute and go to the main primary domain's site, with the sub-domain URL mapped in the rest of it, giving a 404.
When I inspect a link, it looks like this:
<a href="https://x0.site.com/x1-Pg2" target="_self" class="dropdown-toggle">Sub-Domain x1, Page 2</a>
When it should look like this:
<a href="https://x1.site.com/x1-Pg2" target="_self" class="dropdown-toggle">Sub-Domain x1, Page 2</a>
I have all the additional attributes checked for each sub domain to override core functionality. Not sure why it's not working.
I'll PM you the actual URLs.
Thanks in advance!
I didn't yet have a look at the actual sites but just to start off, do you have the "Navigation Helper" override enabled under Multiple Domains common settings?
And are you using the "Multiple Domains Auto-Nav" instead of the core block?
Antti / Mainio
Double checked, and yes, all the Enhanced Core Components are checked.
I believe it did that when it installed by default as the documentation indicates. However, I've noticed quirks in older c5.6 before with checkboxes not turning on/off on pages when not in edit mode. So I figured, what the heck, I'll turn these on and off.
So I disabled Navigation Helper & Auto-Nav blocks.
Oddly, this seemed to make it work. When I inspect the links on the sub-domain auto-nav, they are still absolute and pointing at primary server (i.e.http://x0.site.com/x1-Page). But when clicked the sub-domain sticks (i.e.http://x1.site.com/x1-page).
Oddly unexpected, but it's working it seems, just not sure if it's working correctly.
Next I turned on Auto-Nav Enhanced Core Component. Test. Still working as before.
Turned on Navigation Helper Enhanced Core Component. The issue returns, doesn't work and auto-nav links go to primary domain and produce a 404.
So, I'm throughly confused as to what the proper setting should be. Documentation indicates that the auto-nav override goes into effect by default. Should I copy the auto-nave block controller from:
OK, this seems weird. We'll test this out on the latest c5 version in the upcoming days to see if we can replicate the issue.
For the block override, yes that is applied automatically as long as you have the "Auto-Nav Block" override in place. No need to copy and manually override.
I’ve left it thus far with the Navigation override turned off, the others turned on.
Seems to work fine, haven’t seen an issue yet.
Could it be that the domain I’m working on is a secondary domain on the server, not the primary?
I contemplated setting it all up on Digital Ocean instead so it could be a primary, but by that point everything was working well.
> On Aug 25, 2016, at 3:37 AM, concrete5 Community <[email protected]> wrote: