Hello Chris, This is the correct list to use, since the sourceforge ones are deprecated and you should have received a message when trying to subscribe.
Now, your 2 emails made it to the list and the developers who know about transaction import should be getting back to you shortly. Thank you for the patches! Regards, Alvaro On Mon, Nov 25, 2013 at 1:23 AM, Chris Tucker <christucker...@gmail.com> wrote: > I tried to subscribe to the list but am awaiting authorization. According to > the page at http://kmymoney2.sourceforge.net, this is the best way to submit > a bug for the git development code. If not the please point me in the right > direction. > > Another bug found in mymoneystatementreader.cpp when importing from OFX > direct connect. The reader trying to create splits cannot find the brokerage > account for a split using statementTransactionUnderImport so all the imported > transactions are broken. This is likely because the transaction doesn't know > the account name, but m_account does. A patch: > > *** mymoneystatementreader.cpp.orig 2013-11-24 17:27:39.959812598 -0800 > --- mymoneystatementreader.cpp 2013-11-24 20:01:40.339204121 -0800 > *************** > *** 565,570 **** > --- 565,573 ---- > if (brokerageactid.isEmpty()) { > brokerageactid = > file->nameToAccount(statementTransactionUnderImport.m_strBrokerageAccount); > } > + if (brokerageactid.isEmpty()) { > + brokerageactid = file->nameToAccount(thisaccount.brokerageName()); > + } > > // find the security transacted, UNLESS this transaction didn't > // involve any security. > > > -- > > Chris > > _______________________________________________ > KMyMoney-devel mailing list > KMyMoney-devel@kde.org > https://mail.kde.org/mailman/listinfo/kmymoney-devel _______________________________________________ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
