Forum Replies Created

Viewing 15 replies - 1 through 15 (of 24 total)
  • Thread Starter Dpsachou

    (@dpsachou)

    This issue was resolved after unchecking the option “Also aggregate inline CSS” in the Autoptimize plugin.

    Thread Starter Dpsachou

    (@dpsachou)

    Hello. Correct. These are the exact features I have enabled.

    Other info about server that might help:
    Mysql 5,7
    Apache 2,4 with http2 enabled
    PHP handler: PHP-FPM & fcgi

    Hi,

    It works for me with this edits and when entering “1.9.2” in the jquery version field. Do you get any test fields at all when trying to edit the translation?

    • This reply was modified 5 years, 5 months ago by Dpsachou.

    Do the following:
    Open the file transposhedit.js and search for this:

    <textarea cols="80" row="3" name="original" id="'+u+'original" readonly="y"/><span id="'+u+'utlbar"><button id="'+u+'prev">'+v("previous translation")+'</button><button id="'+u+'zoom">'+v("find on page")+'</button><button id="'+u+'next">'+v("next translation")+'</button></span><label for="translation">'+v("Translate to")+'</label><textarea cols="80" row="3" name="translation" lang="'+t_jp.lang+'"id="'+u+'translation"/>

    And replace with this:

    <textarea cols="80" row="3" name="original" id="'+u+'original" readonly="y"/></textarea><span id="'+u+'utlbar"><button id="'+u+'prev">'+v("previous translation")+'</button><button id="'+u+'zoom">'+v("find on page")+'</button><button id="'+u+'next">'+v("next translation")+'</button></span><label for="translation">'+v("Translate to")+'</label><textarea cols="80" row="3" name="translation" lang="'+t_jp.lang+'"id="'+u+'translation"/></textarea>

    This will open the editor, but you should also change the option “Override jQueryUI version” in the Advanced settings of transposh – add 1.8.4 or something between 1.8 – 1.9 should work. Seems like the text areas are closing automatically at the wrong position with the new jquery parser(?).

    This is the solution as proposed by the creator Ofer Wald.

    • This reply was modified 5 years, 5 months ago by Dpsachou.

    Do this:
    Open the file transposhedit.js and search for this:

    <textarea cols="80" row="3" name="original" id="'+u+'original" readonly="y"/><span id="'+u+'utlbar"><button id="'+u+'prev">'+v("previous translation")+'</button><button id="'+u+'zoom">'+v("find on page")+'</button><button id="'+u+'next">'+v("next translation")+'</button></span><label for="translation">'+v("Translate to")+'</label><textarea cols="80" row="3" name="translation" lang="'+t_jp.lang+'"id="'+u+'translation"/>

    And replace with this:

    <textarea cols="80" row="3" name="original" id="'+u+'original" readonly="y"/></textarea><span id="'+u+'utlbar"><button id="'+u+'prev">'+v("previous translation")+'</button><button id="'+u+'zoom">'+v("find on page")+'</button><button id="'+u+'next">'+v("next translation")+'</button></span><label for="translation">'+v("Translate to")+'</label><textarea cols="80" row="3" name="translation" lang="'+t_jp.lang+'"id="'+u+'translation"/></textarea>

    This will open the editor, but you should also change the option “Override jQueryUI version” in the Advanced settings of transposh – add 1.8.4 or something between 1.8 – 1.9 should work. Seems like the text areas are closing automatically at the wrong position with the new jquery parser(?).

    This is the solution as proposed by the creator Ofer Wald.

    • This reply was modified 5 years, 5 months ago by Dpsachou.

    Do this:
    Open the file transposhedit.js and search for this:

    <textarea cols="80" row="3" name="original" id="'+u+'original" readonly="y"/><span id="'+u+'utlbar"><button id="'+u+'prev">'+v("previous translation")+'</button><button id="'+u+'zoom">'+v("find on page")+'</button><button id="'+u+'next">'+v("next translation")+'</button></span><label for="translation">'+v("Translate to")+'</label><textarea cols="80" row="3" name="translation" lang="'+t_jp.lang+'"id="'+u+'translation"/>

    And replace with this:

    <textarea cols="80" row="3" name="original" id="'+u+'original" readonly="y"/></textarea><span id="'+u+'utlbar"><button id="'+u+'prev">'+v("previous translation")+'</button><button id="'+u+'zoom">'+v("find on page")+'</button><button id="'+u+'next">'+v("next translation")+'</button></span><label for="translation">'+v("Translate to")+'</label><textarea cols="80" row="3" name="translation" lang="'+t_jp.lang+'"id="'+u+'translation"/></textarea>

    This should open the editor, but you should also change the option “Override jQueryUI version” in the Advanced settings of transposh – add 1.8.4 or something between 1.8- 1.9 should work. Seems like the text areas are closing automatically at the wrong position with the new jquery parser(?). This solution was proposed by the creator Ofer Wald at another post.

    • This reply was modified 5 years, 5 months ago by Dpsachou.
    • This reply was modified 5 years, 5 months ago by Dpsachou.
    • This reply was modified 5 years, 5 months ago by Dpsachou. Reason: Forgot to add things
    Thread Starter Dpsachou

    (@dpsachou)

    WP Discuz has an option to disable Font Awesome css, and this fixes the problem. This disables some icons in the comment section, but I can live with that. I have not researched further in the Font Awesome files for the culprit.

    Thread Starter Dpsachou

    (@dpsachou)

    It turns out that the issue appears when loading “Font Awesome css lib” in WP Discuz plugin along with “Inline all CSS”. Maybe after a WP Discuz plugin update a week ago.

    Thread Starter Dpsachou

    (@dpsachou)

    Hello,

    I just noticed but this issue did not appear a few days ago, before the update to WordPress 5.3. Tried installing Autoptimize 2.5 and 2.4.4 but the problem remains if I enable “Inline all CSS”. I am guessing maybe a conflict with another plugin causes it, so I will troubleshoot and get back to you.

    Thread Starter Dpsachou

    (@dpsachou)

    Forgot to mention that this issue appeared on version 2.5.1

    Thread Starter Dpsachou

    (@dpsachou)

    I have not enabled minify, but I am using Autoptimize for minification.

    Thread Starter Dpsachou

    (@dpsachou)

    Oh well ok then. Glad this was fixed 🙂

    Thread Starter Dpsachou

    (@dpsachou)

    Hello again,

    I just made a test with the old version of the plugin, and the problem solved with a session_write_close() command at the end of wp-server-stats.php file

    Screenshot

    • This reply was modified 8 years, 6 months ago by Dpsachou.

    Hello again,

    Saumya Majumder discovered that the issue is with themes or plugins that use PHP Sessions.

    After the session_start() command, php session hangs causing a timeout. This prevents the loopback request.

    After making some tests on my own, I found out that when the session is closed with a session_write_close() command, the issue disappears, and everything is working fine again. So the real issue does not seem to be on the php session itself, but rather to the open php sessions that never close.

    I guess that the open session locks the session files in php (?) and creating the problem.

    Thread Starter Dpsachou

    (@dpsachou)

    I get it now, but I don’t understand what’s wrong with php sessions. As far as I know, they don’t pose a security or other risk. Thank you for the detailed answer.

    I am impressed that you found the solution so quickly. You should inform the WordPress developers in this thread as they are trying to replicate the issue for days now.

    I will definitely consider a donation.

    • This reply was modified 8 years, 6 months ago by Dpsachou.
Viewing 15 replies - 1 through 15 (of 24 total)