RidgeStar
About
Locations
Manual
Preface
Introduction
Versions
Version 6.3
Version 6.2
Version 6.1
Version 6.0
Version 5.4
Version 5.3
Version 5.2
Version 5.1
Version 5.0
Version 4.9
Version 4.8
Version 4.7
Version 4.6
Version 4.5
Version 4.4
Version 4.3
Version 4.2
Version 4.1
Version 4.0
Version 3.2
Version 3.1
Version 3.0
Concepts
Construction
Usage
Operations
Questions
Features
Settings
Internals
Appendices
Reference
Service
Logon
RidgeStar

Manual: Versions-Version 5.4

Logontranslateoff
Get Started |Calendar |Locations

August 2018

Version 5.4 is an incremental, but significant upgrade of the RidgeStar Interactive SiteInteractive Site incorporating new concepts and features in the base 5.0 system, as described below:

0. Feature=Responsive provides support for Mobile Devices
RidgeStar (in conjunction with Sound Software) made a strong effort to provide support to Mobile Devices with the delivery of TouchLine, a mobile app distributed via the Apple App Store or Google Play. However, we consistently heard requests to deliver a larger set of functional pages to Mobile Devices, as represented by the website.

Therefore, the 5.4 system offers a "Responsive" implementation that delivers ALL operational pages from the site in a Mobile Friendly format. Sites with Feature=Responsive active will find the narrow presentation most useful for those individuals that are familiar with how the underlying website pages operates, but we're hopeful it will be useful to all Mobile Users.

1. Feature=NWS offers real time weather information
Sites with Location based information (Fields, etc.) can now obtain a real-time display of the National Weather Service available weather data for a specific Location. This offers data for a week at time, thus is only available based upon "Current Date+Time" or for scheduled activities (such as a Match) that has a scheduled Date+Time within the next week.

2. Database storage Engine changed from MyISAM to InnoDB
MySQL database tables are now handled as InnoDB tables to take advantage of row level locking instead of table level locking (to reduce site blockage by long running data activities by one use affecting others).

3. Positions table grouping fields now honors Feature=Multiple
Sites with a Positions table establishing Grouping for Users (usually within the Matches table) can now utilize Feature=Multiple to establish a User definition. This is intended to simplify the number of Positions that need allocation in complex Positions situations.
4. Segment based Alerts can now be dynamically defined via Setting=Alert
Segment entry Alerts can be configured via Setting=Alert to empower the Webmaster with the ability to manage performance elements of the Alert mechanism.

This version of the system is complete and available to existing Clients (contact your account rep)

Enjoy!

- The Development Staff