On 02/05/2014 07:32 AM, Kevin Falcone wrote:
On Tue, Feb 04, 2014 at 08:34:27AM -0800, Tim Wiley wrote:
Is this expected behaviour? How might I work around this?
It is not expected behavior. I reported this a few months ago.
Thomas said that it's already fixed in the 4.2 branch & there's a
ticket to have it fixed in the 4.0 branch. Hit the login as guest
button on the URL below.
http://issues.bestpractical.com/Ticket/Display.html?id=25068
Your best bet may be to upgrade to the 4.2 branch.
To clarify, it's not a branch of 4.2, the current releases of 4.2.2
contain these fixes. Unfortunately, backporting them is non-trivial
so I'm not sure if that will happen for 4.0.
-kevin
Ah yes, I meant s/branch/release/g. Thanks for the clarification, Kevin.
