Summary: | edit an exisiting todo that was created with a template changes the exisiting due date to the current date | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | John Floyd <jfloyd> |
Component: | incidence editors | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | gjditchfield |
Priority: | NOR | ||
Version: | 5.4.3 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
John Floyd
2015-03-21 01:20:24 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life. Running Korganizer V5.4.3 from fedora. The problem is still there but this is using older templates (from previous versions), eg re-open a todo due date June 1, the dialog comes up with the due date filled in with the current date. I have not been able to create new templates that korganizer can find ... I keep trying. So I havent been able to test newer templates. Still trying. This problem is a new template is created and saved, it is listed in following template dialog but cannot be found when clicked to open???? OK I have kludged a fix for this - do a symbolic link from share/korganizer/templates sharekorganizer/templates - it now finds the templ;ates I have made. Problem is the above error still occurs.... The problem may be due to the template that was used, but the dialog display should not do that. If I create a new todo (not using a template) then when I reopen it for editing, the due date stays the same. All this has been tested today... problem still exists Thanks John Thanks for the update; reopening. *** This bug has been marked as a duplicate of bug 332048 *** |