qenvelopes

Sounds great. Looking forward to future releases!

Ah, so it turns out that was only part of the issue. It seems like if you have that request whitelisted but still have the user uploading something on the product’s main page (ie: before the actual designer), then the designer will throw an error when going to add to cart. Without an upload and having it whitelisted allows it to go through without any issues. Thanks for all of the help!

One thing I noticed when testing it a bit more is that the printQ loading overlay tends to get stuck and doesn’t fade out. People would still be able to navigate the designer if they knew where everything was, since it still loads everything in, but it basically looks like it gets stuck for those that wouldn’t know where things are. Not entirely sure what’s causing it since it seems rather inconsistent from tests, but I figured it was still worth bringing up.

I believe the only security related plugin we’re currently using is Wordfence, and I’m not seeing any Ajax related settings anywhere in the plugin. Our .htaccess file looks like

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

and I’m not sure if any of that is terribly relevant to Ajax POST requests. Would there be anything else you can think of that might be preventing these requests?

Sure, no problem. The product we’re currently testing it on is here: https://qenvelopes.com/product/custom-printed-t-shirts/

We’ve just got it set up with a template that we’re testing things with at the moment, so it definitely won’t reflect the final outcome.

Also, is there a way to make it so that customers that don’t wish to use the designer can just skip that step and add the item straight to the cart? It seems like the Personalize button overrides the default behaviour.