Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter inspiringimages

    (@inspiringimages)

    Working fine now, thanks

    Thread Starter inspiringimages

    (@inspiringimages)

    Thanks Josie,

    As suggested I’ve FTP’d the installation and overwritten the existing files, all seems OK (but then I didn’t have any issues before). Thanks for your rapid assistance.

    Regards
    Andrew

    Thread Starter inspiringimages

    (@inspiringimages)

    Thanks Josie,

    I thought that would be the case but worth asking.

    Regards
    Andrew

    Thread Starter inspiringimages

    (@inspiringimages)

    OK, I’ve spent some time trying to bottom this.

    It turns out that the only significant difference between my test server version (which works) and my hosted version is that the configuration variables max_file_uploads, upload_max_filesize and post_max_size are all specified in a format like 25M whereas on my hosted system they are specified in bytes (both seem to be legal and are strings).

    As I read it (and I’m no PHP coder) when you parse them in ewz_to_mb you split $sizestring into the leading numeric part and the trailing text part. When you feed in a string containing only numbers, the $mat array has undefined content (I guess), hence the error.

    I have tested this by changing my php.ini to the ’25M’ format and the error goes away. Maybe the majority of hosts use this format so the problem hasn’t popped up?

    So the error is cured for me now, still can’t track down what is turning the Assert statements on, doesn’t seem to be php.ini or htacceess butI’ll continue looking.

    Thread Starter inspiringimages

    (@inspiringimages)

    Thanks for the prompt reply.

    I’ll have a look round now I know what I’m looking for and get back with any findings.

Viewing 5 replies - 1 through 5 (of 5 total)