Title: Error
Last modified: November 3, 2017

---

# Error

 *  Resolved [BenLinders](https://wordpress.org/support/users/benlinders/)
 * (@benlinders)
 * [8 years, 9 months ago](https://wordpress.org/support/topic/error-986/)
 * I get this error message after upgrading to 20171101 :
 * PHP Warning: htmlspecialchars_decode() expects parameter 1 to be string, array
   given in (…)/user-submitted-posts/library/core-functions.php on line 220
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ferror-986%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 7 replies - 1 through 7 (of 7 total)

 *  [zopfan](https://wordpress.org/support/users/zopfan/)
 * (@zopfan)
 * [8 years, 9 months ago](https://wordpress.org/support/topic/error-986/#post-9647845)
 * I too got the same problem.
 * My website, [http://www.Bathinda.xyz](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](https://codex.wordpress.org/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″
 *  Plugin Author [Jeff Starr](https://wordpress.org/support/users/specialk/)
 * (@specialk)
 * [8 years, 9 months ago](https://wordpress.org/support/topic/error-986/#post-9648462)
 * 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.
 *  Plugin Author [Jeff Starr](https://wordpress.org/support/users/specialk/)
 * (@specialk)
 * [8 years, 9 months ago](https://wordpress.org/support/topic/error-986/#post-9648493)
 * 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.
 *  Thread Starter [BenLinders](https://wordpress.org/support/users/benlinders/)
 * (@benlinders)
 * [8 years, 9 months ago](https://wordpress.org/support/topic/error-986/#post-9648531)
 * 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
 *  Plugin Author [Jeff Starr](https://wordpress.org/support/users/specialk/)
 * (@specialk)
 * [8 years, 9 months ago](https://wordpress.org/support/topic/error-986/#post-9648540)
 * 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.
 *  Thread Starter [BenLinders](https://wordpress.org/support/users/benlinders/)
 * (@benlinders)
 * [8 years, 9 months ago](https://wordpress.org/support/topic/error-986/#post-9648554)
 * Makes sense, thanks Jeff for explaining this! And thank you for your prompt help
   with this issue 🙂
 *  Plugin Author [Jeff Starr](https://wordpress.org/support/users/specialk/)
 * (@specialk)
 * [8 years, 9 months ago](https://wordpress.org/support/topic/error-986/#post-9648578)
 * Glad to help, Ben 🙂

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Error’ is closed to new replies.

 * ![](https://ps.w.org/user-submitted-posts/assets/icon-256x256.png?rev=2567685)
 * [User Submitted Posts – Enable Users to Submit Posts from the Front End](https://wordpress.org/plugins/user-submitted-posts/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/user-submitted-posts/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/user-submitted-posts/)
 * [Active Topics](https://wordpress.org/support/plugin/user-submitted-posts/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/user-submitted-posts/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/user-submitted-posts/reviews/)

## Tags

 * [PHP Warning](https://wordpress.org/support/topic-tag/php-warning/)

 * 7 replies
 * 3 participants
 * Last reply from: [Jeff Starr](https://wordpress.org/support/users/specialk/)
 * Last activity: [8 years, 9 months ago](https://wordpress.org/support/topic/error-986/#post-9648578)
 * Status: resolved