badAd

1.2

1. Support for multisite

2. Shortcode defaults changed

– To settings more likely to be common

1. Settings page improvements

– More shortcode examples and explanation
– Styling is more readable
– Some explanations are more clearly worded
– Layout is unchanged

1. Streamlined database workflow for storing keys

– This is backend behavior which web users won’t notice
– Reduces security risk
– Porting database to new web hosting or refreshing plugin installation should preserve the API connection

1. Developer notes

– Multisite: Callback files are prefixed with the site ID, seamlessly working with both multisite and single sites
– All keys and settings are stored in the database
– The only key stored in the file system is the current test/live public API key, cached in the “callback” subdirectory
– Callback files are created automatically when visiting the admin dashboard, which is the only time they are needed
– Creating callback files via put_contents() is less cost and databse size than creating a custom post type
– Porting the database to a new cloud location should preserve the API connection, whether or not the old plugin folder is ported also
– Callback files are cached in the “callback” subdirectory for API use, but they are largely superflous to web host admins since they are only-always confirmed/created only-always when they are needed
– Visiting the admin dashboard will automatically confirm and/or create the callback file, but the callback is only needed if making or checking the API connection, which requires visiting the plugin settings page in admin dashboard anyway. So, this is moot, but may be useful information for some developers.
– Security improvement: The callback file simply captures and redirects the API connection response to the admin dashboard, which guarantees more security and level permissions checks so script kiddies have less room to mess