InterWorx Version 5 beta 7 & 4.11.7 build 485 released!

We’re pleased to announce the release of 5 beta 7! This is a large update that includes a significant number of bug fixes and enhancements, and it’s also one of the last releases planned before the full release of InterWorx 5. We’d like to especially thank all of the users who have subscribed to the beta channel and provided feedback!

Interested in trying the beta? All you need to do is subscribe to the beta repository – instructions are available here: http://interworx.com/beta

Below is a summary of changes in 5 beta 7 build 540:

Security Fixes:

  • Fixed Bug: hardlinks could be used to compromise the system via backups (thanks Rack911)
[B]Enhancements:[/B]
  • Added support for multiple SSL certificates on a single IP.
  • Upgraded to php-iworx-5.3.27
  • Added user-specific variables to InterWorx infrastructure
  • Added a javascript 'Check for Updates' button to software updates page
  • Fixed the ability to add multi-layer subdomains
  • Added the ability to lock a secondary SiteWorx user to specific domains
  • New bin/iworx-upgrade.pex file to view status of upgrade versions
  • CloudFlare CDN Plugin taken out of Beta
  • Changed upgrade notice to open in a new tab
[B]Bug Fixes:[/B]
  • Improved handling of corrupt archives during import/restore.
  • Fixed Bug: changing a SiteWorx account's IPv6 Pool now works as expected
  • Allowed the software updates web interface to keep running despite maintenance mode during upgrades
  • Fixed handling of SiteWorx packages with two resellers have the same package name
  • Added additional validation to ensure files aren't listed as backup targets
  • Mass-transfer query accounts showing weird zeros / failing to import
  • Fixed Chrome bug where login fields weren't clickable due to Web-Gl stuff
  • Class was renamed, classes referencing it were not
  • External NFS system health monitor not installed properly
  • Corrected a situation where the usage data UUID might be blank
  • Added the full user agent string to web login data collected
  • Improved display of sidebar graphs in older themes
  • Fixed display of multiple checkbox inputs in heliotrope theme
  • Fixed an issue with a server being stuck in "maintenance mode" if an iworx upgrade was run before the license was activated
  • Fixed an issue with creating SiteWorx backups if the "use_user_quota" iworx.ini setting was turned off
  • Suppressed non-critical extraneous error messages during SiteWorx account import
  • Updated clamav package to make sure virus definitions are installed during initial install of clamav
  • Fixed the detection of ipv6 support on new install
  • Fixed handling/adding of IPv6_enabled to the IWorx INI and the edge case of setting non-existent INI indexes to false
  • Fixed a problem with httpd listening on multiple ports with the same IP
  • Fixed a display issue of the NodeWorx login form in Chrome on Windows7
  • When adding a secondary domain in SiteWorx, the tiny notification near the 'Choose Domain Menu' improved in Heliotrope theme
  • Fixed issue with a couple missing command-queue triggered actions on fresh install
  • Fixed a bug where the InterWorx repositories weren't properly disabled on cluster nodes
  • Fixed issue with triggering of interworx updates on cluster nodes
  • Added versioning to individual elements collected by data collection
  • Fixed the 'Mass Transfer Table' in NodeWorx to not be clipped
  • Fixed errors in rails/gem version display in SiteWorx
  • Improvements to SSL page in SiteWorx .css and .tpl in old themes

Below is a summary of changes in 4.11.7 build 485:

Security Fixes:

  • Fixed Bug: hardlinks could be used to compromise the system via backups (thanks Rack911)
[B]Bug Fixes:[/B]
  • Fixed an issue with creating SiteWorx backups if the "use_user_quota" iworx.ini setting was turned off
  • Fixed a bug where the InterWorx repositories weren't properly disabled on cluster nodes
  • Fixed issue with a couple missing command-queue triggered actions on fresh install.
  • Fixed issue with triggering of interworx updates on cluster node

All InterWorx servers that have auto-updates enabled will be updated according to their subscribed release channel over the next 24 hours. To see the full changelog for these and previous releases, head here: http://www.interworx.com/developers/changelog

Feel free to discuss this release or ask questions here, but for the serious issues, open a ticket at the support desk.