BlogEngine.NET 1.5. Russified assembly with themes and extensions
I compiled for myself the distribution kit of the blog engine BlogEngine.NET (version 1.5.0.7), ready to be deployed on the hosting in seconds and Russified as I need (starting from slugs to a lot of translation improvements in the special file and the code itself, including extensions), with various extensions and with a large package of topics, but I thought that maybe someone else would need it.
Next: for those who do not know what BlogEngine.NET is and what it is eaten with - perhaps the story about it will be interesting, for those who are “in the subject” - a list of changes made in the engine.
BlogEngine.NET is a lightweight and fairly functional open-source blog engine written using ASP.NET technology. It can work both with databases (Microsoft SQL, Microsoft SQL Express, MySQL), and with XML files as storage (by default). With normal blog sizes, there is no difference in performance.
BlogEngine out of the box with a standard theme is an engine developer blog .
BlogEngine is not Wordpress. I repeat: this is not Wordpress. Of course, to compare them (in general, the best blog engines on two different platforms). But BlogEngine is a different class engine: not so extensible with ready-made plugins (although you can write your own quickly and simply), but as easy and fast as possible, providing more functionality than is necessary for an ordinary blogger (not playing with his blog, but just writing it) .
It should not be used where any function may be required: unless you really want to learn ASP.NET by writing the necessary UserControls and extensions. But in cases when you need something easy, fast to deploy, easily customizable, convenient for the end user (BlogEngine dashboard is much simpler and easier than the Wordpress panel) - then it makes sense to try BlogEngine. In the developers FAQ, there is a question “Will my mom be able to use it?” :) The answer is yes, it can. Everything is quite simple and intuitive for both the user and the developer. For a developer this way, all you need is to upload a project posted on the official website in Visual Studio and enjoy the convenience of working with beautifully written code :)
')
Nothing of the sort: many serious companies offer Unix and Windows hosting for the same price. Moreover: Windows hosting usually has a test period. Personally, I am satisfied with the Windows hosting from Infobox and Agave , but I absolutely do not insist. In addition, for BlogEngine .NET hosting requires much less powerful than for Wordpress.
If you are only interested in the ASP.NET platform, then this is a good designer for starting. The BlogEngine code is written beautifully and easily, it is quite understandable even without much training in the field of .NET technology. It is free to dig into it and easily correct it for yourself, at the same time gradually understanding ASP.NET. If you have never worked with ASP.NET, but would like to try - just play around, not trying to write your own CMS from scratch - try BlogEngine, you will not regret. On its basis, it is quite possible to make your own CMS, everything is ready for the usual non-blogging CMS (NB is ready does not mean done ;-) For example, there is support for the tree-like organization of the pages in the control panel, but for the actual website you have to code it yourself for now).
BlogEngine works without a database (although it is quite possible to connect it) and for installation it is required only to upload to the hosting and specify write access for the App_Data folder. Then load the main page; for the first time it will load a little longer, but then everything will happen quickly.
Everything is simple: it was necessary to have on hand a ready-to-install distribution of the blog engine for ASP.NET, Russified enough to give control to the hands of a simple user. So that there are themes and extensions already. Those extensions for which use it is not required to enter UserControls in themes. This, of course, is easy, but not for this case :)
Since BlogEngine has enough problems in Russian-speaking spaces from scratch, and moreover - not all problems are solved by editing scripts (for some reason you need to rebuild the kernel, and then not everyone will open Microsoft Visual Studio for this ...), then rummaged, Failed - and laid out.
Even if no one needs it (after all, we have little use of ASP.NET in such a “light” web segment, which is a pity, a very good technology), then at least I need it. :)
Download, bude anyone interested, you can from my site ; there is a list of used themes and extensions with links to sources. If something works incorrectly (it may well not have been industrially tested :) - write, we will understand. :)
Next: for those who do not know what BlogEngine.NET is and what it is eaten with - perhaps the story about it will be interesting, for those who are “in the subject” - a list of changes made in the engine.
What is BlogEngine.NET?
BlogEngine.NET is a lightweight and fairly functional open-source blog engine written using ASP.NET technology. It can work both with databases (Microsoft SQL, Microsoft SQL Express, MySQL), and with XML files as storage (by default). With normal blog sizes, there is no difference in performance.
BlogEngine out of the box with a standard theme is an engine developer blog .
What is BlogEngine not?
BlogEngine is not Wordpress. I repeat: this is not Wordpress. Of course, to compare them (in general, the best blog engines on two different platforms). But BlogEngine is a different class engine: not so extensible with ready-made plugins (although you can write your own quickly and simply), but as easy and fast as possible, providing more functionality than is necessary for an ordinary blogger (not playing with his blog, but just writing it) .
It should not be used where any function may be required: unless you really want to learn ASP.NET by writing the necessary UserControls and extensions. But in cases when you need something easy, fast to deploy, easily customizable, convenient for the end user (BlogEngine dashboard is much simpler and easier than the Wordpress panel) - then it makes sense to try BlogEngine. In the developers FAQ, there is a question “Will my mom be able to use it?” :) The answer is yes, it can. Everything is quite simple and intuitive for both the user and the developer. For a developer this way, all you need is to upload a project posted on the official website in Visual Studio and enjoy the convenience of working with beautifully written code :)
')
What can he out of the box?
- It’s normal to work with caching (without disturbing the user), mobile devices (they are given a special theme by default), trackbacks, pingbacks and even OpenSearch (blog search can be inserted into the search bar of modern browsers in addition to Yandex, Google, Bing, etc.). d.)
- Tree comments, gravatars, notification of comments on the mail, ping services
- Maintaining a multi-author blog, detailed profiles for authors
- Widgets for tag cloud, twitter, favorite blogs, notification of new posts to mail, drag-n-drop work with these widgets
- Avtoresayz downloadable images
- Use bbcode in comments, preview comments
- MP3 audio player on Flash technology
- and many many others!
Windows hosting is expensive !!
Nothing of the sort: many serious companies offer Unix and Windows hosting for the same price. Moreover: Windows hosting usually has a test period. Personally, I am satisfied with the Windows hosting from Infobox and Agave , but I absolutely do not insist. In addition, for BlogEngine .NET hosting requires much less powerful than for Wordpress.
Who is it useful?
If you are only interested in the ASP.NET platform, then this is a good designer for starting. The BlogEngine code is written beautifully and easily, it is quite understandable even without much training in the field of .NET technology. It is free to dig into it and easily correct it for yourself, at the same time gradually understanding ASP.NET. If you have never worked with ASP.NET, but would like to try - just play around, not trying to write your own CMS from scratch - try BlogEngine, you will not regret. On its basis, it is quite possible to make your own CMS, everything is ready for the usual non-blogging CMS (NB is ready does not mean done ;-) For example, there is support for the tree-like organization of the pages in the control panel, but for the actual website you have to code it yourself for now).
Installation
BlogEngine works without a database (although it is quite possible to connect it) and for installation it is required only to upload to the hosting and specify write access for the App_Data folder. Then load the main page; for the first time it will load a little longer, but then everything will happen quickly.
What is changed in this build?
- The official translation in the file \ App_GlobalResources \ labels.ru.resx has been seriously added and corrected .
- Where possible, the names are translated directly in the code (since not everything is in a separate file, and not everything is possible without a lot of changes in the engine; I hope some day this will change)
- \ bin \ BlogEngineCore.dll rebuilt. Now Russian headlines do not turn into slug'and of the form d09ed0b1d0be-d0bcd0bdd0b5 (a headache for BlogEngine, because here you can’t disable rewriting URLs), but are shown directly in Russian letters (a la Wikipedia). Personally, I like it so much :) But the assembly includes an emergency case and a plugin for transliterating slugs at posts (unfortunately, this does not apply to categories and tags, so the solution did not suit me completely ...)
- Added a fully Russified version of TinyMCE instead of English.
- Added a large number of extensions, all translated.
- Included assembly comes 50 different topics. They did not Russify; nevertheless, very few changes are required (on average, significantly less than in Wordpress themes; a simpler code has an effect); I think that this will not be a problem, although in the future I plan to transfer them if necessary.
What else will need to be done
- Not just translate, but translate the engine qualitatively, especially with regard to the control panel. Remove discrepancies in terms (I confess, there is no end of work ...), and in some places correct the code for correct translation.
- Translate topics (at least a few)
- Improve, improve and once again improve BlogEngine :) In general, I would like the whole translation to go in only one file in the future - and then the site would be translated automatically into the language of the user who has come in without tambourines (ASP.NET technology allows this to be done out of the box). Beauty :)
Finally, why did I do it
Everything is simple: it was necessary to have on hand a ready-to-install distribution of the blog engine for ASP.NET, Russified enough to give control to the hands of a simple user. So that there are themes and extensions already. Those extensions for which use it is not required to enter UserControls in themes. This, of course, is easy, but not for this case :)
Since BlogEngine has enough problems in Russian-speaking spaces from scratch, and moreover - not all problems are solved by editing scripts (for some reason you need to rebuild the kernel, and then not everyone will open Microsoft Visual Studio for this ...), then rummaged, Failed - and laid out.
Even if no one needs it (after all, we have little use of ASP.NET in such a “light” web segment, which is a pity, a very good technology), then at least I need it. :)
Download, bude anyone interested, you can from my site ; there is a list of used themes and extensions with links to sources. If something works incorrectly (it may well not have been industrially tested :) - write, we will understand. :)
Source: https://habr.com/ru/post/64255/
All Articles