Page 1 of 1

[SOLVED] CMSMS 1.6 - cms_selflink inside global content block

Posted: Tue Jun 30, 2009 6:37 pm
by oliver341
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?

Re: CMSMS 1.6 - cms_selflink inside global content block

Posted: Tue Jun 30, 2009 8:35 pm
by jmcgin51
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

Code: Select all

<span class="footerText">Privacy Policy</span>
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.

Re: CMSMS 1.6 - cms_selflink inside global content block

Posted: Tue Jun 30, 2009 9:00 pm
by oliver341
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?

Re: CMSMS 1.6 - cms_selflink inside global content block

Posted: Tue Jun 30, 2009 9:03 pm
by jmcgin51
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

Posted: Tue Jun 30, 2009 9:07 pm
by oliver341
jmcgin51 wrote: Check the HTML for your GCB (in other words, turn off the WYSIWYG), and see what's happening there.
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.

On a more general note, my move to 1.6 has not caused any issues.