> > As I understand,
> > templates don't currently work (throw errors),
> We've recently found the same. Chris has been working to fix this
> situation, but that turned out to take longer than expected. The fix is
> planned to be included in one of the upcoming releases.
I saw that issue on github. What's the normal workflow on bug fixing -- ie., if
someone other than Chris wanted to help with it? It doesn't seem that
the github is a focal point for details of errors thrown, suggestions for
code blocks to work on, etc. -- would that be more on irc? (And maybe
this is more of a -devel list topic...)
> > and I'm not sure about
> > the status of recurring transactions. In my upgraded install, existing
> > recurring transactions disappear from the list when I edit them, and new
> > ones (by "Schedule"ing an AR entry, say) don't show up at all.
> That's definitely a bug.
> Does it happen to
> transactions in a newly created database/company? (I'm assuming so and will
> test myself as well.)
What are you getting? FWIW, here's some more details (but should I put
them here on in github issue tracker?)--
1) On an AR transaction, click schedule.
2) Keep date the same, and enter "every 1 month 3 times"
3) Goes back to Ar with "saved schedule" message, but nothing shows on
4) If I change the date, or use some other parameters, I get one of the
following errors (not sure exactly what causes which, etc.)
> > FWIW, I'm thinking about getting more involved in LedgerSMB as a project,
> That would be great! The irc://chat.freenode.net/#ledgersmb channel is
> pretty active these days. If you need help/ want to discuss your questions
> in real time, it might be an option to pop in and see if we can help.
I'll do that soonish, esp. when I get a full chunk of time to work on it.
> > possibly moving into some customizing (I've done a bunch of BIRT reports
> > for the 1.2 version) and possibly coding, etc.
> We highly appreciate any and all contributions: bug reports,
> customizations, coding, testing, UI improvements, documentation, you name
> it. Let us know what you need to be able to contribute and we'll see what
> we can do to provide for it.
Great! I think getting some input on folks' development environments
would be helpful, and more of a layout of the current codebase, best
practices, etc. Sounds like perhaps using IRC to get specific
suggestions on particular bugs and building up from there might be the
way to go based on current practice, so I'll try that.
_______________________________________________ Ledger-smb-users mailing list ..hidden.. https://lists.sourceforge.net/lists/listinfo/ledger-smb-users