CMS Linker adding "../" to start of each URL
Posted: Mon Oct 12, 2015 1:30 pm
Hello all.
We're doing some work for a client and we recently made their website responsive.
We had to upgrade CMSMS in order to do this - it's using version 1.12.1.
After we upgraded and implemented the updated templates, we noticed some odd things happening. One one of the pages, every time we edit the page, a "../" is added to the start of the URL.
In the CMS editor, it looks like this: <a href="../{cms_selflink href='pagetitle' }">Page Title</a>
When changes are saved (I should also mention that when the Submit button is pressed, the page just goes white and does not refresh), the link changes to http://www.domainname.com/http://www.domainname.com//index.php?page=pagetitle, causing the URL to break.
Does anyone have any clue as to what's going on? As you can see from the link above, it's also adding an extra forward slash after the domain name - while this has no effect, it's still very odd. It's not on our own servers which makes it more tricky - is this likely to be a hosting related issue?
We're doing some work for a client and we recently made their website responsive.
We had to upgrade CMSMS in order to do this - it's using version 1.12.1.
After we upgraded and implemented the updated templates, we noticed some odd things happening. One one of the pages, every time we edit the page, a "../" is added to the start of the URL.
In the CMS editor, it looks like this: <a href="../{cms_selflink href='pagetitle' }">Page Title</a>
When changes are saved (I should also mention that when the Submit button is pressed, the page just goes white and does not refresh), the link changes to http://www.domainname.com/http://www.domainname.com//index.php?page=pagetitle, causing the URL to break.
Does anyone have any clue as to what's going on? As you can see from the link above, it's also adding an extra forward slash after the domain name - while this has no effect, it's still very odd. It's not on our own servers which makes it more tricky - is this likely to be a hosting related issue?