v2.1.3 -- Cannot Modify Style List

[BrewDrinkRepeat]

I'm setting up for a "summer beers" competition so I'm unchecking all dark beers, high-gravity beers, etc. These changes are not being stored in the database, unfortunately, and all styles remain selectable when adding an entry.

[geoffhumphrey]

The latest commit package fixes this issue - see Issue #622.

[BrewDrinkRepeat]

Thanks! Sorry I missed the original report...

Upload all the new files (except Site > Config.php)?

Brian

On Jun 28, 2016, at 9:33 AM, geoffhumphrey notifications@github.com wrote:

The latest commit package fixes this issue - see Issue #622.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[BrewDrinkRepeat]

Actually scratch that, I think I see on the original issue page that it's just the one file (process_styles.inc.php):

On Jun 28, 2016, at 6:04 PM, Brian Pylant brian@brewdrinkrepeat.com wrote:

Thanks! Sorry I missed the original report...

Upload all the new files (except Site > Config.php)?

Brian

On Jun 28, 2016, at 9:33 AM, geoffhumphrey notifications@github.com wrote:

The latest commit package fixes this issue - see Issue #622.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[geoffhumphrey]

Yes, if you are upgrading from 2.1.0 or later. Otherwise, you'll need to re-enter your config variables due to the upgrade from mysql to mysqli protocols introduced in 2.1.0.

[BrewDrinkRepeat]

I'm running the latest (2.1.3) for this comp.

[geoffhumphrey]

I would upgrade to 2.1.4 copying all files except the config.php file...

[BrewDrinkRepeat]

OK, will do!

Thanks, as always, for your help and responsiveness! Wish I was smarter at this kind of thing so I could help out!

On Jun 28, 2016, at 6:25 PM, geoffhumphrey notifications@github.com wrote:

I would upgrade to 2.1.4 copying all files except the config.php file...

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.