Hi jtcheng,
I can confirm that the fixed widget code exist for the ToC on the first site, but not the other.
What did you do to fix the widget? Which option did you enable? Is that option still enabled when you check now?
Which version of Fixed Widget do you use on the first site?
I am ignoring your second question because it seems like the one you asked in another thread – which is great for me to keep track of different things.
Thanks,
Thomas
Here’s a couple of screenshots to show what I am doing with the site where the TOC sidebar is not sticking.
Widgets screen:
https://snipboard.io/FzJI1N.jpg
Related plugins in question activated:
https://snipboard.io/cQge7y.jpg
These steps were taken with the older site though the behaviors are different.
Finally, here’s a screenshot showing the versions of the same plugins being used on the old site:
https://snipboard.io/Kko275.jpg
Unfortunately, I don’t have revision control to identify the actual version of the plugin that was installed back in August of last year I believe.
Thanks
Hi @jtcheng, thanks for the screenshots!
I am using Fixed Widget on our own websites as well mostly to make a Table of Contents sticky in the sidebar. So far, it works for me.
I set up a new test site with GeneratePress, LuckyWP Table of Contents, and Fixed Widget.
When I now navigate to the Widgets screen, I see a warning:
Notice: wp_enqueue_script() was called incorrectly. "wp-editor" script should not be enqueued together with the new widgets editor (wp-edit-widgets or wp-customize-widgets). Please see Debugging in WordPress for more information. (This message was added in version 5.8.0.) in /wp-includes/functions.php on line 5768
This message is gone when I removed the LuckyWP ToC plugin.
We had a similar issue with Fixed Widget registering the block script at the wrong time and they probably made the same mistake.
The good news is, they have a “legacy widget” as well. Just search for “table”, then select the block in the middle of the following screenshot.

Now select the Fixed widget option within the widget content.

This worked for me.
Let me know if it does for you.
Thomas
I just see that https://ww.wp.xz.cn/plugins/luckywp-table-of-contents/ wasn’t updated for two years, so you might want to look at alternatives.
Hi Thomas,
Thanks for looking into the Lucky WP TOC issue.
Based on your findings, I gave other TOC plugins a try.
Unfortunately, all of the ones I’ve tried below haven’t worked.
– Easy Table of Contents by Steven A. Zahn (throws errors in Appearance->Widget when activated)
– Table of Contents Plus by Michael Tran (currently in use, but sidebar not sticky just like with LuckyWP Table of Contents)
– Table of Contents Block by WPDeveloper (doesn’t even work; neither in content nor sidebar)
Thus, I still haven’t found a suitable table of contents plugin that works with the q2w3 fixed widget for the BloggingSideHustler site ever since the HomeownerHeadaches site exhibited working behavior last year (and that one still behaves as expected).
So I’m out of ideas as I’m not sure if this is a FixedWidget thing or if all the other TOC plugin authors have made mistakes that prevent the sidebar widget on FixedWidget from working.
Thanks
I also tried the Legacy Widget for the LuckyWP Table of Contents and I’m getting the same errors that I got for the Easy Table of Contents Legacy Widget.
https://snipboard.io/m54kBQ.jpg
So I’ll just keep this site in question on the TOC+ since it’s a different plugin that also isn’t sticking. That way, maybe there’s another piece of data concerning the compatibility of any table of contents widgets with fixed widget plugin.
Thanks
Thanks for your feedback.
I have also tested various TOC plugins with Fixed Widget yesterday. With most of them, I found a solution to make it work. I couldn’t identify a general issue with FW though that would prevent any TOC from not working. We use the Easy TOC plugin for years in combination with Fixed Widget, recently also with GeneratePress.
I will keep looking into the things I found, but since there is nothing working for you, I believe this must be a deeper issue that I might not be able to resolve.
All the best to you and your project!
Thomas