Three problems: Previsualisation, RSS & Captcha

[Fabien]

Hi Garvin,

"But in one of the files, the BOM must happen. Else, it would not be in your Blog's output."
Probably. But I have always installed S9Y with the same softwares without any problem.

"Which method did you pick exactly, how did you search for the BOMs?"
I opn the files with Notepad++ which says the conding method (ANSI, UTF without BOM, UTF without BOM, etc.) and can convert between them.

"Did you check the stackoverflow link to search for files that have a UTF-8 BOM? "
No. I cannot do this on my server.

This morning:

1. I have download again Serendipity 1.6 distribution.
2. I have deleted all the files on my server (except my template and the config_local).
3. I have uploaded all the file from the distribution with Filzilla in binary mode.

And without any modification the two problems where still there.

So, can the S9Y1.6 distribution be corrupted? Can the problem be in any way with my provider (it seems weird, but…)?

Warm regards,
Fabien

[garvinhicking]

Hi!

I am really 100% sure that in one of your files a UTF-8 BOM must be. If you cannot perform the search on your own, I can offer to search through your files - for that I would need the FTP access to download all files, and then I could grep on them locally on my machine for the UTF-8 BOM (of course you could basically also do that, you do not necessarily need to execute it on your server, only make sure the files you download are downloaded in BINARY mode).

Di dyou check your config_local for a UTF-8 BOM? And if your templates contain .php files, did you check those?

The official s9y release files hosted on Sourceforge are not corrupted, I just checked them. Did you download the release there, or on github? If you used the github download I would check that, because those are compiled on github machines, and I haven't checked that out yet.

Best regards,
Garvin

[Fabien]

Hi Garvin,

I have downloaded S9Y 1.6 from this site (http://www.s9y.org/12.html): the link on the page send to SourceForge.

I have verified the config_local and templates files: no BOM and they don't have beend changed before the installation.

I send you the FTP parameters by MP.

Thanks for your help and your patience.
Warm regards, Fabien

[garvinhicking]

Hi!

I found it!

It's inside this file:

./plugins/serendipity_event_commentsearch/UTF-8/lang_fr.inc.php

That file is not available in spartacus, so I think you might have created it yourself? Save the file without BOM (or I can do that for you, if you prefer, since you currently gave me the FTP access) and all should be well. You might need to create a new blog entry to refresh the RSS feed cache before this displays properly; Captchas should immediately start to work.

Best regards,
Garvin

[Timbalu]

BOM BOM BOOM!
SCNR... A Real Bom Day....

[Fabien]

Hi Garvin,

Oh shit! I had just installed this plugin a few days before upgrading to 1.6. So the problem was probably there before the upgrade. And this plugin is not in the standard distribution, so uploading again and again was useless…

I don't understand the link between this plugin and the captchas and rss but…

… IT WORKS PERFECTLY NOW!

THANKS! THANKS! THANKS!

Warmest regards,
Fabien

PS 1: I was not aware of this BOM problem. I'll be watchful now.
PS 2: you can use the corrected lang_fr file and put in in Spartacus.

[garvinhicking]

Hi!

Glad this solves that; and I'm glad you remained patient during this issue which took a bit longer.

I don't understand the link between this plugin and the captchas and rss but…

The link actually is this; all language files and all installed event plugins must be loaded every time the s9y blog is accessed, so also for Captchas and RSS feeds those plugins are loaded (because they might hook into that functionality). PHP parses all language files and plugin files before the first output is made. And if any plugin or language files emits any linebreaks, UTF-8 BOMS or whatever, they would always get appended to every output.

PS 1: I was not aware of this BOM problem. I'll be watchful now.

Sadly it's really something that shouldn't cause such trouble. PHP6 is meant to solve this UTF-8 BOM problem so hopefully in the future this will not really be so troublesome anymore.

PS 2: you can use the corrected lang_fr file and put in in Spartacus.

Good idea, I will try to do that!

Regards,
Garvin