Hi, I have a global content block called "footer". Inside that block I have a tag, "cms_selflink", which looks a bit like this:
{cms_selflink page='12' text='Privacy Policy'}
The trouble is, when the website is viewed, I see:
Privacy Policy
where the cms_selflink is sitting in the footer. I'm not seeing the above in "view source", it is actually visible like that in the browser. When I do View Source, I see the entities > and < are being used.
I don't remember this in 1.5 Anyone else seeing this?
[SOLVED] CMSMS 1.6 - cms_selflink inside global content block
[SOLVED] CMSMS 1.6 - cms_selflink inside global content block
Last edited by oliver341 on Tue Jun 30, 2009 9:07 pm, edited 1 time in total.
Re: CMSMS 1.6 - cms_selflink inside global content block
It sounds to me like you're not looking at the same link. If the link you put in the GCB is being misinterpreted, it would be
The "My link text" text has to be coming from somewhere else.
I don't notice any unusual GCB or selflink behavior in 1.6.
Code: Select all
<span class="footerText">Privacy Policy</span>
I don't notice any unusual GCB or selflink behavior in 1.6.
Re: CMSMS 1.6 - cms_selflink inside global content block
My mistake, the link text is indeed showing as:
Privacy Policy
I've amended the OP, apologies for the confusion. Any idea why this might be happening?
I should also add that the tag is not present in the footer GCB, where is that coming from?
Privacy Policy
I've amended the OP, apologies for the confusion. Any idea why this might be happening?
I should also add that the tag is not present in the footer GCB, where is that coming from?
Last edited by oliver341 on Tue Jun 30, 2009 9:03 pm, edited 1 time in total.
Re: CMSMS 1.6 - cms_selflink inside global content block
Check the HTML for your GCB (in other words, turn off the WYSIWYG), and see what's happening there.
Re: CMSMS 1.6 - cms_selflink inside global content block
Ah, cheers! When I turned off WYSIWYG I could see that the end tag of the cms_selflink was in the wrong place; it was after the tag. Many thanks for your help, I'll mark as solved.jmcgin51 wrote: Check the HTML for your GCB (in other words, turn off the WYSIWYG), and see what's happening there.
On a more general note, my move to 1.6 has not caused any issues.