I too got the same problem.
My website, http://www.Bathinda.xyz, when updated to latest version, was broken down until I disabled the ‘User Submitted Posts’ plugin.
I’m using the latest version of your plugin, i.e. 20171101
And WP installation v is 4.8.3
The error which I’ve been able to find by my host goes like this:
“Notice: wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/bathinda/public_html/Bathinda.xyz/wp-includes/functions.php on line 4139″
Glad to help with this. The new version of the plugin includes some new options, which you should configure:
– Under “Form Fields”, select an option for the “Custom Field” setting
– Under “Custom Field”, specify values for both settings
– Under “Auto-Display Content”, select options for “Custom Field Auto-Display” and “Custom Field Markup”
Then save your changes and the PHP Warning that you are seeing will be resolved.
Let me know if any questions, or if I can help further.
Just FYI: Alternately you may be able to just click “Save Settings” as a shortcut to updating the settings. It should work, but actually updating the settings as in the previous post is recommended.
Thanks Jeff!
I’ve changed the settings as proposed by you, so that should solve it.
One question though: this error is all over my error log, I see dozens or errors per hour. As I don’t expect that my users are submitting that many posts (I get about one per couple of weeks), how come that the USP functions are called that often? Even when there’s nobody on the one page that has an USP shortcode?
Ben Linders
Because the settings were not set, so the plugin could not filter the USP requests from the non-USP requests. Now that you have disabled the new Custom Field, the plugin will be able to skip processing for non-USP posts.
Makes sense, thanks Jeff for explaining this! And thank you for your prompt help with this issue 🙂
