← Back to team overview

ubuntu-bengali-manual team mailing list archive

[Bug 1220746] Re: New Loco log-in rejected a prior user, lost data?

 

Thanks for your informations,

so "Events" are IRL meetings and "Meetings" are IRC meetings, i have
looked at the database and i didn't see any data losses, on the other
side you are right, i have found a minor bug which prevent data from
being saved once submitted throw the form, i have a fix  for it, this
happened because you have not filled all the required fields(this
includes the IRC channel).

if you have any questions please let me know.

** Changed in: loco-team-portal
       Status: New => Triaged

** Changed in: loco-team-portal
   Importance: Undecided => High

** Changed in: loco-team-portal
     Assignee: (unassigned) => Adnane Belmadiaf (daker)

-- 
You received this bug notification because you are a member of Ubuntu
Bengali Manual, which is subscribed to LoCo Team Portal.
https://bugs.launchpad.net/bugs/1220746

Title:
  New Loco log-in rejected a prior user, lost data?

Status in LoCo Team Portal:
  Triaged

Bug description:
  Hi! Just back from a long trip, I went to update our FOSS User Group
  meetings info for tomorrow's meeting (Massachusetts Loco Group). And
  was dumped out, unceremoniously.

  It started better than before, with a good-looking interface that
  prompted me far less ambiguously than it did before. But where are my
  prior meeting announcements? Why will I have to re-invent this
  information? FIX THAT!!

  I made a first attempt at doing so and proceeded. There was a
  compllaint about insufficient information (which I don't understand),
  followed by an apparent loss of my entered data! Try again FROM
  SCRATCH?? WHY?? FIX THAT!!

  I'm in a hurry to get to a meeting elsewhere. I only have time to
  report this shortfall, before I forget why I'm unable to complete my
  volunteered task at this time.

  Thanks for YOUR volunteer time! I hope this helps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/loco-team-portal/+bug/1220746/+subscriptions


Follow ups

References