Forum Replies Created
-
Posts
-
Hi @bhushanjawle!
Sorry you’re having issues with the relate functionality. You’re definitely doing something pretty advanced, which is awesome. I know it’s supported, there must be a bug we need to find (or there’s a syntax I’m not remembering).
Otherwise great question!
We don’t have any present plans on removing the forums. Currently users can get support on the plugin page on WP.org, here, and now Github. I would say that, at least for now, I would recommend that our users that are developers start taking advantage of the issues on Github. The reason being that it’s better suited for exchanging code, referring to other issues/pull requests, and allowing us to organize issues with labels and milestones.
Let me know if this makes sense!
Hi @openmic!
No worries at all. Thanks for understanding!
The primary time that built and maintains the project are all professional developers. We each have our own businesses that we run and use Piklist on virtually every project. So the good news there is that this isn’t just some framework sitting in a bubble. We’re personally invested in it and use it every day on dozens of projects from small to enterprise in size.
We have goals for Piklist, but the intention is that the core of Piklist (what’s referred to as Piklist) will always be free and community maintained. It’s a tool by and for developers to make amazing work in a third of the time. It’s not easy to provide support as quick as we can, although Steve really gives it a shot and does amazing! But we’re at a place now where community support is becoming even more critical.
If you’re an experienced user please help others. Piklist is powerful and it’s hard to document everything it’s capable of (though we try). Users helping users will always be the best form of support for the core.
If you’re an experienced developer, please roll up your sleeves, get familiar with the Piklist code (at least portions, it’s pretty huge) and submit pull requests! In the not too distant future we’ll be adding unit tests to help it become even more robust.
Thanks for using Piklist! 🙂
Hey @openmic!
Sorry for the delayed response. Please understand this is a passion project and no one gets paid. We do the best we can, but it’s difficult to keep up. We’re always working to get the community more involved so experienced users can help one another and contribute to make Pklist even better, which is why we recently opened it up on Github.
For your issue, your scopes are incorrect. Change the following:
terms -> taxonomy
termmeta -> term_meta
Hope this helps! 🙂
Hi again!
Ok, so to be clear you resolved the submitdiv issue?
Now the issue is that on PHP 7 you can’t save a draft in Safari on a Mac?
Hi @brightestspark!
That is strange. Are you extending the submit metabox per chance, or doing anything like that? And are you only seeing this on an iPad?
You’ve got the right idea, but it really depends on the field you’re trying to update. Everything stores simply in the database with the exception of group repeater fields which store as serialized data, which you’ll probably want to pull the array, modify it, and then update using the new array.
Hope this helps! 🙂
It certainly would be a good idea to give a proper comparison in the future!
For now, here’s a few key differences:
- Piklist is code-based while ACF is database-driven. This means a few different things. First, everything you build with Piklist is easily version controlled. That’s a big win. Second, and what drew me to it, is that I’m not limited by some UI. I can create a metabox, for example, and use the Piklist functions to build fields, or do something completely different! As an engineer, I love this.
- Piklist is very careful about how data is stored. ACF has a tendency to store data in a serialized form and then search within serialized data later one. From a performance standpoint, that’s not good. But we also wanted to make it possible to do all sorts of queries that are simple, fast, and clean. So Piklist stores data in a quick, queryable form.
- Piklist loves WordPress. Ok, I’m sure ACF loves WordPress, too, but here’s what I mean by that. In building Piklist we were manic about making sure that Piklist never deviated from WordPress in a way where we were building our own thing entirely. Piklist really just tries to take what WordPress already does and take it to the next level. That means that we use all the best WordPress practices and if you’re familiar with WordPress you’ll be comfortable with Piklist. You can extend Piklist, ignore it, and tweak it using all the usual tools (e.g. hooks, WordPress functions, actions, etc.).
That’s certainly not the whole thing, but it’s a good start. We don’t consider Advanced Custom Fields a bad plugin, and there are certainly similarities. ACF wanted to be a way to bring fields to freelancers and designers and has grown from there. Piklist aims to be a framework that takes WordPress developers to the next level with speed and good practice for everything from small projects to enterprise level work (which we do). We’d like to provide UI plugins in the future that look and feel a bit more like ACF, but we wanted to start by building an incredible core that will always be free.
Hope this helps! 🙂
Hey @stephen!
I use relates quite regularly and should work perfectly in the latest RC version. Please grab it from Github and, if you have any issues and are comfortable with Github, please make an issue with any details you can provide. Better yet, as we’re trying to make Piklist core more about community contribution, feel free to make a pull request if you think you’ve found the solution.
