Y digital 3.0 requires the latest PHP version. I asked Jeff Serani, the strategist of events calendar, about the team’s most interesting point in the future of PHP 5.6 and above. The
The main reason for the adjustment is from the perspective of QA and supporting the familiarization team. When dealing with many edge case scenarios, testing at PHP 5.6 or higher is more efficient than narrowing the scope of testing. Switching to the latest version of PHP can also reduce the time required to report errors from older versions. From the developer’s point of view, flashing bells and whistles are good, but providing customers with a better \/ more reliable experience is the key. I have a concern about getting WordPress from other WordPress developers. The. Org rule considers how to forward these changes to the user when the allowed restricted options are considered. Jeff said how modern tribe solves this problem: The
This change makes the communication bit easy. Most users already use PHP 5.6 or later. For the remaining groups, we introduced negligible banner notifications for male users, posted blogs and KB, and provided information to users by updating press releases. As the year-end promotion approaches, we plan to communicate and continue to use similar channels to make people understand the adjustment. This helps to see that many other plug-in authors have similar plans for the product family. As a community, we are responding to these changes. The
Our initial plan for fallback is a building block to prevent users using PHP 5.6 or later from upgrading to the latest version. Fallback is just that users cannot upgrade again. We will introduce you to the edge shell, which you can restore to an earlier version of the plug-in. But we are still planning how best to deal with this situation. You must safely stop supporting legacy PHP, that is, supporting legacy PHP. There are safe and efficient methods. I think there are two important points to consider when deciding to discontinue support for legacy PHP. The first is the communication of change. The second step is to ensure that the normal replacement occurs when the change is made. That’s hard, and we have to finish it first, so let’s start with communication. The
Take caldera forms as an example, which started with a blog post in March. Then, in the case of older versions of PHP, we made the form look like it could not be created. Everything is still working. The new form button has been replaced with a red warning in the PHP version. Because I am very metaphysical, I introduced a complete API to validate versions and warning messages. You can perform the following simple operations to notify affected users of impending changes and add administrator notifications to guide them to resources related to the PHP version. The PHP minimum version header is also set. The
We recently added freemius analytics to caldera forms, so the data is not good. You see some users deleted through it, but the number is small. After the launch of the PHP 5.6+ dedicated release, we decided on an elegant alternative plan based on useful conversations with Zack and Jeff on the event calendar. I do not want to install plug-ins on incompatible sites, causing the site to crash. It is very important to ensure the security of the main plug-in file PHP 5.2. This is our established practice because we have never supported PHP 5.2 on a commercial plug-in. The default plug-in file checks for dependencies and is incompatible with PHP 5.2 \
\
