Weird Behavior (http://localhost vs http://machine-name)
Permalink
I've been scratching my head on this one and can't seem to figure out what is going on.
Here's a quick rundown:
1. I have an autonav block added to my page which shows all links beneath a particular page.
2. The autonav is working perfectly fine.
3. I moved all child pages that the autonav shows to a new parent and updated the autonav to that new parent.
Here's the weird thing: The autonav works perfectly fine when I am accessing my site throughhttp://localhost, however when I try throughhttp://machine-name, some links in the autonav work fine and others still have the old paths. Even on the ones with the correct path onhttp://machine-name, concrete5 is trying to redirect to the old paths.
There are no alternate aliases created for the pages, each only has it's canonical url.
Why would autonav display such different behavior when I am accessing the EXACT same site? I've tried different browsers so I know it can't be caching.
It doesn't matter if I'm logged in or not the same behavior still occurs. Any ideas or similar experiences?
---------------
Here's another small test to maybe clarify this behavior a bit more:
If I try to access this page by typing directly into the browser bar:
http://localhost:8085/working-with-us/careers/current-opportunities...
It works fine.
If I try to access this page by typing directly into the browser bar:
http://machine-name:8085/working-with-us/careers/current-opportunit...
It tries redirecting me to:
http://machine-name:8085/index.php/working-with-us/current-opportun...
Here's a quick rundown:
1. I have an autonav block added to my page which shows all links beneath a particular page.
2. The autonav is working perfectly fine.
3. I moved all child pages that the autonav shows to a new parent and updated the autonav to that new parent.
Here's the weird thing: The autonav works perfectly fine when I am accessing my site throughhttp://localhost, however when I try throughhttp://machine-name, some links in the autonav work fine and others still have the old paths. Even on the ones with the correct path onhttp://machine-name, concrete5 is trying to redirect to the old paths.
There are no alternate aliases created for the pages, each only has it's canonical url.
Why would autonav display such different behavior when I am accessing the EXACT same site? I've tried different browsers so I know it can't be caching.
It doesn't matter if I'm logged in or not the same behavior still occurs. Any ideas or similar experiences?
---------------
Here's another small test to maybe clarify this behavior a bit more:
If I try to access this page by typing directly into the browser bar:
http://localhost:8085/working-with-us/careers/current-opportunities...
It works fine.
If I try to access this page by typing directly into the browser bar:
http://machine-name:8085/working-with-us/careers/current-opportunit...
It tries redirecting me to:
http://machine-name:8085/index.php/working-with-us/current-opportun...
Did you try clearing C5's Cache from the Dashboard? It looks like things got tangled up when you switched to "pretty URL's". Just a guess...
Nope I didn't try that, thanks for the response. Pretty URLs were the first thing turned on with the installation of c5, so it shouldn't of been causing problems now!
Interesting. I just saw that redirected URL
http://machine-name:8085/index.php/working-with-us/current-opportun...
was not using "pretty URL's", wehereas everything else you showed us is.
http://machine-name:8085/index.php/working-with-us/current-opportun...
was not using "pretty URL's", wehereas everything else you showed us is.
Indeed, another VERY weird behavior I couldn't figure out!
I found similar behavior in a fresh install of c5 when switching page designs as well. I'm going to make a screencast tonight to explain it all and submit it as a bug.
On each of the pages that weren't working, I had to add a block, delete it, and republish the page. Seems to be something wacky with the approvals or something not being updated correctly when pages get moved. There were no pending approvals (according to c5) so these should've been the live versions of the pages.