THIS PAGE HAS BEEN REPLACED! Please go to the new Trac and Wiki for PyCon-Tech

Please first check the PyConTech common installation problems before adding a bug here.

1. Proposal System

URL: http://us.pycon.org/apps07/proposals/

1.1 UTF8 ?/Unicode issues

Severity: HIGH
Status: Completed 11/3/06
Owner: Doug Napoleone
Description: A number of people reported problems with UTF8 ?/Unicode crashes. The problem stems from faulty conversion code in the forms manipulators in propmgr and the base form manipulator html2python() code. We need to first look for any unicode characters in the byte stream and convert to a real unicode character before performing the UTF8 ? encoding for the DB back end. If the string is already UTF8 ? encoded, do nothing. There is also an issue with UTF8 ? encoding on e-mails including their subjects which cause spam filters to filter the e-mails sent from the server. this is due to the default encoding being set to UTF8 ? to get other parts of the system working. In a newer version of django the e-mail encoding can be set seperatly.
Resolution: Added a core utility function safe_utf8_encode and used it for the forms. Also copied and modified the django email code to use new settings DEFAULT_EMAIL_CHARSET and EMAIL_SUBJECT_CHARSET. The subject setting is a hard override while the default emaile charset will fail over to us-ascii then utf8. Both are now set to us-ascii.

1.2 Bad Summary Formatting

Severity: Medium
Status: Completed 11/1/06
Owner: Doug Napoleone
Description: The summary should preserve whitespace but also wrap. There is a django filter which almost does this. Need to create our own and use that instead of the hard <PRE> tag and e-mail/url filter.
Resolution: Added a hack filter to replace newlines with '<br>' and any white space after the new line with ' 's. This will preserve newlines and line indentation in summaries while allowing them to wrap. To bad I didn't do this before editing 50 summaries.

1.3 Bad CSS for ReST ? fields

Severity: Medium
Status: In Progress
Owner: Doug Napoleone
Description: The PMWiki ? section specific <p> tag collides with the django field-set <p> tag in a bad way removing both the top and bottom spacing. Adding in a class for the rest fields in the tempaltes should fix this.

1.4 No view history on the stats pages

Severity: Low
Status: Open
Owner
Description: The organizer stats pages don't use the view history information. The Proposal model needs to be extended with a new base query object which uses the User information. Maybe use the request middleware and thread local hack to make the base Proposal.objects have the 'seen' flag. the trick will be to have seen always be True when there is no logged in user, and not to try to update the anonymous user in the view history. This whould be solved before using this system for other apps.

1.5 Reviewers should be able to see some of the stats pages

Severity: Request (Next Year)
Status: Completed (mid november?)
Owner: Douglas Napoleone
Description: The 'Reviewers' and 'Votes' organizer reports should be available to all PC members, but the system lacks the permission granuality for that. These reports (unlike the others) do not include Author information.
Doug Napoleone 11/6/06:
Reviewers have a hack permissions work around to see the votes stats.

1.6 Proposal form lacks instructions (requirement details)

Severity: Low (next year)
Status: Open
Owner
Description: I've noticed that several proposals lack an outline, and have a descriptive blurb instead. As Mike Pirnat put it: "the submission form seemed a bit unclear to me about the level of detail desired, which field might be used for the published description, etc." Clear instructions (from the Call for Proposals, which might need revision) should be added to the form.

1.7 Add Opt-Out for reviewers with a conflict of interest

Severity: Low (next year)
Status: Completed 11/1/06
Owner: Douglas Napoleone
Description: currently a reviewer who has a conflict of interest must ask to have their proposal assignment removed by an admin. We should have a button/link to automaticly reassign the review slot.
Resolution: Added an opt-out link to the review section for those assigned who have yet to add their review. A minimum of 3 assigned reviewers is maintained.

1.8 Review totals misreported

