[mtassinari]

Good morning,

I was looking into the docs, but I couldn't find if such an option exists.

Basically, what I would like is, if encryption of a file fails for some reason, it should be copied unencrypted in the target location.

Does such option exist?

[alastair]

Hi,

I guess you mean encoding of PHP files rather than encryption. Is that right?

Why would such functionality be useful? If encoding of a PHP file fails then it means that the file contains invalid PHP (at least for that encoding source language). Therefore if it were copied then you would have an invalid unencoded PHP file in the target.

Furthermore. as encoding would have continued, it would be difficult to spot that encoding on a particular file (or files) had failed.
_________________
Alastair

ionCube

[mtassinari]

[alastair]

Hi,

Thanks for the clarification.

Would it not be better then to use the 7.1 Encoder, especially bearing in mind that PHP 7.0 reached its end of life 16 months ago? Otherwise, with the scheme you are suggesting, you could end up with many files that were unencoded in the target. You would also need to ensure that you did a 7.0 syntax check prior to encoding (with "php7.0 -l") so as to distinguish between "real" syntax issues and those arising from using the 5.6 Encoder.

If you are using bundled encodings (like the "5.6 & 7.1" option in the GUI), your suggestion also means that the second encoder, that would expect to find bundled encoded files, would have to ignore any unencoded file it found.
_________________
Alastair

ionCube

[mtassinari]

[alastair]

Hi,

Unfortunately I do not think we would add such the feature you suggested to a future version of the Encoder because there is too much risk for the unwary. That is, somebody unfamiliar with the Encoder might alight upon such an option and use it to "fix" the problems they were having encoding.
_________________
Alastair

ionCube

[mtassinari]

Yes, I understand, and honestly agree, thanks for the feedback anyway!

[jimp]

An option to continue would be helpful with bundling. As if stands now, if a single file in a folder to encode fails, the next bundle of the encoder stops on that file and doesn't continue.

My project has some files that are meant for older PHP versions and some for newer versions. The code knows when to use the file or not, so it doesn't matter if those files are omitted from the encoded result since they won't be included anyway. Because the option --bundle and --add-to-bundle apply to the entire folder, encoding with 7.2 first will result in --add-to-bundle on 7.1 and 5.6 with a file that doesn't exist.

This is an edge case that can probably be fixed with some specific command overrides per encoder pass, but regardless the setup is actually difficult to work with because the encoder doesn't have an option to ignore errors and continue. It will require a careful mix of --bundle and --add-to-bundle, also negating the simplicity of encoding the entire folder. If --bundle could create-or-add that would also help.