Nekomukuro
Forum Replies Created
-
Forum: Plugins
In reply to: [Polylang] Function to get all translations of a stringThank you very much, that’s very helpful!
I just tested the navigation using Polylang as well, and it seems to be working alright! 🙂
Thank you for your work, I hope to see the stable version soon so that I can update my actual site.My host doesn’t allow me to install/update plugins manually, only through the WP interface, so I just did a quick test on my local test server.
It seems to be working as expected with both options ticked, and that’s great. I don’t have Polylang installed here at the moment, though, I should try to see if it still works alright using it, too. I’ll do it as soon as I have a bit more time.The only thing I’d like to point out, under an usability point of view, the description of the options doesn’t make it clear that both checkboxes need to be ticked if you want grouping by parent. From the way it’s worded, it seems that if you select the second you don’t need the first, when in fact you need both.
Anyway thanks a lot for the update 🙂
Wonderful. Thank you!
Thanks for the reply. 🙂
Manga+Press is using a custom version of get_adjacent_post() and get_boundary_post() to create the navigation — I think that’s how those two functions behave when you group posts by category and the behavior you’re describing fits that.
Yes, I actually went through the code and I’ve seen the mpp_get_boundary_comic() function by following the method calls starting from the theme. I thought it’s probably the one at fault, but I just can’t understand what’s going on in there. I’m a programmer, but I know almost nothing of how wordpress works.
Thanks for letting me know, and I’m sorry that I don’t have a solution for you right away, but I should have one soon!
That’s great, I’ll look forward to it, thank you! 🙂
Okay, nevermind, I just found that the PLL_SYNC constant default is set in polylang.php, so I changed it from true to false and it works. Still, I guess this means any time Polylang gets upgraded it will be overwritten… :/ It’s better than nothing though.
I hope this option will be configurable using the UI in the future… 🙂
Forum: Plugins
In reply to: [xLanguage] [Plugin: xLanguage] Editor tools brokenOkay, I wanted to use this plugin for a site and had the same problem, so I went to do a bit of debugging of the scripts and I found the cause and I think got it working (at least so it seems).
The plugin adds the new functions to the TinyMCE editor so that when you press the apply language button it does a few transformations of the text by first striking it through using
<strike>and then retransforming it back to<span lang="it">(I haven’t understood much the logic in the process, but I saw what it does more or less).
The problem is that when it applies the strike to the newly selected text, it uses theexecCommand('Strikethrough')instruction, which does NOT add a<strike>tag, but it adds a<del>tag instead. Since the script looks for “STRIKE”, it cannot find it and the text won’t get correctly tagged.To fix this I opened the js/tinymce-plugin.js inside the plugin directory with a text editor and did a search/replace, replacing all occurrences of STRIKE with DEL.
It seems to be working after doing this. I haven’t tested that much though, and also, I replaced case sensitive at the moment but I don’t know if it’s enough. I haven’t encountered troubles so far but if you do try replacing lowercase as well.
Hope it helps others.I just stumbled on this problem. Clope’s solution worked for me (thank you, I was really lost :))
Indeed, $_SERVER[‘DOCUMENT_ROOT’] returns only the base root of the site, but if WP is on a subdirectory, the plugin doesn’t know it and gets lost.Alternatively to clope’s temp fix, just in order to change much less lines of code, you can just change
define('ABSPATH', $_SERVER['DOCUMENT_ROOT'] . '/');
to
define('ABSPATH', $_SERVER['DOCUMENT_ROOT'] . '/wordpress/');Or instead of ‘/wordpress/’ whatever directory WP is installed into. I just did this and it started working perfectly again.