Hi there
Great to see you got it sorted. For others reading this, I invited him to an MSN chat and gave he me some access details to get into the site via Joomla admin, but then my pizza arrived. By the time i returned he had fixed it by increasing the memory allocation
.
And it was a great pizza.
To answer your question though
I wouldn't use it on once a day, as the way Google works is that every time it uploads, it deletes out the old document which removes your products, and then takes about 24hrs to publish in your next one. So you will have a 24hr gap of when their are no products, which means it will rarely be on.
To get around this, set up one of the other functions such as latest_products.xml in the mambot to upload lets say 9999 products (more than you have) every 2 weeks, this means it will add all your products with that XML doc and also all the others with all_products.xml. Then stagger the 2, one on a Monday for example and the other on the next Monday, so when one is uploading and clearing it will have the other in place still showing your products.
Google has never shown any problems with this trick yet by duplicating products, if it does ill note it on here.
So you only have one upload every week.
You have very small amounts of memory set on your server (8mb up graded to 32mb), most servers are in the hundreds of mb's not 10's. For example this site we are on here has 512mb and assigned, so it will never show any issues in any form. It shouldn't affect the running of your site at all, with the amount of pressure the mambot puts on it, as it only takes a second to work even for many thousands of products.
One of my clients
http://www.mybedroomboutique.com/ has 61,599 at last count and works very happily on his site just using a small VPS server with SEF URLS and loads of other toys running at the same time. So i wouldn't imagine the mambot will have any effect on a few hundred products on your site.
You say that it is "one person", yes somebody will get the message to say it is working, the reason we worked this way, is because it was originally designed for cron jobs, but with people having many types of hosting Dedicated, shared, reseller, and VPS on different types of servers, Linux Windows etc, it wasn't going to be practical at all. So we rebuilt it to work with FTP, this allows it to work perfectly on all servers and not require any server scripting. The only way we found of doing this though, was with a Mambot, as the page rolls, it checks the date and time etc and if it is past the time it was supposed to fire an XML doc out, it does. I am looking to see if i can find a way of hiding message, but i haven't found a way yet. One of my freelancer who helped me build it is also looking at this for a solution as well as a list of about 6 other things including
- Child products
- Shopper groups
- A full message log showing whats happened
- Manual over ride push function
- Removing the error code form front end
And a few other little toys in that order of priority
All the best
Ian
ibexinternet wrote:
QUOTE:
One other thought does the feed rewrite the whole file (we have set to once a day) once each time. Does this mean that one person will get a slow response.
If so what time is set for the feed to run as well set up a cron job to hit the site
Also we have 490 products So not that large amount of things although we are runing ARTO as well.:)
All Products
