Forum Replies Created

Viewing 9 posts - 16 through 24 (of 24 total)
1 2
  • Author
    Posts
  • February 5, 2016 at 3:17 pm in reply to: Metabox, file upload field with custom scope error #5858
    jivedig
    Member

    Wait, they’re not supported?

    I was just using it as a callback to process the field data myself. Is that scary? I’m building a big plugin now on top of Piklist. I need to manually process the data from the fields and save to the db in my own way. I don’t want some of the fields to save anything, just allow me to grab the values via piklist_save_field. Is there another way to do this?

    Hopefully I’m just missing something. Custom scope/processing was one of the big things I liked about Piklist. Can you clear this up for me?

    FWIW, I was chatting with Jason Adams via email and he was the one that recommended using a custom scope to accomplish this. I just assumed it was a thing after that.

    February 1, 2016 at 11:41 am in reply to: Front end form, image field and validation #5815
    jivedig
    Member

    @gfard Piklist is def a developer framework, though it seems to be made in a way that makes it really fast to setup powerful stuff with minimal code. Activating the demos included in Piklist was really helpful for me to get a head start on building specific metaboxes/forms/etc.

    If you’re not a coder, i’m not sure what to recommend. Maybe wait until the GUI inteface plugin is complete. That may help you. But, even if you have a UI for building forms/metaboxes, you’ll still need to code to display that data how you want, for the most part.

    January 31, 2016 at 7:39 pm in reply to: how to use datetime in piklist? #5809
    jivedig
    Member

    I couldn’t get it to work either. I ended up using a text field with a wrapper class (attribute) on the field, and used https://github.com/xdan/datetimepicker with a target of that field element. Working well so far.

    Attachments:
    You must be logged in to view attached files.
    January 31, 2016 at 7:37 pm in reply to: Possible to deactivate css on front end? #5808
    jivedig
    Member

    Following. I’d like to know this as well. I’m sure we could dequeue the script, but would be nice to have a form parameter or filter to disable various scripts.

    January 31, 2016 at 7:35 pm in reply to: Front end form, image field and validation #5807
    jivedig
    Member

    @gfard: Front end posting and editing of Custom Post Types via Piklist is 100% working in the latest version of Piklist trunk. I seemed to have uncovered a minor bug in custom validation with the image field, but I definitely have an image field mapped to the CPT featured image, and it’s working well.

    January 26, 2016 at 10:06 am in reply to: Image upload / preview? #5755
    jivedig
    Member

    @Daniel did you figure this out? It’s on my list of things to check out as well.

    January 26, 2016 at 12:28 am in reply to: front-end form confusion #5751
    jivedig
    Member

    Just jumping in as I’ve been playing with forms quite a bit lately. Try setting the scope to a random string (the same for each). That will allow you to do whatever you want with the data (or in your case, not save it anywhere.

    January 23, 2016 at 10:58 pm in reply to: Conditional fields not working when scope is different #5704
    jivedig
    Member

    Thanks, I realize how important it is for the fields themselves, but didn’t realize it mattered for the conditions themselves. Thanks 😉

    January 23, 2016 at 5:56 pm in reply to: Conditional fields not working when scope is different #5701
    jivedig
    Member

    Interesting update…

    I can add the scope to the conditions array and now it works.

      'conditions' => array(
    array(
      'scope' => 'post',
      'field' => 'post_status',
      'value' => 'future',
    ),
  ),
  • Author
    Posts
Viewing 9 posts - 16 through 24 (of 24 total)
1 2