Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Routine Update #1

Merged
merged 26 commits into from
Nov 8, 2017
Merged

Routine Update #1

merged 26 commits into from
Nov 8, 2017

Conversation

khanrn
Copy link
Owner

@khanrn khanrn commented Nov 8, 2017

No description provided.

figureone and others added 26 commits September 4, 2014 14:33
Previously there was a block doing multiple checks to ensure it was ok to add
a new term. If it failed a very generic json error response was returned. This
did not allow the user/other devs to understand why a term was not being added.
This commit breaks the checks apart into their own conditionals and provides the
user with better feedback when something has gone amiss.
Updated json response messages on invalid add term
Additional next() to choose correct <tr> row (not the hidden one)
Fix radios in quick-edit
Update the Taxonomy Single Term to allow a default to be specified, and if it's not found, fall back to the option for the default.
This is a better situation for new Posts where it hasn't been set and where the 1st item Alphabetically isn't the desired default.
Update class to add in correction to the Set method:
* do early return if property doesn't exist
* add in check for the default to send through the parse method
* updated variables in __get to use $property as expected
* removed if branch as if the property_exists we return, so this doesn't require the other branch. It will always need to throw exception if not existing..
Update to allow for a Default to be set.
Correct accidental mistype of $this->tax_slug
support hierarchical indentation in select element.
@khanrn khanrn merged commit 7b124fb into khanrn:master Nov 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants