Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Hi @borderlain, thanks for taking the time to leave a review. I’m glad to hear the update fixed the issue for you!

    Hi @borderlain,

    If you’ve checked the code of the plugin and it definitely isn’t modified, that seems like a bug with WordFence’s scanning system. It might be picking up an older version of the code even though it hasn’t changed much over the past few years.

    I’ll try pushing an update to version 1.1 now to see if that helps. You should see the update available in your websites within the next 24 hours. After updating, I’m assuming the message in WordFence will disappear. If not, I’d recommend contacting their support team or your host so they can check if there is any modified files that need to be checked, or if the bug in WordFence could be fixed at their end.

    @mrclayton the example looks good and would solve the issue in my opinion.

    Just wanted to add my voice to this thread. I agree that the delay is very long. It takes several seconds to appear, at which point a lot of people will have either bounced or scrolled down without realising Apple/Google Pay is available.

    I appreciate this isn’t a bug with the plugin itself, and is caused by the slowness of the iframe of a 3rd party. However I believe this is still an issue that deserves attention. Is there a workaround? E.g. preloading the iframe or delaying the load of checkout until the iframe as had a couple of seconds to load.

    Plugin Support Sean (pipdig)

    (@seanpipdig)

    Hi @joomart, thanks for clarifying that for me. So to make sure I understand, is it the following steps as an example?

    1. Post published on Blogger on date 25th May 2026 (link is example.com/2026/05/post-title.html)
    2. Post edited in blogger after published, date changed to 15th June 2026 (link remains as May 2026 – example.com/2026/05/post-title.html)
    3. Post imported to WordPress as example.com/2026/06/post-title.html (month 06 instead of 05)

    If that is the case, I don’t think it will be possible to retrospectively change the link. It is imported directly from the Blogger API. Blogger itself must handle that kind of link change outside of its own API, so we would have no way to getting that data.

    However the good news is that the Blogger redirect template (installed as the last step of the migration) will handle this for you. The example.com/2026/05/post-title.html link will automatically redirect to example.com/2026/06/post-title.html and show the post.

    Hopefully I have understood your question. Let me know if not and I’ll be happy to help further.

    Plugin Support Sean (pipdig)

    (@seanpipdig)

    Hi @joomart,

    Yes the links should be identical in your case. Are you able to let me know an example of one of the links that is not correct? If you can let me know the correct link, as well as the imported link (the incorrect link) I might be able to see what has caused it.

    As a guess, it might be related to if the post already exists. For example, if a post link is “example.com/2026/07/post-title.html” but a post already has the title “post-title”, then it would result in “example.com/2026/07/post-title-1.html” by appending the link with a “-1”. This is not controlled by the plugin but is part of WordPress itself. Does it look like the imported links have a number appended to them? Or are they substantially different with different words etc?

    Thanks,

    Sean

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