Which version of the plugin are you using? That looks like rather odd output to me.
It updated by itself, which I was mad about a bit, its the latest version though.
Plugins don’t update on their own, unless you have another plugin installed that enables this, or if your host upgrades them automatically for you. Neither are common, do you mean that WordPress itself updated on it’s own? Since WordPress 3.8, it’s been able to update itself to bug fix and security releases automatically, like to 3.8.1
Like Scott said, it shouldn’t be auto-updating itself. The only other idea I have for that part would be someone else who can update plugins. Not sure how many admins you have.
Regardless, back to the original topic at hand with that widget. Have you enabled WP_DEBUG, if you know what that is? It’d be nice if we could get what file and what line number this is on, so that we can more effectively debug what may be happening. If you don’t know how to turn it on, I can help you with that, but know that it’d show possible PHP errors to visitors if this is on a live production site. If you’re working in a localhost or dev environment, then we won’t worry about that part. If live, it can be a quick thing really by enabling the debug messages, refreshing your widget admin page quick, and then quickly disabling. Let me know if you need help with this part.
Oops, I meant to say 3.7 and 3.7.1, these rapid releases are getting me all confused 🙂
I was talking about the auto updates from the core, not the plugin itself, I need to find that post where it tells you how to disable it. Anyway,
Strict Standards: Declaration of P2P_Indeterminate_Directed_Connection_Type::recognize() should be compatible with P2P_Directed_Connection_Type::recognize($item, $which = ‘current’) in /home/e1739543/public_html/wp-content/plugins/badgeos/includes/p2p/p2p-core/indeterminate-type.php on line 44
Strict Standards: Declaration of P2P_Indeterminate_Directed_Connection_Type::get_final_qv() should be compatible with P2P_Directed_Connection_Type::get_final_qv($q, $which = ‘current’) in /home/e1739543/public_html/wp-content/plugins/badgeos/includes/p2p/p2p-core/indeterminate-type.php on line 44
Strict Standards: Declaration of P2P_Widget::init() should be compatible with scbWidget::init($class, $file = ”, $base = ”) in /home/e1739543/public_html/wp-content/plugins/badgeos/includes/p2p/p2p-core/extra.php on line 86
Strict Standards: Declaration of P2P_Box_Factory::add_items() should be compatible with P2P_Factory::add_items() in /home/e1739543/public_html/wp-content/plugins/badgeos/includes/p2p/p2p-admin/box-factory.php on line 156
All I have for the debug output, if this doesn’t help I will start digging through the core when its not 2:32 AM…
Ah, WordPress core, I was looking for the BadgeOS plugin version. That makes more sense.
Yeah, I’m not seeing anything related to the widgets for that current output. Perhaps just knowing which widget is causing the output, we can do what we can to trace through the code in the meantime. Is the error showing up on the frontend or in the admin?
I can do a var_dump in a couple places and see if I can find it, I do some development myself. Also are you guys building the bulk badge give thing? Its the latest version of the badge builder by the way.
I was thinking maybe it would be possible to have like a bulk action badge thing in the users area maybe? I don’t know, just a suggestion.
If by bulk action badge, you mean the ability to quickly award a badge to many people, it’s been suggested and +1’d by our lead dev, but still needs to be approved by Credly.
a var_dump would be helpful, certainly. Just whatever you can provide.
ever have this one solved somehow brashell? or is it still a lingering issue?
Error: Sorry, Send to Credly Failed.
This appears when you click the button on the widget area, to send to credly. Although yes this has been fixed the error.
I’ve recently been doing a lot of stuff with the shortcodes, and the original is going to be something that comes up, I believe, before there is an ID to work with.
Regarding the second issue from the last post, we had recent tweaks to the Credly API and we’re hoping that that part is now resolved.
