Обновлённый PHP-Fusion Bogatyr / Free CMS PHP-Fusion 7 Bogatyr / The history of the creation of an improved CMS PHP-Fusion 7 Bogatyr
English
In 2009 it was not like in 2018
In 2009, I tried many CMS and chose PHP-Fusion for its convenience and clarity in the administration and refinement of the code.
In 2009, Wordpress was a heavy engine. Since only since version 4 has caching.
In 2009, MODX was also very raw and didn’t even bother to enter the html code correctly in the admin panel.
In 2009, Bitrix did not understand the insertion of HTML code by default and did not have any buttons for editing it.
But it was full of govnosaytov for selling links in Sapa on Wordpress, DLE and Joomla.
Joomla has an incomprehensible admin panel, Drupal is even more incomprehensible. DLE - paid.
40% of webmasters are sick of Wordpress code (according to a survey in VK in 2017). Wordpress code is inconvenient and incomprehensible. So to rule the topic for a long time and painfully. I ruled a lot.
In 2009, PHP-Fusion looked better than other CMS.
At that time, PHP-Fusion looked very good compared to other engines. Because it had normal menus, articles, a forum, photo galleries. The main disadvantage was the lack of an online store for PHP-Fusion.
I remember versions 6 and 7 of PHP-Fusion. 7.00 left in 2009. 6 - in 2008. The difference is that the site on version 6 was broken for me and introduced malicious javascript, but 7-ku was not broken. That's what's great! Fundamental innovations, of course, are few. But for PHP-Fusion you can easily write your extensions.
How I started to collect mods and plugins
I've been working with PHP-Fusion since 2009, and almost always I wanted to improve something in the engine.
I queried on the forum, made changes to PHP-files, saved all versions of the changes.
Over time, the changes accumulated, and making them one at a time for each new site became inconvenient. Similarly, it was a matter of updating the database (adding new rows to the tables and installing the pallets).
And I had the idea to combine all the files I changed into the archive, and all changes to the database - to the file of the installation of changes.
At first I had 3 archives: fashion, plugins and forum mods. Then I began to make 1 archive for everything. It is more comfortable.
I have long wanted to make a multilingual site
In a few years I learned that in order to correctly display French, German and other umlauts (which are not in the English alphabet), it is unreasonable or to use their national locale (which does not support, for example, Russian), or to put the version on UTF8.
I assumed that every five years I would need some text on the site in German, and occasionally customers came across multilingual sites, so I started making the Bogatyr version and the local to PHP-Fusion also on utf8.
After a couple of years I translated my sites to utf8. All worked well, but now php-files on utf8 became the main ones, and then I already re-saved all the modifications in win1251. Some sites I still have in win1251. So I have to percode all updates.
So, what is next
About a year in 2014, I realized that my development path for PHP-Fusion (testing and building all the plugins and mods in one collection) is the most correct one.
A lot of old PHP-Fusion sites have been shut down. There is nowhere to download single files.
And every year more and more plug-ins and mods need to be installed if separately.
Adaptive design for smartphones has come into fashion. And it was necessary to deeply redo the CMS, and not minor edits in one file.
I changed a lot of files. But I try to maintain maximum compatibility with different versions of PHP-Fusion. |