Quote Originally Posted by lruskauff View Post
What if we just had it set the "all" button if it was saved that way?
Well think about it this way.. First the instructions weren't followed (Pick the all button OR choose categories) then, "accidentally" the entire store is marked as everything to be on sale... Now, spend possibly the 15 minutes of the timeout picking and choosing specific categories to be on sale... Now, hit the save button and all of that individual category choosing is lost... Ohh, and now the absolute entire store is on sale... Not just the few items/categories that were chosen.. Customer navigating the site picks a sale item and as it was the price was barely above cost before the sale.. They buy it, now at a loss to you... Why? Because a button was accidentally selected AND categories were selected at the same time..

Yes a message is necessary, at the time I wrote the above code it was to cause the functionality that seemed most conservative to not cause the problem I just described... Hate to say, too bad for aggravating a store owner, but the whole purpose is to make money not lose it... I didn't have the tools available to look through and figure out what message "method" would be best and to include a language define that doesn't yet exist (other error messages are presented from a defined constant). I've even been thinking about other ways to address the issue without using the search method(s), but instead if statements within the applicable loop to ensure the life of the code without multiple modifications.. You know keep it simple type design. :)