PHP Auto Update Script 1.6 brings even more client-side customizations and tons of under-the-hood improvements.
Today, after almost two months of testing, we release new version of PHP auto updates manager to public. New release not only comes with lots of internal changes, but also introduces new options in user module, so let’s take a look at the most important ones:
Added: option to set custom connection timeout interval for updates engine;
In the previous versions, PHP self-update system used fixed 10 seconds connection timeout for each download. In brief, was the best choice in 99% of situations to update PHP scripts. Recently, some authors started pushing update packages that are more than 100 MB in size even after compression. While it’s not a problem for PHP self-update system itself, it might cause connection drop when user’s connection is slow or author’s server is overloaded. With this in mind, PHP Auto Update Script 1.6 enables authors to configure individual connection timeouts for each product. For example, author can set 10 seconds timeout for all small scripts, and set 600 seconds timeout for complex, heavyweight software. This new option is available for configuration in PHP auto updates manager user module (which authors bundle with their scripts). If author chooses not to configure new option, updates engine will use a default value of 30 seconds.
Keep in mind that increasing connection timeout will also slightly increase server resources usage; therefore, contact us for more recommendations in each situation. Now, let’s see another important change:
Added: additional directory permissions check before updates engine is executed;
Added: debug notification for situations when script’s directory is not writable;
As per good coding practice, each developer should integrate many different checks and verifications into his product, so user can only complete installation if his system fully meets all the requirements. Unfortunately, some programmers skip this important step, causing lots of headache for end users. The most essential check for auto updates manager should be directory permissions check. In other words, user shouldn’t be allowed to run upgrade wizard if he has no permissions to download/write new files into script’s directory. Obvious, isn’t it? Sadly, it’s not the case for some developers… Sure thing, PHP Auto Update Script returns a detailed error if upgrade fails because of invalid permissions, but we believe user should see this notification earlier. But is it even possible?
Yes! PHP self-update system 1.6 automatically performs permissions check and doesn’t allow to update PHP script until user fixes this issue. Just like all other notifications in our products, this one is fully customizable by authors. That is to say, user receives a detailed notification along with suggested solution(s) in his preferred language before he even attempts to perform/upgrade his new/existing installation. Obviously, new options are only available in scripts running user module v1.6 or higher, so authors should update their scripts first. As usually, new options are explained in the documentation. Keep in mind that in order for new options to work, you should also update existing configuration file. Not very sure how to do it? Just visit phpmillion support forums for high-priority assistance.
Improved search, enhanced reports, revised API, upgraded internal libraries, and dozens of other changes.
Beside that, new release of PHP auto updates manager comes with lots of internal changes that greatly improve overall functionality. In other words, system now works even faster, offer better compatibility with PHP 7.3 (which was released just a month ago) and load balancers/reverse proxies (in case you use them). You can see the full list of changes at the Changelog page and automatically update your installation using Software Updates section in administration dashboard. Happy using!