0.2.1: da, li & ff for SNAP, option to disable automatic insertion - #2
Open
petermolnar wants to merge 1 commit into
Open
0.2.1: da, li & ff for SNAP, option to disable automatic insertion#2petermolnar wants to merge 1 commit into
petermolnar wants to merge 1 commit into
Conversation
Owner
|
I don't know, is there is a need for an admin page ? |
Contributor
Author
|
The admin page would be there to apply it automatically or not, to maybe exclude services from the list, and so on. |
Owner
|
oh, ok. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Question: should I create an admin options page for the automatic insertion?
I have an abstract class to take care most of the things, like saving options, w/ multisite support, I could move the plugin to those bases. ( See: https://github.com/petermolnar/wp-common )