I see it would need a config_db hook as well so that the setup.sql file gets used...
Also I think you could have left in the pay.php hook... Even though it's not used by any released plugin it might be useful, and we can't exclude someone wrote a plugin using that hook for their freeseat installation, and when they update their plugin would stop working.
I think it makes sense that all pages have at least two display hooks (for people to insert html at the top and bottom of the page) plus, for pages that are the target of a form somewhere, one processing hook that is invoked before any output starts.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Right.
I see it would need a config_db hook as well so that the setup.sql file gets used...
Also I think you could have left in the pay.php hook... Even though it's not used by any released plugin it might be useful, and we can't exclude someone wrote a plugin using that hook for their freeseat installation, and when they update their plugin would stop working.
I think it makes sense that all pages have at least two display hooks (for people to insert html at the top and bottom of the page) plus, for pages that are the target of a form somewhere, one processing hook that is invoked before any output starts.