Upgrade from 2.0.0 to 2.0.2 issue

  • Resolved lofesa

    (@lofesa)


    2 years, 10 months ago

    Hi
    Whit the 2.0.0 version post are centered in a row, upgraded and w/o change any options, then post are in a column and rigth aligned.

    Need to revert the update. If you need to see it I can apply temporally.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Adnan

    (@hiddenpearls)

    @lofesa

    aha, I see.

    Can you please apply it again and share the URL here?

    Thread Starter lofesa

    (@lofesa)

    Hi
    There is a url https://intersindicalrm.org/sanidad-concursos-de-traslados/
    And there is a non updated url https://intersindicalrm.org/ensenanza/basta-ya-de-burocracia-docente/

    • This reply was modified 2 years, 10 months ago by lofesa.
    Plugin Support Muhammad Arslan

    (@wparslan)

    Hey @lofesa

    The issue you are describing is an unusual one and is not the default behavior of Related Posts Thumbnails.

    We are curious about the issue and its origin, can you contact us on our support forum so we can help you resolve it.

    Looking Forward.

    Thread Starter lofesa

    (@lofesa)

    Hi
    I fount the issue root.
    Is incompatibilty with a plugin, Seo Internal Links, but this maybe occurs with similar plugins.

    This plugin add internal links to “key words” (words in titles, categories or tags) and when it add links to titles or exceprt in the related post stuff, it break the layout.

    Searching for how to solve this.

    Thread Starter lofesa

    (@lofesa)

    A workaround:
    Both plugins uses add_filter(the_content... and both with priority 10.
    Making priority less than 10 for Seo Internal Links does the work.
    Until now, I don’t know why, Seo Internal Links runs before Related Post and has no issue, when updated, Seo Internal Links runs after Related Post and the issue comes here.

    Thread Starter lofesa

    (@lofesa)

    Close this as solved with a workaround.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Upgrade from 2.0.0 to 2.0.2 issue’ is closed to new replies.