|
From: will kahn-g. <wi...@bl...> - 2010-01-19 23:23:52
|
I've been thinking about this very issue for a while. I think in this case, it's unlikely that the data can't be made public (e.g. passwords should never show up on the site), so I'd have your plugin return a title/body dict and either request an error template or use the story template. That way if the user checks his/her blog, he/she will see the error and can fix the problem. My guess is that it's more likely the user will check his/her blog after posting than would check the pyblosxom log. It's probably a few lines of code to build an error entry or to log something to the log... You could make it configurable. That's off the top of my head. I'd be interested in hearing other peoples' thoughts. It'd probably be something useful for the "writing a plugin" part of the manual. /will On 01/19/2010 06:11 PM, chombee wrote: > Is there a 'right thing' for this entryparser plugin to do if it catches > an exception because a user's YAML entry didn't parse? I guess you > should use pyblosxom's logger instance to log an error, but what should > the parse method return to pyblosxom given that the entry could not be > parsed? > > On Tue, Jan 05, 2010 at 09:01:31PM +0000, chombee wrote: >> This is a very simple plugin to make your PyBlosxom blog 'tumblelog' >> capable. It's an entry parser plugin that lets you write entries in >> YAML, and additionally lets those entries specify which story template >> they should be rendered with, so that you can have many different story >> templates in your flavour and entries of different types can have >> different YAML structures and different templates, so they ultimately >> get rendered differently by PyBlosxom even though they appear together >> on the same page. I keep trying to come up with a good way of explaining >> but not really succeeding, it's very simple really. It's explained >> better on the web page: >> >> http://github.com/seanh/PyBlosxom-tumblelog >> >> This is a very simple tumblelog plugin. In the future I'll probably want >> to add markdown support to it, and maybe have it figure out the template >> to use for a post depending on the post's category rather than having >> each post specify its template. >> >> Thanks to Will for tips on how to implement it. >> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> pyblosxom-users mailing list >> pyb...@li... >> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users > > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for Conference > attendees to learn about information security's most important issues through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > pyblosxom-users mailing list > pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-users > |