Forum Replies Created

Viewing 15 replies - 1 through 15 (of 19 total)
  • Hi @magicfilou

    I actually steered clear of this bestazon plugin, due to the serious doubts about the ongoing support you, I and probably many others have.
    Like you rightly pointed out, the facts speak a very clear language…

    Instead, I was looking at this plugin:
    This seems like a very solid solution and is definitely actively supported.
    I can confirm this because I actually opened several support threads and the developer Paul was super helpful and nice.

    Check it out, I think it’s a actually a much better option.

    Thanks for the quick reply!
    It’s just strange that there are so many support threads unanswered, even though those people obviously were looking for help or a solution.

    I uninstalled grammarly from chrome and this has fixed part of the problem.
    Posts can be updated again.
    So it definitely seems to be a conflict between Grammarly and WordPress.

    Does anyone know whether or not this is going to be fixed by the Grammarly folks?

    However, the HTML insertion are still all over the place.
    Does anyone know how to remove them efficiently?


    That fixed it, thank you so much :)!
    Probably never would have tried that 😉


    Hi and thanks for your help, I’ll try to give you all information available to me:

    1) English

    2) I am pretty sure that I hit the “plus” button to create the translations (what you have marked as the green option 2 in your screen shot).

    3) Pages are also affected (I’m not using categories).

    4) This issue occurs with Yoast SEO 9.4.0. The update menu doesn’t give me the option of version 9.4.1.

    5) Yes, all other plugins are up-to-date, except Yoast SEO which is running on 9.3 to prevent this issue.

    Additional observation:

    I am using the “more” tag in all posts and so on the main page all the recent blog posts are displayed with content before the more tag showing up (I’m using twenty seventeen theme).
    After updating to 9.4.1 which causes this error, I noticed that the first paragraphs of each post before the more tag are still being shown on the home page.
    Only when clicking the “read more” link or on the feature image does it open the empty posts (“nothing found – ready to start your first post?”

    So that’s weird that on the home page there seems to be content within every post, but going into the posts, there’s none.

    Also, I double checked and it doesn’t matter which language existed first for a given post.
    Whether English was the first version or later created as a translation, only the English versions are affected, none of the other languages.

    Thanks for your help :)!

    • This reply was modified 4 months, 1 week ago by rhisflow.

    I had already contacted Yoast first, a few days before opening this thread.
    Following their very helpful tips, it turned out that the conflict is caused by the interaction of polylang with Yoast.

    As they suggested: “Please report the issue to a third party developer as well”.

    I hope the plugin author or someone else can give advice on how to make those two plugins be nice to each other again 🙂

    Thanks for your detailed reply!

    This happens:
    1) using a default theme (twenty seventeen)
    2) WordPress 5.0.3

    Going through your recommended conflict check, I was able to narrow down the issue.
    The conflict is between the Yoast SEO plugin and Polylang.
    When I update Yoast to 9.4 and have Polylang enabled, the English posts no longer appear.
    Leaving polylang activated and not updating Yoast (but leaving it on 9.3) causes no problems.

    I have also opened a thread on the polylang support, but it may very well be that Yoast plays a part in this issue also.

    Thanks for your support!

    Hi Otto,

    thanks for the detailed explanation and video, really appreciate it 🙂 !
    I have been using this method already, the only downside to it is that in very rare cases, if the screen width is funny, then there is just a letter or two on the left side of the image as the text resizes smaller and smaller.
    With media & text, this issues doesn’t seem to occur, plus there’s the option “stack on mobile” to also prevent this “squeezing” issue of text on small screens.
    What’s your thought on that?

    Also, with media & text, is it intended to not be able to add a caption to the image?
    I can’t see the advantage of not having that option.

    Thanks so much!

    No worries, thanks for the honest answer 🙂 !

    all the best!

    Oh, ok, got it!
    When do you think the first “new” version will be out?
    Just a rough timeline is good enough…days, weeks, months?

    I’m looking forward to the new release!

    Thanks a lot 🙂

    I have not, actually, as I’m hesitant with release candidates.
    I prefer to wait for a stable, official release.
    Since this has been 3 months ago, when do you reckon the version you sent me will be officially released?
    I’ll give it a go then.



    I was just wondering how the next update that you mentioned is coming along?
    The plugin is still giving this hyphen problem when used via shortcode.


    I just tested it and it works like you said it would!
    I got confused because some foreign languages showed up among the translated ones, but that is because there’s no translation for those yet.

    So everything works like a charm, thanks 🙂 !

    Hi Hector,

    I think I didn’t explain myself well.

    No, currently there’s no way to exclude untranslated posts from the listing.

    I wasn’t talking about excluding anything.
    But maybe I’m misunderstanding the functionality of the plugin completely.
    Let’s take my example from before:

    Original author John writes the post “English post”.
    Then Jane translates that post to German, calling it “German post” (which has it’s own URL slug “…/de/…”)

    Let’s assume that the English version get’s read 9 times, and the German version 1 time.
    In the stat counter of WPP, the plugin will attribute 10 times to the English version.
    So far, this is fine with me and I’m in line with your reasoning that this is sound logic, as this post is in fact the most popular, regardless of its language version.

    Now, here is where my misunderstanding might come in:

    How can I display the translated versions of this post to readers who are on the German version of the site?
    Let’s say I implement the plugin on the homepage to display the most popular posts.
    So there is the “” version in English and the “” in German.

    All I’d like to achieve is display the translated version of that popular post to the correct audience, and not show the English title of it to readers of the German site.

    Does this make sense?

    Hi Hector,

    thanks for your quick and comprehensive reply.
    Of course I absolutely respect your decision to not change anything about the table structure.
    Is there at least a workable solution to return the post title in an alternative language?
    So I’m thinking while the DB table might keep on tracking the original post as you explained – after retrieving that as the most popular one, can a filter check if that post has a translation?
    So there would be no need to change anything at the DB level, while still avoiding foreign language posts on other languages of the same site.
    You know what I mean?

Viewing 15 replies - 1 through 15 (of 19 total)