5.6.3.3 login redirect to www when BASE_URL defines otherwise
Permalink
PLEASE IGNORE THIS POST. I WOULD DELETE IT IF I COULD. Thanks for looking however.
I have a website I've developed in Concrete5 for a client that uses 5.6.3.3. I've set the BASE_URL in the config/site.php to exclude the www portion of the URL. However, when I visithttp://example.com/login (I have pretty URL's turned on), Concrete5 quickly redirects me to www version and then back to the version defined in my config/site.php file. This is the only website for C5 that does this. Lastly, something else that is strange is that when I comment this out and login using www and try to edit any blocks, any save actions prompts C5 to open a new window and returns a JSON result.
The client controls their DNS so I'm wondering if they have setup masking or something? I'm at a total loss because I don't get any console errors and have NO idea what is going on.
I have a website I've developed in Concrete5 for a client that uses 5.6.3.3. I've set the BASE_URL in the config/site.php to exclude the www portion of the URL. However, when I visithttp://example.com/login (I have pretty URL's turned on), Concrete5 quickly redirects me to www version and then back to the version defined in my config/site.php file. This is the only website for C5 that does this. Lastly, something else that is strange is that when I comment this out and login using www and try to edit any blocks, any save actions prompts C5 to open a new window and returns a JSON result.
The client controls their DNS so I'm wondering if they have setup masking or something? I'm at a total loss because I don't get any console errors and have NO idea what is going on.
Forgot to mention that even if I turn off pretty URL's I still get the same issue. I've also removed the htaccess file and that does nothing.
FIXED:
Well that was annoying. A marketing person at the firm I'm working with had me install Google Tag Manager. Well, apparently, Google Tag manager doesn't like the "www" and interferes when the user is trying to Save or Add any blocks. You can, but it forces the opening of a new Window on form submission Ajax requests. Heads up...
Well that was annoying. A marketing person at the firm I'm working with had me install Google Tag Manager. Well, apparently, Google Tag manager doesn't like the "www" and interferes when the user is trying to Save or Add any blocks. You can, but it forces the opening of a new Window on form submission Ajax requests. Heads up...
