Title: mlochmann's Replies | WordPress.org

---

# mlochmann

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

 *   [Profile](https://wordpress.org/support/users/mlochmann/)
 *   [Topics Started](https://wordpress.org/support/users/mlochmann/topics/)
 *   [Replies Created](https://wordpress.org/support/users/mlochmann/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/mlochmann/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/mlochmann/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/mlochmann/engagements/)
 *   [Favorites](https://wordpress.org/support/users/mlochmann/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: [[Toolset Types - Custom Post Types, Custom Fields and Taxonomies] 1.6.2 and 1.6.3 Custom Fields Not saved](https://wordpress.org/support/topic/162-and-163-custom-fields-not-saved/)
 *  [mlochmann](https://wordpress.org/support/users/mlochmann/)
 * (@mlochmann)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/162-and-163-custom-fields-not-saved/#post-5322781)
 * Hi guys,
 * updated to 1.6.4 – not working. Same issue. Changed all custom fields to text
   fields. No luck. Turned off all validation and numeric fields. Nope. Not working.
   Now rebuilding custom post type and new data field set. Annoying bug.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Toolset Types - Custom Post Types, Custom Fields and Taxonomies] 1.6.2 and 1.6.3 Custom Fields Not saved](https://wordpress.org/support/topic/162-and-163-custom-fields-not-saved/)
 *  [mlochmann](https://wordpress.org/support/users/mlochmann/)
 * (@mlochmann)
 * [11 years, 10 months ago](https://wordpress.org/support/topic/162-and-163-custom-fields-not-saved/#post-5322766)
 * Hi Marcin, just tried it. No, not working. Also I’m not seeing my group of custom
   fields (personal data like name, email, phone etc.) in my custom post (person)
   admin page – it shows up briefly and then disappears. I have to activate it again
   at the top under options to show. I can change custom values with the wordpress
   own custom value fields though (eg. wpcf-name) – but not in the types custom 
   values fields. It won’t save anything. Javascript console show no errors. WP 
   4.0, php 5.4 Taxonomies and other admin stuff working fine. Oh, and of course
   I tried deactivating all other plugins first. No luck either.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Toolset Types - Custom Post Types, Custom Fields and Taxonomies] 1.6.2 and 1.6.3 Custom Fields Not saved](https://wordpress.org/support/topic/162-and-163-custom-fields-not-saved/)
 *  [mlochmann](https://wordpress.org/support/users/mlochmann/)
 * (@mlochmann)
 * [11 years, 10 months ago](https://wordpress.org/support/topic/162-and-163-custom-fields-not-saved/#post-5322763)
 * confirmed. Having this issue too.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Photo Gallery, Sliders, Proofing and Themes - NextGEN Gallery] Known Plugin & Theme Conflicts with NextGEN 2.0](https://wordpress.org/support/topic/known-plugin-conflicts-with-nextgen-20/)
 *  [mlochmann](https://wordpress.org/support/users/mlochmann/)
 * (@mlochmann)
 * [13 years ago](https://wordpress.org/support/topic/known-plugin-conflicts-with-nextgen-20/page/7/#post-3979575)
 * Ok, found this one: Using ob_start(“ob_gzhandler”); in the theme header – and
   now your version 2.0.0 breaks the site with an “330 (net::ERR_CONTENT_DECODING_FAILED)”.
   Removing the compression from the header solves the issue – but slows the site
   down. Tried to outcomment the lzw module in the plugin without success. Any ideas?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Connections Business Directory] [Plugin: Connections] Page admin tinymce broken in 3.4](https://wordpress.org/support/topic/plugin-connections-page-admin-tinymce-broken-in-34/)
 *  Thread Starter [mlochmann](https://wordpress.org/support/users/mlochmann/)
 * (@mlochmann)
 * [14 years, 2 months ago](https://wordpress.org/support/topic/plugin-connections-page-admin-tinymce-broken-in-34/#post-2834981)
 * @ Steven Zahm – your right, I’ve already done that – per .htacces and php.ini
   and wp-config.php. The problem is, when your’re on an old 1and1.com contract,
   you’ll get only 30 MB php process memory. The newer dual hosting contracts have
   80 MB.
 * A quick&dirty solution is to comment out all functions in the tinymce wp-langs.
   php file which causes the error. There are only string cleaning functions in 
   there. I haven’t figured quite out why these cleaning functions cause so much
   memory allocation. But now it works.

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