HTML TemplatesFlash TemplatesWordPress ThemesDrupal Themese107 ThemesFree Joomla TemplatesXOOPS ThemesphpBB StylesFree SMF ThemesMagento ThemesOpenCart ThemesosCommerce TemplatesPrestaShop TemplatesVirtueMart TemplatesZen Cart TemplatesTumblr Themes
Website Templates | Coupons | Blog | News | Reviews | Tutorials | Login

News

Why we make b2evolution (vs. WordPress, Joomla and Drupal)

Collections view in b2evolution CMS v7
Different Collections of various kinds which can be sections of a single site or even separate websites

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.

Read more...

Posted May 4, 2019 | 4:46 am

View all b2evolution News...

Drupal Association collaborates on new, long-awaited tech initiative as featured on TagTeamTalk

The Drupal Association collaborated on Automatic Updates, one of the Drupal Core Strategic Initiatives that was funded by the European Commission. We are excited to partner with MTech, Tag1 Consulting, and the European Commission FOSSA program on this new initiative and share information with you about its features.

Automatic Updates has three components.

Public safety messaging

This feature pulls a feed of alerts from Drupal.org directly into Drupal's administrative interface. This helps ensure that critical Public service announcements (PSA) or Security Advisories (SA) from the Drupal security team will be seen directly by site owners. 

  • This provides yet another communication mechanism before an update so site owners can verify they are ready for an upcoming update, before it lands.

  • The feed of alerts comes directly from the feed of PSAs and SAs that the security team and release managers are already producing. 

  • This will vastly increase the ability of the Drupal project to get the word out about critical and highly critical updates - ensuring the community can respond fast. 

Readiness checks, or “Pre-flight” checks

These automated and extensible readiness checks are built into the Automatic Updates system to verify that a site doesn't have any blockers that would prevent it from being updated.

  • These checks are slated to run at least every 6 hours on a site via Drupal Cron and will inform site owners if they are ready to auto update their site.

  • Examples of the readiness checks include:

    • Is the site is running on a read-only file system?

    • Have any files included in the update been modified from what they should be? 

    • Does the site still need to run database updates, etc.? 

There’s about 8 or 9 of these readiness checks and some are warnings (Cron isn’t running frequently enough to automatically update the site in a timely manner) and some are errors (the file system is read-only). Warnings won’t stop automatic updates, but errors will.

In place updates

Finally, the key pillar of the automatic updates feature is the update itself. Drupal.org generates a signed and secure package of files which can be overlaid atop the existing site files in order to apply the update. 

  • This update package is downloaded as a signed zip file from Drupal.org. The automatic updates module on the site then compares the signature of the zip file using drupal/php-signify, which is based on BSD’s Signify and libsodium to verify the package.

  • It then proceeds to backup the files about to be updated and updates the site.

  • If all goes well, the site is upgraded. If something fails, the backup is restored.

  • Many workflows are supported and you can customize how the updates are performed. Updates can flow through your CI/CD system, be staged for review and approval, and or automatically go live.

In the past few weeks, the Drupal Association has been invited to participate in TagTeamTalks, a new recorded talk series about various tech projects supporting the Drupal project. This bi-weekly format provides real-time shared collaboration and informative discussions. 

TagTeamTalk launched its webinar focused on Automatic Updates this week. The group dives deep into the nuts and bolts of Drupal's groundbreaking Automatic Updates feature, and the strategic initiative sponsored by the Drupal Association, MTech, Tag1 Consulting, and the European Commission. Guests include Preston So (prestonso), Contributing Editor at Tag1 and Moderator of the TagTeamTalks; Michael Meyers (michalemeyers), Managing Director of Tag1; Lucas Hedding (heddn), Senior Architect and Data and Application Migration Expert at Tag1; Fabian Franz (Fabianx), Senior Technical Architect and Performance Lead at Tag1; and Tim Lehnen (hestenet) CTO at the Drupal Association. Read the TagTeamTalks blog.

Content marketing is one of the most effective ways to promote your brand and capabilities - it has been a really powerful approach for the organizations that I’ve worked for,” said Michael. “The goal is to give our team an opportunity to talk about the cool things they’re working on and excited about and to share it with people. It helps get the word out about the latest developments in the open source communities we contribute to, and it promotes Tag1’s expertise - it helps us recruit new hires, and drives new business.” 

Meyers is the Managing Director of Tag1, and has been involved with the Drupal community for over 15 years. He was Founder and CTO of the first venture backed drupal based startup, CTO of the first Top 100 website on Drupal, and VP of Developer Relations at Acquia before joining Tag1.  “The great thing about TagTeamTalks is that it doesn’t take a tremendous amount of effort or energy. Our engineers are subject matter experts. We decide on a topic for the week, spend 15 minutes brainstorming a rough outline as a guide, and then record the talk. We don’t want to be rehearsed. The conversation is what makes it dynamic and enjoyable for us to do, and for people to listen to. And, the team loves it because they want to talk about what they are working on, and this format doesn’t take a lot of time away from what they enjoy doing most - writing code.” 

