(3) If ionCube is really the issue why Scriptcase can’t go beyond PHP7.4, then why don’t they simply sever ties to this “7-people”-company with a falling net asset value of just under GBP 500.000 (check their public UK filings) and work with an encoder/loader-solution who supports PHP8 already? Does Scriptcase has actually a current 2022er-ionCube license? So why don’t they update at the very least their website, downloads, installation pages, etc, so that users can develop & deploy under PHP 7.4 - ASAP?īTW: the current automatic/full-installer for SC 9.7 installs an “ioncube.dll”-file from 2019(!) in the “php”-folder. (2) Scriptcase must be aware of the sensitivity-issue that PHP 7.3 is an “old hat”. (1) How far away is ScriptCase’s source code away from PHP8.0? From PHP8.1? Give us a rough timeline, PLEASE! So here are three main questions I would like to get an honest answer from ScriptCase’s top tier management: There is absolute NO WAY that these companies would run public projects on their websites with EOL-Scriptcase/PHP7.3 deployments! SC lists on their home page “45.000+” developers with corporate logos from global GIANTS like “HP”, “Cisco”, “Siemens”, “Bosch”, “Mercedes-Benz”, etc. That is disgraceful and raises quite frankly legal issues, since SC sold their last major upgrade to v9.7/PHP7.3 just a few weeks before PHP7.3 went into EOL! This de facto DISQUALIFIES current Scriptcase9.7/PHP7.3 to be used by any security compliant company since two (2) months already as of today! Many if not most larger corporations, including universities or governmental entities don’t allow software to be running on their servers which have surpassed EOL!Ĭheck the PHP release & eol-schedules here: On the production side we have tested with PHP 7.4.27 as well without any issues so far.Ĭan Scriptcase support please officially validate that this is a possible workaround until is right, you cannot currently deploy SC code under PHP8.x.īut at least you can develop AND deploy with PHP 7.4 (rather than 7.3), which is crucial because PHP 7.3 is NO longer supported by PHP with security updates as of Dec 6th, 2021. It has worked so far with our projects with almost 300 applications without a single error. The Scriptcase instructions for “manual installations” fail to mention to do the rename, they should update that part. Unzip, rename the file “ioncube_loader_win_7.4.dll” into “ioncube.dll” and put it in the new PHP 7.4 “php”-folder. įrom there download the zipped version of either “Windows VC15 (Non-TS) (64 bits)” or “Windows VC15 (Non-TS) (32 bits)” as needed. The ionCube version number is 11.0.1, released Jan 12th, 2022, Link. Next you need to download the right ionCube PHP 7.4 encoder file and put it into the PHP 7.4 “php”-folder. IMPORTANT: Copy the “php.ini”-file from the PHP 7.3 “php”-folder into the new PHP 7.4 “php”-folder. Unzip the files, rename the folder into “php” and replace the existing PHP7.3-one (do a backup!). Scriptcase 9.7 does work already with PHP 7.4 - at least under Windows and if you do a manual installation (or exchange the “php”- folder from the “standard”-installation). Still, ionCube supports at least PHP 7.4 which gives a little breathing room until when PHP’s Security Support will end. Why don’t the makers of Scriptcase go back to SourceGuardian? I remember earlier versions of Scriptcase were working together with PHP encoders from SourceGuardian, which supports PHP8+ for quite a while now. In terms of PHP8.0/8.1 support, Scriptcase is currently joined at their hips with ionCube who doesn’t have a release schedule at all and are miles behind their competitors.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |