Wrong placement in latest update

  • Resolved squeebo

    (@squeebo)


    5 years, 11 months ago

    The recent update, either 2.02 or 2.01, has caused the TOC to be placed inside of the first H2 tag on the content, instead of before the first H2 tag like it was before. I just noticed it this morning, and a couple days ago I’m sure it was fine. I noticed that the font size was unusually large of all of a sudden, and I confirmed the weird code placement by looking at the source.

    It is the same on all of my posts, whether they begin with an H2 tag or begin with a P tag; the TOC is inside the first H2 tag, wherever it may be.

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

    (@shazahm1hotmailcom)

    5 years, 11 months ago

    Please share a link to an affected page.

    Thread Starter squeebo

    (@squeebo)

    5 years, 11 months ago

    Can I share the link privately somehow? I don’t share my website URL publicly when I’m having technical issues, due to issues in the past with my website’s problems coming up in the SERPs.

    Steven

    (@shazahm1hotmailcom)

    5 years, 11 months ago

    well… take a screenshot of the address and share a link to the screenshot.

    Steven

    (@shazahm1hotmailcom)

    5 years, 11 months ago

    Ok, I see what the issue is… the last update made matching a little less strict because page builders dynamically add classes/id and such to heading which make it very challenging to insert the in page links. Looks like this will negatively affect the placement when auto insert is set to before/after first paragraph. I suggest rolling back to 2.0.1 for now.

    Thread Starter squeebo

    (@squeebo)

    5 years, 11 months ago

    Rolling back to 2.0.1 worked, thanks!

    Steven

    (@shazahm1hotmailcom)

    5 years, 11 months ago

    @squeebo

    Version 2.0.3 should correct the insertion bug. Trying to account for all the page builders has been an interesting challenge requiring all sorts of little tweaks. I think its getting a little more solid each release even if a issue sneaks past testing. Apologies for the trouble.

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

The topic ‘Wrong placement in latest update’ is closed to new replies.