A: If you see this message, check the following:

-Verify in uploads/feeds that the CSV file has been downloaded and check when file was write on disk to discover if is the right file. If file doesnt exist check chmod (should be 755) and chown of feeds directory.

-Ensure a valid license exists in the database. In the settings table, you should have license_active = yes, product_slug = affiliate-elites-app and a legit license key.

-Check your hosting provider's resource limits. The upload_max_filesize and post_max_size values in your PHP configuration must be larger than the file you are trying to upload.

-Check the existence of the file license_email.txt in the cache directory. It must contain the email you used during the installation process (it may be different from the admin email).

-The last cron import process might have been abruptly interrupted. In this case, it's a good idea to delete files from logs directory.

A: Clear your browser's cookies for the site.

A: This message indicates that the feed cannot be downloaded at the moment. The solution is to wait and try again later.

A: Check to make sure the products in your imported feed are not marked as "Out of stock."

A: Follow these steps:

In app.php, ensure the APP_URL constant is set to the correct website link (e.g., define('APP_URL', 'https://www.sitename.com');).

In database, the settings table must contain the correct license_code, license_active = yes, and product_slug = affiliate-elites-app. 

A: The system behaves differently based on the tag structure:

Nested Tags: For a nested structure the system correctly maps the content of these sub-tags to the attribute name and attribute value fields in the database.

Non-Nested Tags: If you map a non-nested tag to attributes, the system will use the tag name itself (g:product_type) as the attribute_name and the tag's content as the attribute_value.

A: If you add these IDs after the import process, you must delete the feed and add it again. As a workaround, you can force a re-import by making a small change to the category mappings, running the import, reverting the change, and running the import one more time. 

A: This is typically caused by a browser extension like uBlock Origin, AdBlock, or Privacy Badger. Such extensions can prevent Google Analytics scripts from running and block new tabs from opening.

A: This error usually means the server's timeout or packet size limits are too low. You need to increase the values for wait_timeout and max_allowed_packet in your MySQL configuration file (e.g., /etc/my.cnf). 

A: You need to increase your server's PHP settings. In your php.ini file, increase the values for upload_max_filesize and post_max_size to accommodate your large file. 

A: For optimal performance with large files, consider setting the following values in your php.ini file:
memory_limit = 2048M
post_max_size = 1100M
upload_max_filesize = 1000M

A: This is likely a file permissions issue. Check the permissions (chmod) and ownership (chown) of the relevant directories to ensure the web server user can write to them.

A: Check the file system permissions for the Uploads/Images directory. The web server user needs permission to read files from it (chmod and chown)

A: This usually happens because your CSRF token has expired. Close all site open tabs and reloading the login page should fix the issue.

A: This error indicates that the database you are installing already contains tables and procedures from a previous installation. You should use a fresh database or clear the existing one before proceeding.

A: This is a session-related warning. Logging out and then logging back in will resolve it.

A: An HTTP 401 error means "Unauthorized." This indicates that the feed credentials (e.g., username and password for CJ.com) you entered are incorrect.

A: This is likely a caching issue. Clear your browser's cache and cookies, especially if the incorrect search terms are appearing in search suggestions.