Title: ABASE &#8211; Function and Security Issue
Last modified: August 31, 2016

---

# ABASE – Function and Security Issue

 *  [eddlang](https://wordpress.org/support/users/eddlang/)
 * (@eddlang)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/abase-function-and-security-issue/)
 * Not sure why … I try to get ABASE up to work.
 * I’m getting this error message:
 * #1. [abase]
    Fatal Error (636)
 * You have an error in your SQL syntax; check the manual that corresponds to your
   MySQL server version for the right syntax to use near ‘-L1’ at line 1
 * Could someone please give me a hint what could cause the issue?
 * +++++++++++++++++++++++++++++++++++++++++++
 * During my testing I’ve recognized that the error message may show very sensitive
   data 🙂 – is there a possibility to disable such messages or store them in a 
   log file?
 * #1. [abase]
    Fatal Error (613) – Couldn’t connect to MySQL server on ‘demohost’.
 * This shortcode uses Database #1. If this is correct, then see the Warning above.
   One or more of the following settings for Database #1 is probably not correct.
   
   Database host: ‘demohost’. Database user: ‘demouser’. Database user password:‘
   demopsw’.
 * [https://wordpress.org/plugins/abase/](https://wordpress.org/plugins/abase/)

The topic ‘ABASE – Function and Security Issue’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/abase.svg)
 * [ABASE](https://wordpress.org/plugins/abase/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/abase/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/abase/)
 * [Active Topics](https://wordpress.org/support/plugin/abase/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/abase/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/abase/reviews/)

 * 0 replies
 * 1 participant
 * Last reply from: [eddlang](https://wordpress.org/support/users/eddlang/)
 * Last activity: [10 years, 2 months ago](https://wordpress.org/support/topic/abase-function-and-security-issue/)
 * Status: not resolved