Bug: ?Header Label‘ Option Not Updating in CATEGORY, TAG individually

Hi, thank you for reaching out to us. Could you please confirm which editor you are using? Additionally, kindly share a short video demonstrating the steps you’re taking and the issue occurring on your end. This will help us check it in the same way.

Classic editor.

If I add a TOC manually with a tag like [ez-toc header_label=”Your Title”], header_label is on a CATEGORY or TAG page ignored. The last functional version was 2.0.69.

Hi,

We have checked on our end and did not find any such issue. Kindly update the plugin to the latest version (2.0.71) and give it a try. If the issue still persists, please share a short video of the steps you are taking on your end so we can recreate the issue in the same way.

Hello, yes,

I experience this error on x.71. See settings:
https://ibb.co/0sthtLt
https://ibb.co/W0NDs70
https://ibb.co/BjqfwrQ
https://ibb.co/Fz6jJM4
https://ibb.co/472bk3F
https://ibb.co/ZWfV3sy
https://ibb.co/GQcJK2z

See backend and frontend (tag settings):

https://ibb.co/tBVrtCH
https://ibb.co/khV3B71

It possibly happens only when FIRST article in a TAG or CATEGORY is using also TOC menu. Then it is used the header_menu value from this first article.

See first article in this category:
https://ibb.co/2j15hYk

And menu in this article:
https://ibb.co/hdFj6m5
is used as a main menu in the whole category.

Hi, could you please share the exported settings of the TOC so we can import them on our end and check? This will help us recreate the issue. Please export the TOC setting, upload it to Google Drive, and provide the link.

Additionally, please provide the URL where you need assistance.

Sure. Here it is:

https://pastebin.com/BvnrR5ha

FYI: Last working version without this bug was x.69 (this bug appeared new in x.70 version).

Hi, thank you for sharing this. We have reviewed this and confirmed that it is a valid issue. A GitHub ticket has been raised for this concern, and it will be addressed in the upcoming update. We kindly request your patience in the meantime.

Here is the GitHub Ticket.

Hi, Hope you are doing well. We have released the new update version 2.0.72, in which we have addressed this concern. Kindly update the plugin to the latest version, clear the cache, and give it a try.