Bug 282508 - a change in the account book is not saved.
Summary: a change in the account book is not saved.
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.5.3
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-21 20:47 UTC by Claus Rebler
Modified: 2011-09-22 16:23 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Claus Rebler 2011-09-21 20:47:57 UTC
Version:           4.5.3 (using KDE 4.6.0) 
OS:                Linux

when a transaction processed in the account book and want to save these can not be the program.


Reproducible: Always

Steps to Reproduce:
* I create a new file.
* I import into the bank account of an ofx file with my transactions.
* Click the account book I edit a transaction on
* I wear to "pay" a recipient to supply a
* For category I put "content"
* Then I can not save my changes the program


Expected Results:  
my changes should be saved
Comment 1 allan 2011-09-21 21:13:25 UTC
On Wed, 21 Sep 2011 20:47:57 +0000
Claus Rebler <c.rebler@gmail.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=282508
> 
>            Summary: a change in the account book is not saved.
>            Product: kmymoney4
>            Version: 4.5.3
>           Platform: openSUSE RPMs
>         OS/Version: Linux
>             Status: UNCONFIRMED
>           Severity: normal
>           Priority: NOR
>          Component: general
>         AssignedTo: kmymoney-devel@kde.org
>         ReportedBy: c.rebler@gmail.com
> 
> 
> Version:           4.5.3 (using KDE 4.6.0) 
> OS:                Linux
> 
> when a transaction processed in the account book and want to save
> these can not be the program.
> 
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> * I create a new file.
> * I import into the bank account of an ofx file with my transactions.
> * Click the account book I edit a transaction on
> * I wear to "pay" a recipient to supply a
> * For category I put "content"
> * Then I can not save my changes the program
> 
> 
> Expected Results:  
> my changes should be saved
> 

When you edit one of the transactions, is it the edit of the transaction
that cannot be entered, rather than being unable to save the file after
the edit?

If so, is the date of the transaction earlier than the opening date of
the account?  If so, edit the account and change the opening date.

Allan
Comment 2 Claus Rebler 2011-09-22 15:56:14 UTC
I could not fault the somewhat narrow.

the error must be date-dependent. all entries that are older than 5 months have these.

short description
* transaction older than 5 months
I click on edit at a bank transfer
the board is "enter" the field-gray
I change the entry "pay" and category
the "Enter" field stays gray

* transaction less than 5 months
I click on edit at a bank transfer
the board is "enter" the field-colored and clickable
I change the entry "pay" and category
the "Enter" field is still clickable
I can save

there is a month barrier?
Comment 3 Alvaro Soliverez 2011-09-22 16:02:41 UTC
Check the opening date of your account.

Go to the account, edit the account.

The opening date should be about 5 months old. Change it to the actual opening date.
Comment 4 Claus Rebler 2011-09-22 16:09:04 UTC
ok then the fault is clearly on my side

Only those who think of something that there is a lock for editing.

It should be a warning window when the lock has come since. I'll bet there are more people purely on the problem! that should be borne in mind, perhaps.


another question
there is no news kmymoney twitter blog?
Comment 5 Alvaro Soliverez 2011-09-22 16:11:29 UTC
The date turns red, and hovering over it shows a tooltip with the explanation.

But if you have some other suggestion, not involving a popup, that would be welcome.
Comment 6 Claus Rebler 2011-09-22 16:23:19 UTC
The tooltip tells me that I still have no assigned category.

my tip would be
* Priorities with the tooltips provide. fault-block or have at the tips will prevail. correct tips are only marked out when no problem exists.
* Tootips window or make it bigger and it will fail or lock and display tips.