Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure custom IDs are not overwritten. #179

Open
Imran-imtiaz48 opened this issue Sep 25, 2024 · 0 comments
Open

Ensure custom IDs are not overwritten. #179

Imran-imtiaz48 opened this issue Sep 25, 2024 · 0 comments

Comments

@Imran-imtiaz48
Copy link

It seems like the Bigblow theme might have its own ID generation logic that overrides the custom IDs you've set in your headings. Since you’ve already overridden the table of contents (ToC) with success, you could explore similar areas to resolve this.

Here are a few approaches you could try:

  1. Check for an ID generation function: The theme likely has a function that generates IDs dynamically for sections and headings. Look for functions like generateId, slugify, or anything related to heading IDs in the theme's JavaScript or backend files. You can override this function or prevent it from replacing your custom IDs.

  2. HTML/Post-processing Hook: If Bigblow is rendering the final HTML output, you can try inserting a hook or custom filter that replaces the theme-generated IDs with your custom ones. This can be done during the post-processing phase before rendering.

  3. Disable Automatic ID Generation: There might be an option or flag to disable automatic ID generation in the theme’s configuration. Since you’ve already overridden a ToC-related function, it’s possible there are additional options you can modify to stop it from assigning random IDs.

If none of these help, you may want to explore whether the theme's maintainers or documentation offer a specific setting for handling custom IDs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant