[Mahara-contributors] [Bug 1382890] Re: Message window too large on upgraded site
** Changed in: mahara Status: New = In Progress ** Changed in: mahara Importance: Undecided = High ** Tags added: regression -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1382890 Title: Message window too large on upgraded site Status in Mahara ePortfolio: In Progress Bug description: 1.10RC1 using an upgraded site On /artefact/multirecipientnotification/sendmessage.php the Message window is too wide (see screenshot). This does not happen on a fresh install. The site has been continuously updated since 1.4. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1382890/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1382890] A patch has been submitted for review
Patch for 1.10_STABLE branch: https://reviews.mahara.org/3832 -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1382890 Title: Message window too large on upgraded site Status in Mahara ePortfolio: In Progress Bug description: 1.10RC1 using an upgraded site On /artefact/multirecipientnotification/sendmessage.php the Message window is too wide (see screenshot). This does not happen on a fresh install. The site has been continuously updated since 1.4. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1382890/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1383029] [NEW] Page not accessible after reporting it as objectionable
Public bug reported: 1.10RC1 1. User 1 reports the page of User 2 as objectionable. 2. User 1 cannot see the page of User 2 anymore although he should still be able to during the objectionable content period. This is a regression from Mahara 1.9. ** Affects: mahara Importance: High Status: Confirmed ** Tags: regression -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1383029 Title: Page not accessible after reporting it as objectionable Status in Mahara ePortfolio: Confirmed Bug description: 1.10RC1 1. User 1 reports the page of User 2 as objectionable. 2. User 1 cannot see the page of User 2 anymore although he should still be able to during the objectionable content period. This is a regression from Mahara 1.9. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1383029/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1382896] Re: Cannot go to page that has been reported as objectionable
** Changed in: mahara 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 forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1382896 Title: Cannot go to page that has been reported as objectionable Status in Mahara ePortfolio: In Progress Bug description: 1.10RC1 Up to Mahara 1.9 an admin saw a More... link in the inbox for a page that was reported as being objectionable. Not so anymore in 1.10. There, the admin only sees the partial page title, but cannot click on it to be taken to it. He can only access the page by clicking on the link in the email if he has emails enabled for these messages. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1382896/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1298646] A patch has been submitted for review
Patch for 1.10_STABLE branch: https://reviews.mahara.org/3834 -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1298646 Title: Add artefact-level sharing Status in Mahara ePortfolio: In Progress Bug description: As was described during MaharaHui 2014, this is an improvement we would like to add to Mahara. Full specs are here https://mahara.org/view/artefact.php?artefact=363268view=1088 To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1298646/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1382902] Re: Hard-coded lang strings in multirecipient messages
** Changed in: mahara 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 forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1382902 Title: Hard-coded lang strings in multirecipient messages Status in Mahara ePortfolio: In Progress Bug description: 1.10RC1 Hard-coded lang strings: htdocs/artefact/multirecipientnotification/theme/raw/indexin.tpl: thFrom User/th htdocs/artefact/multirecipientnotification/theme/raw/indexout.tpl: thFrom User/th htdocs/artefact/multirecipientnotification/theme/raw/indexin.tpl: thTo User/th htdocs/artefact/multirecipientnotification/theme/raw/indexout.tpl: thTo User/th Besides being able to be translated, they should also only read From and To To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1382902/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1382896] Re: Cannot go to page that has been reported as objectionable
** Attachment added: bug1382896 https://bugs.launchpad.net/mahara/+bug/1382896/+attachment/4240248/+files/bug1382896 -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1382896 Title: Cannot go to page that has been reported as objectionable Status in Mahara ePortfolio: In Progress Bug description: 1.10RC1 Up to Mahara 1.9 an admin saw a More... link in the inbox for a page that was reported as being objectionable. Not so anymore in 1.10. There, the admin only sees the partial page title, but cannot click on it to be taken to it. He can only access the page by clicking on the link in the email if he has emails enabled for these messages. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1382896/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1382896] Re: Cannot go to page that has been reported as objectionable
Attaching the Selenium test script I used to replicate this bug. -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1382896 Title: Cannot go to page that has been reported as objectionable Status in Mahara ePortfolio: In Progress Bug description: 1.10RC1 Up to Mahara 1.9 an admin saw a More... link in the inbox for a page that was reported as being objectionable. Not so anymore in 1.10. There, the admin only sees the partial page title, but cannot click on it to be taken to it. He can only access the page by clicking on the link in the email if he has emails enabled for these messages. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1382896/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1382896] Re: Cannot go to page that has been reported as objectionable
Used git bisect to verify that the regression was introduced in https://reviews.mahara.org/#/c/2686/, the patch that added the new inbox multiple-recipient messages. So it was just an oversight in that code. -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1382896 Title: Cannot go to page that has been reported as objectionable Status in Mahara ePortfolio: In Progress Bug description: 1.10RC1 Up to Mahara 1.9 an admin saw a More... link in the inbox for a page that was reported as being objectionable. Not so anymore in 1.10. There, the admin only sees the partial page title, but cannot click on it to be taken to it. He can only access the page by clicking on the link in the email if he has emails enabled for these messages. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1382896/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1157543] Re: Record page editing history
Hi again. I gave this some more thought over the weekend. For DB field changes, I think the best approach going forward would be as follows: When viewing a past revision of an asset, we first apply the diffs to get back to the record as it actually was at the time. We then apply the modifications that would have happened to that row as a result of changes to the database since that date (giving it default values for fields that have been added and removing fields that are no longer used). This would give us a version that should be able to be passed to the current API without causing errors. Hopefully, most of this could be achieved by tracking the DB structure in a similar way to the record changes, but I think we'd need some sort of hook functionality to allow for transformations that are more complicated than the simple addition or removal of fields. And lots of unit tests! -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1157543 Title: Record page editing history Status in Mahara ePortfolio: In Progress Bug description: I'd like to dogfood Mahara's developer documentation by moving it from Mediawiki to the Mahara platform itself, probably as group pages so it could still be edited by many people. One of the features that is lacking to make this feasible, though, is having an edit history. The wiki allows us to keep track of who made what edits, and to revert to older versions if necessary. So, I'd like to see Mahara gain the ability to keep track of a page's edit history. At a minimum it needs: 1. Who made changes, at what time 2. What the page looked like at each revision 3. Ability to revert the page to a previous version Also good would be: 4. Ability to diff versions and highlight what changed 5. Comments that go in the history log 6. Publish ability (including publishing at a later time/date) 7. Versioning file attachments, see also https://bugs.launchpad.net/mahara/+bug/548195 To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1157543/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1157543] Re: Record page editing history
PS: Will give more consideration to whether we can avoid serializing the data. Re using JSON instead, fine - I wasn't aware of those issues. -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1157543 Title: Record page editing history Status in Mahara ePortfolio: In Progress Bug description: I'd like to dogfood Mahara's developer documentation by moving it from Mediawiki to the Mahara platform itself, probably as group pages so it could still be edited by many people. One of the features that is lacking to make this feasible, though, is having an edit history. The wiki allows us to keep track of who made what edits, and to revert to older versions if necessary. So, I'd like to see Mahara gain the ability to keep track of a page's edit history. At a minimum it needs: 1. Who made changes, at what time 2. What the page looked like at each revision 3. Ability to revert the page to a previous version Also good would be: 4. Ability to diff versions and highlight what changed 5. Comments that go in the history log 6. Publish ability (including publishing at a later time/date) 7. Versioning file attachments, see also https://bugs.launchpad.net/mahara/+bug/548195 To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1157543/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1382899] A patch has been submitted for review
Patch for master branch: https://reviews.mahara.org/3835 -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1382899 Title: Regular user can't see Objectionable content in forum as notification type Status in Mahara ePortfolio: Confirmed Bug description: 1.10RC1 Regular users who are group admins receive notifications about objectionable content for the groups that they administer. However, they cannot set the notification type Objectionable content in forum on their Settings - Notifications page because they can't see the type. Only admins can see it. However, anybody who can get objectionable content messages for forum topics and posts (any group admin and forum moderator) should be seeing this notification type. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1382899/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1380433] A change has been merged
Reviewed: https://reviews.mahara.org/3836 Committed: http://gitorious.org/mahara/mahara/commit/a019b2cbae098c9584e783f23528dfb6645adf5a Submitter: Robert Lyon (robe...@catalyst.net.nz) Branch:1.10_STABLE commit a019b2cbae098c9584e783f23528dfb6645adf5a Author: Son Nguyen s...@catalyst.net.nz Date: Mon Oct 13 16:20:38 2014 +1300 Fix the parameters for remote_avatar_url(). Bug 1380433 Change-Id: Idd084a6f0d28c1749bf8a09a502c4eec7032e842 -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1380433 Title: error with profile icon and gravitar Status in Mahara ePortfolio: Fix Committed Bug description: When I have 'use gravitar' turned on and then I go to alter view access and share with friends I get this error: [WAR] ee (lib/user.php:2685) remote_avatar_url: size should be in (16, 20, 25, 40, 50, 60, 100) Call stack (most recent first): log_message(remote_avatar_url: size should be in (16, 20, 25, ..., 8, true, true) at /home/robertl/htdocs/mahara-devel/mahara/htdocs/lib/errors.php:95 log_warn(remote_avatar_url: size should be in (16, 20, 25, ...) at /home/robertl/htdocs/mahara-devel/mahara/htdocs/lib/user.php:2685 remote_avatar_url(fr...@catalyst.net.nz, array(size 2)) at /home/robertl/htdocs/mahara-devel/mahara/htdocs/thumb.php:78 [WAR] ee (lib/user.php:2690) Array to string conversion Call stack (most recent first): log_message(Array to string conversion, 8, true, true, /home/robertl/htdocs/mahara-devel/mahara/htdocs/li..., 2690) at /home/robertl/htdocs/mahara-devel/mahara/htdocs/lib/errors.php:439 error(8, Array to string conversion, /home/robertl/htdocs/mahara-devel/mahara/htdocs/li..., 2690, array(size 4)) at /home/robertl/htdocs/mahara-devel/mahara/htdocs/lib/user.php:2690 remote_avatar_url(fr...@catalyst.net.nz, array(size 2)) at /home/robertl/htdocs/mahara-devel/mahara/htdocs/thumb.php:78 [DBG] ee (lib/web.php:1012) Missing file in theme default: images/no_userphotoArray.png I notice that the $size being passed in is not a string but an array eg: [DBG] ee (lib/user.php:2683) Array ( [maxw] = 25 [maxh] = 25 ) To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1380433/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1380433] A patch has been submitted for review
Patch for 1.10_STABLE branch: https://reviews.mahara.org/3836 -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1380433 Title: error with profile icon and gravitar Status in Mahara ePortfolio: Fix Committed Bug description: When I have 'use gravitar' turned on and then I go to alter view access and share with friends I get this error: [WAR] ee (lib/user.php:2685) remote_avatar_url: size should be in (16, 20, 25, 40, 50, 60, 100) Call stack (most recent first): log_message(remote_avatar_url: size should be in (16, 20, 25, ..., 8, true, true) at /home/robertl/htdocs/mahara-devel/mahara/htdocs/lib/errors.php:95 log_warn(remote_avatar_url: size should be in (16, 20, 25, ...) at /home/robertl/htdocs/mahara-devel/mahara/htdocs/lib/user.php:2685 remote_avatar_url(fr...@catalyst.net.nz, array(size 2)) at /home/robertl/htdocs/mahara-devel/mahara/htdocs/thumb.php:78 [WAR] ee (lib/user.php:2690) Array to string conversion Call stack (most recent first): log_message(Array to string conversion, 8, true, true, /home/robertl/htdocs/mahara-devel/mahara/htdocs/li..., 2690) at /home/robertl/htdocs/mahara-devel/mahara/htdocs/lib/errors.php:439 error(8, Array to string conversion, /home/robertl/htdocs/mahara-devel/mahara/htdocs/li..., 2690, array(size 4)) at /home/robertl/htdocs/mahara-devel/mahara/htdocs/lib/user.php:2690 remote_avatar_url(fr...@catalyst.net.nz, array(size 2)) at /home/robertl/htdocs/mahara-devel/mahara/htdocs/thumb.php:78 [DBG] ee (lib/web.php:1012) Missing file in theme default: images/no_userphotoArray.png I notice that the $size being passed in is not a string but an array eg: [DBG] ee (lib/user.php:2683) Array ( [maxw] = 25 [maxh] = 25 ) To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1380433/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1380433] Re: error with profile icon and gravitar
** 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 forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1380433 Title: error with profile icon and gravitar Status in Mahara ePortfolio: Fix Committed Bug description: When I have 'use gravitar' turned on and then I go to alter view access and share with friends I get this error: [WAR] ee (lib/user.php:2685) remote_avatar_url: size should be in (16, 20, 25, 40, 50, 60, 100) Call stack (most recent first): log_message(remote_avatar_url: size should be in (16, 20, 25, ..., 8, true, true) at /home/robertl/htdocs/mahara-devel/mahara/htdocs/lib/errors.php:95 log_warn(remote_avatar_url: size should be in (16, 20, 25, ...) at /home/robertl/htdocs/mahara-devel/mahara/htdocs/lib/user.php:2685 remote_avatar_url(fr...@catalyst.net.nz, array(size 2)) at /home/robertl/htdocs/mahara-devel/mahara/htdocs/thumb.php:78 [WAR] ee (lib/user.php:2690) Array to string conversion Call stack (most recent first): log_message(Array to string conversion, 8, true, true, /home/robertl/htdocs/mahara-devel/mahara/htdocs/li..., 2690) at /home/robertl/htdocs/mahara-devel/mahara/htdocs/lib/errors.php:439 error(8, Array to string conversion, /home/robertl/htdocs/mahara-devel/mahara/htdocs/li..., 2690, array(size 4)) at /home/robertl/htdocs/mahara-devel/mahara/htdocs/lib/user.php:2690 remote_avatar_url(fr...@catalyst.net.nz, array(size 2)) at /home/robertl/htdocs/mahara-devel/mahara/htdocs/thumb.php:78 [DBG] ee (lib/web.php:1012) Missing file in theme default: images/no_userphotoArray.png I notice that the $size being passed in is not a string but an array eg: [DBG] ee (lib/user.php:2683) Array ( [maxw] = 25 [maxh] = 25 ) To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1380433/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1383056] [NEW] Admin can't see page /artefact that was reported as objectionable
*** This bug is a duplicate of bug 1383029 *** https://bugs.launchpad.net/bugs/1383029 Public bug reported: Mahara 1.10RC1 regression 1. User creates a page and an artefact. No access permissions are set. 2. The page and also the artefact are reported as objectionable. 3. Site admin receives objectionable content message (and can go to it with patch for bug #1382896 applied). 4. Expected behavior: Admin sees the page / artefact to decide whether it is objectionable or not. Actual behavior: Cannot see the page / artefact. Maybe similar to bug #1383029 ** Affects: mahara Importance: High Status: Invalid ** Tags: regression ** Changed in: mahara Status: Confirmed = Invalid ** This bug has been marked a duplicate of bug 1383029 Page not accessible after reporting it as objectionable -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1383056 Title: Admin can't see page /artefact that was reported as objectionable Status in Mahara ePortfolio: Invalid Bug description: Mahara 1.10RC1 regression 1. User creates a page and an artefact. No access permissions are set. 2. The page and also the artefact are reported as objectionable. 3. Site admin receives objectionable content message (and can go to it with patch for bug #1382896 applied). 4. Expected behavior: Admin sees the page / artefact to decide whether it is objectionable or not. Actual behavior: Cannot see the page / artefact. Maybe similar to bug #1383029 To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1383056/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1383056] Re: Admin can't see page /artefact that was reported as objectionable
*** This bug is a duplicate of bug 1383029 *** https://bugs.launchpad.net/bugs/1383029 This specific scenario only happens when the page has no access records and is marked objectionable. The (buggy) objectionable access code was inside the for-loop that went through all the access records. So as long as there was one access record (for anything) then the admin could see it. -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1383056 Title: Admin can't see page /artefact that was reported as objectionable Status in Mahara ePortfolio: Invalid Bug description: Mahara 1.10RC1 regression 1. User creates a page and an artefact. No access permissions are set. 2. The page and also the artefact are reported as objectionable. 3. Site admin receives objectionable content message (and can go to it with patch for bug #1382896 applied). 4. Expected behavior: Admin sees the page / artefact to decide whether it is objectionable or not. Actual behavior: Cannot see the page / artefact. Maybe similar to bug #1383029 To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1383056/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1382896] A change has been merged
Reviewed: https://reviews.mahara.org/3833 Committed: http://gitorious.org/mahara/mahara/commit/3b4fa01e71218682abaed406635ae61129c05f93 Submitter: Son Nguyen (son.ngu...@catalyst.net.nz) Branch:master commit 3b4fa01e71218682abaed406635ae61129c05f93 Author: Aaron Wells aar...@catalyst.net.nz Date: Mon Oct 20 09:33:28 2014 +1300 Use default urltext if non supplied; in new inbox Bug #1382896 Change-Id: I373f97dc088a5c81c9401f6a01d7aa4b2bc09d64 -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1382896 Title: Cannot go to page that has been reported as objectionable Status in Mahara ePortfolio: Fix Committed Bug description: 1.10RC1 Up to Mahara 1.9 an admin saw a More... link in the inbox for a page that was reported as being objectionable. Not so anymore in 1.10. There, the admin only sees the partial page title, but cannot click on it to be taken to it. He can only access the page by clicking on the link in the email if he has emails enabled for these messages. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1382896/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1383058] [NEW] Merge Social media block with Profile info block
Public bug reported: In Mahara 1.10, the Social media block is introduced. Its functionality is doubled up because you can also choose to display the social media addresses in the Profile info block. There needs to be a bit thinking done around how to incorporate the display settings for the social media buttons best, but I think the blocks should be merged. If they aren't merged then the social media items should be taken out of the Profile info block. ** Affects: mahara Importance: Medium Status: Triaged ** Tags: usability -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1383058 Title: Merge Social media block with Profile info block Status in Mahara ePortfolio: Triaged Bug description: In Mahara 1.10, the Social media block is introduced. Its functionality is doubled up because you can also choose to display the social media addresses in the Profile info block. There needs to be a bit thinking done around how to incorporate the display settings for the social media buttons best, but I think the blocks should be merged. If they aren't merged then the social media items should be taken out of the Profile info block. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1383058/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1382896] Re: Cannot go to page that has been reported as objectionable
** 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 forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1382896 Title: Cannot go to page that has been reported as objectionable Status in Mahara ePortfolio: Fix Committed Bug description: 1.10RC1 Up to Mahara 1.9 an admin saw a More... link in the inbox for a page that was reported as being objectionable. Not so anymore in 1.10. There, the admin only sees the partial page title, but cannot click on it to be taken to it. He can only access the page by clicking on the link in the email if he has emails enabled for these messages. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1382896/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1382896] A patch has been submitted for review
Patch for 1.10_STABLE branch: https://reviews.mahara.org/3837 -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1382896 Title: Cannot go to page that has been reported as objectionable Status in Mahara ePortfolio: Fix Committed Bug description: 1.10RC1 Up to Mahara 1.9 an admin saw a More... link in the inbox for a page that was reported as being objectionable. Not so anymore in 1.10. There, the admin only sees the partial page title, but cannot click on it to be taken to it. He can only access the page by clicking on the link in the email if he has emails enabled for these messages. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1382896/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1382896] A change has been merged
Reviewed: https://reviews.mahara.org/3837 Committed: http://gitorious.org/mahara/mahara/commit/684787bb730d5870de2e60e004295f25c5ea4684 Submitter: Robert Lyon (robe...@catalyst.net.nz) Branch:1.10_STABLE commit 684787bb730d5870de2e60e004295f25c5ea4684 Author: Aaron Wells aar...@catalyst.net.nz Date: Mon Oct 20 09:33:28 2014 +1300 Use default urltext if non supplied; in new inbox Bug #1382896 Change-Id: I373f97dc088a5c81c9401f6a01d7aa4b2bc09d64 -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1382896 Title: Cannot go to page that has been reported as objectionable Status in Mahara ePortfolio: Fix Committed Bug description: 1.10RC1 Up to Mahara 1.9 an admin saw a More... link in the inbox for a page that was reported as being objectionable. Not so anymore in 1.10. There, the admin only sees the partial page title, but cannot click on it to be taken to it. He can only access the page by clicking on the link in the email if he has emails enabled for these messages. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1382896/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1298646] A change has been merged
Reviewed: https://reviews.mahara.org/3834 Committed: http://gitorious.org/mahara/mahara/commit/c7a5034451a72fb182b988014f1205d68d404a8f Submitter: Son Nguyen (son.ngu...@catalyst.net.nz) Branch:1.10_STABLE commit c7a5034451a72fb182b988014f1205d68d404a8f Author: Aaron Wells aar...@catalyst.net.nz Date: Mon Oct 20 09:44:50 2014 +1300 Marking a page objectionable caused it to be hidden Bug 1298646: Objectionable pages are meant to remain visible to users until an admin comes along and deletes them. They were accidentally being hidden due to a bug in the logic flow in can_view_view() Change-Id: I2929e11adc048af58b451892bae1c5789af8dcf0 -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1298646 Title: Add artefact-level sharing Status in Mahara ePortfolio: In Progress Bug description: As was described during MaharaHui 2014, this is an improvement we would like to add to Mahara. Full specs are here https://mahara.org/view/artefact.php?artefact=363268view=1088 To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1298646/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1298646] A patch has been submitted for review
Patch for master branch: https://reviews.mahara.org/3840 -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1298646 Title: Add artefact-level sharing Status in Mahara ePortfolio: In Progress Bug description: As was described during MaharaHui 2014, this is an improvement we would like to add to Mahara. Full specs are here https://mahara.org/view/artefact.php?artefact=363268view=1088 To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1298646/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1382890] A change has been merged
Reviewed: https://reviews.mahara.org/3839 Committed: http://gitorious.org/mahara/mahara/commit/daf39f44128cec9f88617ac9390798d9e33abe8f Submitter: Aaron Wells (aar...@catalyst.net.nz) Branch:master commit daf39f44128cec9f88617ac9390798d9e33abe8f Author: Robert Lyon robe...@catalyst.net.nz Date: Mon Oct 20 08:25:07 2014 +1300 Adjusting styles on cloned textarea for correct dimensions (Bug #1382890) Appending the textarea to body was not taking in account for the Change-Id: Icc06b16d8b8028121af1929be9bada4322e71c82 Signed-off-by: Robert Lyon robe...@catalyst.net.nz -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1382890 Title: Message window too large on upgraded site Status in Mahara ePortfolio: Fix Committed Bug description: 1.10RC1 using an upgraded site On /artefact/multirecipientnotification/sendmessage.php the Message window is too wide (see screenshot). This does not happen on a fresh install. The site has been continuously updated since 1.4. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1382890/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1298646] A change has been merged
Reviewed: https://reviews.mahara.org/3840 Committed: http://gitorious.org/mahara/mahara/commit/969b2a6fe7bb2dd43538106e5e9b5230133eb8e3 Submitter: Aaron Wells (aar...@catalyst.net.nz) Branch:master commit 969b2a6fe7bb2dd43538106e5e9b5230133eb8e3 Author: Aaron Wells aar...@catalyst.net.nz Date: Mon Oct 20 09:44:50 2014 +1300 Marking a page objectionable caused it to be hidden Bug 1298646: Objectionable pages are meant to remain visible to users until an admin comes along and deletes them. They were accidentally being hidden due to a bug in the logic flow in can_view_view() Change-Id: I2929e11adc048af58b451892bae1c5789af8dcf0 -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1298646 Title: Add artefact-level sharing Status in Mahara ePortfolio: In Progress Bug description: As was described during MaharaHui 2014, this is an improvement we would like to add to Mahara. Full specs are here https://mahara.org/view/artefact.php?artefact=363268view=1088 To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1298646/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1381740] Re: Block placement pop up improvement
The pop-up is usually called toolkit I think. When I hover over 'Media' I see a box. When I click 'Media' and hover over any of the choices, I don' get a box. Maybe it's not necessary after all. ** Attachment added: pop-up-toolkit.jpg https://bugs.launchpad.net/mahara/+bug/1381740/+attachment/4240316/+files/pop-up-toolkit.jpg -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1381740 Title: Block placement pop up improvement Status in Mahara ePortfolio: Incomplete Bug description: 1.10rc1 This is a clever enhancement. Could there be a pop up box when hovering over block title (I discovered this feature accidentally) and could there be a 'Position: bottom of column'? To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1381740/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1382890] A patch has been submitted for review
Patch for master branch: https://reviews.mahara.org/3839 -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1382890 Title: Message window too large on upgraded site Status in Mahara ePortfolio: Fix Committed Bug description: 1.10RC1 using an upgraded site On /artefact/multirecipientnotification/sendmessage.php the Message window is too wide (see screenshot). This does not happen on a fresh install. The site has been continuously updated since 1.4. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1382890/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1382902] A patch has been submitted for review
Patch for master branch: https://reviews.mahara.org/3841 -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1382902 Title: Hard-coded lang strings in multirecipient messages Status in Mahara ePortfolio: In Progress Status in Mahara 1.10 series: New Status in Mahara 1.11 series: In Progress Bug description: 1.10RC1 Hard-coded lang strings: htdocs/artefact/multirecipientnotification/theme/raw/indexin.tpl: thFrom User/th htdocs/artefact/multirecipientnotification/theme/raw/indexout.tpl: thFrom User/th htdocs/artefact/multirecipientnotification/theme/raw/indexin.tpl: thTo User/th htdocs/artefact/multirecipientnotification/theme/raw/indexout.tpl: thTo User/th Besides being able to be translated, they should also only read From and To To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1382902/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1382902] A patch has been submitted for review
Patch for 1.10_STABLE branch: https://reviews.mahara.org/3842 -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1382902 Title: Hard-coded lang strings in multirecipient messages Status in Mahara ePortfolio: Fix Committed Status in Mahara 1.10 series: Fix Committed Status in Mahara 1.11 series: Fix Committed Bug description: 1.10RC1 Hard-coded lang strings: htdocs/artefact/multirecipientnotification/theme/raw/indexin.tpl: thFrom User/th htdocs/artefact/multirecipientnotification/theme/raw/indexout.tpl: thFrom User/th htdocs/artefact/multirecipientnotification/theme/raw/indexin.tpl: thTo User/th htdocs/artefact/multirecipientnotification/theme/raw/indexout.tpl: thTo User/th Besides being able to be translated, they should also only read From and To To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1382902/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1382902] Re: Hard-coded lang strings in multirecipient messages
** Changed in: mahara/1.10 Status: New = Fix Committed ** Changed in: mahara/1.11 Milestone: 1.10.0 = 1.11.0 ** Changed in: mahara/1.10 Milestone: None = 1.10.0 ** Changed in: mahara/1.10 Importance: Undecided = Medium ** Changed in: mahara/1.11 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 forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1382902 Title: Hard-coded lang strings in multirecipient messages Status in Mahara ePortfolio: Fix Committed Status in Mahara 1.10 series: Fix Committed Status in Mahara 1.11 series: Fix Committed Bug description: 1.10RC1 Hard-coded lang strings: htdocs/artefact/multirecipientnotification/theme/raw/indexin.tpl: thFrom User/th htdocs/artefact/multirecipientnotification/theme/raw/indexout.tpl: thFrom User/th htdocs/artefact/multirecipientnotification/theme/raw/indexin.tpl: thTo User/th htdocs/artefact/multirecipientnotification/theme/raw/indexout.tpl: thTo User/th Besides being able to be translated, they should also only read From and To To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1382902/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1298646] Re: Add artefact-level sharing
Haha whoops, patches https://reviews.mahara.org/3834 and https://reviews.mahara.org/3840 were actually for bug 1383029! I put the wrong bug number in the commit message. -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1298646 Title: Add artefact-level sharing Status in Mahara ePortfolio: In Progress Bug description: As was described during MaharaHui 2014, this is an improvement we would like to add to Mahara. Full specs are here https://mahara.org/view/artefact.php?artefact=363268view=1088 To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1298646/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1381715] A patch has been submitted for review
Patch for master branch: https://reviews.mahara.org/3843 -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1381715 Title: adjust width in configure block Status in Mahara ePortfolio: Fix Committed Status in Mahara 1.10 series: Fix Committed Status in Mahara 1.11 series: Fix Committed Bug description: 1.10rc1 Presently width=500px. If at 625px, editor icons display nicer. See attachments To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1381715/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1381715] A change has been merged
Reviewed: https://reviews.mahara.org/3838 Committed: http://gitorious.org/mahara/mahara/commit/a6f6e6509ad85b175e4ce905895b2fa353c893a0 Submitter: Robert Lyon (robe...@catalyst.net.nz) Branch:1.10_STABLE commit a6f6e6509ad85b175e4ce905895b2fa353c893a0 Author: Aaron Wells aar...@catalyst.net.nz Date: Mon Oct 20 12:48:46 2014 +1300 Widen block configs so TinyMCE won't wrap Bug 1381715 Change-Id: I30fed711addac13be086eee08228fd4057204f8d -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1381715 Title: adjust width in configure block Status in Mahara ePortfolio: Fix Committed Status in Mahara 1.10 series: Fix Committed Status in Mahara 1.11 series: Fix Committed Bug description: 1.10rc1 Presently width=500px. If at 625px, editor icons display nicer. See attachments To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1381715/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1380201] Re: Access to a collection is sent as page access
** Changed in: mahara/1.10 Milestone: 1.10.0 = 1.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 before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1380201 Title: Access to a collection is sent as page access Status in Mahara ePortfolio: Confirmed Status in Mahara 1.10 series: Confirmed Status in Mahara 1.11 series: In Progress Bug description: 1.10RC1 (seems to be general issue not RC1 issue) When you give someone access to a collection, user receives a notification about having access to the first page in the collection. While this is not incorrect, technically, it would be better to state that they got access to the entire collection. Esp. when an instructor created a collection, they want to see that they got access to that instead of just a page as you then know directly that it's a collection and not just one page. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1380201/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1381715] A change has been merged
Reviewed: https://reviews.mahara.org/3843 Committed: http://gitorious.org/mahara/mahara/commit/28b194d82a1b6ee3f16985b97435759536fa0047 Submitter: Robert Lyon (robe...@catalyst.net.nz) Branch:master commit 28b194d82a1b6ee3f16985b97435759536fa0047 Author: Aaron Wells aar...@catalyst.net.nz Date: Mon Oct 20 12:48:46 2014 +1300 Widen block configs so TinyMCE won't wrap Bug 1381715 Change-Id: I30fed711addac13be086eee08228fd4057204f8d -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1381715 Title: adjust width in configure block Status in Mahara ePortfolio: Fix Committed Status in Mahara 1.10 series: Fix Committed Status in Mahara 1.11 series: Fix Committed Bug description: 1.10rc1 Presently width=500px. If at 625px, editor icons display nicer. See attachments To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1381715/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1369830] A change has been merged
Reviewed: https://reviews.mahara.org/3721
Committed:
http://gitorious.org/mahara/mahara/commit/859478ef6e3f05dbdedb0df0d1d2a922bdc16b0e
Submitter: Robert Lyon (robe...@catalyst.net.nz)
Branch:master
commit 859478ef6e3f05dbdedb0df0d1d2a922bdc16b0e
Author: Son Nguyen son.ngu...@catalyst.net.nz
Date: Wed Sep 24 16:01:14 2014 +1200
Allow CSS comments in customised skins. Bug 1369830
Change-Id: I0734ce56a2adee1659150c14f03659e261adde06
--
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 editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1369830
Title:
Comments in CSS disappear in page skins Custom CSS
Status in Mahara ePortfolio:
In Progress
Bug description:
Originally reported on the Mahara forum:
https://mahara.org/interaction/forum/topic.php?id=6443offset=0limit=10
This is more of a feature request.
We are currently on 1.9.2 on Linux w/ MySQL.
The issue is that when creating a page skin, comments in the CSS disappear
from page skins Custom CSS area.
Is there a way of getting the comments to stay?
It is quite important that people can comment what their CSS affects - so if
they make their skin available to others, other people can then know what to
change, and how it will affect the style of their page skin.
For example:
/* This makes the page heading background transparent*/
#top-wrapper {
background: transparent;
}
/* This makes the page footer background transparent*/
#footer-wrap {
background-color: transparent;
}
#footer {
background-color: transparent;
}
/* This will change the colour of the tabbed navigation in a collection*/
ul.colnav li a, ul.colnav li a:link, ul.colnav li a:visited, ul.colnav li
a:active {
background:#A2F7FF;
color:#9F0DF6
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1369830/+subscriptions
___
Mailing list: https://launchpad.net/~mahara-contributors
Post to : mahara-contributors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mahara-contributors
More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1383068] [NEW] Tag forum posts for easier searching
Public bug reported: from Simha Bode: It would be very helpful to have the ability to tag forum posts so it is easier to search through them. ** Affects: mahara Importance: Wishlist Status: Triaged ** Tags: forums -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1383068 Title: Tag forum posts for easier searching Status in Mahara ePortfolio: Triaged Bug description: from Simha Bode: It would be very helpful to have the ability to tag forum posts so it is easier to search through them. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1383068/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1381729] A patch has been submitted for review
Patch for 1.10_STABLE branch: https://reviews.mahara.org/3844 -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1381729 Title: Scoial profile and Social Profiles Status in Mahara ePortfolio: Fix Committed Bug description: I see two choices for social profile which could be confusing to users. I like the new social profile feature but I don't quite see what the functional difference is. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1381729/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1381729] A change has been merged
Reviewed: https://reviews.mahara.org/3829 Committed: http://gitorious.org/mahara/mahara/commit/f95eac3382e7fe36946872bee5dbb8b10bbff7b5 Submitter: Robert Lyon (robe...@catalyst.net.nz) Branch:master commit f95eac3382e7fe36946872bee5dbb8b10bbff7b5 Author: Aaron Wells aar...@catalyst.net.nz Date: Fri Oct 17 11:57:44 2014 +1300 UI improvements for SocialProfile artefact Bug 1381729: 1. Renaming it on the user side to Social media 2. Not asking the user for the network name if they choose a known network type 3. Adding some of the current popular networks to the dropdown list Change-Id: I7e38656cd174e6d6ccc2c5c61a5c844d207164ab -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1381729 Title: Scoial profile and Social Profiles Status in Mahara ePortfolio: Fix Committed Bug description: I see two choices for social profile which could be confusing to users. I like the new social profile feature but I don't quite see what the functional difference is. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1381729/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1381729] A change has been merged
Reviewed: https://reviews.mahara.org/3844 Committed: http://gitorious.org/mahara/mahara/commit/ab3c8861db1eec58bf5589825b9874d35f96cb5b Submitter: Robert Lyon (robe...@catalyst.net.nz) Branch:1.10_STABLE commit ab3c8861db1eec58bf5589825b9874d35f96cb5b Author: Aaron Wells aar...@catalyst.net.nz Date: Fri Oct 17 11:57:44 2014 +1300 UI improvements for SocialProfile artefact Bug 1381729: 1. Renaming it on the user side to Social media 2. Not asking the user for the network name if they choose a known network type 3. Adding some of the current popular networks to the dropdown list Change-Id: I7e38656cd174e6d6ccc2c5c61a5c844d207164ab -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1381729 Title: Scoial profile and Social Profiles Status in Mahara ePortfolio: Fix Committed Bug description: I see two choices for social profile which could be confusing to users. I like the new social profile feature but I don't quite see what the functional difference is. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1381729/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1381729] Re: Scoial profile and Social Profiles
** Changed in: mahara Status: Confirmed = 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 forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1381729 Title: Scoial profile and Social Profiles Status in Mahara ePortfolio: Fix Committed Bug description: I see two choices for social profile which could be confusing to users. I like the new social profile feature but I don't quite see what the functional difference is. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1381729/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1381729] Re: Scoial profile and Social Profiles
Robert was just pointing out to me that, in the end, the patch for this bug doesn't directly address the specific issue Dirk mentioned -- which is that the profile info block and the social media block do much the same thing. I think we can consider this fixed enough for the 1.10.0 release though, because: 1. The name of the block is now Social media, which is not as confusingly similar to Profile information as the old Social Profile name. 2. The Social media block actually has slightly different functionality than the Profile information block. It displays clickable buttons to get to all the users' social media accounts; while the Profile information block lists their profile details (not just social networks) in a different format. 3. The Social media block also has some extra controls that the Profile information block doesn't, to control formatting. This would make it non-trivial to merge the two blocks. Kristina has spun off a separate bug to consider the specific issue of folding the Social media block into the Profile information block: https://bugs.launchpad.net/bugs/1383058 -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1381729 Title: Scoial profile and Social Profiles Status in Mahara ePortfolio: Fix Committed Bug description: I see two choices for social profile which could be confusing to users. I like the new social profile feature but I don't quite see what the functional difference is. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1381729/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1380201] Re: Access to a collection is sent as page access
** Changed in: mahara/1.10 Milestone: 1.10.1 = 1.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 before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1380201 Title: Access to a collection is sent as page access Status in Mahara ePortfolio: Fix Committed Status in Mahara 1.10 series: Fix Committed Status in Mahara 1.11 series: Fix Committed Bug description: 1.10RC1 (seems to be general issue not RC1 issue) When you give someone access to a collection, user receives a notification about having access to the first page in the collection. While this is not incorrect, technically, it would be better to state that they got access to the entire collection. Esp. when an instructor created a collection, they want to see that they got access to that instead of just a page as you then know directly that it's a collection and not just one page. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1380201/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1380201] Re: Access to a collection is sent as page access
** Changed in: mahara/1.10 Status: Confirmed = Fix Committed ** Changed in: mahara/1.11 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 forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1380201 Title: Access to a collection is sent as page access Status in Mahara ePortfolio: Fix Committed Status in Mahara 1.10 series: Fix Committed Status in Mahara 1.11 series: Fix Committed Bug description: 1.10RC1 (seems to be general issue not RC1 issue) When you give someone access to a collection, user receives a notification about having access to the first page in the collection. While this is not incorrect, technically, it would be better to state that they got access to the entire collection. Esp. when an instructor created a collection, they want to see that they got access to that instead of just a page as you then know directly that it's a collection and not just one page. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1380201/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1369830] A patch has been submitted for review
Patch for 1.10_STABLE branch: https://reviews.mahara.org/3846
--
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 editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1369830
Title:
Comments in CSS disappear in page skins Custom CSS
Status in Mahara ePortfolio:
In Progress
Bug description:
Originally reported on the Mahara forum:
https://mahara.org/interaction/forum/topic.php?id=6443offset=0limit=10
This is more of a feature request.
We are currently on 1.9.2 on Linux w/ MySQL.
The issue is that when creating a page skin, comments in the CSS disappear
from page skins Custom CSS area.
Is there a way of getting the comments to stay?
It is quite important that people can comment what their CSS affects - so if
they make their skin available to others, other people can then know what to
change, and how it will affect the style of their page skin.
For example:
/* This makes the page heading background transparent*/
#top-wrapper {
background: transparent;
}
/* This makes the page footer background transparent*/
#footer-wrap {
background-color: transparent;
}
#footer {
background-color: transparent;
}
/* This will change the colour of the tabbed navigation in a collection*/
ul.colnav li a, ul.colnav li a:link, ul.colnav li a:visited, ul.colnav li
a:active {
background:#A2F7FF;
color:#9F0DF6
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1369830/+subscriptions
___
Mailing list: https://launchpad.net/~mahara-contributors
Post to : mahara-contributors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mahara-contributors
More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1380201] A change has been merged
Reviewed: https://reviews.mahara.org/3845 Committed: http://gitorious.org/mahara/mahara/commit/82b97c96d9b8e1c43ab3ccfd0fb8fd13da0928b8 Submitter: Robert Lyon (robe...@catalyst.net.nz) Branch:1.10_STABLE commit 82b97c96d9b8e1c43ab3ccfd0fb8fd13da0928b8 Author: Son Nguyen s...@catalyst.net.nz Date: Fri Oct 17 11:10:47 2014 +1300 Fix the notification about having access to a collection. Bug 1380201 Change-Id: Ie9aa85fbfe244285322f82a0b06b8287424f50d1 Signed-off-by: Son Nguyen s...@catalyst.net.nz -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1380201 Title: Access to a collection is sent as page access Status in Mahara ePortfolio: Fix Committed Status in Mahara 1.10 series: Fix Committed Status in Mahara 1.11 series: Fix Committed Bug description: 1.10RC1 (seems to be general issue not RC1 issue) When you give someone access to a collection, user receives a notification about having access to the first page in the collection. While this is not incorrect, technically, it would be better to state that they got access to the entire collection. Esp. when an instructor created a collection, they want to see that they got access to that instead of just a page as you then know directly that it's a collection and not just one page. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1380201/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1380201] A patch has been submitted for review
Patch for 1.10_STABLE branch: https://reviews.mahara.org/3845 -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1380201 Title: Access to a collection is sent as page access Status in Mahara ePortfolio: Fix Committed Status in Mahara 1.10 series: Fix Committed Status in Mahara 1.11 series: Fix Committed Bug description: 1.10RC1 (seems to be general issue not RC1 issue) When you give someone access to a collection, user receives a notification about having access to the first page in the collection. While this is not incorrect, technically, it would be better to state that they got access to the entire collection. Esp. when an instructor created a collection, they want to see that they got access to that instead of just a page as you then know directly that it's a collection and not just one page. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1380201/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1369830] Re: Comments in CSS disappear in page skins Custom CSS
** Changed in: mahara
Milestone: None = 1.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 before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1369830
Title:
Comments in CSS disappear in page skins Custom CSS
Status in Mahara ePortfolio:
In Progress
Bug description:
Originally reported on the Mahara forum:
https://mahara.org/interaction/forum/topic.php?id=6443offset=0limit=10
This is more of a feature request.
We are currently on 1.9.2 on Linux w/ MySQL.
The issue is that when creating a page skin, comments in the CSS disappear
from page skins Custom CSS area.
Is there a way of getting the comments to stay?
It is quite important that people can comment what their CSS affects - so if
they make their skin available to others, other people can then know what to
change, and how it will affect the style of their page skin.
For example:
/* This makes the page heading background transparent*/
#top-wrapper {
background: transparent;
}
/* This makes the page footer background transparent*/
#footer-wrap {
background-color: transparent;
}
#footer {
background-color: transparent;
}
/* This will change the colour of the tabbed navigation in a collection*/
ul.colnav li a, ul.colnav li a:link, ul.colnav li a:visited, ul.colnav li
a:active {
background:#A2F7FF;
color:#9F0DF6
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1369830/+subscriptions
___
Mailing list: https://launchpad.net/~mahara-contributors
Post to : mahara-contributors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mahara-contributors
More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1369830] A change has been merged
Reviewed: https://reviews.mahara.org/3846
Committed:
http://gitorious.org/mahara/mahara/commit/816b6f44e30de7a29f0f2e11c67dcbaa74b941fe
Submitter: Robert Lyon (robe...@catalyst.net.nz)
Branch:1.10_STABLE
commit 816b6f44e30de7a29f0f2e11c67dcbaa74b941fe
Author: Son Nguyen son.ngu...@catalyst.net.nz
Date: Wed Sep 24 16:01:14 2014 +1200
Allow CSS comments in customised skins. Bug 1369830
Change-Id: I0734ce56a2adee1659150c14f03659e261adde06
--
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 editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1369830
Title:
Comments in CSS disappear in page skins Custom CSS
Status in Mahara ePortfolio:
In Progress
Bug description:
Originally reported on the Mahara forum:
https://mahara.org/interaction/forum/topic.php?id=6443offset=0limit=10
This is more of a feature request.
We are currently on 1.9.2 on Linux w/ MySQL.
The issue is that when creating a page skin, comments in the CSS disappear
from page skins Custom CSS area.
Is there a way of getting the comments to stay?
It is quite important that people can comment what their CSS affects - so if
they make their skin available to others, other people can then know what to
change, and how it will affect the style of their page skin.
For example:
/* This makes the page heading background transparent*/
#top-wrapper {
background: transparent;
}
/* This makes the page footer background transparent*/
#footer-wrap {
background-color: transparent;
}
#footer {
background-color: transparent;
}
/* This will change the colour of the tabbed navigation in a collection*/
ul.colnav li a, ul.colnav li a:link, ul.colnav li a:visited, ul.colnav li
a:active {
background:#A2F7FF;
color:#9F0DF6
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1369830/+subscriptions
___
Mailing list: https://launchpad.net/~mahara-contributors
Post to : mahara-contributors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mahara-contributors
More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1380201] A change has been merged
Reviewed: https://reviews.mahara.org/3828 Committed: http://gitorious.org/mahara/mahara/commit/cee346babfd19b52ebdefe37b457a0c132f17716 Submitter: Robert Lyon (robe...@catalyst.net.nz) Branch:master commit cee346babfd19b52ebdefe37b457a0c132f17716 Author: Son Nguyen s...@catalyst.net.nz Date: Fri Oct 17 11:10:47 2014 +1300 Fix the notification about having access to a collection. Bug 1380201 Change-Id: Ie9aa85fbfe244285322f82a0b06b8287424f50d1 Signed-off-by: Son Nguyen s...@catalyst.net.nz -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1380201 Title: Access to a collection is sent as page access Status in Mahara ePortfolio: Fix Committed Status in Mahara 1.10 series: Fix Committed Status in Mahara 1.11 series: Fix Committed Bug description: 1.10RC1 (seems to be general issue not RC1 issue) When you give someone access to a collection, user receives a notification about having access to the first page in the collection. While this is not incorrect, technically, it would be better to state that they got access to the entire collection. Esp. when an instructor created a collection, they want to see that they got access to that instead of just a page as you then know directly that it's a collection and not just one page. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1380201/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1268746] Re: Squelch PHP 5.4+ strict standards errors
** Changed in: mahara/1.9 Status: Confirmed = 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 forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1268746 Title: Squelch PHP 5.4+ strict standards errors Status in Mahara ePortfolio: Fix Committed Status in Mahara 1.10 series: Fix Committed Status in Mahara 1.7 series: Fix Released Status in Mahara 1.8 series: Fix Released Status in Mahara 1.9 series: Fix Committed Bug description: Mahara sets its error reporting to E_ALL (in error.php). Prior to PHP 5.4, E_ALL, despite the name, did not include E_STRICT. Starting with PHP 5.4, it does include E_STRICT. Since Mahara has been running all this time with E_STRICT messages silenced, there are a lot of E_STRICT violations in the codebase, and on PHP 5.4+ servers, the logs are so full of them as to be useless. In the long term we should fix all the E_STRICT warnings, but for the short term we should just silence them. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1268746/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1382899] A change has been merged
Reviewed: https://reviews.mahara.org/3835 Committed: http://gitorious.org/mahara/mahara/commit/89f4e1c52bcc67099fc8843e0ee845ea2ee2c05e Submitter: Son Nguyen (son.ngu...@catalyst.net.nz) Branch:master commit 89f4e1c52bcc67099fc8843e0ee845ea2ee2c05e Author: Robert Lyon robe...@catalyst.net.nz Date: Mon Oct 20 10:35:59 2014 +1300 Allowing users to see more notification types (Bug #1382899) Adding a get_special_notifications function to allow for the adding of special case notification options to non admin user's notifications list Allowing the 'Objectionable content in forum' notification type to be seen/set by forum moderators/admins Change-Id: I69ab8b9de850345868346a85342f48d1f0b0f2aa Signed-off-by: Robert Lyon robe...@catalyst.net.nz -- 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 editing or unsubscribing it! https://bugs.launchpad.net/bugs/1382899 Title: Regular user can't see Objectionable content in forum as notification type Status in Mahara ePortfolio: Fix Committed Bug description: 1.10RC1 Regular users who are group admins receive notifications about objectionable content for the groups that they administer. However, they cannot set the notification type Objectionable content in forum on their Settings - Notifications page because they can't see the type. Only admins can see it. However, anybody who can get objectionable content messages for forum topics and posts (any group admin and forum moderator) should be seeing this notification type. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1382899/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1382899] Re: Regular user can't see Objectionable content in forum as notification type
** Changed in: mahara Status: Confirmed = 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 forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1382899 Title: Regular user can't see Objectionable content in forum as notification type Status in Mahara ePortfolio: Fix Committed Bug description: 1.10RC1 Regular users who are group admins receive notifications about objectionable content for the groups that they administer. However, they cannot set the notification type Objectionable content in forum on their Settings - Notifications page because they can't see the type. Only admins can see it. However, anybody who can get objectionable content messages for forum topics and posts (any group admin and forum moderator) should be seeing this notification type. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1382899/+subscriptions ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
