we just want to let you know that this bug still affects us. Fortunately, it does not appear to affect user experience; at least, we haven't received any user complaints until now :-)
Our main problem with this one is that it makes us kind of "blind" w.r.t. our error monitor check, since this error occurs many times a day. So regardless of OSF's budget, we would like to have this bug fixed.
Chris, Paul, could you help us classifying this bug and determine whether it can be/needs to be fixed or at least be handled in a way that it is ignored by the error monitor? W.r.t billing, could you provide us with a quote? We then still can decide whether to wait for a new budget from OSF, pay it ourselves (gocept) or bill it to our customer(s), respectively.
Hello,
we just want to let you know that this bug still affects us. Fortunately, it does not appear to affect user experience; at least, we haven't received any user complaints until now :-)
Our main problem with this one is that it makes us kind of "blind" w.r.t. our error monitor check, since this error occurs many times a day. So regardless of OSF's budget, we would like to have this bug fixed.
Chris, Paul, could you help us classifying this bug and determine whether it can be/needs to be fixed or at least be handled in a way that it is ignored by the error monitor? W.r.t billing, could you provide us with a quote? We then still can decide whether to wait for a new budget from OSF, pay it ourselves (gocept) or bill it to our customer(s), respectively.
Thanks in advance,
Alex