Hi Aaron,
Yes - that's exactly it. When I followed your instructions to get to the
notes for group page the tutor role had no rights, so it was an issue
with inheriting permissions. I can now fix the problem, though it will
take a bit of time to work through (the main group this affects was a
Public bug reported:
Hi,
At the most recent Machara (Scottish Mahara User Group) meeting we had a
short session on usability and workflow to come up with ideas for
improving usability - I'll submit a couple of ideas resulting from that.
This isn't a bug - more of a logical workflow issue.
The
Public bug reported:
Hi,
Feature/resource request.
At a recent Machara meeting (Scottish Mahara User Group) we looked at usability
and workflow. One of the common points raised is the where do I start
question - with almost everyone saying that they found copyable templates very
useful for
It seems to be a combination of both of those things. I think users are
generally quite happy to receive notifications as long as they're
relevant and useful (and not confusing), and rewording the notification
as suggested would certainly help to improve that.
However, I still think it would be
Reviewed: https://reviews.mahara.org/2929
Committed:
http://gitorious.org/mahara/mahara/commit/690f60061810cd6a225430dc01ed7e6f197d6f06
Submitter: Robert Lyon (robe...@catalyst.net.nz)
Branch:master
commit 690f60061810cd6a225430dc01ed7e6f197d6f06
Author: Aaron Wells aar...@catalyst.net.nz
** Changed in: mahara
Status: Confirmed = In Progress
** Changed in: mahara
Assignee: (unassigned) = logan walker (avkiwi)
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for
Public bug reported:
There are some access keys used in Mahara but there is no place that
explains what access keys are available and what they do.
As there is no standardization on what access keys should be used for
what action we need to add a table somewhere that explains to users what
is
Another problem is the Learn more link on a user's wall. I think we
need to handle the possibility of relative/absolute positioned elements
in an element's ancestry. If MochiKit can't handle it then using
jQuery's position() function for calculating the position of the help
box might be more
Patch for master branch: https://reviews.mahara.org/2940
--
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
Milestone: None = 1.9.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 before
Reviewed: https://reviews.mahara.org/2940
Committed:
http://gitorious.org/mahara/mahara/commit/632a498058ae834826cd7b714e82b1683d7d1064
Submitter: Robert Lyon (robe...@catalyst.net.nz)
Branch:master
commit 632a498058ae834826cd7b714e82b1683d7d1064
Author: logan walker avk...@icloud.com
Date:
Julius Serrano suggested that the information about the accesskeys
should be added to the Mahara User Manual. Or, if they're already in the
manual, they should be updated.
** Changed in: mahara
Assignee: (unassigned) = Kristina Hoeppner (kris-hoeppner)
** Changed in: mahara
Importance:
I agree, a mass-permissions-changing tool for groups could be useful.
I'll have to give some thought as to where would be a good place for
this to live... what you'd need is a screen that shows that matrix of
checkboxes, and lets you select what it should look like for all
artefacts in the group.
** 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
14 matches
Mail list logo