|
noah
|
November 21, 2013 at 9:29 am
according to the final post in this thread, you can add a few lines of code to fix this issue.
I’m wondering if this be overwritten by future updates (until it is included)?
If it will, is there a way to add the code without it being overwritten by updates?
I just know that we are going to screw up our class launches every month until this gets fixed.
|
|
Tony
|
November 21, 2013 at 10:26 am
Hi,
Yes if you use the fix in that post it will be overwritten by future updates unfortunately.
Currently there is no way to make that fix update-proof as all fixes include modifying core files.
|
|
noah
|
November 21, 2013 at 11:16 am
Tony,
That’s what I thought but I wanted to check.
Do you know if the fix in that post is still in the development track for 3.1.37?
Thanks
|
|
Tony
|
November 21, 2013 at 11:52 am
I’ve just gone through and checked that it is.
Once its been through testing within 3.1.37 and verified it should be included in the release.
|
|
noah
|
November 21, 2013 at 12:34 pm
Thanks Tony,
I can’t wait for the update.
|
