Unable to load front-end builder when logged in
-
Hi. When I’m logged in as an admin account I can’t access the front end of the builder. Whilst not really a problem, it means that when an order comes in I can’t actually look at the design up close because the builder doesn’t load. Have I not ticked something I should have?
The page I need help with: [log in to see the link]
-
Hi there,
Could you describe what happens when you access the page logged in?
Also could you open the browser console when you access the page and try open the configurator, and share the eventual errors you get?Marc
So the page loads, but the builder won’t open. And because this is set in the css
.configurator_is_opened:not(.configurator_is_inline) {
overflow: hidden}the page won’t scroll obviously. Here’s the error in the console…
Uncaught SyntaxError: Invalid or unexpected token (at admin-ajax.php?action=pc_get_data&data=init&view=js&fe=1&id=889&ver=1651745951:1:1)
TypeError: Cannot read properties of undefined (reading ‘prod_889’)
at n.initialize (configurator.js?ver=1651746407:19:34)
at n.h.View (backbone.min.js?ver=1.4.0:2:14139)
at new n (backbone.min.js?ver=1.4.0:2:23426)
at Object.PC.fe.open (product_configurator.js?ver=1651746407:224:30)
at HTMLButtonElement.configurator_init (product_configurator.js?ver=1651746407:94:11)
at HTMLBodyElement.dispatch (jquery.min.js?ver=3.6.0:2:43064)
at HTMLBodyElement.v.handle (jquery.min.js?ver=3.6.0:2:41048)
at Object.trigger (jquery.min.js?ver=3.6.0:2:71515)
at HTMLButtonElement.<anonymous> (jquery.min.js?ver=3.6.0:2:72110)
at Function.each (jquery.min.js?ver=3.6.0:2:3003)I am facing the same problem. For logged-out users, configurator window opens after clicking on Configurator but it does not open for the logged-in users. Please help me out.
Hi there,
This could be due to a double Gzip compression, which can happen if you have a plugin which adds it to everything.
You can try the following code to disable Gzip compression on the configurator’s data:
add_filter( 'mkl_pc_get_configurator_gzip_data_js_output', '__return_false' );Marc
I’ve tried disabling every plugin and the issue still comes up. The only other thing I have active is Cloudfare. Where shall I add that code?
If you use a child theme or a custom theme, you can add this to
functions.php.
Iffunctions.phpdoesn’t exist, you can create it and add this inside:<?php add_filter( 'mkl_pc_get_configurator_gzip_data_js_output', '__return_false' );Otherwise if you’re not familiar with PHP, you might need a plugin that allows adding PHP code snippets from the backend.
Thanks — that’s fixed it when added to the functions.php file.
Appreciated
I’ve also got an image with the layer selections not being pulled through to the cart and backend order. The choices selected are shown listed in the car, but the image doesn’t correlate with it. For example if someone is selecting an orange product, the image in the cart and order is showing as white (causing quite a lot of confusion for the customer not knowing if what they’re ordering is correct). Happy to send over image examples if you can provide an email. Thanks
I made a quick test and the image looks correct:
Could you send me a message here with more details about the specific selection which gives this issue?
Some of them do display okay that’s the strange thing..
Style: 1
Colour: Green
Outer Hood: Sand
Inner Hood: Green
Logo: Navy
Pocket: Kangaroo
Pocket colour: SandI see, it looks like you’ve changed the order of some layers using CSS:
.base-style { z-index:1!important} .robe-colours { z-index:2!important} .logo-colours { z-index:3!important} .pocket-colours { z-index:4!important;}This will only be reflected in the frontend, and not on the generated images.
In order to fix this, you should select “Order images” in the Layers section, and change the order according to the desired result.
Images first in the list will be below the next ones.
That’s great thanks. I’ve never seen that option to order images in layers, hence adding z-indexs. Thanks very much
The topic ‘Unable to load front-end builder when logged in’ is closed to new replies.