|
#11
|
||||
|
||||
|
No, there are no garbage characters in the file.
I've checked the settings for my text editor for configuring file types, and here's what they are set at for html files (and all other file types listed as well): ![]() Note that I have it set to detect UTF8 files without a BOM, and I have the setting for adding a BOM to the file unchecked. I've pretty much given up being able to track this down right now. Maybe I'll stumble on what the problem is in the next few days. If I do, I'll post back here and let all of you know. Thanks again everyone for all the help and suggestions - it is much appreciated!
Last edited by dhdesign; 01-14-2008 at 07:28 PM. |
|
#12
|
||||
|
||||
|
Ok, it looks as if your image template file is the banger.
Which FTP client do you use? Did you upload the index.php and template files as ASCII? Could it be possible the client does some changes like adding a BOM? Try using FileZilla, it is free. If you want you can email me your template files to 2ATkg3.de and I'll check them with my editor. If it is the same with a new FTP client and after proving your files, last question is your ISP... perhaps the hoster has some server-side "BOMming" (don't know if this is even possible) |
|
#13
|
||||
|
||||
|
I don't think it is the template. If you validate the image_template.html, you get errors, but the validator isn't seeing the BOM that's causing the validator to break. My guess would be that an addon is causing the trouble. You might want to disable all your addons then revalidate. If it validates with them turned off you know you know where the problem is, you'll just have to turn them on, one by one, revalidating after each. Once you get the error you know which addon is causing the error.
__________________
My Photoblog If you find my help useful please consider feeding the PixelPost Kitty If you're short on cash just feed my ego |
|
#14
|
||||
|
||||
|
Dakwegmo - I've already tried turning off all the addons, and there was no change - the page still wouldn't validate.
Austriaka - I'll get the template files zipped up and in the mail to you shortly. The webhost where this is installed is TextDrive, and they only allow SFTP, which means I have to use WinSCP to upload to the server. I've checked the settings in the WinSCP client, and I've made sure that the transfer mode is set to auto-detect the file type. I had taken a look at FileZilla before, but really didn't care for it. Will have to ask in TxD's forum if it's possible that they are adding something, but the fact that I was able to get this issue resolved for all the template files except image_template.html leads me to believe it's something on my end. I really appreciate all the help!
|
|
#15
|
||||
|
||||
|
Have you tried validating either of the templates that come with PP1.6? If you don't get an error with either of those, then I think you can be sure the issue is with the custom template you're using.
__________________
My Photoblog If you find my help useful please consider feeding the PixelPost Kitty If you're short on cash just feed my ego |
|
#16
|
||||
|
||||
|
I just ran the validator again after changing the theme in the admin panel, first to Simple, then to Horizon. Here are the results:
Simple: image_template.html - failed with the same error (weird characters at the beginning) about_template.html - passed validation browse_template.html - passed validation Horizon: image_template.html - failed with the same error (weird characters at the beginning) about_template.html - passed validation browse_template.html - passed validation The issue seems to be with the image_template.html file in all 3 templates (Simple, Horizon, and mine). Where in the code is the image_template.html file called to display the images? I've looked, and can't find it. |
|
#17
|
||||
|
||||
|
It's going to be a bit of a chore tracking this down. The image_template.html is called from the index.php look around line 258. However, every time a new tag is implemented the contents of the template are changed.
If you haven't already done so, I would consider setting up a test environment on another directory with another database, to see if the issue still occurs in a completely clean install of PP.
__________________
My Photoblog If you find my help useful please consider feeding the PixelPost Kitty If you're short on cash just feed my ego |
|
#18
|
||||
|
||||
|
After exhausting all other methods of finding the problem, including Austriaka taking a look at my template files, I finally broke down and did a clean install as a test to see if I could track down the issue.
Before doing this, I had noticed that my template, along with the 2 default ones, were having a 25px margin added to the top of the page that uses image_template.html - the same page that I was having the problems with the weird characters showing up before the doctype when I would validate the page. This margin only showed up in IE6. Firefox 2.0.0.3 and Opera 9.0 displayed the page just fine. Going on advice given by Schonhose in another thread this AM regarding an ASCII text editor, I downloaded and installed Programmers Notepad on my laptop. I then made sure all of the settings were correct for the encoding and the line endings. Outlined below is the step-by-step method that I used to set up the test install: 1. I downloaded a fresh copy of Pixelpost 1.6 this morning. I used FileZip to open the archive and extract the files to a folder. 2. I used Programmers Notepad to open pixelpost.php and enter my database information. I did not open or edit any of the other files that are part of Pixelpost. 3. I used SmartFTP to upload the files to my server (made sure the file transfer setting was for "automatic" for filetype, and codepage was set to "utf8"). I changed the permissions on images and thumbnails to 777. I went through the installation process, then deleted install.php from the admin directory. 4. I logged into the admin section, went to Options, and made sure those were set properly. I left the template set for Simple. 5. I uploaded 1 image, adding the requested information. 6. I opened the test install in Firefox 2.0.0.3 and the page rendered correctly. Using the validation tool in the Web Developer Toolbar, I validated the html for the page that uses image_template.html. This time, it validated, with no weird characters at the beginning and no warning that there was a byte order mark in the file. I also validated the browse and about pages, with the same results. This template works fine in IE6 - no margin at the top of the image page. 7. I then switched to the Horizon template, and went through the validation process again, with all pages passing validation, and no byte order marks in the files. However, there is one issue with the Horizon template that needs to be fixed. In IE6, on all 3 pages, the area of the header on the right that has the website name is cut off on the bottom. There is no font-size specified in the css file for this <h1> tag, so IE6 is using the default size and the font is too large, causing it to be cut off on the bottom. I would recommend adding a font-size of 20 or 22 pixels to resolve the issue in IE. I have one other question though. Since doing this test install, I opened the lang-english.php and admin-lang-english.php files using Programmers Notepad, and noticed that in lang-english.php, there are both CR and LF at the end of each line. In the admin-lang-english.php file, there are only LF at the end of each line. Most other language files only had LF, but there were a few that had both CR and LF at the end of each line. Are the CR supposed to be in there or not? If not, how do I get rid of them??? |
|
#19
|
||||
|
||||
|
For the last question: save as unix format. That should do it.
__________________
My photoblog, powered by PixelPost 1.9 dev SVN | My Pixelpost Addons | My Cool Photoblog profile
|
|
#20
|
||||
|
||||
|
That fixed it - thanks!!
|
| Post Reply |
| Thread Tools | |
|
|