Joomla 3.9 – the Privacy Tool Suite release!

The Joomla project team has just released Joomla 3.9 that has over 250 improvements and the highly anticipated Privacy Tool Suite.

The latest nightly build of Community Builder 2.2.1 and all Joomlapolis add-ons work just fine with Joomla 3.9 also when the Joomla privacy tool suite is enabled. You can see everything in action on our demo site.

phpList 3.3.4 released

phpList 3.3.4 released: 3 new features, 5 UX improvements, 23 fixes

New functionality has been added

Checking lists your campaign is sending to, or has been sent to, is now even easier. To avoid possible mistakes in lists you have targeted, each campaign in the ‘Active’ and ‘Sent’ tab will have the lists conveniently displayed.

The new ‘Copy to draft’ button for sent campaigns will allow your campaign to stay in the sent tab with its own statistics, even if you wish to resend the content again.

Joomla 3.8.12 Security and Bug Fixes Release

The Joomla project team has recently released version 3.8.12 that addresses 3 low level vulnerability issues and fixes over 20 bugs.

Community Builder 2.2.1 (latest build) and all Joomlapolis add-ons work just fine with Joomla 3.8.12. You can see everything in action on our demo site.

The Joomla 3.8.12 is a highly recommended upgrade for all Joomla 3.x series sites. As always, before any Joomla upgrade on your live website, take a backup just in case anything goes wrong.

CB Paid Subscriptions 4.2 released!

CB Paid Subscriptions (CBSubs) 4.2 is here with 25 new features and 52 bug fixes!

CB Paid Subscriptions (CBSubs GPL) 4.2 is mainly a features and maintenance release that requires Community Builder 2.1.4.

Of the 25 new features, we would like to focus on the following:

  • Many Improvements in admin area with better search and batch actions
  • Minor improvements in front-end area with better subscription workflow
  • New payment gateway for Stripe with autorecuring payments and SEPA support
  • Improvements in PayPal Pro with new Payflow API and Paypal Advanced with support for new partners
  • Quickpay payment gateway for new API
  • Support for PHP 7.1 and 7.2

Revive Adserver version 4.1.0

This version of the world’s most popular, free, open source ad serving system contains several enhancements and improvements (described in detail below) and some bug fixes. The most important enhancements are: support for HTML5 ads (beta), new delivery rules for whitelisting and blacklisting domains, and a WYSIWYG editor for HTML banners.

Below is a list of enhancements and improvements included in Revive Adserver v4.1:

  • We added a new (optional) setting to prevent a user from being redirected to the landing page associated with a banner, when the banner has been deactivated or when the campaign it belongs to is no longer active. In such cases, impressions and clicks on those banners will no longer be counted either.
  • When generating invocation codes (tags), there is a much shorter comment than in earlier releases (long comments can be switched on while generating tags if so desired).
  • In the user interface, a number of terms have been renamed, to bring the language used into line with modern terminology used in the advertising industry:
    * ACLs are now Delivery Options;
    * Delivery Limitations are now Delivery Rules;
    * Targeting Channels are now Delivery Rule Sets.
  • We added some new Site Delivery Rules, to enable white-listing or black-listing based on hostnames and/or registerable domain names. The development of this feature has been sponsored by a generous donor who has asked to remain anonymous.
  • We added a new security feature to invalidate all the active sessions of the current user when changing or recovering their password.
  • We added the option to use TinyMCE as a WYSIWYG HTML editor (just like in WordPress) when creating and editing HTML banners. The editor is switched off by default, for
    increased backwards compatibility, but it can be enabled by default via the user interface account preferences. This preference is ignored when editing HTML ads containing scripts or iframes in order to avoid inadvertently altering 3rd party tags. The development of this feature has been sponsored by a generous donor who has asked to remain anonymous.
  • We added a new {img_url_prefix} magic macro that will print the configured http/https images URL during delivery, depending on the calling protocol.
  • We added (beta) support for HTML5 banners, allowing the upload of banners in IAB compliant ZIP file formats. The development of this feature has been sponsored in part by Aqua Platform, a company specializing in Revive Adserver hosting at enterprise scale.
  • We added support for ordering advertisers, campaigns, banners, websites and zones by the date each was last updated, on the main index page for each, to make finding recently updated entities easier in large installations.
  • We added automatic switching to the mysqli driver when mysql is selected as the database type in the configuration file, but the mysql extension is not available (and vice versa).
  • We added custom events for Javascript Async delivery, allowing the website to better interact with Revive Adserver, e.g. to refresh some ad placements or modifying the data that is sent to and received from the ad server.
  • There have also been many other smaller enhancements and improvements, described in detail in the release notes.
  • We have fixed numerous bugs, and there are also some non-backward compatible changes, so please make sure you carefully study the release notes.

Important: this v4.1 release has a Non-Backwards Compatible Change. Support for PHP 5.5 has been dropped and Revive Adserver now requires at least PHP 5.6.0.

Full release notes for v4.1.0 can be found on our Github page.

Download, install and upgrade

Revive Adserver v4.1 is available for download now.

Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server being used meets the minimum technical requirements.

What is XNU?

XNU kernel is part of the Darwin operating system for use in OS X and iOS operating systems. XNU is an acronym for XNU is Not Unix. XNU is a hybrid kernel combining the Mach kernel developed at Carnegie Mellon University with components from FreeBSD and C++ API for writing drivers called IOKit. XNU runs on I386, X86_64 for both single processor and multi-processor configurations.

1 2 3 25