Adicionando suporte as novas funções de term meta na classe de metabox para termos #370
Conversation
This file contains 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
matheusgimenez
changed the title
claudiosanches
added a commit
that referenced
this pull request
Dec 21, 2015
Adicionando suporte as novas funções de term meta na classe de metabox para termos
|
Uhu.. estamos prontos para o 4.4! |
|
Estou arrumando isso daqui ainda xD |
claudiosanches
added a commit
that referenced
this pull request
Dec 21, 2015
Also added code to help migrate to new 4.4 meta meta
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.
Galera, só um adendo, desse jeito que eu fiz aqui eu não estou dando suporte para as versões antigas do WP, somente 4.4 pra cima. Acham que devo mudar isso? Adicionar condicionais verificando a versão?
No mais, essa classe ta funcionando com os campos antigos também (options API), mas sempre dando prioridade ao term meta, isso é, sempre que um campo for salvo da aqui pra frente, vai no term_meta e não no options api. Mas ainda deixei retornando valores do options, verificando por condicional se não existe no term meta e depois buscando no options.
Em breve podemos pensar num script pra migrar os campos antigos e arrancar de vez as funções antigas.
Abraços