Yeah, I'm trying to track it down. It appears its having to do with the change in plugins in order for the template version to work. Back at the 1.0.0 release, I was using a hook for parse_templates, and had the file. The hook was removed in 1.0.1, but the file most likely remained (unless a person manually deleted it). In 2.0.0, parse_templates is being used again, therefore overwriting the old parse_templates file and causing this issue. What makes no sense though, it that file hasn't been called by anything since 1.0.0, so it shouldn't matter. I will continue to look into it and update as I track down the issue.
---------- Post added at 08:57 ---------- Previous post was at 00:21 ----------
It looks like I have it sorted out, so now I just need to repackage it and upload the hotfix. Here is what I have determined...
I need to add a control to allow the use of vBSlider anywhere as an option for ONLY the CMS. So, if you want to have the slider inside the header, or under the navbar, etc. (templates that are shared across the CMS and Forum), then you will need to ENABLE this option and remove the widget. If the option is DISABLED, the widget will work on the CMS, yet you will still be able to place the slider in any template that just affects the FORUM (showthread, etc.). This should fix all the issues. Again, sorry for not catching this before the product was released.
![Frown :( :(](https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f641.png)
I'll update the thread once the hotfix is available.
---------- Post added at 09:27 ---------- Previous post was at 08:57 ----------
Hotfix is now available for download. You'll need to upload files again, as well as import the product again. Let me know if you continue to have problems.