Issue with Google Category Mapping – 403 Forbidden & JS Error

Hello Product Feed Pro Support Team,

I am experiencing a persistent issue with the Google Category Mapping feature. On the mapping page, the list of Google’s official categories fails to load. I am unable to search, type, or select any Google category, which prevents me from completing my product feed setup.

When I try to use this feature, the browser’s developer console shows two specific errors:

1. A server access error:Failed to load resource: the server responded with a status of 403 ()
2. A subsequent JavaScript error:Uncaught TypeError: Cannot read properties of undefined (reading ‘split’) at pfp-google-taxonomy.js?ver=13.4.6:103:17

This indicates that a security rule or permission issue on my server is blocking access to the Google taxonomy file, which then causes the JavaScript to fail.

Troubleshooting Steps Already Taken:

Before contacting you, I have performed an extensive diagnosis to rule out common issues. The problem still persists after trying all of the following:

• Checked Server Security Logs: I have reviewed the firewall and incident logs on my Cloudways server and found no specific blocking events related to this.
• Whitelisted IP: I have whitelisted my own IP address to ensure I am not being blocked.
• Disabled .htaccess: I temporarily renamed my .htaccess file to disable all its rules, but this did not solve the problem.
• Checked File Permissions: My hosting provider (Cloudways) manages file permissions, and they are set to the standard 755 for directories and 644 for files.
• Reinstalled the Plugin: I completely deactivated, deleted, and then reinstalled the Product Feed Pro plugin. The issue remained.
• Checked for Conflicts: I have ruled out a conflict with other plugins or my theme by systematically deactivating them. The issue persists even with a minimal setup.

My Environment Details:

• WordPress Version: 6.8.2
• WooCommerce Version: 10.1.2
• Product Feed Pro Version: 13.4.6
• PHP Version: 8.2
• Hosting: Cloudways (NGINX + Apache stack)

Given that the root cause appears to be the 403 Forbidden error when fetching the taxonomy file, could you please provide guidance on the specific file path the plugin is trying to access? Or could you suggest a reason why a standard server security setup might be blocking this specific resource?

Thank you for your time and assistance.

Best regards,

Luis

The page I need help with: [log in to see the link]