jQuery 3.x patch
-
Currently, when you select the jQuery version as “WordPress default” in the jQuery Migrate settings, Transposh’s translation edit mode does not work.
So, I tried to modify Transposh’s jQuery program from legacy 1.12.4 to jQuery 3.x as follows, but it doesn’t work. Maybe there’s a problem with the core of WordPress 5.6, but I’m not sure.
I would like to receive a professor from someone who has any other hints.If there is no patch for Transposh as it is, “jQuery Migrate” will be abolished in the release of WordPress 5.7 (jQuery 3.5.1), and Transposh may not work completely, so I would like to ask the author for support.
◇ transposh.js
c(“.”+r+”setdeflang”).click(function(){return c.ajax({url:t_jp.ajaxurl
↓
c(“.”+r+”setdeflang”).on(“click”,function(){return c.ajax({url:t_jp.ajaxurl◇ jquery.ui.menu.js
.bind → .on
.unbind → .offremoveAttr → ???
◇ admin/contexthelp.js
!function(l){l(“.tp_help”).live(“click”,function(e){e.preventDefault(),window.scrollTo(0,0),l(“#tab-link-“+jQuery(this).attr(“rel”)+” a”).trigger(“click”),l(“#contextual-help-link”).hasClass(“screen-meta-active”)||l(“#contextual-help-link”).trigger(“click”)})}(jQuery);
//# sourceMappingURL=contexthelp.js.map
↓
!function(l){l(document).on(‘click’,’.tp_help’,function(e){e.preventDefault(),window.scrollTo(0,0),l(“#tab-link-“+jQuery(this).attr(“rel”)+” a”).trigger(“click”),l(“#contextual-help-link”).hasClass(“screen-meta-active”)||l(“#contextual-help-link”).trigger(“click”)})}(jQuery);
//# sourceMappingURL=contexthelp.js.map◇ admin/languages.js
i(this).click(clickfunction)})}}),
↓
i(this).on(“click”,clickfunction)})}}),
etc.,◇ admin/contexthelp.js.map
$(‘.tp_help’).live(‘click’, function (event) {\n
↓
$(document).on(‘click’, ‘.tp_help’, function (event) {\nThe page I need help with: [log in to see the link]
-
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.
The browser is the Chrome version of Microsoft Edge.
If I set the jQuery version setting to “Legacy 1-12-4-wp”, the edit dialog will be displayed normally as shown in the screenshot below.https://www.senris.com/images/screenshot/Transposh-2021-02-03-2.jpg
P.S.
I just made a big discovery!
It was displayed normally in the Chrome browser on Android.
The display seems to be broken on Microsoft Edge (Chrome version).
The screenshot is at the following URL.https://www.senris.com/images/screenshot/Transposh-2021-02-03-3.jpg
- The topic ‘jQuery 3.x patch’ is closed to new replies.
