Tagged: 

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • April 3, 2025 at 12:20 pm #1480712
    orianos

    After the latest Enfold 7 and 7.1 update, many of the pages on the site (see below url) give me this error:

    >’It seems you are currently adding some HTML markup or other special characters. Once all HTML tags are closed the preview will be available again. If this message persists please check your input for special characters and try to remove them.

    Up to version 6.x I am sure this error did not exist.
    Since the pages on which I get this error are so many… it is impossible for me to identify where the error code is.
    Do you have any suggestions for finding the solution.

    Best regards
    Oriano

    April 3, 2025 at 12:35 pm #1480713
    orianos

    I did this test: I duplicated one of the pages giving the error “HTML markup error”, then go to edit the duplicate page, and the error is no longer reported 😳
    Do you have any suggestions?

    Best regards,
    Oriano

    April 3, 2025 at 12:48 pm #1480714
    orianos

    No, I was wrong, duplicating the page does not solve the error problem.

    I also don’t think it has anything to do with the new Enfold 7.x version, because on the other sites I use Enfold on, I don’t encounter the same problem.
    So it seems to be a problem specific to the site in question.

    Please could you please help me identify the point(s) (tag) causing the error?

    Best regards,
    Oriano

    April 3, 2025 at 7:07 pm #1480729
    Rikard

    Hi,

    Please send us a temporary WordPress admin login and login URL so that we can have a closer look. You can post the details in the Private Content section of your reply.

    Best regards,
    Rikard

    April 4, 2025 at 2:38 pm #1480773
    orianos

    Hi Rikard,
    brief update, with surprise.
    Yesterday I noticed that the error (HTML markup error) was only visible if I edited pages with Safari 18.4, whereas if I opened the same pages with Firefox 136.0.4, the error was not reported 😲 , also because in reality the tag error was not there.

    I have now cleared all the Safari caches, and it seems that Safari also reads the code pages correctly.

    At this point, if we want to continue to use html tags (like in the titles (ALB Special Heading), to avoid a browser getting confused and reporting an error that does not exist, what is the best and safest solution? 😳

    Best regards,
    Oriano

    April 4, 2025 at 3:56 pm #1480775
    Rikard

    Hi,

    Thanks for the update. So this problem only happens in Safari 18.4?

    Best regards,
    Rikard

    April 4, 2025 at 4:10 pm #1480777
    orianos

    Hi Rikard,
    I emptied Safari’s cache, and the error (HTML markup error) is no longer reported in Safari 18.4.

    What should we do to be able to continue using html tags (such as <strong></strong>) in ALB Special Heading and prevent the browser from getting confused and reporting an error that they do not exist?

    Best regards,
    Oriano

  • Author
    Posts
Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.