Title: tomas.k.7's Replies | WordPress.org

---

# tomas.k.7

  [  ](https://wordpress.org/support/users/tomask7/)

 *   [Profile](https://wordpress.org/support/users/tomask7/)
 *   [Topics Started](https://wordpress.org/support/users/tomask7/topics/)
 *   [Replies Created](https://wordpress.org/support/users/tomask7/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/tomask7/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/tomask7/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/tomask7/engagements/)
 *   [Favorites](https://wordpress.org/support/users/tomask7/favorites/)

 Search replies:

## Forum Replies Created

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

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress Related Posts] Plugin could not be activated because it triggered a fatal error.](https://wordpress.org/support/topic/plugin-could-not-be-activated-because-it-triggered-a-fatal-error-471/)
 *  [tomas.k.7](https://wordpress.org/support/users/tomask7/)
 * (@tomask7)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/plugin-could-not-be-activated-because-it-triggered-a-fatal-error-471/#post-10132278)
 * Plugin author uses “new” arrays declaration such as “$array = [];”… in files 
   config.php and analytics.php. This is not supported in PHP 5.3 and older.
 * Is it possible, for backward compatibility, to use former syntax (“$array = array();”)
   instead? I had to change it manually after upgrade 🙁
 * Thanks
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Related Posts for WordPress] Arrays declaration](https://wordpress.org/support/topic/arrays-declaration/)
 *  Thread Starter [tomas.k.7](https://wordpress.org/support/users/tomask7/)
 * (@tomask7)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/arrays-declaration/#post-10132273)
 * my mistake – wrong plugin, apologies.
 * correct one is [https://wordpress.org/support/plugin/wordpress-23-related-posts-plugin](https://wordpress.org/support/plugin/wordpress-23-related-posts-plugin)
    -  This reply was modified 8 years, 1 month ago by [tomas.k.7](https://wordpress.org/support/users/tomask7/).
    -  This reply was modified 8 years, 1 month ago by [tomas.k.7](https://wordpress.org/support/users/tomask7/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Rich Text Tags] non-breakable space issue](https://wordpress.org/support/topic/non-breakable-space-issue/)
 *  Thread Starter [tomas.k.7](https://wordpress.org/support/users/tomask7/)
 * (@tomask7)
 * [11 years, 10 months ago](https://wordpress.org/support/topic/non-breakable-space-issue/#post-5063317)
 * core issue (from wp-includes/formatting.php::function wp_htmledit_pre($output)):
 * var_dump(htmlspecialchars(html_entity_decode(‘A& nbsp ;A’), ENT_NOQUOTES, ‘UTF-
   8’ )); // –> string(0) “”
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress Related Posts] Virtual "page" -> fail to load page](https://wordpress.org/support/topic/virtual-page-fail-to-load-page/)
 *  Thread Starter [tomas.k.7](https://wordpress.org/support/users/tomask7/)
 * (@tomask7)
 * [12 years, 5 months ago](https://wordpress.org/support/topic/virtual-page-fail-to-load-page/#post-4424312)
 * resolved -> it was combination of two plugins… the sexond one had:
 * include( ABSPATH . ‘wp-admin/includes/image.php’ );
 * instead of
 * include_once( ABSPATH . ‘wp-admin/includes/image.php’ );
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Rich Text Tags] Editor goes blank after a few repeated edits](https://wordpress.org/support/topic/editor-goes-blank-after-a-few-repeated-edits/)
 *  [tomas.k.7](https://wordpress.org/support/users/tomask7/)
 * (@tomask7)
 * [12 years, 5 months ago](https://wordpress.org/support/topic/editor-goes-blank-after-a-few-repeated-edits/#post-4252240)
 * I found out, this is caused by whitespaces in the beginning/at the end of the
   text…
 * you can modify wp_term_taxonomy.description field for for affected term, remove
   characters like \n, \r, & nbsp ; (without spaces)  , \t etc. from the beginning
   and ending of the database field… (a lot faster way to fix if you have access
   to phpmyadmin/any other db admin tool)
 * of course, it would be nice, if author could fix the plugin 🙂

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