Forum Replies Created

Viewing 15 posts - 1 through 15 (of 19 total)
  • Author
    Posts
  • in reply to: Upload Field – No Image on Backend #9465
    conkid
    Member

    Hey Steve,

    I figured it out. The add more that wasn’t functioning was assigned to a page template. The site had since had Gutenberg installed w/ the 5.0 release of WP. Once I disabled gutenberg functionality I was able to update the fields as expected. Very odd but maybe I missed some notice about gutenberg editor breaking field enhancing plugins?

    Thanks for your help.

    in reply to: Upload Field – No Image on Backend #9452
    conkid
    Member

    Spent the whole day trying to figure out how to get this site on the new version of piklist.

    When I run the plugin update it breaks the following:

    – add more fields will not save to database
    – post-relate checkbox fields will not save to database
    – images and regular fields DO save to database properly
    – image previews are broken on the backend

    I love Piklist but this is really bad form in my opinion to try to go baseline on the current production version. Please help.

    in reply to: Upload Field – No Image on Backend #9449
    conkid
    Member

    Steve – I have this in a staging site now and have tested multiple scenarios of upgraded from 0.9.4.31 to 1.04. Could we schedule a remote session and I could show you what is happening?

    I am also noticing now that even before upgrading 0.9.4.31 the add_more field is not saving properly.

    Kind of at a loss on this one. Have been using piklist for approx 3 years.

    in reply to: Upload Field – No Image on Backend #9448
    conkid
    Member

    Yes I was prompted. Yes I ran it and it said successful.

    in reply to: Multiple CheckBoxes Broken 0.11.1 #9050
    conkid
    Member

    And another additional error in admin – piklist – settings

    Piklist Settings
    Warning: Invalid argument supplied for foreach() in /app/public/wp-content/plugins/piklist/parts/shared/admin-workflow.php on line 82

    in reply to: Multiple CheckBoxes Broken 0.11.1 #9049
    conkid
    Member

    Steve – I can select multiple boxes but I’m still seeing this error displayed through debug — Thoughts?

    Warning: array_filter() expects parameter 2 to be a valid callback, no array or string given in /app/public/wp-content/plugins/piklist/includes/class-piklist-form.php on line 1202 Warning: array_filter() expects parameter 2 to be a valid callback, no array or string given in /app/public/wp-content/plugins/piklist/includes/class-piklist-form.php on line 1202

    in reply to: Multiple CheckBoxes Broken 0.11.1 #8984
    conkid
    Member

    Steve can you confirm the error?

    in reply to: Multiple CheckBoxes Broken 0.11.1 #8977
    conkid
    Member
    This reply has been marked as private.
    in reply to: New Piklist Documentation #8664
    conkid
    Member

    Steve & Piklist Team,

    Just getting back into the swing this new year on some web projects and noticed the new documentation up. The design is great and it’s very “app” feely. Feels simplified yet direct. Thanks for the great addition and continued efforts. Piklist is the only plugin I use in everything I build and has been that way for a while now.

    in reply to: Piklist Default 'field' Template – Grid Issue #8282
    conkid
    Member

    Hi McMaster,

    Thank you so much for your advice. I tried .010 and was also successful. I will also take your code structure advice and work to implement into my coding. Thanks again for your help!

    in reply to: Piklist Default 'field' Template – Grid Issue #8275
    conkid
    Member

    Here is the image view … didn’t upload right

    Attachments:
    You must be logged in to view attached files.
    in reply to: Meta Fields Not Saving #7747
    conkid
    Member

    PS some other things I should reference that could add relevance or that I’ve tried:

    + Server hosted on Media Temple
    + Have had no issues or conflicts between MT & piklist in over 2 years of hosting
    + Tried using the following to remove the custom fields from all relevant post types:

    function post_type_support_init() {
        remove_post_type_support('post', 'custom-fields');
        remove_post_type_support('page', 'custom-fields');
    }

    + confirmed custom-fields were not used in the attributes section of the code for the custom custom post types
    + confirmed that the custom post types are built with the standard wordpress functionality and not piklist

    in reply to: User Workflow Guide Request #6566
    conkid
    Member

    Steve,

    I’ll try to read through this documentation (again for the 10th time) tonight. I’ve spent way too much time trying to figure out this functionality at this point. I’ve read this documentation since you posted it. I have used piklist for nearly a year, follow your posts constantly, advocate for piklist to everyone I know who is a WP dev (because I think it’s great) but can’t get past this hurdle.

    If you want me to spend 15 hours trying to figure this out on my own, I already have, I promise.

    As mentioned, if it is a time is money scenario, I’ll be glad to paypal you your hourly rate to set me up with a guide. Or make the plugin paid and offer official support? At this point I’m going to have to just go back to ACF, which I really don’t want to do.

    in reply to: User Workflow Guide Request #6551
    conkid
    Member

    Steve,

    Can you please take 15 minutes and just give me a guide here.

    You’ve been responding that your team is working on docs with little new published. You also mentioned in February you would try to help on this that week. Since I’ve seeked updates and another user has posted having the same issues.

    Please some guidance … I am happy to pay for a guide…

    in reply to: User Workflow Guide Request #6005
    conkid
    Member

    Any update here? As mentioned in my original post I’ve tried to understand from the demos.

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