So your custom style is based on core1, right? I looked into it, and it looks like the updated components we recently turned on break javascript for core1. That wasn't expected, and it didn't come up during the opt-in beta.
For the time being, you can get things working again by opting out of the updates -- go to the beta page and flip "temporarily revert updated journal components" to true, and your cut tag widgets should come back. (And then please keep an ear out for future updates, because you'll want to turn it back on to make sure our eventual fix works!)
We'll need to fix this in the core1 code, but I'm not sure how, yet. You might be able to help me with some more info... to start with, does your style override the Page::print() function?
(OH, alternately: if I'm wrong and your style IS actually based on core2, you can fix it permanently by making sure you call Page::print_wrapper_end() near the end of your Page::print() function, in place of the closing </body> tag.)
Re: new cut tag weirdness?
Oh, yup.
So your custom style is based on core1, right? I looked into it, and it looks like the updated components we recently turned on break javascript for core1. That wasn't expected, and it didn't come up during the opt-in beta.
For the time being, you can get things working again by opting out of the updates -- go to the beta page and flip "temporarily revert updated journal components" to true, and your cut tag widgets should come back. (And then please keep an ear out for future updates, because you'll want to turn it back on to make sure our eventual fix works!)
We'll need to fix this in the core1 code, but I'm not sure how, yet. You might be able to help me with some more info... to start with, does your style override the
Page::print()function?(OH, alternately: if I'm wrong and your style IS actually based on core2, you can fix it permanently by making sure you call
Page::print_wrapper_end()near the end of yourPage::print()function, in place of the closing</body>tag.)