This topic has 11 replies, 4 voices, and was last updated 9 years, 9 months ago ago by Ian Welham
I am getting this error on my site after the contact us form or the chat form is submitted.
Hello,
You’re using old plugins versions.
You can download the latest plugins versions at this link https://www.8theme.com/download-plugins/ ,
enter your purchase code of the theme to get the plugins.
Also please provide us with FTP credentials in Private Content.
Regards,
Robert Hall.
Please see the below ftp
Also, the wish-list icon in the header is not connecting to the wish list page.
sorry about all the messages.. I updated woo commerce and now the wish list is working, however, there is a strange up and down icon over the qty box on a product page that is not allowing me to see what qty I am entering
Actually, I can view the wish list page.. but when I add a product to it, it’s not there.
Hello,
The problem with sending email was caused by https links.
I’ve added the code in .htaccess file as written in this article:
http://454media.com/cross-origin-resource-sharing-cors-fix/
Please check contact form and clear browser cache before.
Concerning wishlist, the issue persists with default WordPress theme too. So you have to contact the plugin author for the solution.
Thank you.
Regards,
Eva Kemp.
Thanks! the contact us form works but the chat box in the lower right-hand corner does not work.
also, in safari I am getting the strange arrows over the qty boxes that didn’t used to be there.
Hello,
As I see you didn’t add your email address in Screets Chat settings. Go to Chat Console > Options > “Where should offline messages go?” > type your email address.
Could you please show a screenshot of the arrows you’re talking about?
Thank you.
Regards,
Eva Kemp.
Hi Jamie
I get exactly the same issue using Safari – the arrows to change the quantity of the products page are on top of the box and you can’t read the number. I was given custom.css code to actually remove the buttons, which to be honest I prefer. Try using this in custom.css until they have fixed the issue
input[type=”number”] {
position: initial !important;
}
The issue related to '‘ERROR WHILE AJAX REQUEST’' has been successfully resolved, and the topic is now closed for further responses