A: Your HTML code should look like:
A: Please refer to The Code Repository section.
A: Please refer to The Configuration Preset section.
A1: Make sure your original code is fully ECMA compliant.
Please make sure that the JS script is fully ECMA compliant; even if it is working it is possible that it does not fully comply with ECMA specifications – web browsers are somehow more relaxed when validating JS syntax against ECMA. The obfuscator is sensitive to that and can produce invalid JS after obfuscation.
A common issue is forgetting about proper placing of semicolon ( ; ) after each statement – please check your original code if it has proper semicolons.
For instance if your HTML included a JS using:
A3: Nevertheless, it is also of course possible the obfuscator to have a bug.
In order to track it down, please turn off all the obfuscation options from your active configuration file:
$config->DO_DECOY = false; $config->DO_MINIFY = false; $config->DO_LOCK_DOMAIN = false; $config->DO_SCRAMBLE_VARS = false; $config->ENCRYPTION_LEVEL = 0; $config->EXPIRATION_DATE = null;
If the obfuscated code is not working with all the options off (yes, it is not really obfuscated with all the options off, but it is still served through the obfuscator), it means that there is a problem similar to the one described at points A1 or A2.
After turning off all the settings, turn them back on one-by-one so that only one should be active at a time. This will test individually each protection feature to see if there is a problem with it. After each turning on please check if the obfuscated code stops working.
If this is the case, please inform us about it and we will investigate further.
It means that no obfuscation was performed.
Alerts are quite self-explanatory and describe the actual problem with high accuracy.
Because the bytecode encryption feature was also active.
Encryption enlarges payload size. The higher encryption level, the higher protection is achieved and the larger obfuscated code will result.
Because the bytecode encryption feature was active.
Using encryption can bring some performance loss because the obfuscated code needs to be decrypted before run.
Yes. Just turn of the minifying feature.
A: Yes it is possible under certain conditions.
Check official PHP documentation to see how to enable remote file opening.
HTML code should look like:
A: Probably yes. Although the script have not been tested on other servers, it should work fine if PHP requirements are fulfilled.
A: Yes, but not so easy.
But, it could be easier just to use some other off-line or on-line obfuscators as well. Also,
A: No. When purchasing you will get the full code, full documentation and samples.
A: Not yet. We are thinking seriously to create an obfuscation engine for WordPress also.
A: All of them. It is a server-side solution and it is independent of the browser used.
A: Licensing terms are imposed by envato.
For more information please visit: http://codecanyon.net/licenses or please ask envato directly.
A: No. But, you are free to play as long as you want with the online demo and also we will more than happy to answer you to any pre-sale questions.