Plugin Contributor
Qurl
(@qurl)
The first notice: Something is wrong with your widget config where you’re using the URL filter.
The documentation for wp_get_theme() doesn’t mention it’s deprecated.
http://codex.ww.wp.xz.cn/Function_Reference/wp_get_theme
It’s saying use wp_get_theme instead of current_theme_info. I haven’t looked at the code but i’m assuming that’s what it meant.
https://developer.ww.wp.xz.cn/reference/functions/current_theme_info/
As for the config… I’ll look into it. They have a LOOOT of stuff in there so… not sure where to start. Do you have any idea or suggestion as to what it may be… something in one of the text widgets conflicting? …uh.. I know that’s a tough question to answer but I guess I’m looking to see if you’ve seen anything cause that issue before and what common things you think would cause it to give me an idea of where to start.
Thx
Plugin Contributor
Qurl
(@qurl)
It’s the URL module, that will probably shrink the selection down. Looking at notice, it seems the data within the configuration is corrupt or so. Not sure how that can happen actually.
Hmm… you might be right about the WP function. I know the WordPress Codez is sometimes lacking that kind of information. I always check on that kind of notices before I release a new version. I might have missed it the last time.
Hah no worries man – it happens. I do appreciate you taking the time to read and respond however.
I’ve run FG Fix Serialized Strings and nothing was ‘fixed’. Still trying to track this down. There was a domain migration recently so I assume it was something with urls in widgets… which I assume would be fixed upon saving the widget again? but doesn’t seem to have any effect. Thoughts?
ok tracked down in the URL expander of one of the text widgets I have this:
<br />
<b>Warning</b>: implode(): Invalid arguments passed in <b>/wordpress/wp-content/plugins/dynamic-widgets/mods/url_module.php</b> on line <b>53</b><br />
Turned the URL field to no… saved… seems to have worked. But I’m new to this plugin (inherited a site using it) so not familiar with the features.
Plugin Contributor
Qurl
(@qurl)
Yeah, I can understand the warning message. That’s where the faulty string at your end was unserialised. Probably the (re)saving fixed the issue.
seems to have yes. Thx; cheers man. #closing
I have the same problem.
I don’t understand how to fix this issue (I’m not a programmer).
Please help me!
