Sonnich

That will be my work around. My client want to move from this ISP to another, as there are other problems. Usually once a year the do something and we have remind them about rights etc. It usually takes them a week and a daily mail to react. After all, once I have copied their data out the will finish with this ISP

Then I need something else...

No, that is not what I am looking for. I made a script so I could try multiple Codepages at once, for the download, and started figuring out which one it right. Knowing that I am in the Baltics then 775 and 1257 were obvuious choices after some failures, and it work - here for now. But how can I get to know what CP to use in other cases? Using no CP conversion on one server causes the filenames to contain wrong charactes, e.g. ü becomes _ (underscore) etc. On another server it is not an issue and I can use the filename directly

I am moved a clients system from one ISP running PHP5.5 to a new ISP running PHP7.2 My problem is coding of filenames when I create zip files, with non English letters. I found this to work with CP775. $dl[$z]=iconv("UTF-8", "CP775//TRANSLIT", $dl[$z]); $zip->addFile($file, implode("/", $dl)); Now, would it be possible to detect what CP to use from the system? I found mb_detect_encoding but it does not tell me much.

I used PHP 11 years ago and I move my clients stuff. I dont see php.ini, not might I have access to it on my clients's ISP's systems. Unless I can create php.ini myself and have it. Sorry, I dont know much here. Some guidelines please....

Hi all My code give this: <b>Warning</b>: file_exists(): open_basedir restriction in effect. File(/tmp) is not within the allowed path(s): (/home/clients/........ I get the tmp folder and check for its existanse and whether it is writeable $t=sys_get_temp_dir(); writelog("t=$t"); if(file_exists($t)) writelog("t1=YES"); else writelog("t1=NO"); if(is_writable($t)) writelog("t2=YES"); else writelog("t2=NO"); Both gives no which is fine, I can process that. I do it to avoid the output above, but I still get that. How should I check for allowed paths? This runs on several systems where I cannot access php.ini or other system stuff.

Yes I would like to fix it. The broken zip I have found. Any suggestions what to look at for the encoding problems? I feel lost and I am asking for help....

Hi all I am updating a old system to transfer files, and implementing download data as zip. My client want to move to a new ISP due to problems with the current ISP The old system run "5.5.38-1~dotdeb+7.1" (not sure how to read it, why plus seven?), and the new systenm "7.2.31-pl0-zoneos". The code, same on both can zip and unzip. However the old system causes me problems as: 1) the new system can handle non English characters, the old cannot, eg replacing Ü with _ and ä with õ. How can I get around this? 2) the old system can make a zip and I can download it. However on win7 and some old zip stuff there I can open it. I cannot upload to the new server, I get error 19, not a valid zip. Same when downloading to win10, it cannot open the zip. 7-zip cannot open it either. The old system can accept the zip from it self. Zips from my windows both 7 and 10 can upload to both as well as zip from the new system. No problems. A work-around - I download the weird zip on win7, unzip and re-zip with windows and upload to the new system. It works, it just leaves me with some weird character. There are 7705 files so I will not correct it manually. So my problems is, some old system running "5.5.38-1~dotdeb+7.1" cannot handle non-English characters and the zip is not valid. Does anyone have any idea how to handle the charcaters, and maybe - why the zip is in an old format not readable by newer systems?

So every server has it own needs?

Thanks for the answer. They system is actually 12 years old and I last tuched it in 2016, cannot remember much. I found my system is on use on 3 servers, with 3 different results Questions: how should I output things? I follewed your ideas and read this about UTF-8. I now changed from 8859 to UTF-8. https://www.w3schools.com/charsets/ When uploading (using <input type=file>) I can upload, and it saves it as is (when I check the uploaded and saved file with WS_FTP. So say Ærøskøbing stays the way it should. Next, I read stuff, using readdir. Looks like readdir reads things from the disk as they are. What is then the right way to output things? echo $fileame; echo utf8_encode($filename); I guess that htmlentities is not the right thing when working with UTF-8. Or is the string itself UTF8, or just plain ASCII? I am new to all this, so sorry for asking. I tried to read but got more confused than smarter in the subject.

Hi all I hope I have come to the right place. My system reads files stored on a drive and lists them to users through plain HTML, I made it 11 years ago and have to refresh my memory. My problem is that filenames seem to come in different formats, to how to decode/encode them is an issue... My users use Scandinavian letters (æøåäöüõ) and it seems like one filename is in one format and another in another format. There is no logic to what format the filenames comes it. All files are ok and downloads as they should, they just dont list well. I tried downloading one with Æ and uploading it again as -2 and it lists differently. Any idea how I can handle this issue?