Title: [Plugin: Front-end Editor] incompatible with plugin PDO (SQLite) For WordPress
Last modified: August 20, 2016

---

# [Plugin: Front-end Editor] incompatible with plugin PDO (SQLite) For WordPress

 *  [oscarlosan](https://wordpress.org/support/users/oscarlosan/)
 * (@oscarlosan)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/plugin-front-end-editor-incompatible-with-plugin-pdo-sqlite-for-wordpress/)
 * does not work well with plugin **PDO (SQLite) For WordPress**.
 * a greeting.
 * [http://wordpress.org/extend/plugins/front-end-editor/](http://wordpress.org/extend/plugins/front-end-editor/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [scribu](https://wordpress.org/support/users/scribu/)
 * (@scribu)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/plugin-front-end-editor-incompatible-with-plugin-pdo-sqlite-for-wordpress/#post-2292151)
 * With one exception, the Front-end Editor plugin doesn’t use any custom queries.
   It only uses the functions that WordPress provides.
 * Therefore, the problem is most likely with the PDO plugin.

Viewing 1 replies (of 1 total)

The topic ‘[Plugin: Front-end Editor] incompatible with plugin PDO (SQLite) For 
WordPress’ is closed to new replies.

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

 * 1 reply
 * 2 participants
 * Last reply from: [scribu](https://wordpress.org/support/users/scribu/)
 * Last activity: [14 years, 9 months ago](https://wordpress.org/support/topic/plugin-front-end-editor-incompatible-with-plugin-pdo-sqlite-for-wordpress/#post-2292151)
 * Status: not resolved