Hi, I am testing growthbook pro in the self hosted...
# ask-questions
v
Hi, I am testing growthbook pro in the self hosted version - but I fail to use the visual editor. I think I have entered everything in the Chrome Extention but the editor does not come up and instead throws a "Uncaught SyntaxError: Invalid or unexpected token (at visual_editor.js210118)" error in the chrome dev tools console. Any idea why that might be the case?
f
Hi Bernhard - can you share any more info on this? Can you share or DM me the site you're trying this on?
v
Sure, maybe its a conceptual thing 🙂 as I am just testing, I have set up posthog in a local docket container, so my posthog API is localhost:3100 or something similar. Then I installed the chrome extension and entered the data I got from creating a new API key. I tried to add the snippet to a HTML page hosted locally, but then also on some test server of us: <script async data-api-host="http://localhost:3100" data-client-key="sdk-gq..." src="https://cdn.jsdelivr.net/npm/@growthbook/growthbook/dist/bundles/auto.min.js"></script> <script src="https://cdn.tailwindcss.com"></script> </head> Then when I open the page, I can see the extension is working (being colored, not grey) - but I get the error in the console, and no option to modify anything
ok - interesting, I just tried it again, no error message now. Weird...but I still dont get the visual editor screen as seen here: https://blog.growthbook.io/visual-editor/
I also do get this:
f
is the website you're looking to load the visual editor on public?
The editor itself just requires the dev tools to work - the SDK is needed to launch and run the experiment, but not to set it up
If you can share the website name, we can take a look, see if we can reproduce it
v
sure: https://vmax2.maxodus.com/test/index3.html it's just a very basic sample page from tailwindui
ok I changed it to be a super simple page (no tailwind, just some text) - and the syntax error is back, now
f
huh
I can reproduce it with your site
I'll ask the team to take a look
v
thank you :)
so, the trial premium is running out soon, any idea whats keeping the visual editor from working in my case?
f
Hi Bernhard - i'm raising the issue with my team still
v
OK, thank you 🙂
f
Okay - we figured out what was going on, and a fix is in review right now
sometimes takes Google a little bit to publish changes to a chrome tool
in the mean time, you could add a meta tag: <meta charset="utf-8">
to the head
v
sure, one sec 🙂
perfect, the console error is gone now. I can now open the visual editor for the page 🙂