July 2, 2014 at 4:20 am 22708
|Harsha||Hi. In every page that I put a form shortcode I used WPUF FORM META BOX too, like instructions says. But users can't edit their published posts. They get a message in a yellow box, saying that they haven't permissions to edit. I checked the option to give users ability to edit in options, but it doesn't work. Any suggestion?|
July 2, 2014 at 5:54 pm 22758
I have the same problem after the update to version 2.2. When I look in the code of edit-profile.php, I see that the variable $post is used to get information. However, the $post variable is holding information about the current page (the dashboard page), and not the posts which it should. So $post->ID will get the ID of the dashboard and not the posts. get_the_ID() should be used in the loop instead.
July 2, 2014 at 7:13 pm 22765
July 2, 2014 at 7:16 pm 22766
No problem! Just remember that is bad practice to edit core files, as they will be overwritten in future updates and all your changes will be lost. Let’s just hope that this will be fix in future versions. 😉
July 2, 2014 at 7:24 pm 22769
Yep, but I think Tareq will correct it soon, so, no matter about hacking this core file 🙂
July 2, 2014 at 8:33 pm 22777
I’ve pushed the update: v2.2.1
July 2, 2014 at 9:31 pm 22783
How long will it take before WordPress automatically updates the plugin? I am experiencing this too.
July 2, 2014 at 9:39 pm 22785
It takes about 12 hours. But if you don’t to want to wait, you can download from your account here and update manually.
July 2, 2014 at 9:54 pm 22787
I have just done that. It’s fixed both the issue described and another problem with strange incorrect data being re-loaded into the form again properly.
Excellent. Can I ask a serious question though? Shouldn’t some form of ‘beta testing’ pick this sort of issue up? Do you have a working group of folk who can contribute ?
July 2, 2014 at 10:10 pm 22789
We did test by in-house devs/support but sadly it did catch our eyes. Sorry for the trouble.
July 2, 2014 at 11:22 pm 22796
Update 2.2.1 is working for me.
August 9, 2014 at 1:03 am 24818
Looks like this change/fix was missed in the PRO version. I’ve applied the change manually. Wanted to give a heads up.