Summary: | Cannot enter non-gmail based account information | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Ritesh Raj Sarraf <kde-bugs> |
Component: | GoogleData Resource | Assignee: | Adenilson Cavalcanti <savagobr> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | ashl1future, fabo, jani-matti.hatinen, oli, robert, tokoe, vkrause, yg |
Priority: | NOR | ||
Version: | 4.3 | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | screen shot |
Description
Ritesh Raj Sarraf
2009-08-17 13:28:48 UTC
Created attachment 36215 [details]
screen shot
This is a left over from the time where the resource (and libgcal) only supported gmail.com accounts. At the time of KDE 4.3 release, I was not allowed to change the strings in the resource thanks to translation work. I guess now the string can be changed to something better (i.e. "hosted accounts please insert domain name"). *** Bug 212523 has been marked as a duplicate of this bug. *** *** Bug 246558 has been marked as a duplicate of this bug. *** *** Bug 231925 has been marked as a duplicate of this bug. *** *** Bug 231208 has been marked as a duplicate of this bug. *** The GUI I think should be in two ways. First, user should enter full e-mail address (if in gmail, mail@gmail.com is needed). Another way the title should be like: Your Google mail username (@gmail.com will be appended if needed). So if I enter non-email, only username, try @gmail.com, try full text in the field as login instead. Like a Google has. The UI string has been changed in Akonadi Googledata 1.2.0. While waiting for an update to the Debian package, you can get the newer version from packages.ubuntu.com. This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |