Closed TheGreatRedDuke closed 2 years ago
Ah I remember token attacher having to update scenes and stuff automatically after updates. Could you try without CF enabled, then after Token Attacher updates everything re-enabling it and refreshing?
I can confirm:
So that seems to have fixed up that specific issue. Is this just a process I should repeat each time Token Attacher updates?
Yeah from what i understand occasionally Token attacher will go through all scenes and perform an update on them after updating to a newer version. Disabling CF temporarily is a workaround for now but I will definitely prioritise this issue as it will get a bit annoying having to disable CF to continue.
Sounds good! Thank you!
Hi, sorry for the long wait.
Can you try installing this test version of Compendium Folders and seeing if you still get the error?
To install you need to uninstall your current version and install this one using the manifest text box on the install module screen: https://raw.githubusercontent.com/earlSt1/vtt-compendium-folders/09x-update/test/module.json
Should be fixed as of v2.4.4 (similar issue #141)
Hi, sorry, I've been away, and just got back to see this. But I can confirm I'm not longer seeing the error in my tests. Thanks!
Describe the bug Foundry is throwing a JS error when loading both the Compendium Folders and Token Attacher modules at the same time. I'm not sure if this is an issue steaming from Compendium Folder or Token Attacher, but the error indicates Compendium Folders.
I'm running into other strange behavior that may be related to Compendium Folders functionality, but I believe it may be a side effect of this JS error and can be reviewed after this issue is resolved (if it remains).
To Reproduce Load a world using both the Compendium Folders and Token Attacher modules, then check Dev Tools.
Expected behavior No JS errors.
Screenshots The JS error I'm receiving on Foundry load:![js-error-on-load](https://user-images.githubusercontent.com/78890368/152453585-0a2745d2-6548-4a09-a65b-8315c2cc67e3.png)
Information
*enabling only minimum required modules for this specific integration test: