** Changed in: mahara
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask
on #mahara-dev or mahara.org forum
** Changed in: mahara/15.10
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask
on #mahara-dev or mahara.org
Okay, the README.md file points users to the wiki for upgrade advice.
And the wiki *already* tells you that extracting the new code over the
old code is not recommended because of these sorts of issues.
I've updated it make this even clearer, and I've added a section to the
FAQ at the end, with
... and now that's resolved, updating this bug to "Won't fix", to
indicate that we haven't and won't be making any code changes to make
Mahara compatible with copy-over upgrading.
We still might want to put in place a sanity check to detect copy-over
upgrading. As mentioned above, that's been
Filed a related bug 1519519 for the idea of putting in a sanity check to
warn users off of this practice.
In the meantime, I think I'm just going to tackle this with this
approach:
1. Make sure our official upgrade documentation is not telling people to
upgrade by copying over their existing
5 matches
Mail list logo
