Forum Replies Created
-
AuthorPosts
-
Anh Tran
KeymasterHi Michael,
Can you please share the screenshot of the view(s) screen? I think there is something that we miss in the discussion that might cause the error.
Thanks,
AnhKeymasterHey guys, it's just the browser cache problem. Please use Ctrl-F5 or clear the browser cache and refresh again.
June 2, 2020 at 8:45 AM in reply to: ✅Missing text-domain "Click here to reset your password" #20163KeymasterThanks for your feedback. I've just fixed it and will release a new version soon.
June 1, 2020 at 2:25 PM in reply to: ✅Reciprocal relationships do not follow the order of the admin #19943KeymasterHi,
I commented on the PR. Let's keep discussing over there for better reference of the code.
Thanks for your help!
KeymasterHi Steve,
It's best to use MB Include Exclude.
KeymasterPlease try again. There was a small problem with your account which we've fixed.
KeymasterHi Dave,
It might relate to how
rwmb_metawork with custom tables. We implemented a cache layer for the custom table storage, the code is in theinc/class-rwmb-table-storage.php, which is like this:public function get( $object_id, $meta_key, $args = false ) { if ( is_array( $args ) ) { $single = ! empty( $args['single'] ); } else { $single = (bool) $args; } $default = $single ? '' : array(); $row = MB_Custom_Table_Cache::get( $object_id, $this->table ); return ! isset( $row[ $meta_key ] ) ? $default : maybe_unserialize( $row[ $meta_key ] ); }In this case, as you already use
$wpdbto update data, I'd suggest using it to get data to avoid the caching problem.KeymasterStrange, I see it's similar to my setup. I can think only about the downloaded version via Composer. Can you check the files in the vendor folder to see if they're the same as in the individual plugin?
KeymasterHi Joe,
I've just set up a simple test plugin with nothing than just Meta Box + MB Settings Page and I see the backup & restore field works properly. Please see my video for details:
KeymasterWe added support for FontAwesome in the version 1.2.0, see this changelog and documetation.
KeymasterThank you!
I've released a new version for MB Conditional Logic. The update for AIO will come next week.
KeymasterHey guys, can you help me to test the fix before releasing a new version? Please try changing
parse_conditionsfunction to:private function parse_conditions( $conditions ) { $output = []; if ( ! empty( $conditions['visible'] ) ) { $output['visible'] = $this->parse_condition( $conditions['visible'] ); } if ( ! empty( $conditions['hidden'] ) ) { $output['hidden'] = $this->parse_condition( $conditions['hidden'] ); } return $output; }The previous code does JSON-encode all field settings, which contains something like field description and value, which might break the JSON. The new code only encodes the conditions, which eliminate this issue and might improve the performance as well.
KeymasterThanks a lot for your feedback! Looks like the json encode is the problem. I'll check and fix that.
KeymasterHi Brian, Aart and Austin,
I've debugged with your code and still can't reproduce the error. Although I can add code as Austin suggested, but am not sure the root cause. I also tried Aart's code above, and Austin case with taxonomy and still see nothing.
Can you guys provide me a full code that shows the error?
KeymasterI've added support for
display_nameand other user fields in version 1.7.0. Thanks @pza for your suggestion. -
AuthorPosts