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

b2evo 6.10.3 is out!

You will find details about this new release here.

With this new version, we are releasing features that didn’t need to wait for version 7.0 to come out. Yes, v7 is coming soon. It’s just that it’s such a major thing (really !) that it has a lot of little bugs to iron out.

Now, this seemingly small 6.10.3 release is actually a major milestone in b2evolution’s shift from glorified blogs to full-featured Content Management System. In this release you can define Item Types with very refined custom fields. You can then create Items of the desired types. You can use the custom fields in various ways (either in your content or in your skin code) and you can even compare items of same or different types with each other (b2evolution will automatically produce detailed comparison tables like this one).

Once again, we are describing big concepts here and we should actually show some examples. We’re guilty of that again. We’d like to promise we’ll solve that once 7.0 is out, but history tells us we’ll likely be absorbed into v8 by then…

OK, I don’t know how, but we really need to sort that out!!

Original post blogged on b2evolution.

Read more...

Posted September 27, 2018 | 4:38 pm

View all b2evolution News...

Plan for Drupal 9

This blog has been re-posted and edited with permission from Dries Buytaert's blog. Unfortunately Dries' blog does not allow for comments at the moment, feel free to post them here.

At Drupal Europe, I announced that Drupal 9 will be released in 2020. Although I explained why we plan to release in 2020, I wasn't very specific about when we plan to release Drupal 9 in 2020. Given that 2020 is less than thirteen months away (gasp!), it's time to be more specific.

Shifting Drupal's six month release cycle

A timeline that shows how we shifted Drupal 8's release windows

We shifted Drupal 8's minor release windows so we can adopt Symfony's releases faster.

Before I talk about the Drupal 9 release date, I want to explain another change we made, which has a minor impact on the Drupal 9 release date.

As announced over two years ago, Drupal 8 adopted a 6-month release cycle (two releases a year). Symfony, a PHP framework which Drupal depends on, uses a similar release schedule. Unfortunately the timing of Drupal's releases has historically occurred 1-2 months before Symfony's releases, which forces us to wait six months to adopt the latest Symfony release. To be able to adopt the latest Symfony releases faster, we are moving Drupal's minor releases to June and December. This will allow us to adopt the latest Symfony releases within one month. For example, Drupal 8.8.0 is now scheduled for December 2019.

We hope to release Drupal 9 on June 3, 2020

Drupal 8's biggest dependency is Symfony 3, which has an end-of-life date in November 2021. This means that after November 2021, security bugs in Symfony 3 will not get fixed. Therefore, we have to end-of-life Drupal 8 no later than November 2021. Or put differently, by November 2021, everyone should be on Drupal 9.

Working backwards from November 2021, we'd like to give site owners at least one year to upgrade from Drupal 8 to Drupal 9. While we could release Drupal 9 in December 2020, we decided it was better to try to release Drupal 9 on June 3, 2020. This gives site owners 18 months to upgrade. Plus, it also gives the Drupal core contributors an extra buffer in case we can't finish Drupal 9 in time for a summer release.

A timeline that shows we hope to release Drupal 9 in June 2020

Planned Drupal 8 and 9 minor release dates.

We are building Drupal 9 in Drupal 8

Instead of working on Drupal 9 in a separate codebase, we are building Drupal 9 in Drupal 8. This means that we are adding new functionality as backwards-compatible code and experimental features. Once the code becomes stable, we deprecate any old functionality.

Let's look at an example. As mentioned, Drupal 8 currently depends on Symfony 3. Our plan is to release Drupal 9 with Symfony 4 or 5. Symfony 5's release is less than one year away, while Symfony 4 was released a year ago. Ideally Drupal 9 would ship with Symfony 5, both for the latest Symfony improvements and for longer support. However, Symfony 5 hasn't been released yet, so we don't know the scope of its changes, and we will have limited time to try to adopt it before Symfony 3's end-of-life.

We are currently working on making it possible to run Drupal 8 with Symfony 4 (without requiring it). Supporting Symfony 4 is a valuable stepping stone to Symfony 5 as it brings new capabilities for sites that choose to use it, and it eases the amount of Symfony 5 upgrade work to do for Drupal core developers. In the end, our goal is for Drupal 8 to work with Symfony 3, 4 or 5 so we can identify and fix any issues before we start requiring Symfony 4 or 5 in Drupal 9.

Another example is our support for reusable media. Drupal 8.0.0 launched without a media library. We are currently working on adding a media library to Drupal 8 so content authors can select pre-existing media from a library and easily embed them in their posts. Once the media library becomes stable, we can deprecate the use of the old file upload functionality and make the new media library the default experience.

The upgrade to Drupal 9 will be easy

Because we are building Drupal 9 in Drupal 8, the technology in Drupal 9 will have been battle-tested in Drupal 8.

