I’m trying to use a custom design that we’ve built. The design imports into the designs folder without any errors. I’ve granted permission for public access, made the design live and applied it to my site. When I access the site through a browser I get a whole list of PHP Notices Undefined index: for all but 2 of the graphic files. There are over 50 graphics in this design why only 2 load without problems I have no clue since there is nothing special about them. After all the Undefined index notices there is a
PHP Warning: “Cannot modify header information - headers already sent by (output started at [SYSTEM_ROOT]/core/include/general.inc:174)” then the page tries to load.
If you view the page source all of the links to the graphics files are correct. If you cut an paste them into the browser they do display. One thing I do notice is that th links have the server name in the URL and not the site name but they do load. The links are of the format http://server_name.domain.org/__data/assets/image/825/filename.jpg
I am seeing errors in the apache access log. All of the files that don’t load generate a 404 error and have a odd string preceeding the url like this
“GET /%E2%80%9Chttp://server_name.domain.org/__data/assets/image/868/filename.jpg\” HTTP/1.1" 404 703
Errors in the matrix error log look like this.
[7:Public User][1024:mysource notice][R] (/core/include/mysource.inc:402) - URL “www.site_name.org/âhttp:/server_name.domain.org/__data/assets/image/868/filename.jpg”" not found [SYS0218]
If I apply one of the demo design to the site it works fine. I’m not sure if this problem belongs in the support forum or here. I’m a newbie with Mysource and since this is our first from scratch design I can’t figure out if it’s a design problem or a server configuration problem. Has anyone seen this before or have any suggestions of where else I could look to get this working?
Can you paste your parsefile here? Looks like there are some hidden, non-printing characters in some of the tags that's causing the URL replacement system to break.
[quote]Can you paste your parsefile here? Looks like there are some hidden, non-printing characters in some of the tags that’s causing the URL replacement system to break.
[right][post=“11523”]<{POST_SNAPBACK}>[/post][/right][/quote]
Yes, you are correct. Looking more closely at the parse file I noticed that some of the quotes were the stylized left open/right close quotes around the src tags. The person doing a the web design did a search and replace in a text editor to prepend the mysource_files to each file name and I guess the editor stuck a unicode x93 & x94 quote instead of the plain ole ". Fixing that fixed all the weird URL rewrites but I’m still getting the PHP Notices generated on all the graphic files even though they are showing when you load the page. The only errors I’m seeing are in the mysource logs. Here’s an example.
—Bunch the same error different file names cut from above—
[2006-08-17 12:56:09][7:Public User][8:php notice][R] (/data/private/assets/design/930/design_file.php:186) - Undefined index: parse_r19_c15
[2006-08-17 12:56:09][7:Public User][8:php notice][R] (/data/private/assets/design/930/design_file.php:190) - Undefined index: parse_r20_c2
[2006-08-17 12:56:09][7:Public User][2:php warning][R] (/core/include/mysource.inc:470) - Cannot modify header information - headers already sent by (output started at /core/include/general.inc:174)
I’ve deleted, reloaded and reapplied the design several times without errors until you load the page. I’ve noticed that he’s named all the graphics files parse_X_X.jpg is parse a reserved word for graphics by chance? Any other suggestions?
[quote][2006-08-17 12:56:09][7:Public User][8:php notice][R] (/data/private/assets/design/930/design_file.php:186) - Undefined index: parse_r19_c15
I’ve deleted, reloaded and reapplied the design several times without errors until you load the page. I’ve noticed that he’s named all the graphics files parse_X_X.jpg is parse a reserved word for graphics by chance? Any other suggestions?
[right][post=“11537”]<{POST_SNAPBACK}>[/post][/right][/quote]
Those errors don’t have “.jpg” at the end – are there some references to the files that are perhaps incorrect?
[quote]Those errors don’t have “.jpg” at the end – are there some references to the files that are perhaps incorrect?
[right][post=“11539”]<{POST_SNAPBACK}>[/post][/right][/quote]
Correct again! It was the alt= tag that was written like alt=“mysource_files/filename” didn’t have a .jpg on the end. Changing it to alt=“mysource_files/filename.jpg” fixed it or changing to anything like alt=“my pretty picture” works fine. I’ll assume your parsing routine was was picking up on the mysource_files keyword in the alt tag and trying to do something with it which caused it to gack up the PHP “undefined index” as well as the “Cannot modify headers” error. I would think that it would be best just ignore alt tag contents for the most part. Of course that assumption cost me several hours of troubleshooting time.
Thanks for the help.
[quote]I would think that it would be best just ignore alt tag contents for the most part. Of course that assumption cost me several hours of troubleshooting time.
[right][post=“11541”]<{POST_SNAPBACK}>[/post][/right][/quote]
We can’t ignore any instance of mysource_files/filename.ext because it could appear almost anywhere in the HTML (as an image, inside JavaScript, etc).
I’d also like to point out that the alt tag should really not contain anything like the filename or path to the file itself. The ALT tag is used to represent alternative text. In accessibility standards, it should be used to briefly explain the contents of the image for vision impared users.
If an image is purely for design purposes and contains no information, you should use an empty alt parameter (e.g. alt=""). You should never omit it, though. Otherwise, if your image contains text, you should put the text inside the alt tag.
[quote]I’d also like to point out that the alt tag should really not contain anything like the filename or path to the file itself.
[right][post=“11542”]<{POST_SNAPBACK}>[/post][/right][/quote]
I agree, which is another reason to ignore the contents of the alt tag.
Thanks for the help.