I'm seeing this error in debug.log when users visit forms:-
PHP Warning: array_key_exists(): The first argument should be either a string or an integer in /home/xxxx/public_html/wp-content/plugins/types-access/application/controllers/permissions_post_types.php on line 447
I've made no changes to either user permissions or the access settings for my forms for months. This error has only started appearing since the last update. I've double checked the settings though and they are correct.
Hi, I haven't seen any other recent reports of this but with Access there are lots of variables to contend with. If you've tried the basic debug steps then I could try to reproduce this with a clone of your site if you can send me a download link. Please let me know if there is a specific User I should be testing with, on a specific Form, or if you haven't pinned it down to a specific Form please let me know where a few Forms are that I can interact with and try to narrow it down. Thanks!
hi Christian
Link to files provided in private box.
Have used my basic test site which has been upgraded to wordpress 5.2.1, Access 2.7.3 and Views 2.8.1.1 and replicated the issue when visiting 'create post' as logged in user with custom role based on contributor. Have left debug log for you to see.
On the site I'm developing where I first had the issue, I'm using Cookie Notice plugin (by dfactory) and this isn't working correctly now (the cookie notice re-appears on pages other than the one where the user has made a choice to allow or decline cookies). This works again if I roll back to Access 2.7.2. thought I'd mention it in case it helps troubleshooting.
Let me know if you need anything else.
Thanks, I'm escalating this to 2nd tier now. I'll let you know what I find out.
Our developers have produced a patch file for this issue. Please replace the same file in types-access/application/controllers with the unzipped file you can download here: https://drive.google.com/file/d/1uhigtLg5v5WcwB_xEDEdA15KcSJOZwui/view?usp=sharing
Then let me know if the problem is not completely resolved. Thanks!
Thank you Christian - no errors now 🙂
Access 2.7.4 is out now and contains the fix for this problem. The patch is no longer necessary.
thanks for the heads up - much appreciated!