I'm starting to wonder if a using [[neighborhood_feeds]] is right. We already took extra care to not change the author when updating (because an update was necessary to republish the feed item after making a project public). Maybe we need a different macro, that does precisely what we need for the Motorola neighborhood page
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
summary: Make sure that neighborhood feeds macro updates when news items are updated after posting --> Create neighborhood news macro
Description has changed:
Diff:
--- old +++ new @@ -1,1 +1,1 @@-Apparently the feeds need to update when blog posts update.+Pull directly from the blog artifacts. Make sure permissions are checked (e.g. project could be private, tool could be non-readable)
size: --> 4
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Change is on allura js/2372. To test, create some new blog entries then add [[neighborhood_blog_posts]] to a neighborhood wiki (should not work anywhere else). The blog posts should show up on the wiki page. Make sure permissions are respected for unpublished posts and posts in private projects.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I know this is assigned to Wayne, but I took a quick look since I wanted to make sure it'd work well for Motorola. A few things:
there should be a test
neighborhood_id defaults to None for existing blog posts, so the macro won't find any prior posts, right? Is there a way to make it work for prior?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2011-07-20
Originally by: algorithms
Code looks good. The blog entries themselves need to have their Markdown eval'd before it is presented out to the user. See patch. Screenshot: http://i.imgur.com/Pda9v.png
I added a summary option, applied Wayne's patch, made a test, and created a script to add the neighborhood_id to existing posts. To test the script, load your sandbox on dev, create some blog entries, check out the branch, run the script, and make sure posts you created before checking out the branch show up in the macro. Run the script like this: allurapaste script /var/local/config/production.ini /var/local/allura/scripts/migrations/015-add-neighborhood_id-to-blog-posts.py
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm starting to wonder if a using
[[neighborhood_feeds]]
is right. We already took extra care to not change the author when updating (because an update was necessary to republish the feed item after making a project public). Maybe we need a different macro, that does precisely what we need for the Motorola neighborhood pageDiff:
Change is on allura js/2372. To test, create some new blog entries then add [[neighborhood_blog_posts]] to a neighborhood wiki (should not work anywhere else). The blog posts should show up on the wiki page. Make sure permissions are respected for unpublished posts and posts in private projects.
I know this is assigned to Wayne, but I took a quick look since I wanted to make sure it'd work well for Motorola. A few things:
Originally by: algorithms
Code looks good. The blog entries themselves need to have their Markdown eval'd before it is presented out to the user. See patch. Screenshot: http://i.imgur.com/Pda9v.png
assigned_to: Wayne Witzel III --> Jenny Steele
status: code-review --> in-progress
Originally by: algorithms
This might be another ticket, but I could see having an option of summary=True being nice. So it doesn't dump the full content of the blog post.
I added a summary option, applied Wayne's patch, made a test, and created a script to add the neighborhood_id to existing posts. To test the script, load your sandbox on dev, create some blog entries, check out the branch, run the script, and make sure posts you created before checking out the branch show up in the macro. Run the script like this: allurapaste script /var/local/config/production.ini /var/local/allura/scripts/migrations/015-add-neighborhood_id-to-blog-posts.py