Problem with Content Blocks

[gavinhowells]

Hi,

First up, apologies if this has been covered before or if its something so simple a dead badger could achieve but I’m fairly new to this whole content management malarkey having only created static HTML pages in the past.

This morning, upon recommendation of a friend, I installed CMSMS and was pleasantly surprised with it. However I cant seem to get the {content block="xxxxxx"} to work. I input it in the template and see the box displayed in the CMS but any content I type in isn't visible when I view the page. Its just a blank field. However if I use the {content} tag it flows in perfectly!

Any ideas as to why this wouldn't work. I'm new at all this so a point in the right direction is greatly appreciated.

Kind Regards

Gavin

[gavinhowells]

I apologise once again. In my haste i seem to have posted this in the wrong forum. Just one of those days I guess. LOL. If an Admin would be so kind as to move it to somewhere more suitable I would greatly appreciate it.

[Signex]

do you mean Global content blocks?

the tag should be {global_content name="XXXXXX"}

good luck

[Dee]

No, this is about multiple content blocks...

Odd, the example in the default "CSSMenu top + 2 columns" template works for you?
It uses single quotes {content block='Sidebar'}, but I guess that shouldn't make a difference.

If I understand well the second block appears in the editor? Does it save/remember changes (are they still there when you edit the page again)?
On the front-end, check the source code of the page from your browser - is the content you typed visible there? (maybe the block is there with content, but doesn't show because of css rules or something).

[Ted]

Could it be possible the WYSIWYG is changing the " to " before saving?  Try using the single quotes and see if that DOES help...

[Dee]

Could it be possible the WYSIWYG is changing the " to " before saving?  Try using the single quotes and see if that DOES help...

Nah, also my first thought, but there's no WYSIWYG in the template editor... 

[Dr.CSS]

Are you leaving the original {content} tag in the template also, you have to have the default 'content' tag then add more content blocks...

[gavinhowells]

Are you leaving the original {content} tag in the template also, you have to have the default 'content' tag then add more content blocks...

Thanks for your reply Mark. I am using the {content} tag too. That seems to work perfectly, however the {content block='xxxxx'} seems to do nothing. I must admit, it has me really confused. If I can just get around this minor setback I believe CMSMS would be perfect for me.

Could it be possible the WYSIWYG is changing the " to " before saving?  Try using the single quotes and see if that DOES help...

Thanks for your reply Ted. The HTML definately contains quotes and not "

No, this is about multiple content blocks...

Odd, the example in the default "CSSMenu top + 2 columns" template works for you?
It uses single quotes {content block='Sidebar'}, but I guess that shouldn't make a difference.

If I understand well the second block appears in the editor? Does it save/remember changes (are they still there when you edit the page again)?
On the front-end, check the source code of the page from your browser - is the content you typed visible there? (maybe the block is there with content, but doesn't show because of css rules or something).

Thanks for your reply Dee. The "CSSMenu top + 2 columns" template seems to work fine, I changed the tag to single quotes just in case but it made no difference.

You are correct, the second block does indeed appear in the editor and it does save/remember the changes I make. I did as you suggested and checked the source of the output preview and the {content} tag text is displayed however the {content block='xxxxxx'} tag has been stripped out!

My css experience is limited to that of aesthetics. There must be something I'm missing but I just cant seeing and its resulting in me tearing what little hair I have left out. lol 

If anyone has any further ideas I would really appreciate it. This is confusing me to no end!

Kind Regards

Gavin

[gavinhowells]

Just incase it helps. Here is the HTML code i am using. Like I said, I'm usually only creating basic html pages with tables. Nothing too fancy. Any help would be greatly appreciated.

Welcome
{stylesheet}






























XXXX




XXXXX XX




XXX XXXXXXXXX XXXXXXXXX




XXXXXXXX
XXXX




XXXXXX XX




XXXXXX
XXXXXX




















"The function
of education is
happiness."







T.S. Eliot











"Music is the
strongest form
of magic."







Marilyn Manson














"The important
thing is not to
stop questioning."







Albert Einstein


















WELCOME





{content}

{content block='home'}



























{content block='home2'}

[gavinhowells]

Odd, the example in the default "CSSMenu top + 2 columns" template works for you?
It uses single quotes {content block='Sidebar'}, but I guess that shouldn't make a difference.

Just a quick update as i've been tinkering with it for most of the day. Now it seems i cant get any content to appear in the "CSSMenu top + 2 columns" using {content block='Sidebar'} either. I thought it might be something to do with my install so i went to the demo at http://opensourcecms.com/index.php?opti ... iew&id=452 and played around with content on "CSSMenu top + 2 columns" there. I see the edit box 'Sidebar' and type text in but like before this isn't visible when viewing the page.

   

Gavin

[Dr.CSS]

Wow no wonder I've never used table layout...

You may want to change the DOC type to...



I believe it needs the address to find the parsing information...

If it doesn't 'take' the input you will just see a blank space for {content block='xxx'} these will never show in the rendered view, unless you put {literal}  {/literal} tags around it but then it wont show as an editable content box either...

[gavinhowells]

Thanks for taking the time to reply Mark. I'll see if it makes any difference tomorrow and keep you posted!

Kind Regards

Gavin

[gavinhowells]

Wow no wonder I've never used table layout...

You may want to change the DOC type to...



I believe it needs the address to find the parsing information...

If it doesn't 'take' the input you will just see a blank space for {content block='xxx'} these will never show in the rendered view, unless you put {literal}   {/literal} tags around it but then it wont show as an editable content box either...

Ah Mark. You star! It seems to be working. I can't thank you enough!