The Foxy forums are on the move!

We're in the process of moving our forums over to a new system, and so these forums are now read-only.
If you have a question about your store in the meantime, please don't hesitate to reach out to us via email.


itisnot_meitisnot_me Member
in Help edited February 2011
Ahhhh problems.

ok so i know that the subscription xml is supposed to be sent to the same datafeed as the transaction when it gets canceled. But the xml never did get sent to my server.

I am testing out my cancel part of the subscription and so on the 7th i canceled one of the test accounts and it says that it was set to cancel on the 8th. Then on the 8th i kept checking to make sure that it indeed cancel but it did not.

i got not error warnings within the error log and none of my queries within my script got triggered. So im at a loss why the subscription didnt get canceled
  • brettbrett FoxyCart Team
    I see a sub that was ended on the 8th, but to clarify, you're saying you didn't get the sub XML datafeed, right?

    Have you tried using the API to refeed the sub XML? Check the "subscription_datafeed" method:
    That'll allow you to refeed it immediately, so you might be able to debug whether it's an issue on your end or on ours. Let us know what you find.
  • correct. i did not get the xml datafeed.

    also i dont think that its an issue on my end. cause if canceled gets run there is a query that inserts a cancel into the system without any data grabbed from the xml. Its is anonymous data for statistical purposes to view gains vs losses.

    truthfully i have not really learned the api per i thought that i would not need it. its going to take me a while implement that.
  • brettbrett FoxyCart Team
    You actually could just run a curl request from your terminal (get Cygwin if you're on Windows). It'd be something like this:
    curl -d "api_token=PUT_YOUR_API_KEY_HERE&api_action=subscription_datafeed" https://example.foxycart.tld/api
    I added that here:
  • as you can see from the api post there is an issue somewhere that we need to fix first
Sign In or Register to comment.