15 replies to this topic

[Destiny67]

I am having a little trouble with this image code here:

<img scr='/style_images/zodiac/{key}.gif'> {content}

I have the images in the right directory and added the names as so to the option content for the drop down like this:

aquarius=Aquarius
aries=Aries
cancer=Cancer
capricorn=Capricorn
gemini=Gemini
leo=Leo
libra=Libra
pisces=Pisces
sagittarius=Sagittarius
scorpio=Scorpio
taurus=Taurus
virgo=Virgo

Images not showing so I guess I haven't done the code correctly.  

[Martin]

If it's for the forum in your signature, the folder/images aren't in there. Going to http://www.dailychat...iac/scorpio.gif gives a 404, and so does http://www.dailychat...e_images/zodiac

If you're unsure how to determine the correct path for your images, let me know step by step how you navigate to the folder in your FTP program.

[Destiny67]

You know when it's been a long day when you have forgotten to upload the images...   

I know I meant to do that....Okay, still not working though. I think I must have missed something else..

[Martin]

The images are there (see the last link in my post), but the first character in the file name is upper-case. Either rename the files, or change the profile field to reflect that.

[Destiny67]

Yeah, I noticed that I had given the Z a capital but changed it back. Still not showing up but thanks for your help.  

[Martin]

Nope, the images have an upper-case char.
http://www.dailychat..._images/zodiac/
Aquarius.gif
Aries.gif
Cancer.gif
Capricorn.gif
etc

[Destiny67]

I keep changing it around to try and see what is working.   The characters are back in small case but not working.

Thanks though for trying to help.

[Martin]

Chocco, on 26 January 2011 - 08:11 AM, said:

I keep changing it around to try and see what is working.   The characters are back in small case but not working.

Thanks though for trying to help.

For some reason, there are still have a capital first letter in the image names.

Try this as the code for the dropdown instead:

Aquarius=Aquarius
Aries=Aries
Cancer=Cancer
Capricorn=Capricorn
Gemini=Gemini
Leo=Leo
Libra=Libra
Pisces=Pisces
Sagittarius=Sagittarius
Scorpio=Scorpio
Taurus=Taurus
Virgo=Virgo

That should work.

[Destiny67]

Martin, on 26 January 2011 - 11:21 AM, said:

Chocco, on 26 January 2011 - 08:11 AM, said:

I keep changing it around to try and see what is working.   The characters are back in small case but not working.

Thanks though for trying to help.

For some reason, there are still have a capital first letter in the image names.

Try this as the code for the dropdown instead:

Aquarius=Aquarius
Aries=Aries
Cancer=Cancer
Capricorn=Capricorn
Gemini=Gemini
Leo=Leo
Libra=Libra
Pisces=Pisces
Sagittarius=Sagittarius
Scorpio=Scorpio
Taurus=Taurus
Virgo=Virgo

That should work.

Yeah, tried that but not working neither. It only shows the name in the posting field ie...Libra but not the image.
It must the the image link I am using, something to do with that I presume.

[AndyF]

I think the problem is in the topic view format when you set the custom fields up.

Looking at the page source when viewing one, I see (for example)

<img scr='/style_images/zodiac/Libra.gif'>

src not scr

[Destiny67]

AndyF, on 26 January 2011 - 11:36 AM, said:

I think the problem is in the topic view format when you set the custom fields up.

Looking at the page source when viewing one, I see (for example)

<img scr='/style_images/zodiac/Libra.gif'>

src not scr

Ah, that's the one.   Thank you both for your help.

Going to be awkward now...is there a way to have to have the image underneath the zodiac name at all?

[AndyF]

Try putting a <br /> just before the {content} part in the topic view format.

You 'might' have to put in two. Worth a quick try.

[Destiny67]

AndyF, on 26 January 2011 - 12:01 PM, said:

Try putting a <br /> just before the {content} part in the topic view format.

You 'might' have to put in two. Worth a quick try.

That worked. Actually if there a way for me to remove the 'Libra' name and just have the image? Sorry to be a pain.  

[AndyF]

Try removing the {content} part completely. Not tested

[Destiny67]

AndyF, on 26 January 2011 - 12:25 PM, said:

Try removing the {content} part completely. Not tested

That's it! So much better now. Thanks so much Andy and Martin.  

[AndyF]

The issue this topic was opened for has now been resolved.