We just deployed some updates to the Custom JavaScript.
Visitors are now able to choose Allow/Deny on the Campaign, and no longer have to Favorite the Campaign. (Until the choice is made, the Campaign's Custom CSS will not be applied for that visitor. This is so that the Custom CSS can't be used to alter the Allow/Deny popup.)
This should be a much simpler experience.
If you want to disable the Custom JavaScript on a Campaign where you already Allowed it (like if you put an infinite loop in your code and can't get in to fix it), then you can just visit [your campaign slug].obsidianportal.com/reset-custom-js, and that will remove the cookie that allows the Custom JavaScript to run on your device.
Comments
Totally agree! The changes I'm working on won't require favoriting anymore. It should be much simpler.
Obsidian Portal Developer
Awesome to hear. Sorry to sound like I'm complaining, I'm not. Just want to see OP thrive.
Not complaining at all. I seriously appreciate the feedback!
Obsidian Portal Developer
I agree with everything @Keryth987 said above- we should be looking for ways to grow OP.
Just trying to help out.
We just deployed some updates to the Custom JavaScript.
Visitors are now able to choose Allow/Deny on the Campaign, and no longer have to Favorite the Campaign. (Until the choice is made, the Campaign's Custom CSS will not be applied for that visitor. This is so that the Custom CSS can't be used to alter the Allow/Deny popup.)
This should be a much simpler experience.
If you want to disable the Custom JavaScript on a Campaign where you already Allowed it (like if you put an infinite loop in your code and can't get in to fix it), then you can just visit [your campaign slug].obsidianportal.com/reset-custom-js, and that will remove the cookie that allows the Custom JavaScript to run on your device.
Obsidian Portal Developer