{5} Assigned, Active Tickets by Owner (Full Description) (12 matches)

Currently there's no support for the Atom API in Typo. Once it gets implemented we can get Lifeblog working with Typo - currently only Typepad gets the privilege to use Lifeblog for mobloging. Here's the documentation for Lifeblog's Posting Protocol Spec - http://europe.nokia.com/BaseProject/Sites/lifeblog_54603/CDA/Categories/NokiaLifeblogTrilobiteEN/Blog/_Content/_Static_Files/lifeblog_posting_protocol_specification_1.0.pdf

Thanks,

Jose Marinez

This patch updates Scribbish to use the submit_to_remote helper on the comments form in favour of manually constructing the AJAX call.

<%= submit_to_remote('preview', 'Preview!',
                     :update   => 'preview',
                     :complete => "Element.show('preview')",
                     :url      => { :action => 'comment_preview' }) %>

This patch also adds some js to the submit button to make comment submission less error-prone: the submit button is disabled after it's clicked, and the comment-preview area is hidden so that it doesn't show after a new comment is recieved:

<%= submit_tag 'Submit', :onclick => "this.disabled=true; Element.hide('preview');" %>

I tried out Typo and there is a lot to like however it seems very limiting that there is no permission/role model for additional users. For example I'd like to add authors, editors and subscribers. Correct me if I am wrong, but the only role is admin by default right?

For both hosted appliances and content-separation for standalone blogs we need multi-blog support which is still considered one of the remaining killer-features of the competition.

I recently upgraded the development version of typo, and the page caching no longer works. Considering this is *the* reason I use typo, its a pretty big bug, IMHO. Quick check in the source code shows that it was completly removed.

Overall its a huge performance hit. In a properly configured lighttpd-fcgi environment performance goes from 1000req/sec to 80req/sec, and for users in a CGI shared hosting environment they will max out somewhere around 10-15req/sec maximum.

Although moving to action caching DOES enable more features, the option of page caching would be really nice for people who can live without those features.

Is removal of this feature a sign that people should start using MovableType or will the option to use page caching be re-added in the near future?

I wrote an article that used a quoted phrase in the title (The lay of the land at "milestone05"). When importing the feed into Firefox's RSS reader one of my readers got the following message:

http://rewrite.rickbradley.com/xml/atom10/feed.xml

XML Parsing Error: not well-formed
Location: http://rewrite.rickbradley.com/xml/atom10/feed.xml
Line Number 22, Column 42:    <link title="The lay of the land at
"milestone05"" length="47548" rel="enclosure" type="image/png"
href="http://rewrite.rickbradley.com/files/screen-milestone-051.png"/>

It appears that the feed generator is not properly escaping " characters inside the "-ed title attribute of the link element in the atom10 feed.

I did an svn update, found the code which generates it, and found the test code for atom10, but now I'm not going to have a chance today to finish the test and patch, so I'm filing a ticket. I've changed the title to something without "s for the time being, but the problem should be easily reproducible.