code_id and user_id in a separate db table #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have changed the plugin to store the relation of user_id and code_id in a separate table instead of using one entry in the options table. This should scale much better if you expect several hundred users, who are using the sponsored membership.
I did not succeed using the dbDelta() function to create the table, so I used a simple $wdpb->query() instead. Also, there is no conversion to import the old option setting into the table (yet). So there should be a warning for users who want to update from an older version (or there should be an import function).