TOC shortcode doesn’t work with Thrive Architect

Hi garlick,

Are you adding the shortcode this way:

https://help.thrivethemes.com/en/articles/4425743-using-shortcodes-with-thrive-architect

If not, can you please try that?

Thanks,

David

Hi David, thank you for the response. I tried putting the shortcode into a WordPress Content element in the sidebar as you suggested, but unfortunately, the result is the same. The shortcode is translating to the entire page content, rather than the Wiki TOC like it does on all the other pages that use the same template.

Thanks,

-Tim.

Hi David, it looks like the Wiki posts are not using the Gutenberg editor, but the classic WP editor. Is that correct?

One workaround I was going to try was to use the Gutenberg editor to add Thrive Architect blocks to my content (that’s a thing). But when I went to edit a test page, the edit bar looks different, and I don’t have the option to add blocks. I haven’t been doing WP for very long, so I’m not sure, but I think it’s the old WP editor. Is there any way to use the Gutenberg editor with Yada Wiki posts, in case we can’t resolve the shortcode conflict?

Thanks,

-Tim.

Hi garlick,

It is not ideal, but you might try going into the editor for the TOC and copying all of the content (control-a control-c) and then going into the WordPress content element in the sidebar like you tried before and pasting it in. My guess is that would get rid of the duplication problem. If it does, then you could try wrapping that content in a DIV with a max-width style. Something like:

<div style="max-width:300px;">
pasted toc contents
</div>

You could adjust the 300px part until you got the width you want.

The TOC output works by programmatically getting the content of the TOC article and running it through apply_filters( 'the_content', $the_toc->post_content );.

I suspect Thrive is doing this also because they want to inject their special additions into the content, thus adding another copy. Normally I wouldn’t expect that since the wiki TOC article is not written with Thrive Architect (right?).

Yes, Yada Wiki uses the Classic Editor and not Gutenberg. It doesn’t work with Gutenberg at this time.

I hope this helps,

David

This article is what I was trying to do:

https://help.thrivethemes.com/en/articles/4661170-how-to-use-the-thrive-blocks-in-the-wordpress-editor-gutenberg

Since Yada Wiki doesn’t use Gutenberg I don’t think that will work.

Hi David, you are correct, the actual TOC article was not written with Thrive Architect, just the classic WP editor.

I tried your suggestion and pasted the TOC listing (just shortcodes to the articles) into my Theme Builder wiki page template’s sidebar. I went ahead and kept it in a WordPress Content element, although I suspect that it would have worked in a regular Text element as well. This worked!

It’s not too surprising, I suppose, since the wiki article shortcodes have been working in my other Thrive Architect-based content. It seems like only the TOC shortcode is not being rendered correctly by Thrive Architect/Theme Builder.

It does mean that I’ll have to remember to update the sidebar if/when I add new categories to my wiki, but at least it’s rendering correctly and I can move on.

Do you have any plans to add support for the Gutenberg editor in the future? That might resolve this issue better, as I’d only have one source for the TOC.

Thanks again, I’m really happy with Yada Wiki; it’s the first wiki/kb type plugin that I’ve tried that works with my theme. I appreciate your help.

-Tim.

Hi garlick,

Yea! It worked.

It would be nice to have Yada Wiki working with Gutenberg, but there are no firm plans or target dates.

Best regards,

David

Hi David, I went back to the Thrive Themes support folks who sent this issue to their developers. This is their reply (from the support team, who copy-and-pasted from the developer team):

Hello Tim,
Thank you for your patience.
We have received an update from the developers. I will copy and paste it so you can forward it to your developer.
                                        global $post;
					$old_post    = $post;
					$post        = $the_toc;
					$the_content = apply_filters( 'the_content', $the_toc->post_content );
					$post        = $old_post;
You can send the user to that developer with this.

?We won't add any fix to this ‘the_content’ filter should be used on the global $post not on specific post with rendering another one.

This doesn’t make much sense to me, but I’m hoping it does to you? It seems they are saying that “the_content” filter is perhaps being applied a little incorrectly in the Yada Wiki plugin, so they won’t do anything on their end to “fix” it. Does th is make any sense to you? Is there any hope of a remedy?

Thanks again,

-Tim.

Hi Tim,

Thank you for the information. I’m busy now, but I’ll try to take a look in a week or so and let you know.

Best regards,

David

Hi David, thanks for your response. I look forward to your update when you have some time to look into this.

-Tim.

Hello Tim,

I updated the plugin. Could you please try it and confirm the update works for you?

In this case you would use the Yada Wiki TOC widget in your sidebar, not a shortcode.

Thank you,

David

Hi David, I didn’t see your reply until this morning. Unfortunately, I’m seeing the same output from the TOC shortcode on my TA-created pages. See https://ferule.org/wiki/accessories-and-toys/.

I cleared the cache, and I added the TOC shortcode ([yadawikitoc show_toc=”true”]) in a simple text element in the template’s sidebar. It’s still displaying the wordpress post content rather than the shortcake’s intended TOC output.

I got so excited, too! Let me know if you want me to try anything in particular to help you troubleshoot it.

Thanks!

-Tim.

“In this case you would use the Yada Wiki TOC widget in your sidebar, not a shortcode.”

Were you able to try the widget?

Yes, the widget actually works. I don’t know why I didn’t see that in your previous comment; I was just trying it out. It’s not ideal, only because TA only gives you one general-purpose “default widget” area so I can’t use any other widgets elsewhere on my site, but it’s definitely better than maintaining the TOC in two places.

Thanks,

-Tim.