Why 1C-Bitrix from December 1, 2019 can turn into a pumpkin
If you have been following the updates of the “boxed version” of Bitrix (not 24) for the last ten years, then you have already noticed that only the store module and its environment are updated. All other modules, as they were once written a long time ago, remain in this state and still receive only tiny changes in order to increase the numbers in the version.
Despite this, presentations of new versions of Bitrix are full of beautiful headlines and try to maintain the illusion of development among potential customers, promising speed, reliability and most important security, confirmed by the old FSTEC certificate
In PHP version 7.2, the mbstring.func_overload directive is deprecated .
It’s kind of like little things, but Bitrix relies heavily on this functionality and requires an overload of all string functions (mbstring.func_overload = 2). This value is verified during product installation and internal testing.
This may be a coincidence, but for Bitrix, the highest supported version of PHP is still 7.1. Support for this version by the language developers will end on December 1, 2019.
If Bitrix doesn’t rewrite the whole legacy code with heroic efforts until December 1, then from this date it cannot be considered safe, since security updates for PHP 7.1 will no longer be released. From now on, it will be somehow not very correct to declare from the scene about super-popular and mega-safe solutions for large organizations and government agencies.
They can just take it and go to 7.2 or 7.3, but there are now problems with some string functions. For example, in the standard forum module when reducing user names.
This superficial record will be some addition to another not very detailed article . I hope that the owners of Bitrix still read Habr, and not just the golden tips from the marketing guru, and these modest notes will force them to spend part of the marketing budget on increasing the productivity of the development department.
The more we discuss bitrix issues, the more likely they are to fix them.
Despite this, presentations of new versions of Bitrix are full of beautiful headlines and try to maintain the illusion of development among potential customers, promising speed, reliability and most important security, confirmed by the old FSTEC certificate
But there are nuances
In PHP version 7.2, the mbstring.func_overload directive is deprecated .
It’s kind of like little things, but Bitrix relies heavily on this functionality and requires an overload of all string functions (mbstring.func_overload = 2). This value is verified during product installation and internal testing.
This may be a coincidence, but for Bitrix, the highest supported version of PHP is still 7.1. Support for this version by the language developers will end on December 1, 2019.
If Bitrix doesn’t rewrite the whole legacy code with heroic efforts until December 1, then from this date it cannot be considered safe, since security updates for PHP 7.1 will no longer be released. From now on, it will be somehow not very correct to declare from the scene about super-popular and mega-safe solutions for large organizations and government agencies.
They can just take it and go to 7.2 or 7.3, but there are now problems with some string functions. For example, in the standard forum module when reducing user names.
Why is this all?
This superficial record will be some addition to another not very detailed article . I hope that the owners of Bitrix still read Habr, and not just the golden tips from the marketing guru, and these modest notes will force them to spend part of the marketing budget on increasing the productivity of the development department.
The more we discuss bitrix issues, the more likely they are to fix them.
All Articles