You are here:  » Deregister


Deregister

Submitted by designserve on Tue, 2006-04-25 19:01 in

Suggestion - a deregister batch tool would help especially when testing :)

Regards,
Mike

Submitted by henk on Tue, 2006-04-25 19:28

Thats true, and also when you parse the products into the database maybee there is a way to empty the xml file this will leave an lot of extra space.

A sort of ghost xml file :)

Henk

Submitted by designserve on Tue, 2006-04-25 20:42

Still deregistering 1 hour 40 later, I would like to reinforce what I said above. I keep getting distracted onto other work and forgetting that I have to keep deregistering these files.

Good idea about the empty xmls, especially for those without dedicated servers.

Submitted by support on Wed, 2006-04-26 06:57

Hi Mike,

I'm sorry it's taken so long to de-register. The process only involves a DELETE FROM the products table against an indexed field so it should be quite quick. How many feeds did you have to deregister?

It might be worth noting that if you intend to deregister every feed it is probably best just to DROP the database (you can use a tool such as PHPMyAdmin or Webmin to do that), and then run setup.php again.

With regards to empty feeds to save disk space, I agree that this is a good idea and it would certainly be possible to create a "ghost" file of the same name using the touch command, for example:

$./import.php merchant.xml
$rm ../feeds/merchant.xml
$touch ../feeds/merchant.xml

This of course just after downloading the feed. The touch command just creates an empty file, so doing this will save lots of disk space.

Submitted by designserve on Mon, 2006-05-01 16:55

Droping the database and running setup sounds like a good option. I only had around 15 feeds but some of them took 20 mins to deregister.

Cheers,
Mike