Title: greftek's Replies | WordPress.org

---

# greftek

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

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

 Search replies:

## Forum Replies Created

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

 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Can’t Remove/Edit Widget in WordPress 2.5](https://wordpress.org/support/topic/cant-removeedit-widget-in-wordpress-25/)
 *  [greftek](https://wordpress.org/support/users/greftek/)
 * (@greftek)
 * [18 years ago](https://wordpress.org/support/topic/cant-removeedit-widget-in-wordpress-25/#post-732149)
 * How exactly is that a fix? IMO is should work on both browsers.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Insert/Edit Image Bug in 2.3](https://wordpress.org/support/topic/insertedit-image-bug-in-23/)
 *  [greftek](https://wordpress.org/support/users/greftek/)
 * (@greftek)
 * [18 years, 2 months ago](https://wordpress.org/support/topic/insertedit-image-bug-in-23/#post-627067)
 * This bug is very consistent. TinyMCE seems to ‘asume’ in IE7 that whenever the
   dimensions field is left empty it should make it at least 1 pixel in both dimensions.
 * I see the ticket was closed as fixed in 2.5. So now what? Sit on our thumbs and
   wait for that version to come out? How about a patch for 2.3.x people?
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [realTinyMCE is not defined](https://wordpress.org/support/topic/realtinymce-is-not-defined/)
 *  [greftek](https://wordpress.org/support/users/greftek/)
 * (@greftek)
 * [18 years, 6 months ago](https://wordpress.org/support/topic/realtinymce-is-not-defined/page/3/#post-527065)
 * Actually I got it running fine with safe-mode. Setting up safe mode (and open_basedir
   as well) takes a lot of tweaking to get it working right.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Memory Limit Problem During Upgrade – Solution](https://wordpress.org/support/topic/memory-limit-problem-during-upgrade-solution/)
 *  [greftek](https://wordpress.org/support/users/greftek/)
 * (@greftek)
 * [18 years, 6 months ago](https://wordpress.org/support/topic/memory-limit-problem-during-upgrade-solution/#post-626209)
 * From a system administrator point of view just upping the memory limit from 8
   to 16M in PHP is potentially hazardous thing to do.
 * You have to realize that this is 8M per child extra, almost doubling the memory
   usage. Those figures stack up fast if you realize that a semi-productive server
   easilly can have about 80 childs running. Do the math. 😉
 * Unfortunately this IS the only answer for the end-user. I am sure the WordPress
   team can consider reviewing the code to reduce the memory burden it places on
   PHP installations.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [realTinyMCE is not defined](https://wordpress.org/support/topic/realtinymce-is-not-defined/)
 *  [greftek](https://wordpress.org/support/users/greftek/)
 * (@greftek)
 * [18 years, 6 months ago](https://wordpress.org/support/topic/realtinymce-is-not-defined/page/3/#post-527063)
 * If all of this fails I have another possible solution to the problem of a failing
   tiny_mce:
 * Disable display_errors.
 * I came across a similar problem on a wordpress copy I was running on a development
   server (where for debugging purposes display_errors on is a good thing ;)) I 
   had multiple blogs running on live servers with a similar setup so I could not
   pin down what the problem was.
 * Then I started firebug to check what the heck was going on and came across 3 
   lines through my javascript:
 *     ```
       <br />
       <b>Warning</b>:  realpath() [<a href='function.realpath'>function.realpath</a>]: Unable to access /home/1234/public_html/wp-includes/js/tinymce/plugins/inlinepopups/langs/nl_nl.js in <b>/home/1234/public_html/wp-includes/js/tinymce/tiny_mce_gzip.php</b> on line <b>195</b><br />
       <br />
       <b>Warning</b>:  realpath() [<a href='function.realpath'>function.realpath</a>]: Unable to access /home/1234/public_html/wp-includes/js/tinymce/plugins/inlinepopups/langs/nl.js in <b>/home/1234/public_html/wp-includes/js/tinymce/tiny_mce_gzip.php</b> on line <b>195</b><br />
       <br />
       <b>Warning</b>:  realpath() [<a href='function.realpath'>function.realpath</a>]: Unable to access /home/1234/public_html/wp-includes/js/tinymce/plugins/inlinepopups/langs/en.js in <b>/home/1234/public_html/wp-includes/js/tinymce/tiny_mce_gzip.php</b> on line <b>195</b><br />
       ```
   
 * Apparently the code is searching for language pack files in a plugin folder which
   it cannot find and this results in PHP WARNINGS. In my opinion someone should‘
   condition’ the code a little better to prevent it from tripping/breaking over
   something as trivial as this.

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