Re: [Gramps-users] Unwanted Christmas Present

[<ben...@ug...>]

Graham,

As Don told in another mail, since version 2.2.3 GRAMPS stores 
automatic backups
on exit. So your data of the previous days should be present on your PC if you
look arount for it (I saw from your bug report you have 2.2.3).

About your bugs. There are two ways for reporting bugs: the automatic mail
GRAMPS allows to send you on a crash (which you did), and using the bug
tracker: http://bugs.gramps-project.org

At the moment, if you want your bugs quickly looked at, you should select the
second option. There are few developers, and very little time to go over the
automatic mails and see what can be done about them. As Don noted in his 'what
you can do to help GRAMPS'-mail we need people to go over the bug 
mailing list,
select what are real bugs, delete doubles, and enter them into the 
bug-tracker.
The bugs on the bug-tracker tend to get priority, as nobody seems to have time
to go over the bug mailing list.

To help you, I looked at the bug you submitted on GEDCOM export (you find it
here: http://sourceforge.net/mailarchive/forum.php?forum=gramps-bugs, as you
can see many bugs arrive every day). Your bug looks like you write a person to
GEDCOM with no name (AttributeError: 'NoneType' object has no attribute
'encode'). I suggest you file a bug at http://bugs.gramps-project.org, and
upload the part of your data that produces this crash (if private data, send
the file to Don or Alex, they will delete it after the bug is solved).
Help on submitting bugs:
http://developers.gramps-project.org/tiki-index.php?page=HowToReportBugs

Benny

Quoting his...@sc...:

> Just had a failure saving a GEDCOM file. Sent bug report. Closed GRAMPS.
> Re-opened GRAMPS which failed again. Sent bug report. Noticed in "recently
> opened" that my grdb file appeared twice. Opening the upper one caused
> another failure. Opened the lower file successfully. This may have been a
> mistake. Decided to check the changes I'd made recently were OK. They were
> missing. Don't know how many are missing but it's at least a couple of  days
> work. I've now got to got through all the records in the database and compare
> them with the source spreadsheet - only about a thousand people. Had a look
> at when the record on each person was changed. They were all changed at the
> same time - within a two second period - so that wasn't very useful.
>
> Any suggestions as to how I avoid this happening again - apart from making a
> backup file every day? Every hour?
>
> Graham
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Gramps-users mailing list
> Gra...@li...
> https://lists.sourceforge.net/lists/listinfo/gramps-users
>



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.