Forum Replies Created
-
AuthorPosts
-
January 29, 2025 at 11:27 AM in reply to: Critical error after custom fields set to display on custom post type #47554
[email protected]
ParticipantI don't know if this is related or not, but I can't even create a new post type without getting a critical error message. I run MB on many of my other sites (I haven't dared to test this on those sites) and haven't encountered this issue straight out of the box before. I'm hoping whatever the new update is resolves this, because as it stands, it's actually unusable currently which is really disappointing.
[email protected]
ParticipantHi Anh, it looks like this issue arose again in the latest release of Meta Box. Same conflict with Squirrly, so I had to deactivate that for the field to show.
Can you please take a look again on your end to see if the conflict is present that you were able to fix last time? Would it be fruitful to work with the Squirrly team to see if there is an amicable way to resolve this between both platforms?
Thanks
[email protected]
ParticipantHello, I tried that previously, before creating this post. Just to ensure I wasn't crazy, I went back in and set it up and included "none" in the sanitize advanced settings - still doesn't output the code as expected.
Again, with sanitize: none, I have this page: https://lyonmentalhealth.com/email-archive/second-post/
The first tab is the Rich Text field with sanitize none, the second tab is the WP Content field, both using the same code, both coming from the same form (I added 'title, content') to it. I don't know the intricacies of how WordPress ultimately passes that data along, but it just shows that even when going through Meta Box, the desired outcome is possible, but something isn't quite right as is.I know this isn't fully related, but when I tried something similar using Bricksforge's Pro Forms to then make updates to the post, that's when it 'broke' the code upon a second submission. I was hoping that MetaBox would more or less permanently not sanitize the code so that on every submission, either to create a post or update it, the code would remain intact for what was passed through it. This doesn't appear to be the case, even for the initial submission.
September 14, 2023 at 12:22 AM in reply to: Users Losing Access to Post Submission with Admin Interference #43247[email protected]
ParticipantI tried that and still the same outcome/result.
I am using the following snippets on the site, I'm not sure if one is misconfigured, but if not, then I don't know what to say...other than the Meta Box submission isn't working as intended, for one reason or another.
September 13, 2023 at 1:14 AM in reply to: Users Losing Access to Post Submission with Admin Interference #43232[email protected]
ParticipantHere is a brief walkthrough of the issue and the steps I take and what ends up happening. The first screenshot is also what the user is left seeing after I edit their post:
https://note.sapphirewolf.co/l/A6jkDdSeptember 13, 2023 at 1:05 AM in reply to: Users Losing Access to Post Submission with Admin Interference #43231[email protected]
ParticipantI do edit the posts in the admin area, yes, since that's the only way I see them after they're initially created. When the post is first created, it lives under their front-end dashboard exclusively, which is why I have to go through the back-end.
Is there a different area I should be managing their details?
It's definitely changing the author of the post when I go into the Custom Post Type submission, which is causing a lot of issues
[email protected]
ParticipantThanks for the quick update, Anh! That appears to have done the job. Much appreciated!
[email protected]
ParticipantAt this point, I'm not sure if the issue is actually with Squirrly or not, or if it's something in MB that is conflicting with other plugins. I know my client is waiting on this to be resolved so that we can move forward with the front-end submissions.
[email protected]
ParticipantHmmmm. Okay, (un)fortunately I've isolated the issue. When I activated Squirrly SEO, it broke the media upload custom field only. I'm not sure why that is.
When I deactivate the plugin, the media field works as expected. I'm wondering if you know of a workaround. I know it's technically a Squirrly issue then, but if you have experienced this before and know of a viable solution where I can inject some code somewhere to bypass that issue, that would be greatly appreciated. Thanks again![email protected]
ParticipantHi Peter,
Here is a pastebin link:
https://pastebin.com/HrvnM74jI have included all 3 forms that are facing this issue currently.
It's weird because I can see the image field now on the back-end in Oxygen, but it's still not showing on the front-end.
Thanks!
July 7, 2023 at 8:24 AM in reply to: ✅Frontend Submission --> Custom Title and Slug from Fields #42512[email protected]
ParticipantThank you! That worked like a charm. I'm not sure if this is the most optimized code, but in case anyone stumbles upon this, here is the final PHP code for the desired result:
<div> add_action( 'rwmb_frontend_after_save_post', 'update_bio_post_title'); function update_bio_post_title( $object ) { $post_type = $object->post_type; if ( 'bio' == $post_type ){ $post_id = $object->post_id; // Get the field value $my_meta = rwmb_meta( 'counselor_full_name', '', $post_id ); // Get the post title $my_post_title = get_the_title( $post_id ); // Prepare update post $post_slug = sanitize_title_with_dashes ($my_post_title,'','save'); $post_slugsan = sanitize_title($my_meta); $my_post_title = array( 'ID' => $post_id, 'post_title' => $my_meta, 'post_name' => $post_slugsan, ); wp_update_post( $my_post_title );} } </div> -
AuthorPosts