| Age | Commit message (Collapse) | Author |
|---|
|
|
|
condition edit page renders again
|
|
|
|
|
|
condition check
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
sure hope so
|
|
|
|
|
|
(closes 1863)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
this patch, also revert gratuitous whitespace changes
|
|
|
|
|
|
table option in access_user::agentnums_sql so this is easy to fix for other reports too)
|
|
therefore selecting all retryable events, and having to filter later. On a system with a running history, this caused bad O() types of situations for performance, especially bad when this was called by something that a user would be awaiting feedback from
|
|
lines into two simple method calls
|
|
with a -m flag, daily will queue billing jobs instead of running each. freeside-queued will then pick it up, allowing multiple simultaneous jobs to run, as well as multiple machines.
Also adds a 'Secure' column to the queue system, allowing for billing jobs to define themselves as 'secure only' in cases where a box might be using the encryption. This allows you to
run secure only jobs (such as a collect) on boxes that can.
|
|
Condition tests to see if the Invoice bills for a particular service.
|
|
the event loop creates a 'NEW' record, as a placeholder. We need to not die from that.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
should understand the "most recent invoice per customer" and invoice # min/max options
|
|
|
|
|
|
|
|
xxEK, thanks to _vlad_ for tracking this down and providing a fix
|
|
|
