Title: sacrefizz's Replies | WordPress.org

---

# sacrefizz

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

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

 Search replies:

## Forum Replies Created

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

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Loco Translate] Titre : OpenAI translations contain JSON escape artifacts (\/ and \n)](https://wordpress.org/support/topic/titre-openai-translations-contain-json-escape-artifacts-and-n/)
 *  Thread Starter [sacrefizz](https://wordpress.org/support/users/sacrefizz/)
 * (@sacrefizz)
 * [4 months ago](https://wordpress.org/support/topic/titre-openai-translations-contain-json-escape-artifacts-and-n/#post-18821913)
 * Hi Tim,
 * I replicated your fix by hooking into http_request_args and re-encoding the batch
   JSON with JSON_UNESCAPED_SLASHES before it reaches the OpenAI API. The
   <\/p> 
   artifacts are gone.
 * The \n issue also seems resolved in my tests — likely because the LLM no longer
   tries to “match” the escaped style it receives in the input.
 * Looking forward to 2.8.2. Thanks for investigating and fixing this!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Loco Translate] Titre : OpenAI translations contain JSON escape artifacts (\/ and \n)](https://wordpress.org/support/topic/titre-openai-translations-contain-json-escape-artifacts-and-n/)
 *  Thread Starter [sacrefizz](https://wordpress.org/support/users/sacrefizz/)
 * (@sacrefizz)
 * [4 months, 1 week ago](https://wordpress.org/support/topic/titre-openai-translations-contain-json-escape-artifacts-and-n/#post-18815886)
 * Thanks Tim. The <\/p> is actually valid JSON escaping — OpenAI’s response is 
   correct JSON. The issue is that Loco embeds the raw API JSON string
   into its 
   own AJAX response without decoding it first, causing double-encoding. A json_decode()
   before re-serializing would fix this. I’ve written aclient-side workaround (jQuery
   dataFilter) that cleans the response before Loco parses it, which confirms the
   issue is in the decode/re-encodepipeline, not the model output.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[LoginPress | wp-login Custom Login Page Customizer] Password reset email in English](https://wordpress.org/support/topic/password-reset-email-in-english/)
 *  [sacrefizz](https://wordpress.org/support/users/sacrefizz/)
 * (@sacrefizz)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/password-reset-email-in-english/#post-18264431)
 * What is the issue ?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[ProfileGrid – User Profiles, Groups and Communities] Icon-pictures @ Groups](https://wordpress.org/support/topic/icon-pictures-groups/)
 *  [sacrefizz](https://wordpress.org/support/users/sacrefizz/)
 * (@sacrefizz)
 * [2 years, 4 months ago](https://wordpress.org/support/topic/icon-pictures-groups/#post-17432009)
 * same

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