For Drupal core contributors, this means that we have a limited set of tasks to do in Drupal 9 itself before we can release it. Releasing Drupal 9 will only depend on removing deprecated functionality and upgrading Drupal's dependencies, such as Symfony. This will make the release timing more predictable and the release quality more robust.

For contributed module authors, it means they already have the new technology at their service, so they can work on Drupal 9 compatibility earlier (e.g. they can start updating their media modules to use the new media library before Drupal 9 is released). Finally, their Drupal 8 know-how will remain highly relevant in Drupal 9, as there will not be a dramatic change in how Drupal is built.

But most importantly, for Drupal site owners, this means that it should be much easier to upgrade to Drupal 9 than it was to upgrade to Drupal 8. Drupal 9 will simply be the last version of Drupal 8, with its deprecations removed. This means we will not introduce new, backwards-compatibility breaking APIs or features in Drupal 9 except for our dependency updates. As long as modules and themes stay up-to-date with the latest Drupal 8 APIs, the upgrade to Drupal 9 should be easy. Therefore, we believe that a 12- to 18-month upgrade period should suffice.

So what is the big deal about Drupal 9, then?

The big deal about Drupal 9 is … that it should not be a big deal. The best way to be ready for Drupal 9 is to keep up with Drupal 8 updates. Make sure you are not using deprecated modules and APIs, and where possible, use the latest versions of dependencies. If you do that, your upgrade experience will be smooth, and that is a big deal for us.

Special thanks to Gábor Hojtsy (Acquia), Angie Byron (Acquia), xjm(Acquia), and catch for their input in this blog post.

Read more...

Posted December 12, 2018 | 10:38 am

View all Drupal News...

e107 v2.1.9 Bootstrap CMS Released

We're happy to announce the release of e107 v2.1.9!

This release contains some great improvements as well as bug fixes. We recommend everyone upgrade immediately. 

