Title: Plugin crash
Last modified: February 21, 2017

---

# Plugin crash

 *  Resolved [saadhh](https://wordpress.org/support/users/saadhh/)
 * (@saadhh)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/plugin-crash-4/)
 * News Announcement Scroll v8.8.4 crashes, browser console reports:
    Uncaught ReferenceError:
   v_content is not defined at gAnnounce.js?ver=4.7.2:8
 * Thanks

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

 *  Thread Starter [saadhh](https://wordpress.org/support/users/saadhh/)
 * (@saadhh)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/plugin-crash-4/#post-8832557)
 * Found error to be one of the news lines causing a javascript unterminated string
   literal thus (v_content array not defined). Maybe code should cater for such 
   instances.
 * Thanks
 *  Plugin Author [storeapps](https://wordpress.org/support/users/storeapps/)
 * (@storeapps)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/plugin-crash-4/#post-8839603)
 * [@saadhh](https://wordpress.org/support/users/saadhh/),
 * Could you please let us know what news lines/characters in news caused the v_content
   array not defined error, so that we could handle such instances in the future
   releases of the plugin.
 *  Thread Starter [saadhh](https://wordpress.org/support/users/saadhh/)
 * (@saadhh)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/plugin-crash-4/#post-8842940)
 * Sorry I did not keep a copy of news line that caused the error but it was Arabic
   script with NO quotes or double quotes but with diacritics that probably caused
   the error.
 * Thanks.
 *  Plugin Author [storeapps](https://wordpress.org/support/users/storeapps/)
 * (@storeapps)
 * [9 years, 2 months ago](https://wordpress.org/support/topic/plugin-crash-4/#post-8860654)
 * [@saadhh](https://wordpress.org/support/users/saadhh/),
 * We would try reproducing the same issue on our end and try fixing it in the future
   release of the plugin.
 *  Thread Starter [saadhh](https://wordpress.org/support/users/saadhh/)
 * (@saadhh)
 * [9 years, 2 months ago](https://wordpress.org/support/topic/plugin-crash-4/#post-8903371)
 * Just faced the same issue again, this time the string in question (which was 
   copied directly from a web page) contained a CR/LF at the beginning of the string.
   I think a trim before appending the string to the array should do it.
 * Regards,

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

The topic ‘Plugin crash’ is closed to new replies.

 * ![](https://ps.w.org/news-announcement-scroll/assets/icon-256x256.png?rev=1472251)
 * [News Announcement Scroll](https://wordpress.org/plugins/news-announcement-scroll/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/news-announcement-scroll/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/news-announcement-scroll/)
 * [Active Topics](https://wordpress.org/support/plugin/news-announcement-scroll/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/news-announcement-scroll/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/news-announcement-scroll/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [saadhh](https://wordpress.org/support/users/saadhh/)
 * Last activity: [9 years, 2 months ago](https://wordpress.org/support/topic/plugin-crash-4/#post-8903371)
 * Status: resolved