Forum Replies Created

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • in reply to: Image in repeater issue (WordPress 4.5 + Piklist 0.9.9.8) #6399
    adrianm
    Member

    It seems the issue comes from this section

    
              if (!$element.hasClass('wp-editor-wrap'))
              {
                $element = $element.addBack();  // I COMMENTED THIS LINE AND IT WORKS
              }
    

    That makes the hidden input be moved in the DOM.

    in reply to: Image in repeater issue (WordPress 4.5 + Piklist 0.9.9.8) #6334
    adrianm
    Member

    Upon some investigation I think the issue is because you don’t put the hidden input fields inside the .piklist-field-preview . The HTML code coming from the server seems correct but I think your JS is moving things around. I hope this can help you fix this issue sooner.

    in reply to: Image in repeater issue (WordPress 4.5 + Piklist 0.9.9.8) #6333
    adrianm
    Member

    Correction:

    From what I saw the problem is that the _post_meta[slides][0][image][] input fields are not updated correctly. When you remove the image the value of the associated field is cleared, but the input stays on the DOM and when you add an image there is not input field appended to the DOM.

    in reply to: Piklist don't save anything #5095
    adrianm
    Member

    @Steve, Disabling the W3TC Object Cache feature solved the issue. The issue appeared both on Windows and Linux.

    in reply to: Piklist don't save anything #5081
    adrianm
    Member

    I had the same issue. I don’t know if the same cause but here’s what I’ve found:

    1. I have piklist 0.9.4.24 and the W3TC plugin with only the Object Cache enabled
    2. I’ve looked a little bit at the code and I’ve found that in class-picklist-validate.php your code is

    
    public static function check(&$stored_data = null)
      {
        if (!isset($_REQUEST[piklist::$prefix]['fields_id']) || !$fields_data = get_transient(piklist::$prefix . $_REQUEST[piklist::$prefix]['fields_id']))
        {
          return false;
        }
    

    which is not clearly readable (!$fields_data = get_transient(…) so I replaced it with

    
    public static function check(&$stored_data = null)
      {
        if (!isset($_REQUEST[piklist::$prefix]['fields_id']) || !($fields_data = get_transient(piklist::$prefix . $_REQUEST[piklist::$prefix]['fields_id'])))
        {
          return false;
        }
    

    The transient is not retrieved (ie: $fields_data data is always false)

    If I disable the W3TC Object Cache, everything works as expected.

    Apparently the cache file is not written by the W3TC plugin. I don’t know why. Maybe the transient’s lifetime is too short? The file to be written too big?

    in reply to: Custom field tutorial or template repo? #3577
    adrianm
    Member

    I have WP_DEBUG set to true and I got some warnings. Otherwise, I was able to create my first Piklist custom field 🙂

    in reply to: Settings page without 'piklist_admin_pages' #3562
    adrianm
    Member
    This reply has been marked as private.
    in reply to: Settings page without 'piklist_admin_pages' #3561
    adrianm
    Member

    @Steve. I know about making a settings page using the standard Wodpress functions. How can I make piklist render and handle the form for that page?

    I will upload a zip file soon as I suspect this is a bug due to filters/actions priorities.

    in reply to: Locked not working #3553
    adrianm
    Member

    Thanks, @Steve

    in reply to: License Information #3536
    adrianm
    Member

    @Steve – The plan for the plugin is to remain free, right?
    I am asking thigs because I’m starting a new project and I have to decide Piklist vs CMB2.

    in reply to: Cannot download the Toolbox #3523
    adrianm
    Member

    It works. Thanks!

    in reply to: Cannot download the Toolbox #3521
    adrianm
    Member

    No, I didn’t. Still, there is the problem that the website didn’t respond to my action; the spining icon is there after 2 minutes. The EDD plugin makes an ajax call to wp-admin… this might be the reason…

Viewing 12 posts - 1 through 12 (of 12 total)