Avoid unless you enjoy regularly fixing update-related problems

I have used this plugin on a number of projects (a few of which were inherited – so not chosen by me). While the plugin generally performs as advertised, I think I have spent more time fixing update-related problems for this plugin than on all other plugins combined! For example, just this morning I was contacted by a client who informed me that ticket availability was again showing on the ticket form – despite having been hidden over a year ago. There “should” be an administrative toggle to disable this, but the method recommended by support is to either hide this using CSS or use a template override. The field was hidden via CSS until an update changed the structure of the form and the field was showing again. This is not a rarity; this sort of thing happens ALL THE TIME. To boot, after the update the previously nicely styled form’s styles were being overwritten by plugin’s stylesheet: colours, fonts and other effects that looked hideous on the site in question. Template overrides are similarly prone to breaking. Like the previous reviewer, I am not a fan of the developer’s ‘rapid development cycle’. I wish they would put more thought and testing into these updates before releasing them. Bottom line: avoid unless you can’t find an alternative or unless you enjoy regularly fixing update-related display & functional issues.