Forum Replies Created
-
AuthorPosts
-
John
ParticipantThanks Long, that's working great now. Is there a way to force the first option in the dropdown to be selected (it most cases there will only be one) or should I use javascript to do this on page load?
ParticipantThanks. It's so annoying when companies use ACF only.
For now, is there any issue with running ACF (free) alongisde metabox to get access to a few custom fields?
ParticipantThanks but the problem is plugins like DiviFlash which only work with ACF. They check in the code for the presence of ACF classes and call the methods to get the fields, even though they only support basic ones.
As a temporary work around - unless I give in and use ACF instead - I've also installed ACF at the moment and setup the same fields that I want to be able to get into the DiviFlash modules.
Is there a chance this will cause problems? It doesn't feel particularly safe, even though they are both doing the same thing (and I'm only using it for access to text fields at the moment - although images would be useful too).
Thanks
March 30, 2022 at 5:16 PM in reply to: ✅Getting Custom Category/Taxonomy field values in Divi ? #35373ParticipantI've asked Divi support why it isn't working but frankly their support isn't great (it was the first couple of times I asked but this particular support guy I keep getting ignores my detailed question and provides a link to a document about the basics that I made clear I already know..)
For this use case, I've ended up using dynamic css (generated with php and rwmb_meta to get the background image url).
Thanks
October 13, 2021 at 10:16 PM in reply to: ✅Basic question about taxonomies vs CPT relationships #31303ParticipantThanks. I'm going to use my own form and code to do it and create or edit the taxonomy on submit.
October 13, 2021 at 11:55 AM in reply to: ✅Basic question about taxonomies vs CPT relationships #31286ParticipantSorry Long, but is it possible to display/edit the custom taxonomies on the front end using Frontend Submission? So far it doesn't seem to work and a search of the forum seems to suggest that, at least as of last year, it wasn't possible.
This is something users need to set themselves. Am I better using MB User Meta for the front end form and then creating/editing the taxonomies in a post save filter ?
October 13, 2021 at 10:46 AM in reply to: ✅Basic question about taxonomies vs CPT relationships #31283ParticipantBrilliant, thanks Long. I thought it was the right way originally - and I am already using MB Term Meta - but then I had a wobble because when it came to adding the custom fields in code I was trying to do it exactly the same as with a CPT. I'd simply forgotten to look at the MB Term Meta documentation again.
Obviously this is my fault, but if I have one issue with working with MetaBox it's the fact so much is split over so many different plugins and I find it hard to remember to look in the right place to find something when, to my mind, it's all part of the same system but documentation-wise it's in different places.
Thanks so much, I thought I'd have to redo a lot of work - but now I just need to make that " 'taxonomies' => 'category', " change to my code basically!
Best wishes
JohnParticipantThanks. I'll just do my own for now, not a major problem.
ParticipantThanks Long
ParticipantAh ok, thanks. Any idea why the PHP Generation is hanging please?
ParticipantAh, thanks! Although I'm a programmer, I've not used metabox programmatically before and didn't realise this.
ParticipantHi Long,
Sorry, I've tried your first solution - https://docs.metabox.io/save-wysiwyg-content-post-content/ - but it's not working.
I'm not even trying to get the mediumeditor bit to work at the moment so I don't confuse things.
So on the frontend page I have this:
[mb_frontend_form post_fields="title"]
instead of
[mb_frontend_form post_fields="title,content"]
I've also tried
[mb_frontend_form post_fields="title,wysiwyg"]
as well as the original. But the wysiwyg add's nothing (just title is showing), and using the original with content shows the original form.
I have the code, copied exactly from that page, as a snippet which is running on the front end only.
I've test it is running by putting a die("Here"); in front of each function and the first two are "working", ie die is being called.
But this function isn't:
add_filter( 'rwmb_content_field_meta', function() { ...
The die statement is never called - not when the form is displayed or when it is submitted.
What could I be doing wrong please?
Thanks
JohnParticipantI've managed to install quite a few of the standalone plugins so far, all that I think I need for now anyway. None of them contain this issue.
ParticipantThanks Long!
I'm actually struggling at the moment as the theme I am using (Mediumish) has a conflict with Metabox Pro (using AIO) - "Cannot redeclare tgmpa()" - I wrote to them yesterday but not heard anything yet.
Currently progressing my work with Pro turned off but obviously not ideal.
Is there a particular plugin that could be causing this? I know it's no doubt their fault, but if it's just one particular plugin and I could install the rest without installing AIO that could be a solution for now.
Their theme comes with the lite version of Frontend Post Submission Manager and considering going Pro on that, only $18.
Thanks
JohnAugust 13, 2021 at 9:24 PM in reply to: ✅Only showing certain custom fields on the frontend submission? #30234ParticipantThanks Long!
-
AuthorPosts