search

ziguifrido93 / procurement

Automatically exported from code.google.com/p/procurement
0 stars 0 forks source link

Individual buyouts not overriding tab buyouts #437

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Procurement Version: 1.8.5
OS: Windows 8
The problem is quite unpredictable, I do not know how to reproduce it.

Procurement is listing some of the gems in my shop at the tab buyout price (1 
alc) even after I have manually added a buyout for the gem. The price appears 
correctly in Procurement even after re-loading it, however it is incorrect in 
my shop thread.

Debug log doesn't look relevant so I removed the stack traces:

System.Security.Cryptography.CryptographicException: Key not valid for use in 
specified state. (This has been there since Procurement 1.7.2)

System.ArgumentException: An item with the same key has already been added.
(something about a ring, not sure how old this is.)

Buyouts.xml (individual item buyouts removed):
<?xml version="1.0" encoding="utf-8"?>
<Buyouts>
  <ItemBuyouts>
  </ItemBuyouts>
  <TabBuyouts>
    <!--Add your tabwide buyouts here Eg"-->
    <Item id="C Jewellery" value="1 alch" />
    <Item id="C Other" value="1 alch" />
    <Item id="Red Gems" value="1 alch" />
    <Item id="Blue Gems" value="1 alch" />
    <Item id="Green Gems" value="1 alch" />
  </TabBuyouts>
</Buyouts>

Original issue reported on code.google.com by HHAX...@gmail.com on 21 Oct 2014 at 2:44

GoogleCodeExporter commented 8 years ago 
It sounds like your buyout file might have some invalid entries. As a test, 
backup your buyout file and replace it with a default one.

Then add your tab buyouts, set a buyout on an item and test to see if the 
buyout for that item gets overridden.

Original comment by stickymaddness on 20 Nov 2014 at 4:15

GoogleCodeExporter commented 8 years ago 
Hi,

Procurement moved to github over a year ago, and I have not been monitoring the 
google code issue tracker. 

Google is shutting down google code in 3 weeks time, as such I am disabling 
this issue tracker as I will not be able to reply after that date.

If you are still having issues please relog your issue on Procurement's github 
page at https://github.com/Stickymaddness/Procurement

Original comment by stickymaddness on 30 Jul 2015 at 3:45