Forum Replies Created
-
AuthorPosts
-
June 27, 2021 at 9:41 PM in reply to: ✅Massive bug found (?) with relationships between posts and users!!!! #29153
Long Nguyen
ModeratorHi friends,
This issue has been fixed on this commit https://github.com/wpmetabox/mb-relationships/commit/bee433a26e25633329b32d6009ce7a8b5f99bcfc
Let me know if it works with your case.
Long Nguyen
ModeratorHi,
To get the employer connected from the job, you need to create a loop to get the relationship nested in the loop that gets the job. Please check this code
{% set args = { post_type: 'job', posts_per_page: 5 } %} {% set jobs = mb.get_posts( args ) %} {% for job in jobs %} <a href="{{ mb.get_the_permalink( job.ID ) }}">{{ job.post_title }}</a> {% set emp_args = { post_type: 'employer', nopaging: true, relationship: {id: 'job_to_employer', from: job.ID} } %} {% set employers = mb.get_posts( emp_args ) %} {% for employer in employers %} <a href="{{ mb.get_the_permalink( employer.ID ) }}">{{ employer.post_title }}</a> {% endfor %} {% endfor %}remember to correct the slug of CPT job, employer, and the relationship ID with your own.
Long Nguyen
ModeratorHi Nicholas,
Instead of doing a lot of works to create a comment system, add the custom fields for comments on the frontend. I think you can follow this topic to add some fields to comments on the frontend and save them to the
wp_commentmetatable of WordPress.
https://wordpress.org/support/topic/add-a-new-field-to-comment-form/Long Nguyen
ModeratorHi,
Thank you for getting in touch.
I think you can do it on your own with a few lines of code. Follow the guidelines
- Get post terms: https://developer.wordpress.org/reference/functions/get_the_terms/
- Get term meta base on the term ID: https://docs.metabox.io/extensions/mb-term-meta/#getting-field-valueJune 27, 2021 at 10:39 AM in reply to: ✅WYSWIYG field - Render Contact Form 7 Shortcode on Front End #29144Long Nguyen
ModeratorHi,
You can use that way to render a shortcode in the WYSIWYG value or use the helper shortcode to render it
[rwmb_meta id="wysiwyg-field-id"]Long Nguyen
ModeratorHi Tron,
Let me explain two shortcodes. For example, I have a post type with the slug
manpower- On the frontend submit page ID = 1867, the shortcode should be
[mb_frontend_form post_fields="title,content" post_type="manpower"]- On the frontend dashboard page, the shortcode should be. The
post_typeattribute does not need to add to this shortcode.
[mb_frontend_dashboard edit_page="1867"]Screen record https://share.getcloudapp.com/yAurKdQp
June 27, 2021 at 10:12 AM in reply to: ℹ️Feature request: Interpret NULL value in field settings to prevent creation. #29142Long Nguyen
ModeratorHi,
To simplify this case, I think you can use conditional logic to show/hide another field slider based on the value of
$slider_activated. Have you tried to use it?
https://docs.metabox.io/extensions/meta-box-conditional-logic/Long Nguyen
ModeratorHi Eddy,
Please see this screen record to distinguish the default Categories box of WordPress and the Custom taxonomy of Meta Box. https://share.getcloudapp.com/nOuPRG57
Regarding the conditional logic, it can work with the field ID from other meta boxes. But you need to add the taxonomy ID instead of the taxonomy name like the Toggle rules. Screen record https://share.getcloudapp.com/kpuDJ04o
Long Nguyen
ModeratorHi,
Thank you for your feedback.
I will check the settings
bind_if_emptyand get back to you later.Regarding the binding address, it only accepts one address component. If you add two components, the error message will appear.
Long Nguyen
ModeratorHi,
It looks like you use the
taxonomycustom field in a custom metabox instead of the default meta box of WordPress, so it might not work.I recommend using the conditional logic option instead of Toggle rules.
Long Nguyen
ModeratorHi,
Please share the credentials via this contact form https://metabox.io/contact/.
June 25, 2021 at 9:37 AM in reply to: ✅Taxonomy Advanced: Set starting node of categories with query_args #29116Long Nguyen
ModeratorHi,
The message shows the error with the field
select_tree, notselect_advancedNotice: Undefined offset: 0 in /Users/hoefs/Essentiell/Websites/htdocs/dab-wp-base/wordpress/wp-content/plugins/meta-box/inc/walkers/select-tree.php on line 52
the query args setting
parentdoes not work with theselect_treefield but works well with theselect_advancedfield. Can you please re-check it?If you want to show all child terms on select, you can create your own custom field type. Follow this documentation to get more details https://docs.metabox.io/custom-field-type/
and refer to this topic https://support.metabox.io/topic/select-a-gravity-form-to-assign-to-a-cpt/June 24, 2021 at 6:39 PM in reply to: ✅WP_Query Multiple Relationships relation = AND doesn't work ? #29107Long Nguyen
ModeratorHi friends,
We are working tirelessly on this issue. Please check the commits in the repository https://github.com/wpmetabox/mb-relationships/commits/master
Long Nguyen
ModeratorHi Quint,
Please share your site credentials via this contact form https://metabox.io/contact/, I will help you to check the issue.
Long Nguyen
ModeratorHi guys,
Just to clarify that the attribute
post_typeneeds to add to the shortcode frontend submission, not the shortcode frontend dashboard.[mb_frontend_form id="meta-box-id" post_fields="title,content" post_type="cpt-slug"] -
AuthorPosts