Forum Replies Created
-
AuthorPosts
-
Sam
Participant+1 - MB guys (and gals?), payments are the last missing major feature (besides Captcha V2 to keep away registration bots)...at minimum, offer Paypal, as you've done a version for your AutoListings plugin (which nobody here wants to purchase and modify - that's a totally different customer than your core MB members). From there, MB users can use for pay-to-post or code it for memberships (although, you might as well bring that over membership AutoListings feature too).
Low hanging fruit
June 10, 2023 at 6:50 AM in reply to: Please develop a payment feature for frontend submission. #42153Sam
ParticipantIt would be great if Metabox would comment here. Many are curious and interested, and would like to know if this is in the pipeline, or not.
Thanks
SamSam
ParticipantThank you, Peter.
Regards,
SamSam
ParticipantHi Peter - Thank you for your reply. The JS code was only meant as an example of what I was trying to accomplish. It certainly doesn't need to be JS, by me.
Any alternatives to accomplishing this within MB parameters?
And FYI, I'm trying to avoid adding extra input values to keep Registration inputs to the absolute minimum, and thus with the least friction to registration (email & password only).
Thanks,
SamMay 31, 2023 at 12:25 AM in reply to: ✅Custom fields lose info when I switch taxonomy field type #41984Sam
ParticipantThanks Peter, I will give it a shot in the near future...I have a few things going on with development that would make this a bad time to do another RESTORE if it still doesn't work, so I'm going to hold off trying this for now. I will update when I get a chance though.
Regards,
SamMay 26, 2023 at 6:49 PM in reply to: ✅Custom fields lose info when I switch taxonomy field type #41945Sam
ParticipantHi Peter - Screenshot here and here's the json file that will be burned after 1 use.
Thanks,
SamMay 25, 2023 at 7:08 PM in reply to: ✅Custom fields lose info when I switch taxonomy field type #41931Sam
ParticipantHi - I guess I wasn't clear in my description about the effects of the issue...yes, I understand that switching to Select tree requires you to choose the parent first, then child, etc...but I'm talking about the fact that all data in OTHER fields go blank (outside of groups, which aren't affected for some reason). Very unusual, and damaging.
Can you reproduce this? We have absolutely no idea what's making this happens other than the switching of taxonomy field type (which it clearly doesn't like).
Thanks,
SamSam
ParticipantHi Peter - Any feedback from your development team that this is a bug (MB Revisions not showing custom fields when in use with custom table), and is working on it? We have had to take our plugin offline as it requires the ability to see the custom field revisions. Any chance they can prioritize, if they confirm?
Thanks again,
SamSam
Participantvery cool. will try soon. thanks
Sam
Participantthank you, Peter
Sam
ParticipantHi - me again - Just wanted to say that the post "Last Modified" date would be perfectly sufficient for my purposes, too, if easier.
Thanks again,
SamSam
ParticipantHi Peter - This was helofull to me as well...just one more refinment question though, please...how do I also add a sortable column for Revisions (MB Revison)? This is not a custom field of course, but I need this as well to see which posts were modified (revised) most recently.
thanks,
SamFebruary 21, 2023 at 8:31 PM in reply to: ✅Setting Default Values For MB Builder Custom Field Types #40641Sam
ParticipantGreat thread, James (and Peter). Hopefully Metabox comes to support this natively in the near future, as this is a standard expectation of inputs nowadays.
Sam
Sam
ParticipantThank you, Peter...but just so we're on the same page, MB custom field do work on the front end (eg, front end submission). Just not for the comments category. Works for the categories of posts, users, etc.
Regrds,
SamSam
ParticipantThank you. I now see the notation at the end of the page (https://metabox.io/plugins/mb-comment-meta)
It's important to note that MB Comment Meta works only in the back end. It does not add custom fields for comments in the front end.
That's too bad though. This would be SOOOO useful, and unique. Any plans on adding front end support? Or workaround documentation?
Thanks,
Sam -
AuthorPosts