Page 3 of 3

Re: [UPDATE]

Posted: Tue 2. May 2006, 09:32
by Alex123
flip-flop wrote: [UPDATE]At this time 02.05.06 06.37 (European time) there is no "clean" 1.2.6DEV (including CR LF) available. :cry:

Gruß Knut
What do you mean by that, flip-flop :?:

Posted: Tue 2. May 2006, 09:55
by flip-flop
Hi,
What do you mean by that, flip-flop
The last full stable version 1.26 at sourceforge.net hasn´t include the CR LF at "End Of Line".
I think that´s a problem for some WIN-FTP programms.

See the posts above.

Gruß Knut

Posted: Tue 2. May 2006, 10:25
by Oliver Georgi
the last 1.2.6 is not called DEV anymore. So proof your infos before posting.

And yes, there are some files containing MAC line breaks. Normally this is no problem. So use 7zip to decompress files and FileZilla or SmartFTP to transfer. Next release will not contain a Mac line break anymore.

Oliver

Posted: Tue 2. May 2006, 12:46
by flip-flop
the last 1.2.6 is not called DEV anymore. So proof your infos before posting.
Yes it´s my fault, but tell me please how did you describe this version? --- STABLE, official, unofficial or nothing???
I have created a patch for 1.2.x releases. Before this is published as official I would like it to be tested
At 27/28.04 the text for this version sounds like this: "I have created a 1.2.6 release. Before this is published as official I would like it to be tested".

I have tested it. Works fine for me and stable. Cache permanently disabled at all switches. Sites output feels a little bit slower. But it´s ok.

Gruß Knut

Posted: Tue 2. May 2006, 13:20
by Oliver Georgi
It's no dev anymore. So it is a stable release.

Oliver

Posted: Tue 2. May 2006, 16:07
by s_zwerg
Oliver Georgi wrote:So use 7zip to decompress files and FileZilla or SmartFTP to transfer.

Oliver
So I did (Zip: 7-Zip 4.32, FTP: FileZilla 2.2.18 on WinXP, using AUTO as transfer type) and got the same problem.

Posted: Tue 2. May 2006, 16:22
by Oliver Georgi
Sorry - then I don't know.

I will re-upload a "clean" release.

But this is definitly not the problem of phpwcms. There must be a misconfigured server setting or whatever.

Oliver

Posted: Tue 2. May 2006, 16:37
by flip-flop
@s_zwerg
What is the result using a binary ftp-transfer?

@Oliver Georgi -> A very good idea I think. Seems so the locally used software generates the problems.

Gruß Knut

Posted: Tue 2. May 2006, 16:40
by s_zwerg
flip-flop wrote:@s_zwerg
What is the result using a binary ftp-transfer?
Still running. Success report follows.

Posted: Tue 2. May 2006, 17:04
by s_zwerg
@flip-flop:

No errors after uploading in binary mode.
Seems to be no server misconfiguration.

Posted: Tue 2. May 2006, 19:08
by flip-flop
Hi at all,

I have made a little test uploading a file via FTP during binary and text:
First 16 characters of the file: setup.func.inc.php
3C3F7068700D2F2A2A2A2A2A2A2A2A2A
Upload via FTP - mode Text:

Code: Select all

< ? p h p / * * * * * * * * *  
3C3F7068702F2A2A2A2A2A2A2A2A2A 
PHP can´t interpret this. No EOL he did found.

Upload via FTP - mode Binary:

Code: Select all

< ? p h p . / * * * * * * * * * 
3C3F7068700D2F2A2A2A2A2A2A2A2A2A 
Thats better. But the right EOL at an unix maschine are the #0A.


Here it is: ------------------------------ :D
First 16 characters of the file: setup.func.inc.php including #0D#0A from an older installation
3C3F7068700D0A2F2A2A2A2A2A2A2A2A
Upload via FTP - mode Text:

Code: Select all

< ? p h p . / * * * * * * * * * 
3C3F7068700A2F2A2A2A2A2A2A2A2A2A 
Thats the right way. PHP interpreter has an correct EOL.

Upload via FTP - mode binary:

Code: Select all

< ? p h p . . / * * * * * * * * 
3C3F7068700D0A2F2A2A2A2A2A2A2A2A 
Thats isn´t right but it works.

Gruß Knut