As far as I can see, Steve’s last answer is dated of Nov 07, right before the election day… I hope he did not move to Canada hahaha…

I apologize for the joke and the bellow, this is not a forum I know but if we will be supporting Piklist in the future, we need to have a clear vision.

Let’s give the support team some time to react and see, maybe they are on a break or there is a personal matter going on, they have a small team and this is all free for now.

On the other hand, I noticed that the WordPress repository policy will start to be enforced more severely and will not be allowing frameworks there anymore… and recommend to include frameworks in plugins instead. (https://wptavern.com/the-wordpress-plugin-directory-will-no-longer-accept-frameworks)

Previously allowed frameworks like Piklist do not seem to be affected by this new resolution for now though.

When you’ll get a chance Steve please, could you let us know what to expect from Piklist on the long run and if there will be repercussions on Piklist due to the new WordPress repo resolutions? Will Piklist have to pivot?

As a developer who relies currently on Piklist I’m admitting today that I will eminently have to make a choice… I may have to switch towards the old way and write my own classes instead of depending on somebody else’s code.

I love Piklist and I add my voice to dameer’s to say that I would gladly pay for a long term support version. What about a yearly fee?

How can we move forward safely?

Regards

I just spoke with Kevin. He’s been under the gun most of the year and is just starting to come up for air again.

I’ve been frustrated as well, but I know he is committed to Piklist and I have faith that they will continue to support it going forward.

Donna

Hey guys!

I’m one of the authors of Piklist and, while Kevin has been very busy this year, Steve and I are still around. I apologize I’m not as reliably on the forums as Steve. He’s killer at support. My agency uses Piklist on every single project, so it is far from dead. We haven’t really added any new features in a while, but in my opinion Piklist has needed a season os solidifying and fixing bugs for a while. I’ve continued to fix bugs as I find them, but I’ve really found very few as it is getting pretty solid (and the bugs are pretty niche).

Rest assured the project is by no means dead. 🙂

@eddie2390: Come on, man. It’s not quite so black and white as all that. I went ahead and posted a solution to that thread. I apologize that it wasn’t answered at the time, I can appreciate the inconvenience. 🙂

Hi Sergey!

Thanks for taking an interest! Please don’t take a dip in public activity as Piklist being dead. That’s a bit of a leap users sometimes make in a panic. Piklist is free and open-source, as such all users are able to fork Piklist and do whatever they need. That said, it’s a project of passion for us authors and we use it regularly so we want it to be high quality. If there’s a specific bug that’s breaking all of your work, can you please open another thread and point it out so we can best look into it? Thanks!