Forum Replies Created

Viewing 15 posts - 16 through 30 (of 122 total)
  • Author
    Posts
  • in reply to: MySQL error from Query Monitor #4627
    Kevin
    Keymaster

    @kplaneta-

    Do you happen to have the query we could look at?

    Thanks,

    Kevin

    in reply to: Add More + GROUP data not correct [0.9.9.2] #4601
    Kevin
    Keymaster

    @Justin-

    Check out the latest version, this issue should be resolved with the latest update to the upgrade script.

    Thanks,

    Kevin

    in reply to: Creating conditional field for something not equal to 'none' #4600
    Kevin
    Keymaster

    @Rachel-

    Check out the compare option for conditions, I think that’s what your looking for.

    https://piklist.com/user-guide/docs/field-parameters/conditions/

    Thanks,

    Kevin

    in reply to: Post_relate -bugs [0.9.9.2] #4598
    Kevin
    Keymaster

    Also please make sure you only have the one Piklist field on the page named __relate_post (‘_’ . piklist::$prefix . ‘relate_post’) or the last one submitted will always take over in the save process.

    Thanks,

    Kevin

    in reply to: Post_relate -bugs [0.9.9.2] #4597
    Kevin
    Keymaster

    @Justin-

    Check out the latest version we just released (0.9.9.3). The additional odd fields are actually the html fields, they were being saved in the previous release and thats been resolved.

    Thanks,

    Kevin

    in reply to: CPT with multiple featured images and attached images #4361
    Kevin
    Keymaster

    @WebGuy-

    Looks good to me, however scope is usually unnecessary. For example, if you are creating a post-meta field in a file in meta-boxes then the scope of post_meta is assumed. Let us know how it goes.

    Thanks,

    Kevin

    in reply to: PikList WYSIWYG breaking format in PikList Group #4360
    Kevin
    Keymaster

    @shayneol-

    I had a chance to test your fields against the upcoming beta and they work wonderfully. The next beta will be released early next week so stay tuned.

    Thanks,

    Kevin

    in reply to: PikList WYSIWYG breaking format in PikList Group #4299
    Kevin
    Keymaster

    @hyperarts- We received the file and successfully tested the field.

    in reply to: PikList WYSIWYG breaking format in PikList Group #4297
    Kevin
    Keymaster

    @hyperarts- We are aware of this issue and it has been fixed in the next beta release which will be available later this week, stay tuned!

    Thanks,

    Kevin

    PS If you want to send your code to [email protected] we will triple check to make sure you are all set with the upcoming release.

    in reply to: performance drop with lots of conditional statements #4293
    Kevin
    Keymaster

    @pionect-

    We have had a chance to check out your conditions against the latest beta and with few tweaks we are looking good. We are seeing at least a 50-60% improvement in speed on conditions execution. Stay tuned for the next beta later this week.

    Thanks,

    Kevin

    in reply to: performance drop with lots of conditional statements #4291
    Kevin
    Keymaster

    @pionect-

    Can you send a copy of the code for your meta-boxes to [email protected]? We are rounding out the next version and I would like to test your code against it to make sure its working better.

    Thanks,

    Kevin

    in reply to: Postmeta – Delete_metadata and Save_metadata #3654
    Kevin
    Keymaster

    @spitfire-

    Love the avatar, I am a big fan of the P51 Mustangs. Also, great question. I have mulled over this countless times and have even written code trying different ideas and methods. The long story, put shortly, is that it just doesn’t matter. As we add and remove meta in WordPress without Piklist we still have the same issue with the ids. However there are form coherency issues that it will help with in the future but the biggest reason at the moment is that the order they are inserted into the database is the order they should be pulled out. We do this without any extra meta information like other plugins use, trying to leverage WordPress as much as possible without changing every single possible query that an end user could make for the data (the more complicated the machine the more likely it is to break). The maximum size of a bigint is 2^64… so if you managed to ever hit that, WordPress and any plugins aside, you should probably already be optimizing or rethinking your application architecture.

    There are a few other reasons for this we will demonstrate in the future, but rest assured we have spent a considerable amount of time on this decision and we believe it to be the best course for the meta tables.

    Let me know if you have any other questions.

    Thanks,

    Kevin

    in reply to: Validation of multiple custom fields at the same time? #3263
    Kevin
    Keymaster

    @hirschbrat-

    I spoke a little too soon, but not by much. We are very close to our next release and this version has a few upgrades to validation allowing you to inspect other fields in your callback. Email us at [email protected] and we will send you a snippet with a version of the beta this week.

    Thanks,

    Kevin

    in reply to: Validation of multiple custom fields at the same time? #3254
    Kevin
    Keymaster

    Actually yes. Can you post your meta-box code? This way we can show you a relevant example.

    Thanks,

    Kevin

    in reply to: Piklist and CPU use #3194
    Kevin
    Keymaster

    Hi all-

    Just wanted to post an update on this one. The current method we use to determine grouped meta can add a large number of queries given the right circumstances. However in the current beta we are prepping for release, we have rewritten and it is extremely fast no matter what. In fact the upcoming version has a number of major improvements for queries not only in Piklist but WordPress itself, more on that later. If you need the update before the next version, please email [email protected] and we will get you taken care of.

    Thanks,

    Kevin

Viewing 15 posts - 16 through 30 (of 122 total)