Replies: 3 comments 1 reply
-
|
Some people have reported this to me today also. For them the solution was to:
and/or
You can also manually set the KTL version to the most recent version: 0.38.1 but that's not recommended, unless you have specific reasons to do so. If you still have the issue, email me so I can help you out and see why it's doing this: nd@ctrnd.com Norm |
Beta Was this translation helpful? Give feedback.
-
|
Sorry @eliw13, I completely misread your issue. I guess it was a bit late when I wrote the above post. Still, I'd like to know more and see what could have caused that. Norm |
Beta Was this translation helpful? Give feedback.
-
|
Hi @eliw13, Thanks for the detailed explanation. I'm glad to see we have another Local mode user! I'd like to learn more about your specific use case, more specificly why you're running a customized KTL version. To answer your question: yes, there are other Local mode users, but not many. To my knowledge, about 5 people are currently using this setup, though there could be more since I have no way to track it. I'm convinced there's a straightforward solution for what you need. Rather than having you maintain a separate fork of the KTL (which would be a maintenance burden for you going forward), I'd prefer we find a more elegant approach that works within the standard KTL configuration. Could you send me a private email (nd@ctrnd.com) so we can book a meeting to discuss this? That way I can better understand your requirements and we can work out a clean solution together. Norm |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Hi all - we've taken a copy of the repository and have been rocking with v0.32.0 of the KTL locally hosted on a web server and making our call out there instead of the GitHub repo. We do this so that updates to the KTL are not made without us first reviewing the release notes beforehand to ensure we do not impact customer experiences with any potential unintended bugs.
Today, after Knack's classic/next-gen outage, we noticed that our javascript was unable to reach out and grab some code, causing the KTL to make the app fail and refresh over and over again. Just wondering if we're the only ones experiencing this or if someone else has run into this issue?
Beta Was this translation helpful? Give feedback.
All reactions