[Mahara-contributors] [Bug 1195269] Re: Resume birthdate field, if empty auto-fills to 1 Jan 1970
** Also affects: mahara/1.8 Importance: Undecided Status: New ** Changed in: mahara/1.8 Status: New = Fix Committed ** Changed in: mahara/1.8 Importance: Undecided = Medium ** Changed in: mahara/1.8 Assignee: (unassigned) = Aaron Wells (u-aaronw) ** Changed in: mahara/1.8 Milestone: None = 1.8.0rc1 ** Changed in: mahara Status: Fix Released = Confirmed -- 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/1195269 Title: Resume birthdate field, if empty auto-fills to 1 Jan 1970 Status in Mahara ePortfolio: Confirmed Status in Mahara 1.8 series: Fix Committed Bug description: To replicate: 1. Create a new user 2. Go to Content - Resume - Introduction 3. Fill in a Place of birth and leave all other fields empty. 4. Click Save 5. Navigate away from this page (for instance, by going to Dashboard) 6. Navigate back to Content - Resume - Introduction Expected Result: Because no birth date was filled in, the birthdate field should still be empty Actual Result: the birth date field will show Jan 1, 1970 It would appear that what's going on here is that the field that displays it is interpreting the null value from the database as a 0, and so it's displaying the Unix 0 epoch as your birthdate. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1195269/+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 1228543] Re: Typo in 'search/elasticsearch/lang/en.utf8/search.elasticsearch.php noticenotenabled'
Thanks, dajan. I'll fix this during the last round of lang string checks before the RC. ** Changed in: mahara Assignee: (unassigned) = Kristina Hoeppner (kris-hoeppner) ** Changed in: mahara Milestone: None = 1.8.0rc1 ** Changed in: mahara Status: New = Triaged ** Changed in: mahara Importance: Undecided = Low -- 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/1228543 Title: Typo in 'search/elasticsearch/lang/en.utf8/search.elasticsearch.php noticenotenabled' Status in Mahara ePortfolio: Triaged Bug description: Missing a capital E on Elasticsearch (string 4379 : The elasticsearch plugin is not currently enabled. To activate it, select it in the a href=%ssite options in the search settings/a.) To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1228543/+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 1228917] [NEW] false positive on changing folders in file attachments
Public bug reported: The leave page (dirty changes) warning appears on form pages where there is a file attachment selector option in a form (eg journal entries) when trying to go from one file directory to another. To test: 1) Upload some file in Content - files to a new subdirectory. 2) Fill in details on a form that has file attachments (eg Journal entry) 3) Click 'Add a file' button and choose to navigate to a subdirectory Expected result: go to the subdirectory and pick a file Actual result: get prompted about leaving page The bug is to do with the dirty changes patch and how file attachments work. When changing directories the form looks to save it's state and re-display itself but the dirty changes is not recognising this and thinking data is being lost when it is not. ** Affects: mahara Importance: Medium Status: Confirmed -- 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/1228917 Title: false positive on changing folders in file attachments Status in Mahara ePortfolio: Confirmed Bug description: The leave page (dirty changes) warning appears on form pages where there is a file attachment selector option in a form (eg journal entries) when trying to go from one file directory to another. To test: 1) Upload some file in Content - files to a new subdirectory. 2) Fill in details on a form that has file attachments (eg Journal entry) 3) Click 'Add a file' button and choose to navigate to a subdirectory Expected result: go to the subdirectory and pick a file Actual result: get prompted about leaving page The bug is to do with the dirty changes patch and how file attachments work. When changing directories the form looks to save it's state and re-display itself but the dirty changes is not recognising this and thinking data is being lost when it is not. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1228917/+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 1168213] A change has been merged
Reviewed: https://reviews.mahara.org/2510 Committed: http://gitorious.org/mahara/mahara/commit/799431782e793000e7b03370c377731dc936ac8d Submitter: Robert Lyon (robe...@catalyst.net.nz) Branch:master commit 799431782e793000e7b03370c377731dc936ac8d Author: Aaron Wells aar...@catalyst.net.nz Date: Fri Sep 20 15:23:30 2013 +1200 Skins: Fixing bug in the raw theme editviewtabs.tpl Bug 1168213 Change-Id: I7d65ff28707eec9f88742486dc5e524096772e62 -- 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/1168213 Title: Wishlist/Feature Request: Customise page themes (skins) Status in Mahara ePortfolio: Fix Committed Bug description: - exact version of Mahara: 1.5.7 - operating system: Redhat Linux 5.6 - database: MySQL 5.0.xx - Chrome 26, IE9, FireFox 20, Safari 5 I am not registering a bug, but a wishlist/feature request. I have had a lot of users (approx 95% I talk to) mention that they would love the ability to have the choice to customise their page themes. I realise this is no small undertaking, and it looks as though some site themes can be customised via the admin/institution pages - is this possible for configuring page themes? I have attached an image with a rough idea for implementation. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1168213/+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 1228930] [NEW] Skins should get a help icon or a line on the overview page to know how to edit it
Public bug reported: Currently, on 1.8.0dev, when you are on /skin/ you can easily see how to delete or export a skin. However, you cannot see how to edit it. You need to click the skin in order to change its properties. It would be good to have a little help sentence below the Skins heading or a help icon to that effect: Click on a skin to edit it. ** Affects: mahara Importance: Medium Status: Confirmed ** Tags: help -- 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/1228930 Title: Skins should get a help icon or a line on the overview page to know how to edit it Status in Mahara ePortfolio: Confirmed Bug description: Currently, on 1.8.0dev, when you are on /skin/ you can easily see how to delete or export a skin. However, you cannot see how to edit it. You need to click the skin in order to change its properties. It would be good to have a little help sentence below the Skins heading or a help icon to that effect: Click on a skin to edit it. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1228930/+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 1228930] Re: Skins should get a help icon or a line on the overview page to know how to edit it
I agree, this was one of the things that irked me about manage skins page. If you hover your cursor over the skin image it will tell you 'click to edit' but it needs to be more up front. -- 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/1228930 Title: Skins should get a help icon or a line on the overview page to know how to edit it Status in Mahara ePortfolio: Confirmed Bug description: Currently, on 1.8.0dev, when you are on /skin/ you can easily see how to delete or export a skin. However, you cannot see how to edit it. You need to click the skin in order to change its properties. It would be good to have a little help sentence below the Skins heading or a help icon to that effect: Click on a skin to edit it. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1228930/+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 1228934] [NEW] Exporting a skin has wrong background image
Public bug reported: Scenario: I have a bunch of skins on a site, and also have a bunch of images in content - files. I make a skin and give it a background image. I export the skin. I then import the skin into another site where lots of image files already exist. Outcome - for this particular skin it has wrong background image - The wrong background image didn't exist before on either of the test sites (though must have existed in dataroot). So for some reason it is picking up the wrong image to export. ** Affects: mahara Importance: High Status: New -- 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/1228934 Title: Exporting a skin has wrong background image Status in Mahara ePortfolio: New Bug description: Scenario: I have a bunch of skins on a site, and also have a bunch of images in content - files. I make a skin and give it a background image. I export the skin. I then import the skin into another site where lots of image files already exist. Outcome - for this particular skin it has wrong background image - The wrong background image didn't exist before on either of the test sites (though must have existed in dataroot). So for some reason it is picking up the wrong image to export. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1228934/+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 1195269] A change has been merged
Reviewed: https://reviews.mahara.org/2515 Committed: http://gitorious.org/mahara/mahara/commit/d63822bf8e72669c9bb2979cd2120a8e25ab935c Submitter: Aaron Wells (aar...@catalyst.net.nz) Branch:1.5_STABLE commit d63822bf8e72669c9bb2979cd2120a8e25ab935c Author: Aaron Wells aar...@catalyst.net.nz Date: Thu Jun 27 23:47:29 2013 +1200 Stop empty resume birthdate from auto-filling to Jan 1, 1970 Bug1195269 Change-Id: Ia0652570c7fc495b34e04716a6b339956e5ff017 -- 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/1195269 Title: Resume birthdate field, if empty auto-fills to 1 Jan 1970 Status in Mahara ePortfolio: Fix Committed Status in Mahara 1.5 series: Fix Committed Status in Mahara 1.6 series: Fix Committed Status in Mahara 1.8 series: Fix Committed Bug description: To replicate: 1. Create a new user 2. Go to Content - Resume - Introduction 3. Fill in a Place of birth and leave all other fields empty. 4. Click Save 5. Navigate away from this page (for instance, by going to Dashboard) 6. Navigate back to Content - Resume - Introduction Expected Result: Because no birth date was filled in, the birthdate field should still be empty Actual Result: the birth date field will show Jan 1, 1970 It would appear that what's going on here is that the field that displays it is interpreting the null value from the database as a 0, and so it's displaying the Unix 0 epoch as your birthdate. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1195269/+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 1195269] Re: Resume birthdate field, if empty auto-fills to 1 Jan 1970
Backporting to previous affected versions: 1.5: https://reviews.mahara.org/2515 1.6: https://reviews.mahara.org/2516 1.7: https://reviews.mahara.org/2517 -- 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/1195269 Title: Resume birthdate field, if empty auto-fills to 1 Jan 1970 Status in Mahara ePortfolio: Fix Committed Status in Mahara 1.5 series: Fix Committed Status in Mahara 1.6 series: Fix Committed Status in Mahara 1.8 series: Fix Committed Bug description: To replicate: 1. Create a new user 2. Go to Content - Resume - Introduction 3. Fill in a Place of birth and leave all other fields empty. 4. Click Save 5. Navigate away from this page (for instance, by going to Dashboard) 6. Navigate back to Content - Resume - Introduction Expected Result: Because no birth date was filled in, the birthdate field should still be empty Actual Result: the birth date field will show Jan 1, 1970 It would appear that what's going on here is that the field that displays it is interpreting the null value from the database as a 0, and so it's displaying the Unix 0 epoch as your birthdate. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1195269/+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 1195269] A change has been merged
Reviewed: https://reviews.mahara.org/2516 Committed: http://gitorious.org/mahara/mahara/commit/0503ba11ee34af04a9d209d4d5506b4081f103f9 Submitter: Aaron Wells (aar...@catalyst.net.nz) Branch:1.6_STABLE commit 0503ba11ee34af04a9d209d4d5506b4081f103f9 Author: Aaron Wells aar...@catalyst.net.nz Date: Thu Jun 27 23:47:29 2013 +1200 Stop empty resume birthdate from auto-filling to Jan 1, 1970 Bug1195269 Change-Id: Ia0652570c7fc495b34e04716a6b339956e5ff017 -- 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/1195269 Title: Resume birthdate field, if empty auto-fills to 1 Jan 1970 Status in Mahara ePortfolio: Fix Committed Status in Mahara 1.5 series: Fix Committed Status in Mahara 1.6 series: Fix Committed Status in Mahara 1.8 series: Fix Committed Bug description: To replicate: 1. Create a new user 2. Go to Content - Resume - Introduction 3. Fill in a Place of birth and leave all other fields empty. 4. Click Save 5. Navigate away from this page (for instance, by going to Dashboard) 6. Navigate back to Content - Resume - Introduction Expected Result: Because no birth date was filled in, the birthdate field should still be empty Actual Result: the birth date field will show Jan 1, 1970 It would appear that what's going on here is that the field that displays it is interpreting the null value from the database as a 0, and so it's displaying the Unix 0 epoch as your birthdate. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1195269/+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 1195269] A change has been merged
Reviewed: https://reviews.mahara.org/2517 Committed: http://gitorious.org/mahara/mahara/commit/95b50d9a6e052a82c7edf6f7e76e0bbb92cb5eaa Submitter: Aaron Wells (aar...@catalyst.net.nz) Branch:1.7_STABLE commit 95b50d9a6e052a82c7edf6f7e76e0bbb92cb5eaa Author: Aaron Wells aar...@catalyst.net.nz Date: Thu Jun 27 23:47:29 2013 +1200 Stop empty resume birthdate from auto-filling to Jan 1, 1970 Bug1195269 Change-Id: Ia0652570c7fc495b34e04716a6b339956e5ff017 -- 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/1195269 Title: Resume birthdate field, if empty auto-fills to 1 Jan 1970 Status in Mahara ePortfolio: Fix Committed Status in Mahara 1.5 series: Fix Committed Status in Mahara 1.6 series: Fix Committed Status in Mahara 1.8 series: Fix Committed Bug description: To replicate: 1. Create a new user 2. Go to Content - Resume - Introduction 3. Fill in a Place of birth and leave all other fields empty. 4. Click Save 5. Navigate away from this page (for instance, by going to Dashboard) 6. Navigate back to Content - Resume - Introduction Expected Result: Because no birth date was filled in, the birthdate field should still be empty Actual Result: the birth date field will show Jan 1, 1970 It would appear that what's going on here is that the field that displays it is interpreting the null value from the database as a 0, and so it's displaying the Unix 0 epoch as your birthdate. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1195269/+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 1195269] Re: Resume birthdate field, if empty auto-fills to 1 Jan 1970
** Also affects: mahara/1.5 Importance: Undecided Status: New ** Also affects: mahara/1.6 Importance: Undecided Status: New ** Also affects: mahara/1.7 Importance: Undecided Status: New ** No longer affects: mahara/1.7 ** Changed in: mahara Status: Confirmed = Fix Committed ** Changed in: mahara/1.5 Milestone: None = 1.5.12 ** Changed in: mahara/1.6 Milestone: None = 1.6.7 ** Changed in: mahara/1.5 Status: New = Fix Committed ** Changed in: mahara/1.6 Status: New = Fix Committed ** Changed in: mahara/1.5 Assignee: (unassigned) = Aaron Wells (u-aaronw) ** Changed in: mahara/1.6 Assignee: (unassigned) = Aaron Wells (u-aaronw) ** Changed in: mahara/1.5 Importance: Undecided = Medium ** Changed in: mahara/1.6 Importance: Undecided = Medium -- 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/1195269 Title: Resume birthdate field, if empty auto-fills to 1 Jan 1970 Status in Mahara ePortfolio: Fix Committed Status in Mahara 1.5 series: Fix Committed Status in Mahara 1.6 series: Fix Committed Status in Mahara 1.8 series: Fix Committed Bug description: To replicate: 1. Create a new user 2. Go to Content - Resume - Introduction 3. Fill in a Place of birth and leave all other fields empty. 4. Click Save 5. Navigate away from this page (for instance, by going to Dashboard) 6. Navigate back to Content - Resume - Introduction Expected Result: Because no birth date was filled in, the birthdate field should still be empty Actual Result: the birth date field will show Jan 1, 1970 It would appear that what's going on here is that the field that displays it is interpreting the null value from the database as a 0, and so it's displaying the Unix 0 epoch as your birthdate. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1195269/+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 1222200] Re: Admin forced to change users password when masquerading as another user
I agree, the notice could be more prominent, as could the link that you have to click on. Here's a screenshot of it in 1.7. I've circle the notice, and I've placed a rectangle around the link. ** Attachment added: screenshot.png https://bugs.launchpad.net/mahara/+bug/100/+attachment/3835408/+files/screenshot.png -- 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/100 Title: Admin forced to change users password when masquerading as another user Status in Mahara ePortfolio: New Bug description: Admin logs into the site and creates a new user, specifying a username and password. He visits the new users profile page, and clicks the 'Log in as' button. Admin gets the 'Change password screen' with the message 'You are required to change your password before you can proceed.' Only the actual user should see the change password screen, and not the mahara site admin. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/100/+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 1207140] Re: The embedded iframe filter doesn't support scheme-relative URLs such as //youtube.com (now used in the YouTube and Vimeo embed code)
** Summary changed: - YouTube iframe filter doesn't support the //youtube.com URLs YouTube now provides in embed code + The embedded iframe filter doesn't support scheme-relative URLs such as //youtube.com (now used in the YouTube and Vimeo embed 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/1207140 Title: The embedded iframe filter doesn't support scheme-relative URLs such as //youtube.com (now used in the YouTube and Vimeo embed code) Status in Mahara ePortfolio: Fix Committed Status in Mahara 1.6 series: Fix Committed Status in Mahara 1.7 series: Fix Committed Status in Mahara 1.8 series: Fix Committed Bug description: In response to FireFox's change in not supporting iframes with a http/https protocol that doesn't match the protocol of the parent page, YouTube's embed code now lists protocol-relative URLs. These start with //www.youtube.com, no http://;. This is a standard type of relative URL/URI, but our code doesn't support it. Since we already store the allowed iframe domains without a protocol in front of them, we should also support these protocol-relative URLs. To replicate: 1. Open up a YouTube video on youtube.com 2. Click Share and then Embed 3. Make sure you have NOT ticked the Use old embed code box 4. You should get an iframe embed code, like this: iframe width=420 height=315 src=//www.youtube.com/embed/NkyEOrQiGMQ frameborder=0 allowfullscreen/iframe 5. Paste this into an external media block or a text block in Mahara Expected result: You should be able to view the video once you've saved the block Actual result: The block will not display the video To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1207140/+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 1158086] Re: Forum: error after deleting a post that is the child of another deleted post
=== How to Test === 1. Create a Group 2. Create a forum topic 3. In that topic, post a reply A 4. Then post a reply to A, called B 5. Delete A 6. Delete B 7. confirm post has been deleted and user is not redirected to 404 page not found page. === Test Result === User taken to conformation page - user clicks yes to delete. on click the user is taken back to the forum page. Both replies are now grayed out. The page displays A post by name (first name, last name and user name) was deleted. The message is grayed out and is not click-able, no other information about the post is given. User was NOT redirected to any other page. Catalyst QA Approved ✔ -- 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/1158086 Title: Forum: error after deleting a post that is the child of another deleted post Status in Mahara ePortfolio: In Progress Bug description: If you delete the child of a deleted post, it deletes successfully but then you're sent to a page that says Not found. The page you are looking for could not be found. The post with ID '21' is not found or deleted!' It appears that what's happening is that after you delete a post it tries to send you to the URL for that post's parent. If the post's parent is deleted, then you get this error. To replicate: 1. Create a forum topic 2. In that topic, post a reply A 3. Then post a reply to A, called B 4. Delete A 5. Delete B Expected result: You should delete B, and then see the forum with A B deleted Actual result: You successfully delete B, but then you see a Not found error page. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1158086/+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 1158086] A change has been merged
Reviewed: https://reviews.mahara.org/2502 Committed: http://gitorious.org/mahara/mahara/commit/151b0d2eac47776d9142633ff73b01fa3950eb7d Submitter: Aaron Wells (aar...@catalyst.net.nz) Branch:master commit 151b0d2eac47776d9142633ff73b01fa3950eb7d Author: Robert Lyon robe...@catalyst.net.nz Date: Tue Sep 17 15:02:05 2013 +1200 Errors when deleting forum post bug 1158086 - some cases the check of parent post throws an error I believe this is due to '' being not the same as null Change-Id: Ib2eb287f3e31c02a545b8b42afcbfb9b54ea3abd 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/1158086 Title: Forum: error after deleting a post that is the child of another deleted post Status in Mahara ePortfolio: In Progress Bug description: If you delete the child of a deleted post, it deletes successfully but then you're sent to a page that says Not found. The page you are looking for could not be found. The post with ID '21' is not found or deleted!' It appears that what's happening is that after you delete a post it tries to send you to the URL for that post's parent. If the post's parent is deleted, then you get this error. To replicate: 1. Create a forum topic 2. In that topic, post a reply A 3. Then post a reply to A, called B 4. Delete A 5. Delete B Expected result: You should delete B, and then see the forum with A B deleted Actual result: You successfully delete B, but then you see a Not found error page. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1158086/+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 1220639] Re: mp4 file has wrong icon
Ok - the problem here is not fixed by my patch (just avoided). The problem looks to be in file_mime_type() function The function relies on finfo(), which has problems with the /usr/share/misc/magic.mgc file. The file is not working correctly for the version of PHP that some are using - see: https://bugs.php.net/bug.php?id=61940#1336148541 Or it relies on mime_content_type() which is deprecated. So the question is now that it really only relies on finfo() how are we going to deal with the magic.mgc file being incorrect for some? Can we include the needed magic.mgc files that work like mentioned in the above link? Will that be allowed? will it cause headaches? is there an alternate way to check mimetypes? ** Bug watch added: bugs.php.net/ #61940 http://bugs.php.net/bug.php?id=61940 -- 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/1220639 Title: mp4 file has wrong icon Status in Mahara ePortfolio: In Progress Bug description: On master (1.8.0dev) in Firefox: When an mp4 file is uploaded, it does not have the media icon of a camera, but just the generic document icon. I think the match-up of mime type and icon doesn't work properly. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1220639/+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 1187964] Re: Use adodb mysqli instead of mysql
** 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/1187964 Title: Use adodb mysqli instead of mysql Status in Mahara ePortfolio: Fix Committed Bug description: Mahara is currently using the adodb mysql driver for MySQL connections. This is based on an older PHP library which is no longer in active development and lacks certain features, most notably transactions (see for instance https://mahara.org/interaction/forum/topic.php?id=5434 ). We should probably switch to the adodb mysqli driver, which is built on the newer mysqli PHP library and *does* support transactions. There are two ways we could go about this gracefully: 1. When a user supplies the string mysql5 in their config.php file, we could silently interpret this to mean that they want to use the mysqli driver. (We could alternately provide some other way to indicate they want to use the older mysql library if we really want to support it.) 2. OR, we could show the admin a warning message after they upgrade/install, which tells them they should really change the mysql5 in their config.php to mysqli. I support option #1. Given that we only support mysql and postgres, there's no reason we shouldn't abstract away the connection between config.php and the name of the underlying adodb driver. (For that matter, we should probably change the recommended dbtypes from mysql5 and postgres8 to just mysql and postgres). To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1187964/+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 1187964] A change has been merged
Reviewed: https://reviews.mahara.org/2477 Committed: http://gitorious.org/mahara/mahara/commit/ac9e5527b3071447d6ee49ec2420f71f901dd167 Submitter: Aaron Wells (aar...@catalyst.net.nz) Branch:master commit ac9e5527b3071447d6ee49ec2420f71f901dd167 Author: Aaron Wells aar...@catalyst.net.nz Date: Thu Sep 5 18:26:55 2013 +1200 Upgrade our ADODB driver from the long-obsolete mysql driver to the actively developed mysqli driver Bug 1187964: The biggest improvement is that the ADODB mysqli driver actually supports transactions! Change-Id: I8e55ea28cd6e6b8ed5c883646c1172d318af5554 -- 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/1187964 Title: Use adodb mysqli instead of mysql Status in Mahara ePortfolio: Fix Committed Bug description: Mahara is currently using the adodb mysql driver for MySQL connections. This is based on an older PHP library which is no longer in active development and lacks certain features, most notably transactions (see for instance https://mahara.org/interaction/forum/topic.php?id=5434 ). We should probably switch to the adodb mysqli driver, which is built on the newer mysqli PHP library and *does* support transactions. There are two ways we could go about this gracefully: 1. When a user supplies the string mysql5 in their config.php file, we could silently interpret this to mean that they want to use the mysqli driver. (We could alternately provide some other way to indicate they want to use the older mysql library if we really want to support it.) 2. OR, we could show the admin a warning message after they upgrade/install, which tells them they should really change the mysql5 in their config.php to mysqli. I support option #1. Given that we only support mysql and postgres, there's no reason we shouldn't abstract away the connection between config.php and the name of the underlying adodb driver. (For that matter, we should probably change the recommended dbtypes from mysql5 and postgres8 to just mysql and postgres). To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1187964/+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 1228930] Re: Skins should get a help icon or a line on the overview page to know how to edit it
https://reviews.mahara.org/2514 ** Tags added: skins ** 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/1228930 Title: Skins should get a help icon or a line on the overview page to know how to edit it Status in Mahara ePortfolio: Fix Committed Bug description: Currently, on 1.8.0dev, when you are on /skin/ you can easily see how to delete or export a skin. However, you cannot see how to edit it. You need to click the skin in order to change its properties. It would be good to have a little help sentence below the Skins heading or a help icon to that effect: Click on a skin to edit it. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1228930/+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 1158086] Re: Forum: error after deleting a post that is the child of another deleted post
** Changed in: mahara Status: In Progress = Fix Committed ** Changed in: mahara Milestone: None = 1.8.0rc1 ** Changed in: mahara Assignee: (unassigned) = Robert Lyon (robertl-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 before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1158086 Title: Forum: error after deleting a post that is the child of another deleted post Status in Mahara ePortfolio: Fix Committed Bug description: If you delete the child of a deleted post, it deletes successfully but then you're sent to a page that says Not found. The page you are looking for could not be found. The post with ID '21' is not found or deleted!' It appears that what's happening is that after you delete a post it tries to send you to the URL for that post's parent. If the post's parent is deleted, then you get this error. To replicate: 1. Create a forum topic 2. In that topic, post a reply A 3. Then post a reply to A, called B 4. Delete A 5. Delete B Expected result: You should delete B, and then see the forum with A B deleted Actual result: You successfully delete B, but then you see a Not found error page. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1158086/+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 1228934] Re: Exporting a skin has wrong background image
I discussed this with Robert, and this issue may be due to the fact that Robert's second installation is a dev one, where the database has been wiped and reinstalled but the dataroot directory has remained empty between installations. So, the first step in investigating this should be to see whether it can be replicated on a site that was done as a complete clean install, with an empty dataroot directory. ** Tags added: skins ** Changed in: mahara Status: New = Incomplete ** Changed in: mahara Assignee: (unassigned) = Robert Lyon (robertl-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 before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1228934 Title: Exporting a skin has wrong background image Status in Mahara ePortfolio: Incomplete Bug description: Scenario: I have a bunch of skins on a site, and also have a bunch of images in content - files. I make a skin and give it a background image. I export the skin. I then import the skin into another site where lots of image files already exist. Outcome - for this particular skin it has wrong background image - The wrong background image didn't exist before on either of the test sites (though must have existed in dataroot). So for some reason it is picking up the wrong image to export. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1228934/+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 1228917] Re: false positive on changing folders in file attachments
** Changed in: mahara Importance: Medium = Low ** Changed in: mahara Milestone: 1.8.0rc1 = None -- 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/1228917 Title: false positive on changing folders in file attachments Status in Mahara ePortfolio: Confirmed Bug description: The leave page (dirty changes) warning appears on form pages where there is a file attachment selector option in a form (eg journal entries) when trying to go from one file directory to another. To test: 1) Upload some file in Content - files to a new subdirectory. 2) Fill in details on a form that has file attachments (eg Journal entry) 3) Click 'Add a file' button and choose to navigate to a subdirectory Expected result: go to the subdirectory and pick a file Actual result: get prompted about leaving page The bug is to do with the dirty changes patch and how file attachments work. When changing directories the form looks to save it's state and re-display itself but the dirty changes is not recognising this and thinking data is being lost when it is not. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1228917/+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 1228917] Re: false positive on changing folders in file attachments
** Changed in: mahara Milestone: None = 1.9.0rc1 -- 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/1228917 Title: false positive on changing folders in file attachments Status in Mahara ePortfolio: Confirmed Bug description: The leave page (dirty changes) warning appears on form pages where there is a file attachment selector option in a form (eg journal entries) when trying to go from one file directory to another. To test: 1) Upload some file in Content - files to a new subdirectory. 2) Fill in details on a form that has file attachments (eg Journal entry) 3) Click 'Add a file' button and choose to navigate to a subdirectory Expected result: go to the subdirectory and pick a file Actual result: get prompted about leaving page The bug is to do with the dirty changes patch and how file attachments work. When changing directories the form looks to save it's state and re-display itself but the dirty changes is not recognising this and thinking data is being lost when it is not. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1228917/+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 1226745] Re: rss feed module causes nonrecoverable error
Hi Paul, Since you're using IIS and we can't replicate the issue, it's possible this is a problem specific to IIS. So, it would be helpful if we could get a better error message in order to find out exactly what line of code the problem is on. On Linux machines, the PHP errors that come up while loading a Mahara page will by default get loaded into the Apache error logs, which in a standard configuration are at /var/log/apache2/error.log As Kristina mentioned, the PHP error log is likely to be someplace else in IIS. If you can't find the output for that, though, you can just configure your Mahara instance to show errors directly in the web browser. Just go into your Mahara site's config.php site and add this line: $cfg-productionmode = false; Then try adding one of the feeds. You should see a big ugly PHP error stack on the page instead of that generic nonrecoverable error message. If you could copy/paste that whole ugly error stack into this ticket, that would help a lot in tracking it down. Note that setting $cfg-productionmode = false will also put a big notice at the top of each page that says This site is not in production mode. So you'll probably want to do it during off hours so as not to disturb your users. Cheers, Aaron -- 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/1226745 Title: rss feed module causes nonrecoverable error Status in Mahara ePortfolio: New Bug description: Mahara 1.7.1 MSQL 5.5.27 Mozilla Firefox 23.0.1 Microsoft-IIS/7.5 MySQL client version: mysqlnd 5.0.8-dev - 20102224 - $Id: 65fe78e70ce53d27a6cd578597722950e490b0d0 $ PHP extension: mysqli Documentation To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1226745/+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 1168213] Re: Wishlist/Feature Request: Customise page themes (skins)
Okay, while fixing other issues I changed skin/style.php to use a page template (skin/style.tpl). So now themes can override the skin stylesheet. Theme developers can use this to try to make the skin stylesheet be compatible with their particular theme. https://reviews.mahara.org/#/c/2518/ Hm... it's actually probably not compatible with Page Themes... but that's a matter for another day. -- 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/1168213 Title: Wishlist/Feature Request: Customise page themes (skins) Status in Mahara ePortfolio: Fix Committed Bug description: - exact version of Mahara: 1.5.7 - operating system: Redhat Linux 5.6 - database: MySQL 5.0.xx - Chrome 26, IE9, FireFox 20, Safari 5 I am not registering a bug, but a wishlist/feature request. I have had a lot of users (approx 95% I talk to) mention that they would love the ability to have the choice to customise their page themes. I realise this is no small undertaking, and it looks as though some site themes can be customised via the admin/institution pages - is this possible for configuring page themes? I have attached an image with a rough idea for implementation. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1168213/+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 1215190] Re: LDAP support for non-standard port LDAP Urls
** Also affects: mahara/1.5 Importance: Undecided Status: New ** Changed in: mahara/1.5 Milestone: None = 1.5.12 ** Changed in: mahara/1.5 Status: New = Fix Committed ** Changed in: mahara/1.5 Importance: Undecided = Medium -- 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/1215190 Title: LDAP support for non-standard port LDAP Urls Status in Mahara ePortfolio: Fix Committed Status in Mahara 1.5 series: Fix Committed Status in Mahara 1.6 series: Fix Committed Status in Mahara 1.7 series: Fix Committed Status in Mahara 1.8 series: Fix Committed Bug description: This came up from a user asking for help on IRC. They had upgraded their site from Mahara 1.4 to Mahara 1.5 and found that LDAP authentication stopped working. Their LDAP host URL field was in this format: ldap://fake-dc1.fake.ac.uk:3268; In Mahara 1.4, this string would be passed in as the first and only parameter to ldap_connect(). In Mahara 1.5, the code is smarter and notices the final colon before the port number 3268. It strips this off of the URL, and passes ldap://fake-dc1.fake.ac.uk; as the first parameter and 3268 as the second parameter to ldap_connect(). The problem is, if the first parameter to ldap-connect is in URL style starting with a protocol ldap:// or ldaps://, ldap_connect() IGNORES the second parameter. And so the port was stripped off, and then ignored, and the connection didn't work. Making matters worse, the documentation tells people to put a protocol header on the front of their Host URL. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1215190/+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
