June 18, 2015 at 2:35 AM #2293
I always work with wp_debug message on while developing and get this error on every page:
Notice: Undefined offset: 7 in /***/wp-content/plugins/acf-widgets/includes/admin-setup.php on line 215
Please fix that. Thank you.June 18, 2015 at 2:37 AM #2294
and after adding a new acf widget, i get this error:
Notice: Undefined offset: 7 in /***/wp-content/plugins/acf-widgets/includes/admin-setup.php on line 215 Warning: Cannot modify header information - headers already sent by (output started at /***/wp-content/plugins/acf-widgets/includes/admin-setup.php:215) in /***/wp-admin/post.php on line 235 Warning: Cannot modify header information - headers already sent by (output started at /***/wp-content/plugins/acf-widgets/includes/admin-setup.php:215) in /***/wp-includes/pluggable.php on line 1196
your plugin is unusable for me!June 18, 2015 at 9:21 AM #2295
Hi Nic! Thanks for supporting the plugin! I really appreciate it 🙂
So it seems that you’re using a modified version of the WordPress admin panel. Most likely a plugin. That line of code specifically, places the “ACF Widgets” menu item directly beneath “Widgets”. In your case, the widgets menu item isn’t in the expected position so the insertion is failing.
Are you using some sort of re-arranging plugin for the admin menu items? This would cause the behavior that you’re seeing. I’m really sorry about that! I alway develop with WP_DEBUG as well, but unfortunately, it’s impossible to account for every environment/plugin configuration!
My recommendation would be to deactivate any conflicting plugins and see if the error goes away. If it does, report back with the plugin you were using, and I’ll try to push out a fix for it ASAP. I’m really sorry for the inconvenience! 🙁
– DaronJune 18, 2015 at 9:23 AM #2296June 18, 2015 at 9:26 AM #2297
Awesome! Thanks for the quick reply!
So what I’m going to do is add a check to see if the correct
key => valuepair for the insertion is available, and if not, just add the menu item “normally” so this hopefully won’t happen again for anyone else. I’ll post an update here when I get that finished! 🙂June 18, 2015 at 9:46 AM #2298
Hey Nic! Good news! I found the a solution and I’ll be pushing a fix out today. Unfortunately I’m stuck at my day job for a few more hours until lunch, and then I will have access to my usual setup.
If you’re comfortable editing the source yourself, you can reference the GitHub issue and insert that snippet yourself, and when the update is pushed later today, it will overwrite your edit with the official updated source.
Let me know if you have any more questions! I’m happy to help where I can 🙂
June 18, 2015 at 9:47 AM #2300
- This reply was modified 6 years, 4 months ago by Daron Spence.
wow. great! but i can wait one or two days. no problem! thanksJune 19, 2015 at 12:36 AM #2306
Hi Nic, I pushed out the v1.5 release. you should be able to update from your Dashboard.
Again, I apologize about that! Shouldn’t happen again 🙂 (though your experience will be a little different because of your installed plugins).
If you have any feature requests later on as your developing, feel free to open a ticket in the appropriate thread or ping me on Twitter. I’m not to picky at this stage in the plugin’s life. 🙂
Cheers mate!June 19, 2015 at 1:51 AM #2307
thank you daron. new version does not appear in dashboard. i think i have to wait?June 19, 2015 at 9:10 AM #2313
It’s probably a caching thing. Plugins will only look for a new version every few hours or so to keep from pinging servers every 5 seconds when someone reloads the page 🙂
- The topic ‘Notice error with wp_debug’ is closed to new replies.