CMS Made Simple Forums

hello,


firstable i shall make reference to this post of Calguy annoncing future version cmsms 1.9
http://forum.cmsmadesimple.org/index.ph ... #msg225230

12) The behavior of the {content_image} tag has been altered to address common complaints.  Again we've made every effort to retain backwards compatibility.  However, it will now output absolute URLS in all cases.

OK: but i like to know if it is possible to have it works with alias_page
i meen that each content page from one template could get it's own directory images

we tried something like that without success it would be nice in future vesion  to have this kind of use the content would aproach very closely
to the well know CCK Content Construction Kit

Any ideas Thanks

The content image tag can't read a page alias when you are editing the page only when the page is rendered/shown on the front end does it kick in and read page_alias...

Hi! Dr CSS
thank you for answering

i think i have understood the first part of your answer

The content image tag can't read a page alias when you are editing the page only when the page is rendered/

only rendering content or content_image, not editing with page_alias.  WELL

shown on the front end does it kick in and read page_alias...

i don't understand really that bit, is this a question ?

the (normal) content tag {content_image= is working fine in editing image content but we get access only to one directory (images or whatever) what we try to do is in a way (like the drupal module cck, sorry about that ) to give  possibility to our editors to post their own preformated content in each  editorial block

we have ne online block for  title
another for sub title

one or two  for content

one for content_image, but each editor should have only access to is own photo directory (no mess) that,s why we tried this method with page_alias

Now may be there are others issues, as it was seing and annoncing in the roadmap http://www.cmsmadesimple.org/development/roadmap/ for the 2.1 cmsms version

2.1

   * Tree based page permissions
   * Complex content types (think: CCK)
   * More separation of pages and content

any other ideads or should we give up and wait for future versions

A+

Phil Did

This "only when the page is rendered/shown on the front end does it kick in and read page_alias..." means the the {$page_alias} is only read by the smarty engine when the page shows in the front end...

It's not a question, sorry for any confusion...

Re,

Allright then

I guess the only way we still have is to carry on with the (select image) in content page edition and the tag page_image See you

Phil Did