Hi, Haley

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

1. I can see that you have a CORS error on this front-end page, if i try to press "Continue" on this booking here.

But i see other issues, also.

The booking element looks really strange, it seems it is either some kind of conflict with your current theme/other plugin;

or it might be an issue, if you placed the New Form with any Old Form on same page.

Please check if that is the case,  then remove any old Forms from this page > just leave the New Step Form.

Also, sometimes this can be a caching issue. Please purge all cache from your site, and cache + cookies of your browser, refresh the page.

If you still see the same issue -  Press F12 to open browser console, and check the Console tab , if you can see this CORS error again.

-

Then we should resolve this CORS errror.

CORS is industry standard for accessing web resources on different domains. It is very important security concept implemented by web browsers to prevent Javascript or CSS code from making requests against a different origin.

Let’s consider this scenario:

You have link from Domain1 which is opened in browser and asking for a JavaScript file from Domain2. Now your web browser makes call to Domain2. If on Domain2, you have a policy to accept request like JavaScript or CSS from only Domain2 and ignore all requests from another domains, then your browser’s Domain1 request will fail with an error.

You can check on this link one of the solutions, but all is related to the CORS policy, so can you please contact your hosting provider about this because as I can see the CORS errors on other pages as well 

-

Let me know if this helped.

-

2.

If not, perhaps it is another issue.

Can you please check, if you are logged as Admin, can you then see the new Form without errors?

And the errors happen only when not logged in, or in incognito browser mode?

If that's the case :

The old Form is based on Vue Framework 2;   but the New Form is based on Vue Framework 3;

There are most probably some security measures on your site - that are related to Vue Framework 3,

If you can see the Form as logged in, but can not as non-logged in visitor, the issue is not with Amelia, but something is blocking the access.

The best option would be to reach out to your hosting provider, send them the link of the booking page and tell them exactly what you told us - you can see the page when you're logged in as an admin, but you can't see it from an incognito window (or when you're logged out). 

They should be able to find what is blocking the Vue Framework 3 for non-logged-in users.

Let us know how it goes, please.

-

Also, check if you have any optimisation plugin, such as WP Rocket.

I you have WP Rocket, check if you have enabled this "Minify JS files" - if so, disable that, and refresh the page -check if the error goes away.

We will be here to help you resolve this issue as quick as possible, and to advise on further troubleshooting.

Let me know how it goes.

Thank you

Hello, Haley 

thanks for reaching out to us.

We have responded to Moe's ticket - and waiting for reply, here we will focus on your page, Haley.

I noticed several issues, that might be causing this.

I can see this Form, but it seems it is one of the Old Forms?

1.

Please check if you placed the Old Form with the New one on same page.  If so, please remove any Old Forms.

The Old Form is based on Vue 2 Framework, the New one on Vue 3 > so they will have a conflict if together on same page.

-

2.

Also, we got this CORS error on the page, as you see, in the browser Console.

CORS is industry standard for accessing web resources on different domains. It is very important security concept implemented by web browsers to prevent Javascript or CSS code from making requests against a different origin.

Let’s consider this scenario:

You have link from Domain1 which is opened in browser and asking for a JavaScript file from Domain2. Now your web browser makes call to Domain2. If on Domain2, you have a policy to accept request like JavaScript or CSS from only Domain2 and ignore all requests from another domains, then your browser’s Domain1 request will fail with an error.

You can check on this link one of the solutions, but all is related to the CORS policy, so can you please contact your hosting provider about this because as I can see the CORS errors on other pages as well 

3.

 It might be a caching issue.  Please make sure to purge all cache on site,  and clear cache of your browser, then refresh the page.

4.

If not, perhaps it is another issue.

Can you please check, if you are logged as Admin, can you then see the new Form without errors?

And the errors happen only when not logged in, or in incognito browser mode?

If that's the case :

The old Form is based on Vue Framework 2;   but the New Form is based on Vue Framework 3;

There are most probably some security measures on your site - that are related to Vue Framework 3,

If you can see the Form as logged in, but can not as non-logged in visitor, the issue is not with Amelia, but something is blocking the access.

The best option would be to reach out to your hosting provider, send them the link of the booking page and tell them exactly what you told us - you can see the page when you're logged in as an admin, but you can't see it from an incognito window (or when you're logged out). 

They should be able to find what is blocking the Vue Framework 3 for non-logged-in users.

Let us know how it goes, please.

-

Also, check if you have any optimisation plugin, such as WP Rocket.

I you have WP Rocket, check if you have enabled this "Minify JS files" - if so, disable that, and refresh the page -check if the error goes away.

We will be here to help you resolve this issue as quick as possible, and to advise on further troubleshooting.

Let me know how it goes.

Thank you

Hi Haley and Moe

Firstly, my sincerest apologies for all the waiting time.

We don't have any bug in regards the New Step Form,  as you can see, it works without issues on our Demo page here.

So these issues are either a conflict between something on your site and Amelia, or a security issue, or optimizations conflict.

-

- You guys are not the first two users to report this,

but since the New Step Form is in its Beta stage, we were expecting some issues, as it is with all new features, that can happen.

We have resolved this issue for all other users so far, so i am pretty confident.

-

Now, i have sent you both several steps to check - and i don't seem to notice you responding to what you did to check them?

1.

Did you check if you have both Old and New Form on same page?

2. 

Haley, did you check with your hosting to fix the CORS issue?  ( i am not sure if Moe might have that, since the pages he sent are not working at this time, but i hope he sends working links)

3.

Sorry about the caching, but we had several users who did have a cache issue, and this resolved it for them

4.

Did you check, how the page looks when you log in as Admin, and how it looks when you are not logged in?

5.

Are there any optimizations on site, such as minifying JS files?

-

There are five points, so if you can please check at least some of them and let me know how it goes?

We are more than happy to assist in resolving this, but we must eliminate some variables, in order to work with facts, before proceeding.

-

If you check at least some of these points, please let me know what your hosting support said - at least i hope they can solve the CORS issue,

then i can log into the WP-Admin for you, to do additional checks.

Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties. 

You can write credentials here just check PRIVATE Reply so nobody can see them except us.

-

Looking forward to your reply

Hi, Haley

Thank you for checking and confirming this for us.

We did have a number of users who used the Wp Rocket optimisation to Minify JS, and that is currently causing a conflict, but our developers are working to improve that as soon as possible.

No problem at all, let us know if you try the new form again, and if you find any issues at all, we will be here to help.

Thank you very much.

- Regarding responding in private, Moe, that is only possible for your tickets - we are unable to send a private reply on others tickets.

Thank you