Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Dan 1288 posts 3921 karma points c-trib
    Jul 11, 2013 @ 15:50
    Dan
    0

    Tea Commerce: what does GetAllFinalizedOrders output?

    Hi,

    I currently have a custom dashboard section in the back-office which renders an XSLT macro to output all finalised orders; at least that's what I'd like it to do.  The xml that's generated by the 'GetAllFinalizedOrders' method is pretty comprehensive though and it's not immediately obvious what it's actually showing.  For example, I had three orders in the Tea Commerce admin area, two new and one completed, yet the 'GetAllFinalizedOrders' contained 7 order nodes.  I deleted all three orders in the admin area I now have 10 order nodes output by 'GetAllFinalizedOrders'.  Does it create a new order node each time the status of an order is changed?  If so, how do I just get all of the 'new' orders, for example?

    This is Tea Commerce version '2.0.0.1 build' by the way.

    Thanks

  • Rune Grønkjær 1372 posts 3103 karma points
    Jul 11, 2013 @ 19:56
    Rune Grønkjær
    100

    Hi Dan,

    In Tea Commerce 2 you can just delete the xml cache file and next time it's requested it will be regenerated from the database. From your information I cannot provide you an answer as to the results you are getting. Try comparing the xml file to the orders in the database and see if something is wrong.

    If it's a bug we need more information. Also, you should upgrade Tea Commerce. A lot of bugs have been fixed since the version you are running :)

    /Rune

  • Merijn van Mourik 58 posts 128 karma points
    Jul 11, 2013 @ 23:35
    Merijn van Mourik
    0

    Hi Rune

    I also experienced this, seems like the xml cache contains the same order 3 times. (in my situation). I'm running lates version.

    Merijn

  • Rune Grønkjær 1372 posts 3103 karma points
    Jul 12, 2013 @ 10:08
    Rune Grønkjær
    0

    Dan: Can you confirm the bug Merijn is writing about?

    If so we'll have to take a look at it and fix it.

    /Rune

  • Dan 1288 posts 3921 karma points c-trib
    Jul 12, 2013 @ 17:29
    Dan
    0

    Hi Rune,

    I've cleared the cache (in App_Data/tea-commerce in case anyone is unsure where this is) and actually there were three cache files in there (finalized-orders-xml-cache-123, finalized-orders-xml-cache-1081 and finalized-orders-xml-cache-1), which is odd as there should have only been 1, right, as I only have one store?  This seems to work now.  I've run 3 orders through the system and changed their status and they all appear (only once) in the XML cache.  When I delete an order it is removed from the cache, which is what I'd expect.

    So I actually can't replicate the issue now.  Perhaps it was something to do with orders not being formatted correctly or something during development.  @Merijn, does deleting the cache file(s) work for you?

    Thanks

  • Rune Grønkjær 1372 posts 3103 karma points
    Jul 12, 2013 @ 20:40
    Rune Grønkjær
    0

    Hm. That's weird. The number at the end of the filename is supposed to be the store id, if I remember correctly.

    We'll take a look at it and see if we can find the problem. Will be a few weeks though as it's holiday season now.

    /Rune

  • Anders Burla 2560 posts 8256 karma points
    Jul 14, 2013 @ 01:51
    Anders Burla
    1

    There was a bug in Tea Commerce that is solved in the latest version that would add the order multiple times to the order xml cache. So be sure to upgrade to the latest version of Tea Commerce to solve that. About the multiple order xml cache files - try to see if that happens again. If it does - try and let us know how to reproduce. Thanks for your help.

    Kind regards
    Anders 

  • Dan 1288 posts 3921 karma points c-trib
    Jul 14, 2013 @ 21:10
    Dan
    0

    Thanks Anders,

    I actually upgraded to the latest version prior to deleting XML cache as above, so that seems to have done the trick.

Please Sign in or register to post replies

Write your reply to:

Draft