New features

  • It is now possible to override the chosen editor pref (WYSIWYG), using the e107::getForm()->bbarea() method by changing the $options array, e.g. $options['wysiwyg'] = 'tinymce4' (#3330)
  • Added option define('X-FRAME-SAMEORIGIN', false); in e107_config to allow for external websites including an e107 website through an iframe (#3101)

Fixes & improvements:

  • Fixed issue in update routine caused by an incorrect version number (#3302 #3311)
  • Added backwards compatibility fix to handle old data formatting better (#3305)
  • Fixed issue with multiple userclass selection in the Admin UI (#3249)
  • The CSS file ensuring backwards compatibility for non-boostrap or legacy themes (backcompat.css) is now correctly loaded
  • Fixed issue with LAN's not loading properly on contact.php page
  • Fixed issue with parsing the sign (#3307)
  • Fixed issue with 'To' textbox not showing in mail-out functionality (#3303)
  • Fixed issue with missing navigation text in Admin Area when using 'medium' width devices
  • Improved support for SVG icons (#1958)
  • Fixed several issues related to the displaying of comments (#2425 #2281 #2937)
  • Fixed issue so 'Items per page' option is now respected on custom pages (#3188)
  • Added default custom fields to Bootstrap 3 template (#3103)
  • Improved support for Cyrillic characters on registration and login (#2440)
  • Plugin Builder generated output improved with examples of custom filter and batch options.
  • Fixed an issue with the language packs not displaying in the Admin Area (#3059)
  • Added e_gsitemap addon to News and Download plugin (#2606)
  • Fixed an issue with error pages and redirection (#3179)
  • Added new event triggers and notifications for the Forum plugin: user_forum_topic_created_probationary, user_forum_topic_updated, user_forum_topic_moved, user_forum_topic_deleted, user_forum_topic_split, user_forum_post_created, user_forum_post_updated, user_forum_post_deleted, user_forum_post_report
  • Added BBcode template for Forum plugin (#3317)
  • New preferences in Forum plugin which allow to choose between BBcode or TinyMCE editor (#3318)
  • Fixed issues with Forum plugin URLs (#3171)
  • Fixed URL issue in Forum plugin when moving a forum topic (#3244)
  • Improved Forum parsing: forum titles are only shown using plain text (no HTML or BBcode) (#3245)
  • Fixed an issue in the forum plugin when marking a forum topic as 'read' (#3338)
  • Fixed issue in the featurebox plugin which caused debug information to show (#3290 #3074)
  • Fixed issue with incorrect 'update required' message showing for the featurebox plugin
  • Several PHP 7 compatibility fixes
  • And dozens more fixes and improvements

For a full list of changes, please go here.

Please see our downloads section to download a copy.

Important Update

Anyone experiencing core-prefs backward compatibility issues after this upgrade, please use this patch

Thank you for continuing to use e107!


Read more...

Posted August 22, 2018 | 10:00 am

View all e107 News...

Geeklog v2.2.0

Geeklog v2.2.0 is now available for download and is the recommended version for all production sites.

New features and fixes in this version include:

  • [Feature] Added Uikit 3 framework and new theme Denim_Three
  • [Feature] Blocks can now appear in more than just the left or right column. Block Locations can now be added by plugins and themes
  • [Feature] New CSS and JS processor to Minify and combine files
  • [Feature] ReCaptcha Plugin now included with the Geeklog Install
  • [Feature] ReCaptcha Plugin now supports Invisible Captcha
  • [Feature] New Passwords must contain a minimum of 8 characters and have at least 1 letter and 1 number
  • [Feature] Two Factor Authentication is available for user accounts
  • [Feature] You can now require all user accounts to have a verified email address (including remote accounts)
  • [Feature] New User Statuses Added (Locked, New Email Required, New Password Required)
  • [Feature] Akismet module now included with the SPAM-X plugin
  • [Feature] Built in Demo Mode
  • [Bug] Fixed After token expired re-authentication returns to a blank page once Authentication is successful
  • [Bug] Fixed Switch Language Block (and COM_getLanguageFromURL) to work on a topic page

... as well as a lot of other improvements and bug fixes. The complete list can be found on Github and in the history text file located in the docs directory of this release.

Note: A bug was found in the installer and Geeklog v2.2.0 that causes an error on servers with PHP v5.3 installed. Therefore for Geeklog v2.2.0 you should consider the minimum PHP version to be v5.5 (note added July 19, 2018)

Note: Make sure your 3rd party Geeklog plugins are updated to the latest version as they are required to use the function COM_createHTMLDocument. This replaces the functions COM_siteHeader and COM_siteFooter. If you are unsure if a plugin supports Geeklog v2.2.0 then either disable it before the Geeklog Upgrade, or uninstall the plugin.

Remember if you would like to chat with any of the community one of the best place to reach us is on Gitter in the Geeklog room.

Read more...

Posted June 26, 2018 | 7:00 am

View all Geeklog News...

Joomla 3.9.1 Release

Joomla 3.9.1

Joomla 3.9.1 is now available. This is a bug fix release for the 3.x series of Joomla including over 40 bug fixes and improvements.

Read more...

Posted November 27, 2018 | 6:45 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...

phpBB 3.2.4 Release - Please Update

Greetings everyone,

We are pleased to announce the release of phpBB 3.2.4 "Bertie's ‘stache". This version is a maintenance and security release of the 3.2.x branch which fixes one security issue and various issues reported in previous versions.

The security issue was discovered with a new exploitation technique called Phar deserialization. An attacker with control over a founder admin account could escalate to remote code execution by abusing PHP’s default unserialization of metadata in Phar files. More information about this technique can be found here.
In order to fix this issue we’ve removed the ability to define absolute paths in the Admin Control Panel. This resulted in the removal of setting the ImageMagick path, so make sure to have the GD image library available instead. A new event to generate thumbnails was added as replacement, so you’re able to write an extension that uses a different image library to generate thumbnails. We would like to thank Simon Scannell and Robin Peraglie of RIPS Technologies for their report and responsible disclosure. The issue has been assigned CVE-2018-19274.

The fixed issues include, among others, compatibility issues with PHP 7.2 and issues with removing users from the newly registered user group more than once.
Among the notable changes are the addition of the list-unsubscribe header to emails sent by phpBB and the ability to reset your password without entering the username.

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.4 and a list of all issues fixed on our tracker at https://tracker.phpbb.com/issues/?filter=14790

The packages can be downloaded from our downloads page.

We recommend following these update instructions for updating your instance of phpBB.

The development team thanks everyone who contributed code to this release: Jakub Senko, MikelAlejoBR, kasimi, Zoddo, v12mike, hubaishan, 3D-I, Matt Friedman, Kailey Truscott, Alec, Alex Miles, Andrii Afanasiev, Anssi Johansson, DSR!, Daniel, Dark❶, David Colón, Ioannis Batas, Jim Mossing Holsteyn, Serge Skripchuk, Toxyy, rxu

If you have any questions or comments, we'll be happy to address them in the discussion topic.

- The phpBB Team

Read more...

Posted November 16, 2018 | 11:58 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: Sched Task Failure - Daily Digest Notifications - Errors in Subs-Post.php

We have 2 thousand members who have all signed up in the last 3 weeks since go live so activity on the site is not an issue.  There are a minimum of a couple of hundred posts per day with users around the world so usage is 24 hours.

So, if it is a know...

Read more...

Posted December 15, 2018 | 9:34 am

View all SMF News...

WordCamp US 2019 dates announced

Save the date! The next WordCamp US will be held on November 1-3, 2019, in beautiful St Louis, Missouri. One of our largest events of the year, WordCamp US is a great chance to connect with WordPress enthusiasts from around the world. This is also the event that features Matt Mullenweg’s annual State of the […]

Read more...

Posted December 13, 2018 | 11:47 am

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-2018 ├╝berbytes LLC