News
Why we make b2evolution (vs. WordPress, Joomla and Drupal)
Some time ago, I got asked why we are making b2evolution. I started writing a blog post about it, but didn’t finish it at the time. Today seems like a good day to round it up ;)
Short answer: we want a system that saves us time on website maintenance. Even more so when you maintain multiple websites: you don’t want to handle upgrades and tuning multiples times.
b2evolution does that by reducing the number of independent pieces that need upgrading and catering. Everything you need is integrated in a single package, including user accounts, forums, private messaging, documentation publishing, and of course: blogs. And that single package can support multiple web sites on a single installation. Finally, it can auto-upgrade itself.
Granted, the amount of integrated features can be a little overwhelming at first, but if you’re in for a rather large and complex website, or better yet: multiple websites, nothing will save you as much time as b2evolution in the long run (meaning: once initial setup is done).
Personally, I have built many websites since I started crafting my first HTML pages at UPenn in 1993. And, throughout the years, I’ve used many different tools to get that done. It started with a plain text editor. That lasted for several years. Then came Dreamweaver. That was a syntax coloring editor with automation functions that made it easy to maintain sites with dozens or even hundreds of interlinked pages. But as the web continued to grow and the amount to publish was growing likewise, I quickly found myself in a situation where I had to publish thousands if not tens of thousands of pages. That is when I had to switch to what we called at the time "a blog engine". Today we call it a CMS: Content Management System.
At the time I chose to use b2 as my blog engine. But, as it turned out, it quickly got abandoned by its author. So I picked it up where he left it, and started extending it under the name b2evolution. Eventually, we rewrote the whole thing. That is the short story. You can find a longer version an dhow it relates to WordPress here.
But today, why continue building our own rather than using another CMS like Wordpress, Joomla or Drupal?
Well, because I tried them and they failed me. They’re probably fine if you want to publish a single website and if that site doesn’t require too many plugins to get to what you need. But in my experience, they quickly require too many different plugins and modules to be installed, upgraded and maintained separately and/or too much custom code, with an even higher maintenance burden. Furthermore, they completely break down if you want to publish many different websites.
The goal with b2evolution was to have everything we needed integrated into a single platform. Install it once. And upgrade it once when there is a new release. No need to upgrade each plugin independently and solve incompatibilities with the other plugins along the way. Beyond that: with a single install of b2evolution, we can actually run multiple sites at the same time. Again a huge time saver on upgrades.
Today b2evolution integrates all the features we need for every new website we create, including user forums, private messaging, email lists, reference materials, multilingual support and of course: multiple blogs.
No other CMS (content management system) is as integrated as b2evolution. No other CMS is as easy to maintain.
b2evolution saves us so much time on website maintenance compared to any other existing solution. In our experience, nothing else even comes close.
That’s why we do it ;)
What could make b2evolution even better?
For a long time b2evolution has insufficient documentation. I believe we hugely improved on that point in the last couple of years. Check out the Online Manual here.
We’ve also been thinking of making feature presentation videos for a long time to show them in action. We have always pushed that to "next month", knowing there was a new user interface coming out soon. That’s an endless loop. At some point we’ll need to just bite the bullet and start cranking out those videos!
Finally, we recognize some users have a hard time getting b2evolution up and running, despite web hosts offering automated install. The auto installers work fine but many times there are other configurations on the web host side that create problems (e-g: Mod Security).
Thus we are wondering if we should offer "b2evolution hosting" ourselves, i-e: a SaaS (Software as a Service) version of b2evolution. That means you could just sign up for a plan that matches your needs and get going. You’d never need to worry about installing b2evolution, about .htaccess files, Linux file permissions, apache modules, upgrades, backups, etc.
Your thoughts on those matters are welcome in the comments below!
Happy May everyone! :)
Original post blogged on b2evolution.
Drupal 8.7.0 is available
What’s new in Drupal 8.7.0?
This release introduces powerful features that will help us all take Drupal to a whole new level. The new stable JSON:API core module as well as the intuitive and accessible stable Layout Builder are game-changing.
Layout Builder is stable
The Layout Builder module was originally introduced as an experimental module in Drupal 8.5.0. As of Drupal 8.7.0, Layout Builder is now stable and ready for production use! It provides a powerful, accessible, mobile-friendly page building tool that is fully compatible with revisions, workflows, and in-context previews.
The Layout Builder enables site builders to rapidly create layout templates for content that speed up the development process. It also permits content authors to easily customize individual pages with unique layouts.
The interface allows drag-and-drop management of your content blocks. It additionally supports keyboard controls and toggling the content preview on and off to give the content editor complete control of their experience while building their layouts.
The result of all these features is a state-of-the art content management solution that streamlines mass-production while also supporting unique creation. 123 individuals and 68 organizations contributed to this feature. More than 40 of the individual contributors volunteered some or all of their time.
Check out this demonstration based on the core Umami demo:
The team is working on implementing translation support for layouts in a future release.
New stable JSON:API support
JSON:API support is now included as a stable core feature. The JSON:API specification is an easy and fast way to build decoupled applications. Drupal core's JSON:API module is feature-complete and easy to use with robust out-of-the-box support and simple setup. JSON:API makes it simpler than ever to build ambitious projects. 147 contributors and 76 organizations contributed to this new feature. Among the individual contributors, more than 50 volunteered some or all of their time.
For example, by simply navigating to a URL like https://example.com/jsonapi/node/article, you can get a list of available articles on your site, and filter further from there, to display your Drupal content in decoupled websites, mobile applications, and so on.
Improvements in experimental Media Library
The experimental Media Library has numerous significant improvements in this release. The Media Library is built on top of the stable Media module, which allows reuse of images, documents, and even embedded remote media like YouTube videos. Items in the Media Library can be managed with drag-and-drop. This release improves the design and accessibility of the user interface, allows inline media creation in the library, and provides more flexible grid and table views. 310 contributors and 122 organizations contributed to this new feature. More than 100 individuals volunteered some or all of their time!
Check out this demonstration based the core Umami demo with Media Library enabled:
There are various tasks left to make Media Library stable in a future release, including WYSIWYG integration.
Revisionable menus and taxonomy terms
Custom menu links and taxonomy terms are now revisionable, which allows them to be used in editorial workflows (similarly to nodes, media, and custom blocks). The Entity system now also provides a new Update API to support conversion of further entity types. It supports converting the schema of any content entity type between non-revisionable or non-translatable and revisionable or translatable, which also works when there is pre-existing data for the entity type whose schema is being changed. All these changes improve core support for the Workspaces module.
New features in the Umami demo profile
The Umami food magazine demo is now more accessible and demonstrates more features out of the box, including a new welcome tour, Layout Builder integration for recipes, and multilingual features. The profile now includes a curated set of Spanish translations, and more languages are in the works. 187 contributors and 84 organizations have contributed to Umami, with more than 60 individuals volunteering some or all of their time.
Umami empowers first-time users to spin up a Drupal project in no time so that they can use to evaluate Drupal and learn about its major components.
On the way to Drupal 9
Drupal 8.7.0 includes optional support for Twig 2 (for sites that can patch their Composer configuration). Optional support for Symfony 4 also received a lot of contributions and should be complete in 8.8. This is important work, because Drupal 9 is planned for June 3, 2020 and will update various dependencies, primarily Symfony. Testing Drupal with updated third-party dependencies will help us get better feedback on our compatibility with these dependencies and any difficulties sites encounter when upgrading.
What does this mean for me?
Drupal 8 site owners
Update to 8.7.0 to continue receiving bug fixes. The next bugfix release (8.7.1) is scheduled for June 5, 2019. (See the release schedule overview for more information.) As of this release, sites on Drupal 8.5 will no longer receive security coverage. (Drupal 8.6 will continue receiving security fixes until December 4, 2019.)
Note that new Drupal 8.7.0 installs now require at least PHP 7.0.8. Existing sites still work on at least PHP 5.5.9 for now, but will display a warning. Drupal security updates will begin requiring PHP 7 as early as Drupal 8.8.0 (December 2019), so all users are advised to update to at least PHP 7.0.8 now.
Updating your site from 8.6.15 to 8.7.0 with update.php is exactly the same as updating from 8.6.14 to 8.6.15. Drupal 8.7.0 also has updates to several dependencies. Modules, themes, and translations may need updates for these and other changes in this minor release, so test the update carefully before updating your production site. Read the 8.7.0 release notes for a full list of changes that may affect your site.
Drupal 6 and 7 site owners
Drupal 7 is fully supported by the community until November 2021, and will continue to receive bug and security fixes throughout this time. From November 2021 until at least November 2024, the Drupal 7 Vendor Extended Support program will be offered by vendors.
Drupal 6 is no longer supported.
You can now use the stable migration path for monolingual Drupal 6 and 7 sites with the built-in upgrade user interface. For multilingual sites, there is experimental support; please keep testing and reporting any issues you may find.
Translation, module, and theme contributors
Minor releases like Drupal 8.7.0 include backwards-compatible API additions for developers as well as new features.
Since minor releases are backwards-compatible, modules, themes, and translations that supported Drupal 8.6.x and earlier will be compatible with 8.7.x as well. However, the new version does include some changes to strings, user interfaces, internal APIs and API deprecations. This means that some small updates may be required for your translations, modules, and themes. Read the 8.7.0 release notes for a full list of changes that may affect your modules and themes.
This release has advanced the Drupal project significantly and represents the efforts of hundreds of volunteers and contributors from various organizations, as well as testers from the Minor release beta testing program. Thank you to everyone who contributed to Drupal 8.7!
e107 v2.2.1 Bootstrap CMS Released
After the release of 2.2.0, we have been working on crushing some bugs that did have some impact on functionality.
We have therefore decided to release 2.2.1 sooner rather than later, and recommend everyone to update.
Please note that the 2.2.0 release was a major release with some important notes. Please refer to the previous post for more information on that release, including an overview of numerous great new features which were added!
New features:
- Added new
Newsshortcode{NEWS_AUTHOR_EUF}to retrieve Extended User Fields (e.g.{NEWS_AUTHOR_EUF: field=biography})
Fixes & Improvements:
- Fixed a database check/update issue that occurred when the database name contains a hyphen (
-) (#3800) - Fixed an issue with the Menu Manager preview not loading in some cases (#3815)
- Fixed frontpage button link to Admin Area (#3775)
- Fixed an issue with inserting a new custom page when using PHP 7.3 (#3812)
- Added tablerender id to error pages (#3801)
- Fixed an issue with (un)seralization (#2990)
- Fixed comment author avatar not showing correctly in comment form (#3813)
- Fixed issue in
Downloadplugin with batch userclass options - Fixed issue in
Forumplugin with forum mderator userclass recognition (#3814), with the Userlist shortcode links (#3809), and added placeholder option in{SEARCH}shortcode - Several
Forumtemplate optimizations for Bootstrap 4 (#2969) - Several PHP 7.3 compatibility improvements
For a full list of changes, please go here.
Please see our downloads section to download a copy.
Thank you for continuing to use e107. Please feel free to tell us what you think about e107 in our Gitter chatroom!
Posted May 29, 2019 | 3:00 am
Geeklog v2.2.1 Release Expected Quarter 4 of 2019
I just wanted to give an update on Geeklogs next release. I was hoping it would happen by the summer but that unfortunately looks not to be the case. We are hard at work on Geeklog v2.2.1 and hope to see the first beta by September 2019.
Some of the new features in Geeklog v2.2.1 include:
- New PHP Session Handling System (move to use PHP built in system)
- A Likes System for articles, comments and plugins (can include likes and/or dislikes)
- PHP 7.2 and PHP 7.3 support
- Updates to the latest library files for CKEditor, jQuery, Uikit, etc...
- Plus more and a large number of bug fixes as well...
Joomla 3.9.8 Release
Joomla 3.9.8 is now available. This is a bug fix release for the 3.x series of Joomla which addresses one bug introduced into 3.9.7 which affects web sites using the French Help Server.
Nucleus CMS is Back (Sort of)
Despite project close announcement one and a half years ago, some enthusiastic Japanese developers and users have been maintaining Nucleus CMS core.And today, we are pleased to announce Nucleus CMS 3.70. This is a direct descent of the original Nucleus CMS, supports the same multiple languages.
Major fixes and improvements in this release are including (but not limited to) the following:
- Enforced password security using phpass library instead of md5 hash
- Default character code set is now utf-8, not iso8859-1
- Added new event PreLoadMainLibs
- Fixed vulnerability described in VCE-2011-3760.
- Support for PHP7 (Fixes in installer, embedded wrapper for mysql functions, etc.)
- [New] Duplicate Item button in the item list screen
- [New] Now you can arrange category order
- ... and more!
You are always welcome to post suggestions and questions for Nucleus CMS in the same old English support forum.
Also, all the core and major plugins are now maintained on GitHub. Please feel free to submit issues and of course pull requests.
Beside this code base, LMNucleus a fork from Nucleus by Leo is also available at http://nucleus.slightlysome.net/ and GitHub.
Cheers, and happy blogging!
The Japanese Nucleus TeamPosted January 27, 2016 | 12:24 am
phpBB 3.2.7 Release
Greetings everyone,We are pleased to announce the release of phpBB 3.2.7 "Bertie’s Force Field". This version is a maintenance release of the 3.2.x branch which resolves issues reported in previous versions.
The fixed issues include, among others, issues with form token validation during login, the inability to change topic types after posting, an issue with viewing private message folders, and potentially incorrectly shortened URL links when using the
[url=] BBCode.Full backwards compatibility for styles released before phpBB 3.2.6 has been introduced, which will enable logins even though these styles have not yet been updated with the latest style changes.
The full list of changes is available in the changelog file within the docs folder contained in the release package. You can find the key highlights of this release on the wiki at https://wiki.phpbb.com/Release_Highlights/3.2.7 and a list of all issues fixed on our tracker at Issues fixed in 3.2.7
The packages can be downloaded from our downloads page.
The development team thanks everyone who contributed code to this release: JoshyPHP, Matt Friedman, mrgoldy, EA117
If you have any questions or comments, we'll be happy to address them in the discussion topic.
- The phpBB TeamPosted May 5, 2019 | 1:18 am
Plone welcomes four students for the 2016 Google Summer of Code
We welcome these promising students exemplifying great diversity in geography and topics, and wish them a great Summer of Code!Posted April 24, 2016 | 5:55 amFive Nights at Freddy's 4 Full Version - Feel the fear one last time
Review
Five Nights at Freddy's 4 is the fourth, and last (supposedly) release in the Five Nights at Freddy's saga. Developed and published by Scott Cawthon, this horror game has delighted all the fans of horror games, and has also raised the criticism from those that say that there are too many FNaF games. This time, you are not a security guard fighting for your life against creepy animatronics. Instead, you are a defenseless kid who struggles every night because of his terrifying nightmares (nightmares about creepy animatronics, of course).
Now, animatronics don't kill you, because they are just nightmares, but they can scare you as they have done since forever. Freddy, Bonnie, Chica, and Foxy have come back, and they have brought new nightmare friends with them. Also, the location is not an office anymore. It takes place in your own room, a room with a bed, two doors, and a dark closet. Each part of the room is dangerous since they are places where the animatronics can hide.
Moreover, the mechanics of the game have significantly changed compared to the previous tree installments in the saga. Now, you do not depend on your vision, or the cameras, because in this release, you don't have them. Now, you have to hear; you have to pay attention to every sound, breath, and laugh, because sound indicates where enemies will come from. It's recommended to play with earphones or with a very high volume. You are free to play with a regular sound volume, but you will not be able to hear your enemies.
Are you ready to say goodbye to your beloved animatronics?
As mentioned, the mechanics have changed. Now, you have nothing more than your senses and a flashlight to defend yourself. You have to control both doors, the closet, and the bed behind you. Animatronics can appear in any of the four places. What you have to do is walk bravely to the doors and the closet, listen carefully and if you hear something, close the door as fast as you can and hold it shut until the sound disappears. In case you don't hear anything, use the flashlight to prevent enemies from coming. The bed at your back has a little Freddy fluffy toy, but sometimes dreadful miniature Freddy's appear, followed by Nightmare Freddy himself. You have to shoo them with the flashlight unless you want Freddy to appear. It can seem easy, but the slightest mistake (using the flashlight when you hear a breath, or not closing the doors in time), will bring an end to the game.
Freddy, Bonnie, Chica, and Foxy have come back, and they have brought new nightmare friends with them
Talking about your friends the animatronics, when you download FNaF4, you will have to face six of them, eight if you take into account the "nonofficial" ones. You already know Freddy, Bonnie, Chica, and Foxy (nightmare version) but let me introduce you to Nightmare FredBear and Nightmare (plainly). All the animatronics in nightmare version are decrepit, broken, and especially scary. They have very long sharp teeth and glowing eyes, but Nightmare FredBear and Nightmare have even longer teeth, and they are very dangerous because they are unpredictable. This is especially true of Nightmare, since he is black and semi-transparent. They start appearing on nights 5 and 7, respectively.
Features
In this version, you can check out the main features of Five Nights at Freddy's 4:
- A new story that reveals what happened in the Bite of the 87
- A gloomy mini-game that allows you to skip the first two hours of the nights (if you are successful)
- Nightmare version of the old and well-known animatronics (Bonnie, Freddy, Chica and Foxy)
- 4 new animatronics: Nightmare, Nightmare FredBear, Plushtrap and Nightmare Cupcake (Chica's cupcake can attack you know)
- A new location
- New mechanics based on the sounds
If you like this horror adventure, feel free to visit the developer's official website to discover all the features before you download it.
System Requirements
You can read here the minimum PC system requirements needed to download and play this game:
- Operating System: Windows XP or later versions
- Processor: AMD Athlon, Intel Pentium @ 2GHz or better
- RAM Memory: 2 GB RAM
- Hard Drive Space: at least 1 GB free available
Posted August 20, 2015 | 6:19 am
Re: How do people get on my site without registering
Thank you everyone for your suggestions I have taken all of them into account and beefed up the questions and added configured post modification from a tutorial I found here. I think I am good for now buttoned up but not stifled
Posted June 20, 2019 | 1:09 pm
WordPress 5.2.2 Maintenance Release
WordPress 5.2.2 is now available! This maintenance release fixes 13 bugs and adds a little bit of polish to the Site Health feature that made its debut in 5.2. For more info, browse the full list of changes on Trac or check out the Version 5.2.2 documentation page. WordPress 5.2.2 is a short-cycle maintenance release. The next […]Posted June 18, 2019 | 11:14 amXOOPS PHPMailer Security Patches Released
The XOOPS Development Team is pleased to announce the release of security patches for XOOPS 2.5.8 and XOOPS 2.5.7.2.These patches includes the latest version of PHPMailer to address a serious vulnerability. All XOOPS users are encouraged to update as soon as possible.
Both full distributions and patch files (from the most recent prior release) for both the 2.5.7 and 2.5.8 series are available.
Any users that are running older XOOPS versions are advised to update to XOOPS 2.5.8.1 now.
Get XOOPS 2.5.8.1
Release files are available on GitHub.
The 2.5.8.1 files are also mirrored on the XOOPS File Repository on SourceForge
Get XOOPS 2.5.7.3
Release files are available on the XOOPS File Repository on SourceForgePosted January 1, 2017 | 12:51 am
