|
FAQ Answers
|
|
Written by Garry McGillivary
|
|
There are times where the redmystic server may have trouble retrieving your product feed. Here are the usual suspects:
- Your site is down for maintenance
- This may seem obvious but you'd be surprised how often this is the cause.
- Invalid SSL Certificate
- By default redmystic will attempt to pull your product feed over https. If your site does not have SSL certificate then you're likely to experience problems. A simple test is to navigate to your homepage in your browser and replace the http with https. If you receive an error then redmystic will not be able to communicate with your site. Changing the configuration setting PINGBACK_SECURE_CONNECTION to "No" will direct redmystic server to communicate over http and should resolve the problem. However anyone selling products and transmitting payment information over the internet should always be using a SSL certificate for secure communications. See your host for more details.
- SEF interference
- Some SEF programs interfer with Redmystics ability to pull feeds (Native Joomla SEF does not have these issues). This often leads to the "content-dispostion" email from redmystic. This simply means we tried to pull your product feed and recieved something else. It is important to exclude the redmystic component from third party sef programs. If you are unsure if this is the problem then try temporarily turning off your SEF program and then manually forcing a product feed push by clicking the "Notify Redmystic" button. ***It is important to note that excluding redmystic from your SEF program will not effect SEF urls within your product feed.
- Hardened-PHP
- If you are using a version of the core component prior to ver 1.3.8 and your host has implemented Suhosin then the component will fail to render feeds and search engine sitemaps. A quick check of your php info and looking for Suhosin.memory_limit settings will identify if your host has implemented these features. The easiest solution is upgrade to the latest version and making sure MEMORY_LIMIT is set to "None".
|
|
Last Updated on Wednesday, 26 January 2011 19:00 |