Input for content_image tag
Input for content_image tag
I found the idea of the content_image tag to be very good. It places a dropdown menu right on the first page of page edit and it allows to use a specific image folder. Unlike page_image which has to be looked up under page edit "options" and which only shows images from the upload/images folder.
Unfortunately on most of my projects I can not use content_image, simply because the tag also generates the whole img src html tag around the images url. I mostly use such top page image embedded in a css tag, so content_image is useless in that occasion.
Of course content_image has an option "urlonly" and I expected it to make it deliver the url only, but I could not try it, because as soon as I include urlonly in {content_image dir='x' block='x' urlonly} I only get an error page. Also the description of the tag option suggests it only gets the tag rid of things like "width", "id" etc...
So what I suggest is, to add an option that really makes it produce a pure url, like page_image does. Or make urlonly do that. And if it really does not, like I experienced, make urlonly work.
Greetings
Thomas
Unfortunately on most of my projects I can not use content_image, simply because the tag also generates the whole img src html tag around the images url. I mostly use such top page image embedded in a css tag, so content_image is useless in that occasion.
Of course content_image has an option "urlonly" and I expected it to make it deliver the url only, but I could not try it, because as soon as I include urlonly in {content_image dir='x' block='x' urlonly} I only get an error page. Also the description of the tag option suggests it only gets the tag rid of things like "width", "id" etc...
So what I suggest is, to add an option that really makes it produce a pure url, like page_image does. Or make urlonly do that. And if it really does not, like I experienced, make urlonly work.
Greetings
Thomas
- paulbaker
- Dev Team Member
- Posts: 1465
- Joined: Sat Apr 18, 2009 10:09 pm
- Location: Maidenhead, UK
- Contact:
Re: Input for content_image tag
Trythomahawk wrote:but I could not try it, because as soon as I include urlonly in {content_image dir='x' block='x' urlonly} I only get an error page.
Code: Select all
{content_image dir='x' block='x' urlonly='1'}
Re: Input for content_image tag
Paul, thank you. You are right, this solves both problems.
So I suggest it is just the help page for this tag, which needs some improvement. urlonly='1' is not mentioned there, it just says "urlonly". Also the description could be more clear by include "url, without "img src" tag and options like "width", "title" etc.".
Thank you again,
Thomas
So I suggest it is just the help page for this tag, which needs some improvement. urlonly='1' is not mentioned there, it just says "urlonly". Also the description could be more clear by include "url, without "img src" tag and options like "width", "title" etc.".
Thank you again,
Thomas
Re: Input for content_image tag
I will look into this
Rolf
Rolf
- + - + - + - + - + - + -
LATEST TUTORIAL AT CMS CAN BE SIMPLE:
Migrating Company Directory module to LISE
Migrating Company Directory module to LISE
- + - + - + - + - + - + -
Re: Input for content_image tag
Fixed in SVN
- + - + - + - + - + - + -
LATEST TUTORIAL AT CMS CAN BE SIMPLE:
Migrating Company Directory module to LISE
Migrating Company Directory module to LISE
- + - + - + - + - + - + -
Re: Input for content_image tag
I'd like to see a "browse" option instead of the dropdown to a single directory. my images directory is broken up into many subdirectories. I realise that {content block='image'} would offer microTiny to achieve this, but the simplicity gets lost with this approach.
Re: Input for content_image tag
install GBFilePicker module and put this (example) in your page template:
Note: GBFilePicker has some options that could/should be set in Extensions menu.
EDIT: the assign parameter in this example assigns the output to smarty variable $fpimage. That can be used in other modules or just in template: {$fpimage}.
Code: Select all
{content_module block="filepicker_block_1" module="GBFilePicker" assign="fpimage" label="Grote foto bovenaan" mode="browser" media_type="image" dir="images"}
EDIT: the assign parameter in this example assigns the output to smarty variable $fpimage. That can be used in other modules or just in template: {$fpimage}.
Re: Input for content_image tag
Thanks a lot. Will try that module (never heard of till now). and thanks to google translate i also now understand "Grote foto bovenaan".
Re: Input for content_image tag
You'll probably gonna love this module. You can also use it in ListIt2. Editors like it a lot because they actually see a thumb of the image in stead of a file name.rotezecke wrote:Thanks a lot. Will try that module (never heard of till now). and thanks to google translate i also now understand "Grote foto bovenaan".
Re: Input for content_image tag
nearly perfect.
the JS popup does not show current directory (to browse) on Firefox 23 but works on older FF and Chrome (didnt try others yet). i suppose this is a FF issue.
the JS popup does not show current directory (to browse) on Firefox 23 but works on older FF and Chrome (didnt try others yet). i suppose this is a FF issue.
Re: Input for content_image tag
Here it works fine on Firefox 23 (Windows)
GBFilePicker 1.3.3
CMSMS 1.11.7
GBFilePicker 1.3.3
CMSMS 1.11.7