** Changed in: mahara/16.04
Status: Fix Committed => 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
** Changed in: mahara/16.04
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
** Changed in: mahara/16.10
Milestone: 16.10.1 => 16.10.0
--
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
This should now be fixed by https://reviews.mahara.org/#/c/7184/
** Changed in: mahara
Milestone: 16.10.1 => 17.04.0
** Changed in: mahara
Status: Triaged => Fix Committed
** Changed in: mahara/16.10
Status: Triaged => Fix Released
** Changed in: mahara/16.04
Status:
** Changed in: mahara/16.10
Milestone: 16.10.0 => 16.10.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
** Changed in: mahara/16.04
Milestone: 16.04.3 => 16.04.4
** Changed in: mahara/15.10
Milestone: 15.10.5 => 15.10.6
** Changed in: mahara/15.04
Milestone: 15.04.9 => 15.04.10
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed
** Changed in: mahara
Milestone: 16.04.2 => 16.04.3
** Changed in: mahara/15.10
Milestone: 15.10.4 => 15.10.5
** Also affects: mahara/16.04
Importance: Undecided
Status: New
** Also affects: mahara/16.10
Importance: High
Assignee: Robert Lyon (robertl-9)
Status:
** Changed in: mahara/15.04
Milestone: 15.04.8 => 15.04.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 Contributors -- please ask
on #mahara-dev or mahara.org forum
** Changed in: mahara
Milestone: 16.04.1 => 16.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 before
** Changed in: mahara/15.10
Milestone: 15.10.3 => 15.10.4
--
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.04
Milestone: 15.04.7 => 15.04.8
--
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
Milestone: 16.04.0 => 16.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
** Changed in: mahara/15.04
Milestone: 15.04.6 => 15.04.7
** Changed in: mahara/15.10
Milestone: 15.10.2 => 15.10.3
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara
Another issue with the view layout system is the use of the label
'columns' on some of the layout related tables.
In view_rows_columns the 'columns' represent the count of the number of
columns in the row
But in view_layout_rows_columns the 'columns' represent an id that maps
to the
Patch 5974 (remove vestigial database field view.numcolumns) doesn't
actually address this bug, so I'm moving it to a separate Bug report:
Bug 1557825.
** Changed in: mahara
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Mahara
Hi Matt,
In belated response to your question about why there are so many tables
to track view layouts, we do have a couple that could be consider
unnecessary if everything was redesigned, but on the whole it's actually
a fairly logical mapping of the flexibility of our page layout engine
into a
** Changed in: mahara
Status: New => In Progress
** Also affects: mahara/15.04
Importance: Undecided
Status: New
** Also affects: mahara/15.10
Importance: Undecided
Status: New
** Changed in: mahara
Milestone: None => 16.04.0
** Changed in: mahara/15.04
And here's a new, possibly related layout problem. I have a shared page
that is displaying as a 2 column, 6 row layout, but the 2nd column
doesn't exist to drop artifacts into. I can only drop artifacts into the
first column (any row).
I tried to change it to a one column layout and got an
I got a description from a user, which doesn't make a lot of sense in
this context:
"I did change the layout of the page, but after I made that change and saved
it, everything
was still working perfectly. I put a few ideas of my own onto the page by using
the text block feature, which also had
To fix the above problem I had to add entries for rows 1 & 2 in
view_rows_columns, and change each entry to have 2 columns (50,50) in
that table, as well as in view_layout_rows_columns.
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to
20 matches
Mail list logo