Severity: Medium
Status: Completed 11/2/06
Owner: Douglas Napoleone
Reporter: David Goodger
Description: In proposals with multiple +0 votes only, the vote total is misreported. E.g. in http://us.pycon.org/apps07/proposals/11/, there are two +0 votes, but the total is reported as +1.0. Perhaps +0.2 or +0(2) instead?
I don't know if totalling votes across vote types is even appropriate. For mixed votes perhaps total each type instead, something like "+n/-n(+0n/-0n)".
Resolution: The total score is as it was intended to be, but the feature should NOT have been enabled and is not part of the PyCon review process. Removed this number from the proposal detail view.

1.9 Changes to attachments should change read/unread status

Severity: High
Status: Closed 11/2/06
Owner: Douglas Napoleone
Reporter: David Goodger
Description: By accident, I noticed that the author of http://us.pycon.org/apps07/proposals/100/ had added an outline as an attachment, per my request in a comment. The addition of the attachment should change the status of the proposal to "unread", so that reviewers don't miss these changes. Perhaps such changes should trigger email notifications like new comments do.
Resolution: Could not reproduce the problem. This was most likely due to a restart of the django apps while the file was being attached to the proposal mentioned. Django transactions are enabled, but it is possable that the update to the proposal timestamp was to occur dirring a seperate transaction.

1.10 Have a ReST ? practice 'editor'

Severity: Request (Next Year)
Status: Open
Owner
Description: Some submitters were having issues learning ReST ? with the deadline looming hours away. Having a practice ReST ? editor which does not require a login account would help solve this along with better instructions on what is expected in the proposal (request above).

1.11 The "My Vote" Column Seems Broken

Severity: Medium
Status: Not a bug 11/05/06
Owner: Doug Napoleone
Description: As a talk reviewer, the "my vote" column acts strange. For those talks on whom I'm -not- an assigned reviewer, it shows a vote of -1 or -0 or +1. Some of those I did indeed vote on but not on most and it shows a value for all such talks. For those I am a reviewer on, it seems to work better but I'm not yet sure it is correct. -Jeff Rush
Resolution: There is no column 'My Vote' on the table which lists talks you are not assigned to. Once you vote on a talk, it becomes assigned to you as one you are voting on and is moved up into the other table.

1.12 Reassigned proposals should generate email notification

Severity: Medium
Status: Completed 11/07/06
Owner: Doug Napoleone
Reporter: David Goodger
Description: A proposal can be unassigned via the "opt-out" button if the originally assigned reviewer cannot do the review. The proposal is reassigned randomly to another reviewer. The reassignment should generate email notification for the new reviewer. Otherwise, it's easy for the new reviewer to miss the proposal.
Resolution: Implemented the missing feature.

1.13 Admin improperly updates the timestamp on proposal reviews

Severity: Medium (next year as propsal process is done).
Status: Open
Owner
Reporter: Doug Napoleone
Description: Sometimes (and only sometimes), when you modify a propsal in the django admin, the reviews which are edit_inline will get re-saved as if they were edited (improperly) and all assigned the current update time.

1.14 Bad HTML in accepted talks and proposal search listing

Severity: High
Status: Completed 1/1/07
Owner: Doug Napoleone
Reporter: Jeff Rush
Description: There is bad HTML being generated in the accepted talks and proposal listing pages. They still render OK in firefox and IE6 ?, but Safari, IE7 ? and Opera each have different issues. Opera is the worst effected as it is rendering exactly as the html says it should be (go figure).

1.15 Django pages are not XHTML compliant

