[Expired for Mahara 1.10 because there has been no activity for 60
days.]
** Changed in: mahara/1.10
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for
[Expired for Mahara 15.10 because there has been no activity for 60
days.]
** Changed in: mahara/15.10
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription f
[Expired for Mahara 15.04 because there has been no activity for 60
days.]
** Changed in: mahara/15.04
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription f
[Expired for Mahara 1.9 because there has been no activity for 60 days.]
** Changed in: mahara/1.9
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for a
** Changed in: mahara/1.10
Milestone: 1.10.4 => None
** Changed in: mahara/1.9
Milestone: 1.9.6 => None
** Changed in: mahara/15.04
Milestone: 15.04.2 => None
** Changed in: mahara/15.10
Milestone: 15.10.0 => None
--
You received this bug notification because you are a member o
** Changed in: mahara/15.04
Milestone: 15.04.1 => 15.04.2
--
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 be
** Changed in: mahara/1.10
Status: Confirmed => Incomplete
** Changed in: mahara/1.9
Status: Confirmed => Incomplete
** Changed in: mahara/15.04
Status: Confirmed => Incomplete
** Changed in: mahara/15.10
Status: Confirmed => Incomplete
--
You received this bug noti
There seems to already be checks in the mahara code to stop one having a
duplicate urlid
I suspect the only way to get the duplication is via adding data to the
database directly - possibly via some migration script.
Until someone can make a test case of how to get this to happen via the
front en
To clarify:
- Any database changes should only be implemented on master.
- Any non-database fix (like the PHP-side validation check I mentioned a few
comments back) can be backported.
** Changed in: mahara/1.9
Status: New => Confirmed
** Changed in: mahara/15.04
Status: New => Con
** Also affects: mahara/15.04
Importance: Undecided
Status: New
** Also affects: mahara/1.9
Importance: Undecided
Status: New
** Also affects: mahara/15.10
Importance: Medium
Status: Confirmed
--
You received this bug notification because you are a member of Mahara
** Changed in: mahara/1.10
Milestone: 1.10.3 => 1.10.4
** No longer affects: mahara/1.8
** No longer affects: mahara/1.9
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara
** Changed in: mahara
Milestone: 15.04.0 => 15.04.1
--
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 e
"Null values are not considered equal. A multicolumn unique index will
only reject cases where all indexed columns are equal in multiple rows."
I think you've got it. The problem is due to both these sentences
together. It means that ('page1', 1, NULL, NULL) does not "equal"
('page1', 1, NULL, NUL
Upping the severity to "Medium" because this probably would be a pretty
annoying and noticeable problem if you're using clean URLs.
This problem will affect all versions of Mahara. I don't anticipate
fixing it in 1.8_STABLE and 1.9_STABLE, though, because it's not a high
severity bug, and the fix
Although actually, we could just add a validation check on the PHP side,
to see whether the urlid is already in use for that
user/group/institution. Add it to the Pieform validation function.
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribe
I did a test on my local instance where I set up two pages:
A) page1 with urlid=page1
B) page2 with urlid=page2
I go to the db and check that the unique index is present
"view_urlowngroins_uix" UNIQUE, btree (urlid, owner, "group", institution)
I then update, via db, the urlid of [B] to 'page1
There's supposed to be a unique index on the VIEW table for the columns
(URLID, OWNER, GROUP, INSTITUTION). This should make it impossible for a
user to have two pages with the same URLID.
Was the site missing this index?
** Changed in: mahara
Status: Confirmed => Incomplete
--
You recei
17 matches
Mail list logo
