Public bug reported:
When you delete a group, it concatenates '.deleted.'.time() that is
about 19 characters. Hence, if your group name is longer than 108
characters it will throw a DB exception for exceeding the 128 characters
field for the group name. To avoid this, I've added the following
Thanks Robert.
So are you saying that this isn't a bug at all, or just for the
situations where the artefact title still makes sense when applied to
the new block instance in its new context? What about when the artefact
title doesn't make sense in the new context, or is even potentially
Reviewed: https://reviews.mahara.org/3516
Committed:
http://gitorious.org/mahara/mahara/commit/e3f1cafa277068af4856ee6e806578413b999367
Submitter: Son Nguyen (son.ngu...@catalyst.net.nz)
Branch:master
commit e3f1cafa277068af4856ee6e806578413b999367
Author: Robert Lyon
** Changed in: mahara
Status: In Progress = Fix Committed
--
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
** Changed in: mahara
Status: In Progress = Fix Committed
--
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
Reviewed: https://reviews.mahara.org/3518
Committed:
http://gitorious.org/mahara/mahara/commit/0efa9f973c72ad02ca76f76415af934bf2361628
Submitter: Son Nguyen (son.ngu...@catalyst.net.nz)
Branch:master
commit 0efa9f973c72ad02ca76f76415af934bf2361628
Author: Robert Lyon
Reviewed: https://reviews.mahara.org/3574
Committed:
http://gitorious.org/mahara/mahara/commit/e96eee4c7a8738b074da8063fc67afa09a1bb6fe
Submitter: Son Nguyen (son.ngu...@catalyst.net.nz)
Branch:master
commit e96eee4c7a8738b074da8063fc67afa09a1bb6fe
Author: Robert Lyon
** Changed in: mahara
Status: In Progress = Fix Committed
--
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
** Changed in: mahara
Status: In Progress = Fix Committed
--
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
** Changed in: mahara
Status: In Progress = Fix Committed
--
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
** Changed in: mahara
Status: In Progress = Fix Released
--
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
Public bug reported:
Discovered while doing some testing in files and folders
** Affects: mahara
Importance: Medium
Assignee: Yuliya Bozhko (yuliya.bozhko)
Status: In Progress
--
You received this bug notification because you are a member of Mahara
Contributors, which is
Patch for master branch: https://reviews.mahara.org/3653
--
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 before
... so I've move it to 1.9_STABLE instead:
https://reviews.mahara.org/#/c/3654
The original bug reporter said that removing the nested subqueries from
that UPDATE statement improved performance from taking 1 minute to 1
second, which is a drastic enough improvement (with no front-end change)
In 1.10 this particular optimization becomes much less important,
because the old message inbox is no longer used unless the site disables
the new multi-recipient message inbox.
Cheers,
Aaron
** Changed in: mahara
Status: New = In Progress
** Changed in: mahara
Importance: Undecided =
** Description changed:
There are a few places which do this:
if (strpos($jsfile, 'http://' === false)) { ...
when they should do this:
- if (stripos($jsfile, 'http://' === false) stripos($jsfile, 'http://'
+ if (stripos($jsfile, 'http://' === false) stripos($jsfile, 'https://'
** Description changed:
Discovered while doing some testing in files and folders
+
+ To reproduce:
+
+ 1. Get fresh install.
+ 2. Login as admin
+ 3. Click content files
+ 4. Add a folder f1
+ 5. Enter folder
+ 6. Add a subfolder f2
+ 7. Edit f2, rename to folder2
+ 8. In SQL client
** Changed in: mahara
Milestone: None = 1.10.0
** Changed in: mahara
Status: In Progress = Fix Committed
** Tags added: regression
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions:
18 matches
Mail list logo
