Page 1 of 1

[ SOLVED ] Some images were missing randomly from pages...

Posted: Thu Feb 24, 2011 11:20 pm
by fearmydesign
Hi, I had this weird issue with one of my pages, it just stopped displaying some images on it for some weird reason. It's using the same template as all my other pages, how could something like this happen? I am using version 1.9.2, I haven't done any updates or anything like that lately.... now, in order to fix this issue, I just added a forward-slash in front of the uploads like such; /uploads/images/etc etc

Has anything like this ever happened to anyone, and did you figure out why? this is really random, and no I am worried that this could happen with any other pages on my site at any time... or even worst with some of my customers sites...

Thanks

Re: Can pages get corrupted just like that...?

Posted: Fri Feb 25, 2011 1:47 am
by Wishbone
Do a 'View Source' and see what path it references.. If it looks correct and hasn't been altered, it's not an issue with CMSMS.

Re: Can pages get corrupted just like that...?

Posted: Sat Feb 26, 2011 12:39 am
by fearmydesign
Do a 'View Source' and see what path it references.. If it looks correct and hasn't been altered, it's not an issue with CMSMS.
Thanks for your response... but I want to know is why some image paths are written 'with' and some 'without' the forward-slash "/" on the same page and still work... is this possible that both of these methods work?

Example:

/uploads/images/etc

uploads/images/etc

Re: Can pages get corrupted just like that...?

Posted: Sat Feb 26, 2011 12:52 am
by Wishbone
Can you give an example page for us to look at?

Re: Can pages get corrupted just like that...?

Posted: Sat Feb 26, 2011 11:26 pm
by fearmydesign
Can you give an example page for us to look at?
http://www.ileansolutions.com

You will see some images are pulling with /uploads/...etc
and others are pulling with uploads/...etc

Re: Can pages get corrupted just like that...?

Posted: Sun Feb 27, 2011 1:02 am
by Wishbone
Hmm.. I see many references to uploads/images, and two using /uploads/images .. I see them all in my browser.. No missing images.

Re: Can pages get corrupted just like that...?

Posted: Wed Mar 02, 2011 8:10 pm
by zenmaster
fearmydesign wrote:
Do a 'View Source' and see what path it references.. If it looks correct and hasn't been altered, it's not an issue with CMSMS.
Thanks for your response... but I want to know is why some image paths are written 'with' and some 'without' the forward-slash "/" on the same page and still work... is this possible that both of these methods work?

Example:

/uploads/images/etc

uploads/images/etc
The first example is saying "find this item relative to the root directory" the second "find this item relative to the current directory".

If the current directory is the root directory then it's the same thing and both will work.

Re: Can pages get corrupted just like that...?

Posted: Thu Mar 03, 2011 3:43 pm
by fearmydesign
Thank you all for your responses... but something weird is going on... for example last week I added an image a blog article on my site and today I checked it and the image is not showing up!!! take a look please:

http://www.ileansolutions.com/cgblog/7/ ... iness.html

??? If it was working fine last week when I added it... and a few days later it just disappears..!!! I haven't even logged into my cmsms... any suggestions ???

My concern is that images will just start randomly disappearing without any warning... which is what's happening now ::)

Thank you everyone ???

Re: Can pages get corrupted just like that...?

Posted: Thu Mar 03, 2011 4:01 pm
by Dr.CSS
You have {metadata showbase="false"} which will stop the <base href= from showing up so when the image says uploads/images/blog/blog-image01.jpg it has no starting point...

Re: Can pages get corrupted just like that...?

Posted: Thu Mar 03, 2011 6:27 pm
by fearmydesign
You have {metadata showbase="false"} which will stop the <base href= from showing up so when the image says uploads/images/blog/blog-image01.jpg it has no starting point...
You are the .CSS { KING: PIN }

Thanks Dr.!