Release Version 2.7.2

Version 2.7.2 is a general bug fix release with a few updates. More details and a complete list of enhancements and fixes is available on the 2.7.2 Milestone, but here are the highlights:

• When judges are using Electronic Scoresheets, they can now:
  • Collapse each major section (Overall Info, Aroma, Appearance, Flavor, Mouthfeel, Overall Impression), helping to quickly navigate through the scoresheet.
  • See a "sticky" visual indication of the areas of the scoresheets where they've provided a score (Aroma, Appearance, etc.). This will help them to quickly see if they've missed providing a numerical score for each requirement on the scoresheet, including Consensus Score.
• A couple of adjustments to the BJCP Points Report XML download to make it more compatible with the BJCP's XML import scripts (Issue #1566 and #1579).
• Added obvious and overt messaging on the My Account page to alert any user that has indicated that they are available to serve as a judge or steward, but has yet to indicate their availability for any judging session. Only pertains to competitions that have multiple judging sessions defined (Issue #1571).
• Fixed bug that excluded display of some winning entries when a competition lists winners by style or sub-style (Issue #1569). Listing winners by table/medal group, by far the most utilized method, is unaffected.
• Fixed bug where uploads of images and documents were being silently rejected by some servers. Had to do with incorrect instantiation of a built-in PHP filter. The problem was fixed and the function surrounding converting file name characters was augmented to be more universally accessible (Issue #1574).
• Aligned printed pullsheets to list entries in the same order as what is displayed on a given user's Judging Dashboard (Issue #1577).

Release Version 2.7.1

Version 2.7.1 is a general bug fix release with a couple of enhancements and updates. More details and a complete list of enhancements and fixes is available on the 2.7.1 Milestone, but here are the highlights:

• Admins now have the ability via Site Preferences to designate up to four incremental per-participant entry limits that will automatically be enforced for a given number of days after the entry window opens.
  • Useful for competitions that have historically experienced high volumes of entrants who add multiple entries as soon as the entry window opens.
  • Ensures competitions can hit their target number of entries while also giving more participants a chance to compete.
  • See Issue #1547 for more information.
• Co-Brewer info is now included on the Admin > Manage Entries list.
• Updated My Account UI to feature more prominent Add Entry and Entries list buttons.
• Participants with alphanumeric AHA member numbers can now have their numbers saved to their account information.
• Czech translation was updated by a native speaker, corrected machine-translated words and phrases.
• Corrected the Co-Brewer information not saving when editing an entry bug.
• Corrected entry requirements for most BJCP 2021 cider styles.
• Corrected a bug introduced in 2.7.0 in the Master Homebrewer Program organizer's report.
• Corrected update failures to the current version from versions prior to 2.5.0.
• Due to accessibility issues, two themes were removed from Site Preferences.

Release Version 2.7.0

Please Note: there was a reported issue with electronic scoresheets with the v2.7.0.0 tagged release. That release has been replaced with this one, tagged v2.7.0.1.

Essentially, there was a reported issue with electronic scoresheets not calculating automatically. One file was changed - /eval/scoresheet.eval.php.

Also reported was a false positive of malware by Windows Defender in one file. This package has passed all scans for malware by Avast locally on Windows and through a battery of tests via virustotal.com. See Issue #1517 for more info.

---

Version 2.7.0 is a fairly extensive release that features a number of bug fixes, enhancements, and updates. More details and a complete list of enhancements and fixes is available on the 2.7.0 Milestone here on GitHub, but here are the highlights:

• Entrants can now specify pouring instructions for any beer style and ABV percentage for any style.
• Entrants can now search for any club name with a special character in the club dropdown when creating or editing their account (e.g., The Brü Club, etc.).
• UI improvements that indicate very explicitly which fields are required when registering/editing an account or when adding/editing an entry. This will ease confusion and emails to organizers from participants that claim they cannot register their account or add an entry, but in fact have missed providing input in one or more required fields.
• Judges and stewards can now disclose if they are part of any brewing team. This helps to alert organizers and judge coordinators whether a particular judge or steward has a potential conflict when assigning to them to tables and/or flights.
• Admins are now able to set a specific date and time when editing of entries will no longer be allowed. Previously, entries could not be edited by participants after the entry window had closed. Admins have the option to extend the editing window beyond that date and time.
• Available to Admins/Organizers on the Admin Dashboard is a reminder and associated list of post-competition tasks they should complete. This reminder will be visible for seven days past the results publication date/time.
• By request of the board of the Master Homebrewer Program (MHP), the download of result data that individual members send to the MHP was deprecated in favor of an all-in-one results report generated by Admins/Organizers for all MHP member participants in the competition. This report is emailed by the Admin/Organizer directly to the MHP Secretary. A reminder to download and sent it is featured in the post-competition tasks alert mentioned above.
• Admins can now specify entry limits for any style type (e.g., beer, cider, mead, etc.). For example, this is useful for competitions that wish to limit the beer entries, but not set a limit for mead or cider. Or vise-versa. Applies to any style type including custom ones.
• Admins can now provide a link to an external site that details past winners. This is helpful for hosted installation owners that keep their own records of past winners or new users who wish to link to past winners published prior to installing BCOE&M.
• Top-Level Admins can now access the Administration Dashboard and all Admin functions when the site is in Maintenance Mode (activated via an explicit boolean variable in paths.php). This allows updating of site data without revealing the changes to non-Admins and the public until ready to publish.

This will be the last major release before version 3.0.0 that will feature updates to the non-Admin user interface and user experience.

Release Version 2.6.2

Updated 2.6.2 - address Issue #1479. New tag: 2.6.2.1.

Version 2.6.2 is a small release that features a short list bug fixes, enhancements, and updates. Most updates were implemented to facilitate the transfer of hosted installations to a new server and domain and, therefore, are generally transparent to users. More details and a complete list of enhancements and fixes is available on the 2.6.2 Milestone, including:

• Entrants can now add their Master Homebrewer Program membership number as part of their account profile.
• Admins now have the option to use the Master Homebrewer Program's Circuit of America points allocation formula when determining Best Brewer and Best Club awards.
• Added Sorting Placards and Sorting Into Tables Placards and Master List reports to assist with organizing sorting day.

Release Version 2.6.1

Updated build addressing various issues. Fixes processing of PayPal payments when PayPal IPN is engaged.

View the changes in the 2.6.1 to 2.6.1.5 comparison.

Like all previous releases, version 2.6.1 features a few bug fixes, enhancements, and updates. More details and a complete list of fixes is available on the 2.6.1 Milestone including:

• Non-judging sessions, if present, will have their own section on the sidebar of all public-facing pages.
• Top-Level Admins can now designate whether an Admin user "who should be able to maintain and administer other aspects of the platform" be allowed to view judging numbers.
• Enhanced compatibility with MariaDB.
• When judges are filling out a electronic scoresheet, the "15 minute warning" modal has been replaced with a less obtrusive warning in the floating progress box. Additionally, if any warnings are present, a warning icon will appear next to the score indicator to inform judges that warnings are present.
• Admins and head judges are now able to designate any Mini-BOS entries at a table from the Judging Dashboard.
  • If there are inconsistencies between judges who did or did not designate Mini-BOS on their scoresheet for a given entry, Head Judges will be alerted.
  • An indicator alert will be present at the top of the Admin > Entry Evaluations screen detailing which entries have inconsistent Mini-BOS indications on associated scoresheets.

Release Version 2.6.0

Updated 2.6.0 Release
New Tag: 2.6.0.1
Address Issues #1442, #1441, #1438, #1437, and #1433 reported since initial release.

---

Like all previous releases, version 2.6.0 features various updates and bug fixes. The largest change is the deprecation of BJCP 2015 styles, along with more Admin control of any custom styles the competition employs. Admins can also add any clubs to the default club list. More details and a complete list of fixes is available on the 2.6.0 Milestone, including:

• The addition of the Northwest Cider Cup styles and electronic scoresheet option.
• The ability for participants to export their individual results data to provide to circuits, including the Master Homebrewer Program.
• Entrants can now specify regional variations for BJCP 2021 style 2A - International Pale Lager.
• Participants on mobile devices can view all of their entry information from their My Account page.
• The ability for judges and stewards to specify industry affiliations while using the Professional Edition – this helps Admins to determine any conflicts of interest when assigning judges or stewards to tables.
• The ability for Admins to add clubs to the default clubs list, customize shipping language, and export results data for circut reporting purposes.
• Admins now have the ability to specify custom style numbers and sub-style identifiers. This helps to fix inconsistencies in the code when assigning them.
• Removal of all deprecated recipe-related columns from the brewing table. Those columns remain in all archived instances, however.
• Updates to BJCP 2021 style 30D: Specialty Spice Beer and BA style Juicy or Hazy Imperial or Double India Pale Ale.

Full change log: v2.5.0.2...2.6.0.1

BCOE&M Version 2.5.0

Edit: THIS RELEASE HAS BEEN UPDATED to incorporate changes requested in Issue #1380 and to address the bug reported in Issue #1381. Current code release tag is 2.5.0.2.

---

Like 2.5.0 Beta, this full release of version 2.5.0 features some fairly substantial behind-the-scenes code changes. Primarily, changes are centered around ensuring that the codebase is compatible with MySQL 8 and PHP 8, as well as converting select MySQL commands to utilize PHP's Prepared Statement protocols.

This release also features, as always, various bug fixes and a few small enhancements. More details and a complete list of fixes is available on the 2.5.0 Milestone here on GitHub; but here are some features and enhancements to highlight:

• Incorporated the Australian Amateur Brewing Championship (AABC) 2022 styles, as well as the 2022 updates to the Brewer's Association (BA) styles.
• Removed the recipe-related UI fields from the add- and edit-entry functions. A future release may incorporate upload of PDF or BeerXML recipe documents for individual entries.
• Added non-judging sessions where potential staff can indicate their availability (Admin Dashboard > Competition Preparation > Non-Judging Sessions). Useful for competitions that wish to have sign-ups for sorting, awards preparation, etc.
• Added a new Staff Availability report provides lists of available people by last name or by non-judging session (Admin Dashboard > Reports > Staff Availability).
• Added the ability for admins to edit all competition dates in one place. (Admin Dashboard > Competition Preparation > All Competition Dates).
• Added the ability for Admins to specify a minimum word count for judge comment/feedback fields when using Electronic Scoresheets (Admin Dashboard > Preferences > Competition Organization).
• Removed the character limit for judge comment/feedback fields when using Electronic Scoresheets.
• Updated PayPal fee calculations to reflect PayPal's changes.
• Enhanced compatibility with Gmail when using PHP's mail() function.
• Enhanced the Awards Presentation when using table/medal groupings as the competition's Winner Place Distribution Method. Admins can now choose to display results by table number (default) or entry count (ascending or descending). This only available from the Launch Awards Presentation button on Admin Dashboard.
• Added an Admin and Staff Notes report (Admin Dashboard > Reports > Notes > Admin and Staff Notes).
• Added a Entry Required Info Scoresheet Labels (Received Entries Only) report option to generate on the fly by table (Admin Dashboard > Reports > Entry Required Info Scoresheet Labels). This report was also cleaned up to provide as much detail as possible as entered by the participant, along with a line for Possible Allergens.
• Added Mini-BOS Cup Mat report options, including a blank report (Admin Dashboard > Reports > Mini-BOS Cup Mats).
• Added Pro-Am/Scale-Up Pullsheet report options (Admin Dashboard > Reports > Pro-Am/Scale-Up Pullsheets). Useful if brewery representative wish to sample more than just the first place entries at the BOS table, for example.
• Added Pro-Am/Scale-Up Cup Mat report options, including a blank report (Admin Dashboard > Reports > Pro-Am/Scale-Up Cup Mats).
• Added Results Report options to sort by number of entries at a table/medal group, ascending or descending (Admin Dashboard > Reports > Results or All Results).

BCOE&M Version 2.5.0 Beta

2.5.0 Beta features fairly substantial behind-the-scenes code changes, thus necessitating the Beta pre-release designation. Primarily, changes are centered around ensuring that the codebase is compatible with MySQL 8 and PHP 8, as well as converting select MySQL commands to utilize PHP's Prepared Statement protocols. This release also features, as always, various bug fixes and a few small enhancements. More details and a complete list of fixes is available on the 2.5.0 Beta Milestone.

This release incorporates the Australian Amateur Brewing Championship (AABC) 2022 styles, as well as the 2022 updates to the Brewer's Association (BA) styles.

Finally, this release removes the recipe-related UI fields from the add- and edit-entry functions. A future release will incorporate upload of PDF or BeerXML recipe documents for individual entries.

The purpose of this release is to gather feedback from users about features and to bear out the underlying code changes. The beta release phase will be at least two months to allow sufficient time for gathering that feedback. A full release is targeted for September, 2022.

This release is not yet stable for production use and should only be downloaded and used by those who very familiar with BCOE&M or those wishing to help find bugs in the software.

BCOE&M Release Version 2.4.0

This release incorporates the recently released BJCP 2021 beer style guidelines. It also features, as always, various bug fixes and a few small enhancements. More details and a complete list of fixes is available on the 2.4.0 Milestone.

BCOE&M Release Version 2.3.2

2.3.2 is mainly a bug fix update, but with a fairly substantial re-write of JavaScript coding governing the add/edit entry form's style choice drop-down and associated display inconsistencies. This release also corrects a PayPal payment bug introduced in 2.3.1 that passed blank payment amounts to PayPal (GitHub Issue #1245). This release also allows the application to run using MySQL 8.0+ (GitHub Issue #1244) and brings it into compliance with the BJCP XML report standard (GitHub Issue #1254). More details and a complete list of fixes is available on the 2.3.2 Milestone.

Full Changelog: v2.3.2...v2.3.2.1