Severity: Medium
Status: In Progress
Owner: Doug Napoleone
Reporter: Jeff Rush
Description: All the django pages are not XHTML compliant. This is different from the 1.14 bug as fixing that does not mean the pages are compliant, just that they render properly.
Doug Napoleone 1/1/07:
Most django pages are now compliant. Some proposal pages and th schedule app are not. Some issues with the schedule app can be fixed (id's and classes on divs in the <td> cells instead of on them); but some cannot (the dojo specific DOM extensions).

2. Talk Schedule

3. Registration

4. Web site -- general

4.1 Page titles too long

Severity: Medium
Status: Completed 11/16/06
Owner: Jeff Rush
Reporter: David Goodger
Description: Web pages are all prefixed by "PyCon - A Conference of the Python Community | ". Wiki pages have "TX2007" also. This forces the important, unique parts of page titles to the end, where they're hard to find. Opened in tabs, multiple PyCon pages are indistinguishable from each other.
Solution: I recommend moving the boilerplate text to a suffix.
Resolution: Doug Napoleone 11/1/06:
Removed the boilerplate from the proposal detail pages entirely to help facilitate the review process.
Jeff Rush 11/16/06:
Changes boilerplate per David's solution.

4.2 Site hard to navigate in lynx and on low res monitors

Severity: Medium
Status: Completed 11/06/07
Owner: Doug Napoleone
Description: Aahz has to page through the sidebar links to get to the meat of the page for reviewing proposals. Others have complained about having to scroll or having the contents squished on low resolution monitors.
Solution: For the wiki pages, the 'Printable View' is passable. For the django apps, a toggle option can be added for a minimal view. The state flag can be stored on the session cookie. The base template can check for the flag (via a context processor) and switch between the pmwiki base and a simple one.
Doug Napoleone 11/6/06:
There is now a 'Minimal/Maximal' switch on all Django apps to remove the side banners. This is done in a sub-optimal way, but it seems to work. The best solution would be to have proper django block markup in the PHP code embedded in comments.
Resolution: The Minimal/Maximal fix is good enough, and Printable view works good enough for the wiki pages.

4.3 Site Options bug when no session cookie present.

Severity

Medium

Status

Completed 1/1/07

Owner

Doug Napoleone

Description

The 'options' framework (currently only the minimal/maximal view sqitch is implemented) has a bug. If no session cookie exists, we crash. this is only currently hit by web crawlers. Need to fix and add 'nofollow' to a large number of our links.
->

     File "/var/hostings/05pcon0912/us.pycon.org/apps07/pycon/views.py", line 33, in set_option    
         if (request.method == 'GET' and request.META['HTTP_REFERER']):
     KeyError: 'HTTP_REFERER'

4.4 Bad Headers on Django pages

Severity: Medium
Status: Completed 1/1/07
Owner: Doug Napoleone
Reporter: Doug Napoleone
Description: The html headers give an encoding type of 'iso-8859-1' (from the PHP base template) but we have django set to render 'utf-8' encoded pages. This conflict is the root cause of some of the Unicode bugs origionally reported under bug 1.1. Some browser/os combinations would go with the meta encoding it was told to use instead of the encoding they discovered when rendering the form (as they should have.

5. User Account

5.1 Reset-Password 'logout' bug

Severity: Medium
Status: Open
Owner
Description: The on-success view for resetting the password improperly sets the 'user' variable in the view context. It is set to the first user found with that e-mail address. This results in the page header giving a bogus "logout 'username'" exposing the username.

5.2 Account Activation not fully implemented

Severity: Low
Status: Open
Owner
Description: If an account is not active and has an activation code, then the login validator should include a link to an activation form for the user to imput the activation code. There should be a link on that form to re-send the activation code. Change link based activation with GET form activation. Also add auto-redirect on the activation view to hide the code from javascript injection (which is why we currently use the link hack).

5.3 User Account str slowing down admin

Severity: High
Status: Completed 11/28/06
Owner: Doug Napoleone
Description: The base __str__ for User objects has been edtended to use the UserProfile ? extension. This means an extra query every time a user is stringified. This makes for easy template code and allows the admin to use the persons name instead of the username, but it makes for a slow admin. Adding a memcache to the __str__ override should greatly reduce the overhead. This will not fix all the django admin slowness. Django needs to implement form field caching to speed up the admin.
Resolution: Added cache of the username override. This reduced the average admin proposal edit page load time from 12sec to 2.5sec, with a max from 16seconds, down to 4 seconds; back within reasonable ranges. The cache is currently set for 1 hour, so the first loading will still take about 4 seconds, per CGI at most once per hout; but that is also reasonable.


10 Member(s) Online Overview Registration Event Calendar Mailing Lists City Map Department Heads Conference Weblog Kiosk Presentations Keynotes Accepted Talks Schedule of Talks Lightning Talks Open Space Talks A/V Recordings Con Activities Tutorial Day Sprinting Days Python Lab Special Meetings Help for Speakers Vendors Travel/Lodging/Food Air Travel Hotel Reservations Ground Transit Food Restaurants Other Stores Points of Interest Help Out Volunteer Sponsor PyCon Spread the Word Items Needed Write Software Past Cons Past Conferences Recordings of Talks 2006 Presentations 2005 Presentations 2004 Presentations PyCon is a 100% Volunteer-run Conference Organized by Members of the Python Community. Site/Questions etc ?	Top / TX2007 / PyConTechBugs Edit Page Printable View Page History	About Search Recent Changes to Site PyCon 2007 is sponsored in part by Platinum Gold Silver Media
	THIS PAGE HAS BEEN REPLACED! Please go to the new Trac and Wiki for PyCon-Tech Please first check the PyConTech common installation problems before adding a bug here. 1. Proposal System URL http://us.pycon.org/apps07/proposals/ ~~1.1 UTF8 ?/Unicode issues~~ Severity HIGH Status Completed 11/3/06 Owner Doug Napoleone Description A number of people reported problems with UTF8 ?/Unicode crashes. The problem stems from faulty conversion code in the forms manipulators in propmgr and the base form manipulator html2python() code. We need to first look for any unicode characters in the byte stream and convert to a real unicode character before performing the UTF8 ? encoding for the DB back end. If the string is already UTF8 ? encoded, do nothing. There is also an issue with UTF8 ? encoding on e-mails including their subjects which cause spam filters to filter the e-mails sent from the server. this is due to the default encoding being set to UTF8 ? to get other parts of the system working. In a newer version of django the e-mail encoding can be set seperatly. Resolution Added a core utility function safe_utf8_encode and used it for the forms. Also copied and modified the django email code to use new settings DEFAULT_EMAIL_CHARSET and EMAIL_SUBJECT_CHARSET. The subject setting is a hard override while the default emaile charset will fail over to us-ascii then utf8. Both are now set to us-ascii. ~~1.2 Bad Summary Formatting~~ Severity Medium Status Completed 11/1/06 Owner Doug Napoleone Description The summary should preserve whitespace but also wrap. There is a django filter which almost does this. Need to create our own and use that instead of the hard <PRE> tag and e-mail/url filter. Resolution Added a hack filter to replace newlines with '<br>' and any white space after the new line with ' 's. This will preserve newlines and line indentation in summaries while allowing them to wrap. To bad I didn't do this before editing 50 summaries. 1.3 Bad CSS for ReST ? fields Severity Medium Status In Progress Owner Doug Napoleone Description The PMWiki ? section specific <p> tag collides with the django field-set <p> tag in a bad way removing both the top and bottom spacing. Adding in a class for the rest fields in the tempaltes should fix this. 1.4 No view history on the stats pages Severity Low Status Open Owner Description The organizer stats pages don't use the view history information. The Proposal model needs to be extended with a new base query object which uses the User information. Maybe use the request middleware and thread local hack to make the base Proposal.objects have the 'seen' flag. the trick will be to have seen always be True when there is no logged in user, and not to try to update the anonymous user in the view history. This whould be solved before using this system for other apps. ~~1.5 Reviewers should be able to see some of the stats pages~~ Severity Request (Next Year) Status Completed (mid november?) Owner Douglas Napoleone Description The 'Reviewers' and 'Votes' organizer reports should be available to all PC members, but the system lacks the permission granuality for that. These reports (unlike the others) do not include Author information. Doug Napoleone 11/6/06: Reviewers have a hack permissions work around to see the votes stats. 1.6 Proposal form lacks instructions (requirement details) Severity Low (next year) Status Open Owner Description I've noticed that several proposals lack an outline, and have a descriptive blurb instead. As Mike Pirnat put it: "the submission form seemed a bit unclear to me about the level of detail desired, which field might be used for the published description, etc." Clear instructions (from the Call for Proposals, which might need revision) should be added to the form. ~~1.7 Add Opt-Out for reviewers with a conflict of interest~~ Severity Low (next year) Status Completed 11/1/06 Owner Douglas Napoleone Description currently a reviewer who has a conflict of interest must ask to have their proposal assignment removed by an admin. We should have a button/link to automaticly reassign the review slot. Resolution Added an opt-out link to the review section for those assigned who have yet to add their review. A minimum of 3 assigned reviewers is maintained. ~~1.8 Review totals misreported~~ Severity Medium Status Completed 11/2/06 Owner Douglas Napoleone Reporter David Goodger Description In proposals with multiple +0 votes only, the vote total is misreported. E.g. in http://us.pycon.org/apps07/proposals/11/, there are two +0 votes, but the total is reported as +1.0. Perhaps +0.2 or +0(2) instead? I don't know if totalling votes across vote types is even appropriate. For mixed votes perhaps total each type instead, something like "+n/-n(+0n/-0n)". Resolution The total score is as it was intended to be, but the feature should NOT have been enabled and is not part of the PyCon review process. Removed this number from the proposal detail view. ~~1.9 Changes to attachments should change read/unread status~~ Severity High Status Closed 11/2/06 Owner Douglas Napoleone Reporter David Goodger Description By accident, I noticed that the author of http://us.pycon.org/apps07/proposals/100/ had added an outline as an attachment, per my request in a comment. The addition of the attachment should change the status of the proposal to "unread", so that reviewers don't miss these changes. Perhaps such changes should trigger email notifications like new comments do. Resolution Could not reproduce the problem. This was most likely due to a restart of the django apps while the file was being attached to the proposal mentioned. Django transactions are enabled, but it is possable that the update to the proposal timestamp was to occur dirring a seperate transaction. 1.10 Have a ReST ? practice 'editor' Severity Request (Next Year) Status Open Owner Description Some submitters were having issues learning ReST ? with the deadline looming hours away. Having a practice ReST ? editor which does not require a login account would help solve this along with better instructions on what is expected in the proposal (request above). ~~1.11 The "My Vote" Column Seems Broken~~ Severity Medium Status Not a bug 11/05/06 Owner Doug Napoleone Description As a talk reviewer, the "my vote" column acts strange. For those talks on whom I'm -not- an assigned reviewer, it shows a vote of -1 or -0 or +1. Some of those I did indeed vote on but not on most and it shows a value for all such talks. For those I am a reviewer on, it seems to work better but I'm not yet sure it is correct. -Jeff Rush Resolution There is no column 'My Vote' on the table which lists talks you are not assigned to. Once you vote on a talk, it becomes assigned to you as one you are voting on and is moved up into the other table. ~~1.12 Reassigned proposals should generate email notification~~ Severity Medium Status Completed 11/07/06 Owner Doug Napoleone Reporter David Goodger Description A proposal can be unassigned via the "opt-out" button if the originally assigned reviewer cannot do the review. The proposal is reassigned randomly to another reviewer. The reassignment should generate email notification for the new reviewer. Otherwise, it's easy for the new reviewer to miss the proposal. Resolution Implemented the missing feature. 1.13 Admin improperly updates the timestamp on proposal reviews Severity Medium (next year as propsal process is done). Status Open Owner Reporter Doug Napoleone Description Sometimes (and only sometimes), when you modify a propsal in the django admin, the reviews which are edit_inline will get re-saved as if they were edited (improperly) and all assigned the current update time. ~~1.14 Bad HTML in accepted talks and proposal search listing~~ Severity High Status Completed 1/1/07 Owner Doug Napoleone Reporter Jeff Rush Description There is bad HTML being generated in the accepted talks and proposal listing pages. They still render OK in firefox and IE6 ?, but Safari, IE7 ? and Opera each have different issues. Opera is the worst effected as it is rendering exactly as the html says it should be (go figure). 1.15 Django pages are not XHTML compliant Severity Medium Status In Progress Owner Doug Napoleone Reporter Jeff Rush Description All the django pages are not XHTML compliant. This is different from the 1.14 bug as fixing that does not mean the pages are compliant, just that they render properly. Doug Napoleone 1/1/07: Most django pages are now compliant. Some proposal pages and th schedule app are not. Some issues with the schedule app can be fixed (id's and classes on divs in the <td> cells instead of on them); but some cannot (the dojo specific DOM extensions). 2. Talk Schedule 3. Registration 4. Web site -- general ~~4.1 Page titles too long~~ Severity Medium Status Completed 11/16/06 Owner Jeff Rush Reporter David Goodger Description Web pages are all prefixed by "PyCon - A Conference of the Python Community \| ". Wiki pages have "TX2007" also. This forces the important, unique parts of page titles to the end, where they're hard to find. Opened in tabs, multiple PyCon pages are indistinguishable from each other. Solution I recommend moving the boilerplate text to a suffix. Resolution Doug Napoleone 11/1/06: Removed the boilerplate from the proposal detail pages entirely to help facilitate the review process. Jeff Rush 11/16/06: Changes boilerplate per David's solution. ~~4.2 Site hard to navigate in lynx and on low res monitors~~ Severity Medium Status Completed 11/06/07 Owner Doug Napoleone Description Aahz has to page through the sidebar links to get to the meat of the page for reviewing proposals. Others have complained about having to scroll or having the contents squished on low resolution monitors. Solution For the wiki pages, the 'Printable View' is passable. For the django apps, a toggle option can be added for a minimal view. The state flag can be stored on the session cookie. The base template can check for the flag (via a context processor) and switch between the pmwiki base and a simple one. Doug Napoleone 11/6/06: There is now a 'Minimal/Maximal' switch on all Django apps to remove the side banners. This is done in a sub-optimal way, but it seems to work. The best solution would be to have proper django block markup in the PHP code embedded in comments. Resolution The Minimal/Maximal fix is good enough, and Printable view works good enough for the wiki pages. ~~4.3 Site Options bug when no session cookie present.~~ Severity Medium Status Completed 1/1/07 Owner Doug Napoleone Description The 'options' framework (currently only the minimal/maximal view sqitch is implemented) has a bug. If no session cookie exists, we crash. this is only currently hit by web crawlers. Need to fix and add 'nofollow' to a large number of our links. -> File "/var/hostings/05pcon0912/us.pycon.org/apps07/pycon/views.py", line 33, in set_option if (request.method == 'GET' and request.META['HTTP_REFERER']): KeyError: 'HTTP_REFERER' ~~4.4 Bad Headers on Django pages~~ Severity Medium Status Completed 1/1/07 Owner Doug Napoleone Reporter Doug Napoleone Description The html headers give an encoding type of 'iso-8859-1' (from the PHP base template) but we have django set to render 'utf-8' encoded pages. This conflict is the root cause of some of the Unicode bugs origionally reported under bug 1.1. Some browser/os combinations would go with the meta encoding it was told to use instead of the encoding they discovered when rendering the form (as they should have. 5. User Account 5.1 Reset-Password 'logout' bug Severity Medium Status Open Owner Description The on-success view for resetting the password improperly sets the 'user' variable in the view context. It is set to the first user found with that e-mail address. This results in the page header giving a bogus "logout 'username'" exposing the username. 5.2 Account Activation not fully implemented Severity Low Status Open Owner Description If an account is not active and has an activation code, then the login validator should include a link to an activation form for the user to imput the activation code. There should be a link on that form to re-send the activation code. Change link based activation with GET form activation. Also add auto-redirect on the activation view to hide the code from javascript injection (which is why we currently use the link hack). ~~5.3 User Account __str__ slowing down admin~~ Severity High Status Completed 11/28/06 Owner Doug Napoleone Description The base __str__ for User objects has been edtended to use the UserProfile ? extension. This means an extra query every time a user is stringified. This makes for easy template code and allows the admin to use the persons name instead of the username, but it makes for a slow admin. Adding a memcache to the __str__ override should greatly reduce the overhead. This will not fix all the django admin slowness. Django needs to implement form field caching to speed up the admin. Resolution Added cache of the username override. This reduced the average admin proposal edit page load time from 12sec to 2.5sec, with a max from 16seconds, down to 4 seconds; back within reasonable ranges. The cache is currently set for 1 hour, so the first loading will still take about 4 seconds, per CGI at most once per hout; but that is also reasonable.
	Content Last Modified: August 14, 2007, at 12:07 AM Edit Page Printable View Page History