Title: jakramer's Replies | WordPress.org

---

# jakramer

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

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

 Search replies:

## Forum Replies Created

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

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Blocks for ACF Fields — Display Custom Fields in the Block Editor] Check for ACF presence too early for ACF bundled with theme](https://wordpress.org/support/topic/check-for-acf-presence-too-early-for-acf-bundled-with-theme/)
 *  Thread Starter [jakramer](https://wordpress.org/support/users/jakramer/)
 * (@jakramer)
 * [5 months, 1 week ago](https://wordpress.org/support/topic/check-for-acf-presence-too-early-for-acf-bundled-with-theme/#post-18835942)
 * Thanks so much! We’re excited that we will be able to use your plugin going forward!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Slider, Gallery, and Carousel by MetaSlider - Image Slider, Video Slider] Fatal Error: must be array, null given](https://wordpress.org/support/topic/fatal-error-must-be-array-null-given/)
 *  Thread Starter [jakramer](https://wordpress.org/support/users/jakramer/)
 * (@jakramer)
 * [1 year, 5 months ago](https://wordpress.org/support/topic/fatal-error-must-be-array-null-given/#post-18313700)
 * Yes, the version you linked above is working for us. Thanks so much for the quick
   response!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[SyntaxHighlighter Evolved] [code] in classic block re-encode , & on every edit](https://wordpress.org/support/topic/code-in-classic-block-re-encode-on-every-edit/)
 *  Thread Starter [jakramer](https://wordpress.org/support/users/jakramer/)
 * (@jakramer)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/code-in-classic-block-re-encode-on-every-edit/#post-17363768)
 * Thanks for looking into this. We would love to walk away from the classic block,
   but unfortunately not an option for this use case. We’ve found a different approach
   that will work with classic though, so we’ll go that way.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[SyntaxHighlighter Evolved] [code] in classic block re-encode , & on every edit](https://wordpress.org/support/topic/code-in-classic-block-re-encode-on-every-edit/)
 *  Thread Starter [jakramer](https://wordpress.org/support/users/jakramer/)
 * (@jakramer)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/code-in-classic-block-re-encode-on-every-edit/#post-17345489)
 * Hi, 
   Thanks for the response. This is exactly the issue. I can do what you suggest
   above, and have, but then if I ever edit the page again, the content gets re-
   encoded, which basically means the page can never be edited after it has been
   created.What I need is for the plugin to correctly identify whether the content
   needs to be encoded/decoded in the context of the classic block.
 * I did find that if I comment out the encoding step in this function:
 *     ```wp-block-code
         // The callback function for SyntaxHighlighter::encode_shortcode_contents()
         function encode_shortcode_contents_callback( $atts, $code = '', $tag = false ) {
           $this->encoded = true;
       // Commenting out the following line fixes bug with classic block (but probably breaks things for other cases)  
         //$code = str_replace( array_keys( $this->specialchars ), array_values( $this->specialchars ), htmlspecialchars( $code ) );
           return '[' . $tag . $this->atts2string( $atts ) . "]{$code}[/$tag]";
         }
       ```
   
 * I am then able to edit the content within the classic block without the characters
   being re-encoded every time, but the display in the visual editor doesn’t show
   the characters correctly.
 * Given that additional context, can you give me any pointers on where to look 
   for the conditions under which that encode function is called, so that I can 
   carve out an exception to make classic editor work correctly (rather than just
   commenting it out completely)?
 * Thanks!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Shibboleth] Clarification of Default Role: None, accounts still created with no role mapping](https://wordpress.org/support/topic/clarification-of-default-role-none-accounts-still-created-with-no-role-mapping/)
 *  Thread Starter [jakramer](https://wordpress.org/support/users/jakramer/)
 * (@jakramer)
 * [7 years, 3 months ago](https://wordpress.org/support/topic/clarification-of-default-role-none-accounts-still-created-with-no-role-mapping/#post-11471340)
 * Sounds good. Thank you.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Password Protect Wordpress] PHP7 Issue](https://wordpress.org/support/topic/php7-issue-3/)
 *  [jakramer](https://wordpress.org/support/users/jakramer/)
 * (@jakramer)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/php7-issue-3/#post-9585720)
 * This sounds pretty shady, but I searched all files for Error and found /lava/
   _classes/h2o/errors.php tries to define ParseError. I renamed the class ppwParseError,
   assuming I’d search for instances of ParseError and replace them with the new
   class name, but I couldn’t find anywhere the class was actually used.
 * This solved my problem in test. I can’t think of any issues this might introduce(
   since the class doesn’t seem to be used), but I’ll test some more before moving
   it to production, just the same.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Custom Contact Forms] cross origin errors with MU and mapped domains](https://wordpress.org/support/topic/cross-origin-errors-with-mu-and-mapped-domains/)
 *  Thread Starter [jakramer](https://wordpress.org/support/users/jakramer/)
 * (@jakramer)
 * [10 years, 5 months ago](https://wordpress.org/support/topic/cross-origin-errors-with-mu-and-mapped-domains/#post-7132188)
 * Thanks. I’ll go test this out!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Custom Contact Forms] cross origin errors with MU and mapped domains](https://wordpress.org/support/topic/cross-origin-errors-with-mu-and-mapped-domains/)
 *  Thread Starter [jakramer](https://wordpress.org/support/users/jakramer/)
 * (@jakramer)
 * [10 years, 5 months ago](https://wordpress.org/support/topic/cross-origin-errors-with-mu-and-mapped-domains/#post-7132087)
 * Here is one example. The same problem occurs for all forms on sites with mapped
   domains.
 * [http://grasp.education.illinois.edu/contact-us/](http://grasp.education.illinois.edu/contact-us/)
 * Thanks!

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