Support Forum » User Profile

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 55 total)
  • Author
    Posts
  • in reply to: Membership site #44169
    SamSam
    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

    SamSam
    Participant

    It 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
    Sam

    in reply to: Regex remove everything after @ (including @) #42111
    SamSam
    Participant

    Thank you, Peter.

    Regards,
    Sam

    in reply to: Regex remove everything after @ (including @) #42093
    SamSam
    Participant

    Hi 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,
    Sam

    SamSam
    Participant

    Thanks 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,
    Sam

    SamSam
    Participant

    Hi Peter - Screenshot here and here's the json file that will be burned after 1 use.

    Thanks,
    Sam

    SamSam
    Participant

    Hi - 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,
    Sam

    in reply to: Custom table + Revision issue & questions #41151
    SamSam
    Participant

    Hi 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,
    Sam

    in reply to: Admin Columns + Revision (column) + sortable #41076
    SamSam
    Participant

    very cool. will try soon. thanks

    in reply to: Custom table + Revision issue & questions #41075
    SamSam
    Participant

    thank you, Peter

    in reply to: Admin Columns + Revision (column) + sortable #41051
    SamSam
    Participant

    Hi - me again - Just wanted to say that the post "Last Modified" date would be perfectly sufficient for my purposes, too, if easier.

    Thanks again,
    Sam

    in reply to: Configure admin columns #41046
    SamSam
    Participant

    Hi 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,
    Sam

    in reply to: Setting Default Values For MB Builder Custom Field Types #40641
    SamSam
    Participant

    Great 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

    in reply to: Unable to get MB Comment Meta to process #40564
    SamSam
    Participant

    Thank 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,
    Sam

    in reply to: Unable to get MB Comment Meta to process #40544
    SamSam
    Participant

    Thank 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

Viewing 15 posts - 1 through 15 (of 55 total)