Jump to content
thirty bees forum
  • 0

Bug in checkout when smart cache for javascript is activated


Question

Posted

Hi,

I am using 1.1.x version (bleeding edge) and I have found a bug within the javascript cache.

I have no guest checkout activated (but If I activate it the problem is the same) so if customers are no login when they arrive to the checkout, it should be visible the registration form to introduce the data. Something like this:

image.thumb.png.0120557ea6af9812aaf8eb8dc691d326.png

 

BUT, if I activate the smart cache for javascript, this is not showed and instead it appears:

 

image.thumb.png.feb2a467f6160228f9f5c9528b130e1a.png

This is wrong because it is showing the guest checkout (but it is deactivated) instead the fields directly.

This bug also affect when guest checkout is activated but the difference is that appearing this last screenshot would be normal, but once I clic in "guest checkout" button, instead of showing the fields without leaving the checkout, it redirects to the account page creation.

 

I have registered it in video:

 

https://www.screencast.com/t/wWwnRF51u

 

Any idea how to correct it?

 

Regards

7 answers to this question

Recommended Posts

  • 0
Posted

in chrome, just click in allow after doing clic in install. It is about 3 sec 😉
about checking....I should know what to check first :S
No dev knowledge here, but since our shop is closed, I activated the smart cache for javascript so you can see the problem yourself if you would like.

Just enter here: https://www.lesielle.com/es/activos/retinol-vitamina-a-03/1 

Click in "reservar" and go to the checkout. You will see both buttons (instead of the registration form), including the guest checkout button (that is deactivated) and whatever you do you will be redirected to "my account" page

  • 0
Posted

Yeah you have multiple console errors (right click in chrome and use inspectation). I would try to deactivate external modules and check again... Dont forget, to delete cache always after changes...

  • 0
Posted

you are right! it seems it is a module because deactivating it, it is solved. I deactivated the module now. Could you tell me from the console if there is something I can correct? (only if it is simple)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...