Tagged: piklist_save_field, process_form
- This topic has 2 replies, 2 voices, and was last updated 3 years, 8 months ago by
Steve.
-
AuthorPosts
-
-
May 26, 2018 at 3:53 am #9023
MarcusMemberHi guys, long time since I’ve posted.
Hopefully you can help.I’ve got a client who’s been using piklist since 2013, and the site and software I created has worked great for 5 years, but recently they reached out to me as something stopped working.
They are using WordPress: 4.2.9
And piklist: 0.9.5mUp until April 18th of this year, they were using WordPress 4.2.1
Here’s the problem. The piklist hook ‘piklist_save_field’ was working up until April 18th.
But now it doesn’t fire on publishes or updates.
In fact, the piklist function ‘process_form’, doesn’t fire on publishes or saves either.
Even ‘template_redirect’ which is attached to process_form, doesn’t seem to fire either.Actions like: wp_insert_post_data aren’t interfering. (disabled them to see)
And I can’t find what has changed that would affect this.
Is there some way I can debug this? Any suggestions?
I have two requests for debugging from the client.They don’t want to upgrade their wordpress, as this one has been secured and all holes fixed. (so they don’t want to have to secure it again with a newer version) and they don’t want to upgrade piklist too much (at my suggestion) as they don’t want to have to redevelop a lot of functions that used old piklist code. (they aren’t budgeting for this, and I’m not a free-well of coding. And it was developed with a really old version of piklist, and hey it worked non-stop for 5 years) 🙂
Pre-thanks.
Marcus
-
May 26, 2018 at 6:11 pm #9025
SteveKeymaster@marcus-eby– Good to hear from you! Hope you’re doing well.
If wp_debug is not returning any useful notices than the way I would debug this is to:
1) Roll back to WordPress 4.2.1 and verify everything is working correctly. It’s a minor version, so 4.2.1 shouldn’t be an issue.
2) Then upgrade to 4.2.2 and verify the everything is working correctly. If not, diff 4.2.1 and 4.2.2 to find the changes which will help you narrow down the issue.
3) If 4.2.2 is working correctly, then go to 4.2.3, and keep repeating.
It’s definitely a slow process, but I can’t think of a better way.
Good luck!
-
June 4, 2018 at 4:30 pm #9037
SteveKeymasterClosing this because it’s not a Piklist problem, it’s a client problem.
-
-
AuthorPosts
- The topic ‘Old Piklist problem…’ is closed to new replies.