Forum Replies Created
Viewing 6 posts - 1 through 6 (of 6 total)
-
AuthorPosts
-
Creditas Soluções Financeiras
ParticipantA workaround we have for now is setting up the META_BOX_KEY with wp cli, like the following:
wp config set META_BOX_KEY ${METABOX_KEY}Creditas Soluções Financeiras
ParticipantIn the case we have a custom field like this:
function custom_wysiwyg(String $name, bool $isRequired, bool $hasQuicktags, int $rows, int $max_length, String $tags_allowed, String $formats_allowed ) { return [ 'name' => $name, 'id' => strtolower($name), 'type' => 'wysiwyg', 'required' => $isRequired, 'options' => [ 'textarea_rows' => $rows, 'tinymce' => [ 'block_formats' => $formats_allowed, 'toolbar1' => $tags_allowed, ], 'quicktags' => $hasQuicktags, ], ]; }The validation would work? I did not understand the part of it not working with the Visual tab.
Creditas Soluções Financeiras
ParticipantHello again.
Is there a way to hide the license key from the URL to install it with composer, inside the composer.json?
We do not like the idea of having the license key exposed.
Creditas Soluções Financeiras
ParticipantHello, this question got me confused.
Does that mean that we cannot get updates for MetaBox from our license that we purchased recently?
Creditas Soluções Financeiras
ParticipantThank you. The problem was that we were not using the clone attribute.
Creditas Soluções Financeiras
ParticipantHello!
Thanks for the answer.
-
AuthorPosts
Viewing 6 posts - 1 through 6 (of 6 total)