Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter vokabre

    (@vokabre)

    It seems that I managed to fix the case (for now).

    First I’ve noticed that the bug dissapears if %post_id% is added to permalinks.
    I’ve tried the plugin with a different and older WordPress installation and got the same result with 404 on posts, so then I re-checked .htaccess files and webserver configs, but nothing came up.

    Then I dug into the plugin’s code and eventually fixed the problem by removing this piece from qtranslate_frontend.php (I’m ignoring a few commented lines for the quote).

    `if($single_post_query){
    $single_post_query = preg_match(‘/ID\s*=\s*[\'”]*(\d+)[\'”]*/i’,$where,$matches)==1;
    }`

    Honestly, I don’t quite understand what happened, but everything seems to be working fine now.

    Thread Starter vokabre

    (@vokabre)

    Thanks for a quick answer!
    For me it’s not so, I’m getting WordPress 404 response.

    As you replied I thought that it might’ve been because of bad code in the theme, or because of some plugin doing something strange, but I’ve tried with the default twenty-fiveteen-theme and no plugins active besides qtranslatex, and still, I get 404 on untranslated posts.

    I’ve also just noticed that with pages everything works fine, only posts are affected.
    That’s confusing.

    Hi again! I got in touch with an author of the original Russian translation. He said that he’s no longer using the plugin and he’s fine with me fixing the translation. As I’m not sure how to push the new translation into the plugin, here’s a link to that russian.txt with fixes: https://vokabre.com/share/russian2.txt Feel free to add this one to new revisions.

    Thanks for the fast reply!

    I’ve tried changing the line 168, but it didn’t work.
    Please excuse my nobbless in the land of code, but I played with the plugin a little bit more, and managed to make it display the text provided by changing line 189 instead.
    from
    $recaptcha_response->error = $answers [1];
    to something like
    $recaptcha_response->error = 'here be dragons';

    Still, I couldn’t make the plugin to display lang_ antispam_error, and also there’s no error message (or success message, fortunately) for an empty recaptcha sent. Not a big issues, but still, those are there.

    I directed my thoughts to the author of the translation, thanks for recommending me to contact him directly.

    Hi DanielSchurter!
    I like your plugin, love the level of customisation there.

    But I got the same issue as the topicstarter, “incorrect-captcha-sol” displayed instead of “language_error_anispam”. I’ve looked briefly through your code, but couldn’t make it display the right error message.

    Also, just not to start a new topic, in the Russian translation there’s a few mistakes.
    Here’re fixed versions of fields with mistakes with comments:

    <antispam><b>Защита от спама</b>
    Введите пожалуйста комбинации букв или цифр в текстовое поле перед отправкой записи в гостевую книгу</antispam>
    —In the original there’s “Вводите” instead of “Введите”, grammatical mistake

    <submit>Отправить</submit>
    —“Записать” isn’t quite a right word, it’s more like “write” than “send” or “submit” which is “Отправить”

    <admin_review>Администратор сайта проверяет эту запись!
    Спасибо за терпение!</admin_review>
    —“терпения”, a grammatically incorrect plural form used instead of “терпение”.

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