Bug 390232 - Don't add new payee from new operation panel
Summary: Don't add new payee from new operation panel
Status: RESOLVED FIXED
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 5.0.0
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
: 391064 391337 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-02-10 17:52 UTC by Aristide
Modified: 2018-03-04 21:46 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.0.1
Sentry Crash Report:


Attachments
strace about Kmymoney (Make on a account test) - Create on new project (261.48 KB, application/zip)
2018-02-10 17:52 UTC, Aristide
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aristide 2018-02-10 17:52:06 UTC
Created attachment 110514 [details]
strace about Kmymoney (Make on a account test) - Create on new project

PROBLEM : 

When I add new operation, and type a payee name, Kmymoney ask me if I want to add new payee. 

→ Click No : Payee is not added (Normal). 
→ Click Yes : Same, Payee is not added, field is clear. 

I join strace kmymoeny with bug report. 

NOTE : When I add payee from payee section, its work
Comment 1 Jack 2018-02-10 19:48:34 UTC
First, I assume you mean "KMM does not create a new payee when adding a transaction" ?

Please check whether the payee has actually been created, but just not set in the transaction.  After you create the transaction, and say yes to creating the new payee, save the transaction.  It saves with no payee.  Edit the transaction and set the payee to the one you just added.  I think it will set it correctly this time, and not ask again if you want to create it. 

I have found this myself, but was still trying to figure out the exact behavior before reporting.

It might be related that if you edit a transaction which has a payee, and try to remove the payee, you can make the payee field blank, but once you save the transaction, the payee is still there.  If you change the payee to one space, and then say "No" when it asks if you want to create that new payee, it does seem to save the transaction with no payee.
Comment 2 Aristide 2018-02-10 20:51:44 UTC
Hello. Its work but I have crash 

→ Create new operation
→ Type payee name (Example : « Test 12345 »
→ Click on YES. Ok, field is clear but payee appear in « Payee ». Its OK. 
→ But I must cancel adding, and recreate new. So, appear. BUT : 

I HAVE TWO CASES : 

→ If I create new operation and select into list payee : Its work. 
→ If I create new operation, and I type directly the name, KMymoney crash. 

https://www.youtube.com/watch?v=OtuAEHyoAzA 

I don't have to forget trace. But I can't add attachment here :)
Comment 3 Mark 2018-02-12 00:36:17 UTC
I also experience this problem (no crash, though) with the new KMyMoney 5.0.0 on Arch Linux. When I enter a payee that is not already in the list of known payees, it disappears when I click the Enter button to commit the transaction. The payee field stays blank. This also happens when I try to edit the transaction after committing it.

The work-around is to first create a new payee over in the separate view/list of all payees.
Comment 4 Thomas Baumgart 2018-02-14 20:19:11 UTC
Git commit d759f8dd6eae306d9c8a71ba4bc3be686a307050 by Thomas Baumgart.
Committed on 14/02/2018 at 20:18.
Pushed by tbaumgart into branch '5.0'.

Fix adding new entries while editing

Adding new entries for payees or tags during the modification of a
transaction was broken. This changes brings back the functionality.
FIXED-IN: 5.0.1

M  +15   -0    kmymoney/widgets/kmymoneymvccombo.cpp
M  +2    -0    kmymoney/widgets/kmymoneymvccombo.h
M  +1    -0    kmymoney/widgets/kmymoneytagcombo.cpp

https://commits.kde.org/kmymoney/d759f8dd6eae306d9c8a71ba4bc3be686a307050
Comment 5 Thomas Baumgart 2018-02-26 19:57:21 UTC
*** Bug 391064 has been marked as a duplicate of this bug. ***
Comment 6 Thomas Baumgart 2018-03-03 13:34:35 UTC
*** Bug 391337 has been marked as a duplicate of this bug. ***
Comment 7 Mark Hunter 2018-03-03 21:12:02 UTC
It seems as though they had something that worked quite well and made it not work very well.  That does not seem to be much of an "upgrade".
Comment 8 Mark Hunter 2018-03-03 21:12:35 UTC
It seems as though they had something that worked quite well and made it not work very well.  That does not seem to be much of an "upgrade".
Comment 9 Olivier Churlaud 2018-03-04 10:54:04 UTC
(In reply to Mark Hunter from comment #8)
> It seems as though they had something that worked quite well and made it not
> work very well.  That does not seem to be much of an "upgrade".

This is rude and not very helpful. This behavior is not too welcome.
Comment 10 Mark Hunter 2018-03-04 21:46:33 UTC
   My apologies but the old version was working very well for a very long
   time and the new version seems to have many "bugs" which are very
   annoying.

   Mark Hunter
   105 Baxter Street
   Bowmanville, Ontario
   L1C 5P8
   mark.s.hunter@bell.net

     ---------- Original Message ----------
     From: Olivier Churlaud <bugzilla_noreply@kde.org>
     Date: March 4, 2018 at 5:54 AM


     https://bugs.kde.org/show_bug.cgi?id=390232

     --- Comment #9 from Olivier Churlaud <olivier@churlaud.com> ---
     (In reply to Mark Hunter from comment #8)
     > It seems as though they had something that worked quite well and
     made it not
     > work very well. That does not seem to be much of an "upgrade".

     This is rude and not very helpful. This behavior is not too
     welcome.

     --
     You are receiving this mail because:
     You are on the CC list for the bug.