iThink Software: Issueshttp://ithinksw.org/http://ithinksw.org/favicon.ico?15549912252011-07-29T19:10:31ZiThink Software
Redmine Philo - Bug #176 (New): Update waldo token generation to use django's crypto utils.http://ithinksw.org/issues/1762011-07-29T19:10:31ZStephen Burrowsstephen.r.burrows@gmail.com
<p>Django's token generation has been updated to be more secure - and in the development version, generic secure signing has been added to django. [1] Waldo should be updated to use these facilities.</p>
<p>[1] <a class="external" href="https://docs.djangoproject.com/en/dev/topics/signing/">https://docs.djangoproject.com/en/dev/topics/signing/</a></p> Philo - Feature #175 (New): Better attribute filteringhttp://ithinksw.org/issues/1752011-07-20T01:45:34ZStephen Burrowsstephen.r.burrows@gmail.com
<p>Right now, it's really painful to filter for attributes with a given value - for example, if one wants to get all BlogEntries that have a "published" attribute. It would be great to have an API to make this kind of filter - or better yet, enable filtering via attributes, a la the django-taggit TaggableManager. This would allow lookups like BlogEntry.objects.filter(attributes__key="hi", attributes__value="lo") (or alternatively, BlogEntry.objects.filter_attributes("hi", "low", "exact"), which would be simpler but less elegant.)</p> Philo - Feature #174 (Resolved): Release noteshttp://ithinksw.org/issues/1742011-07-19T03:36:25ZStephen Burrowsstephen.r.burrows@gmail.com
<p>It would be a good idea to have release notes detailing the changes from 0.9 to (1.0?) and a policy for future release notes being written incrementally with each change.</p> Philo - Bug #173 (Resolved): Waldo email changes assume the email is stored on the user modelhttp://ithinksw.org/issues/1732011-07-14T21:06:05ZStephen Burrowsstephen.r.burrows@gmail.com
<p>This is a problem if e.g. it is in fact stored on the UserProfile. This should be solved by having a method on the form which resets the email to its starting position.</p> Philo - Bug #172 (Resolved): Attribute inlines not displayed for BlogEntry and NewsletterArticle ...http://ithinksw.org/issues/1722011-07-13T18:33:00ZStephen Burrowsstephen.r.burrows@gmail.com
<p>Since Titled and TitledAdmin were removed, BlogEntryAdmin and NewsletterArticleAdmin have inherited directly from AddTagAdmin. Since this is (for no apparent reason) not a subclass of EntityAdmin, none of the EntityAdmin functionality (specifically the Attribute inlines) is available on those admins.</p> Philo - Feature #171 (New): Native comment support for penfieldhttp://ithinksw.org/issues/1712011-07-12T16:16:16ZStephen Burrowsstephen.r.burrows@gmail.com
<p>Blogs and newsletters often feature commenting; however, penfield can't handle that without some hacking. It might be worthwhile to add handling for that case, perhaps via an abstract CommentView in winer.</p> Philo - Feature #170 (New): Use PHILO_MIDDLEWARE in place of signals.http://ithinksw.org/issues/1702011-07-11T18:23:11ZStephen Burrowsstephen.r.burrows@gmail.com
<p>We currently provide a view_about_to_render signal, which is good. It lets developers take action when the page renders, such as inserting arbitrary values into the extra_context of the view. However, things like form handling are impossible, because a) one cannot guarantee that receivers will be processed in any particular order, and b) one cannot replace the returned response with e.g. an HttpResponseRedirect without overriding the view's actually_render_to_response method; this is extremely hackish.</p>
<p>I think it would be useful to use a middleware-like arrangement instead of signals.</p> Philo - Bug #169 (New): Future-compatible ADMIN_MEDIA_PREFIX usehttp://ithinksw.org/issues/1692011-07-04T23:34:57ZStephen Burrowsstephen.r.burrows@gmail.com
<p>ADMIN_MEDIA_PREFIX is deprecated in 1.4... at some point it may not be included in default settings files. Philo relies on this setting in at least one place. It may be worth considering some sort of forwards-compatibility.</p> Philo - Feature #168 (Resolved): Contentlets should not assume template content or safe content.http://ithinksw.org/issues/1682011-06-24T20:46:57ZStephen Burrowsstephen.r.burrows@gmail.com
<p>Currently, contentlets mark their content as safe and even compile it as a template. There is no way for template authors to prevent this. It's legacy code from before the include_string tag; now that we have that, we can and should remove the automatic compilation and the mark_safe call.</p> Philo - Feature #167 (New): Fewer page loads for Attribute inlineshttp://ithinksw.org/issues/1672011-06-22T17:00:21ZStephen Burrowsstephen.r.burrows@gmail.com
<p>Right now, to manually set an attribute, one has to save the page 2-3 times. This is really pretty unacceptable and should be corrected.</p> Philo - Feature #166 (New): Filtered select for Attribute/ManyToMany inlineshttp://ithinksw.org/issues/1662011-06-22T16:57:39ZStephen Burrowsstephen.r.burrows@gmail.com
<p>Right now, Attribute/ManyToMany inlines use a multiple select widget. This is cumbersome and should be replaced with a filtered many-to-many (at least by default.)</p> Philo - Feature #165 (New): Raw id field for Attribute/ForeignKeyValue inlines.http://ithinksw.org/issues/1652011-06-22T16:55:21ZStephen Burrowsstephen.r.burrows@gmail.com
<p>Right now, the attribute/foreignkeyvalue inlines are pretty cumbersome - they generate giant select menus which can't easily be used, and which cause a large number of additional queries on page load. Should be replaced with a RawIdField/popup system.</p> Philo - Feature #164 (Closed): Optimization workhttp://ithinksw.org/issues/1642011-06-22T13:51:54ZStephen Burrowsstephen.r.burrows@gmail.com
<p>Working on optimizing philo - see also: <a class="external" href="http://www.codinghorror.com/blog/2011/06/performance-is-a-feature.html">http://www.codinghorror.com/blog/2011/06/performance-is-a-feature.html</a></p>
<p>Will use this issue to track progress.</p> Philo - Bug #162 (Closed): README should explicitly mention bug tracker.http://ithinksw.org/issues/1622011-06-21T19:06:17ZStephen Burrowsstephen.r.burrows@gmail.com
<p>I think that people would have an easier time finding the bug tracker if we had an explicit link in the README file to <a class="external" href="http://ithinksw.org/projects/philo/issues">http://ithinksw.org/projects/philo/issues</a>.</p> Philo - Bug #160 (New): Shipherd shouldn't require 'request' in the context for {% recursenavigat...http://ithinksw.org/issues/1602011-06-15T15:50:11ZStephen Burrowsstephen.r.burrows@gmail.com
<p>Right now, if 'request' isn't in the context (i.e. if the request context processor isn't installed) shipherd's {% recursenavigation <span>} templatetag will just not work - it'll always render as an empty string. The reasoning behind this was that there's no way to tell if a navigation item is active if the request is not provided. Really, though, {</span> recursenavigation %} could still work without a request, just always returning False for "active". This behavior would make more sense, I think.</p>