Hedding is one of the top 20 most active contributors to Drupal 8, and is also the Drupal Core Migrate Sub-system Maintainer, a core contribution mentor, and a D.O. project application reviewer. “Auto Updates has long been one of the most requested Drupal features, it is a capability the platform really needs that will help everyone using Drupal. Now that the alpha is available, we need to early adopters to start using it, we need feedback so we can continue to improve it. We also need to get more people involved in development, and we need to raise more money from organizations to support the project - it might sound like a simple feature, but it is actually really complex and requires a lot of effort. TagTeamTalks are a great way to get the word out and to enlist support from the Drupal community.”

Lucas added, “The European Commission provided generous funding for this initiative. The focus has been exclusively or largely around the European Commission’s features and functionality. The funding is running out very soon. There is a need for other people to help continue to build Automatic Updates by adding the features they need with their developers or by providing funding.”  

“It is critical for us to spread the message and make that call to action; that this is a community-driven effort and that without continued community support, it is not going to be as successful or as robust in the timeframe that we would like,” said Meyers.

The first year of funding from the European Commission provided for readiness checking, delivery of update 'quasi-patches,’ and a robust package signing system. The focus of this first phase of the Automatic Updates initiative has been on support for security updates in particular. 

In the second phase, as yet unfunded, we hope to extend this foundational work in the following ways:

  • Provide more robust composer support. The first phase of the automatic updates project should be compatible with composer-ready sites, but as the site’s composer.json file and vendor directory of a site change from the default, then more controls and though need to be implemented. 

  • Create an A/B front-end controller for the site being updated to further increase our confidence in the success of the update, allow for additional post-update testing and provide an easy mechanism to roll-back the update. This is also when updates will be able to move into Drupal core from the contrib project.

  • Expand to more types of updates (particularly further support for contrib updates), and also handle multiple updates in a row, for sites that are several versions behind. 

To accomplish all of this, we will continue to seek more funding and more partners. 

“I’m looking forward to seeing where this goes now that we have the first release out, ” said Hedding. “ There’s a larger community needed to get this initiative completed.”

The initial alpha version of the Automatic Updates module can be tested by the community right now. The plan is to: demonstrate Automatic Updates at DrupalCon Amsterdam this month, complete the scope of the funded work by the European Commission by the end of this year, and stabilize Automatic Updates by DrupalCon Minneapolis in May 2020. 

“The Automatic Updates initiative is designed to reduce the friction in keeping a Drupal site secure and up-to-date. The team behind the initiative is architecting a robust system, secure by design, and building components that can be shared with the broader PHP community,” said Tim Lehnen.

Many thanks to MTech, Tag1 Consulting, and the European Commission FOSSA program for funding this initiative. The Drupal Association is proud to be a part of this initiative.

Read more...

Posted October 3, 2019 | 9:40 am

View all Drupal News...

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 News shortcode {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 Download plugin with batch userclass options
  • Fixed issue in Forum plugin with forum mderator userclass recognition (#3814), with the Userlist shortcode links (#3809), and added placeholder option in {SEARCH} shortcode
  • Several Forum template 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!


Read more...

Posted May 29, 2019 | 3:00 am

View all e107 News...

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...

Update (2019-06-24): Please note for Geeklog v2.2.1 we plan to up the minimum PHP version required to PHP v5.6.

Read more...

Posted June 7, 2019 | 6:09 am

View all Geeklog News...

Joomla 3.9.12 Release

Joomla 3.9.12

Joomla 3.9.12 is now available. This is a security fix release for the 3.x series of Joomla which addresses one security vulnerability and contains over 30 bug fixes and improvements.

Read more...

Posted September 24, 2019 | 6:00 am

View all Joomla News...

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
Upcoming version 3.71 is pre-released in Japanese as well. New features in 3.71 are:
  • 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!
Nucleus CMS 3.70 is available for download from download page.

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 Team

Read more...

Posted January 27, 2016 | 12:24 am

View all Nucleus News...

Server Maintenance

Hello,

Today, Monday September 23rd from 9:00 PM (UTC) until 11:00 PM (UTC) we will be performing some maintenance on the infrastructure that powers www.phpbb.com and several subdomains of phpbb.com.

This downtime applies to our various sites, including, but not limited to:
https://www.phpbb.com
https://area51.phpbb.com
https://tracker.phpbb.com
https://wiki.phpbb.com

This downtime will not affect any other installation of the phpBB software other than www.phpbb.com. However, the version check in your administration control panel might give a temporary error message.

Many thanks,

The phpBB Team

Read more...

Posted September 23, 2019 | 9:02 am

View all phpBB News...

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!

Read more...

Posted April 24, 2016 | 5:55 am

View all Plone News...

Five 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

Read more...

Posted August 20, 2015 | 6:19 am

View all PHPNUKE News...

Re: SMF & Wordpress

If you really want it that simple, there are some Wordpress forum plugins.  SMF may be overkill.

Read more...

Posted October 16, 2019 | 5:28 pm

View all SMF News...

Empowering Generations of Digital Natives

Technology is changing faster each year. Digital literacy can vary between ages but there are lots of ways different generations can work together and empower each as digital citizens. No matter whether you’re a parent or caregiver, teacher or mentor, it’s hard to know the best way to teach younger generations the skills needed to […]

Read more...

Posted October 16, 2019 | 1:03 pm

View all WordPress News...

XOOPS 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 SourceForge

Read more...

Posted January 1, 2017 | 12:51 am

View all XOOPS News...

About | Contact | FAQ | Privacy Policy | Terms of Use

© 2006-2019 ├╝berbytes LLC