ticket,summary,type,release,owner,status,created,modified,_description,_reporter
5573,"Cutting  tag (former ""Is it possible to manually split ""header"" and ""body"" of blogpost?"")",enhancement,0.11,osimons,new,2009-07-28T14:50:25+02:00,2020-05-08T04:28:13+02:00,"Hi!

I published some images into my blog and them took a lot of pages, I'd like to make only one visible in list of posts and others - be available under cutline. Is it possible to accomplish this with FullBlogPlugin?

Thank you.",prokher@…
3069,TracLinks cut when specifying max_size in BlogList,enhancement,0.11,osimons,new,2008-05-23T19:51:50+02:00,2020-05-08T04:34:54+02:00,"When using the `BlogList` macro and specifying `max_size`, it simply trims the raw wiki text, which will sometimes cut TracLinks in half.",whitelynx
3558,BlogList macro: Allow the base heading level to be specified,enhancement,0.11,osimons,new,2008-08-15T10:07:33+02:00,2017-06-26T20:31:04+02:00,"When using the !BlogList macro with the full or float formats, blog posts are rendered with their heading inside an h1 tag. Structurally, this infers a top level heading and associated section. This breaks the structure of a document when the !BlogList macro is used to render posts beneath the top level. For example, on the front page of http://www.nvda-project.org/, I use heading level 1 for the page title and heading level 2 for the main section headings. ""News"" is a main section heading (level 2), so the blog post titles should be at heading level 3.",James Teh
3810,Support editing comments to blog posts,enhancement,0.11,osimons,new,2008-09-26T16:26:55+02:00,2020-05-01T06:51:13+02:00,"!TracFullBlogPlugin 0.1 supports editing and deleting blog posts, but only deleting (not editing) comments (according to the author, see http://groups.google.com/group/trac-users/browse_frm/thread/c8948e0189940cf9?hl=en).  I would like to see an ""Edit comment"" option adjacent to the ""Delete comment"" option which is displayed in the upper-right corner of the comment box.  It could work very much like the ""Edit post"" button does.",Steve Strobel
4571,Please add a Reply button to blog and comments,enhancement,0.11,osimons,new,2009-02-04T16:24:29+01:00,2020-05-08T04:27:10+02:00,Please add a Reply button to blog and comments with the same functionality as provided by the Reply button for ticket comments.,Roy Marples
4779,Clone post or template support,enhancement,0.11,osimons,new,2009-03-12T22:26:31+01:00,2020-05-08T04:07:03+02:00,"I'm using FullBlog plugin and it works well. But I have few very similar type of posts and it would be very helpfull, if there would be support for blog post templates.

Probably ""template support"" can be done very simple - by adding ""Clone"" button to every post for all users who can create new posts or make one more clone permission type. User can tag all templates for easy finding and broswing, for example, Templates or any other tag.

Anyway sometimes Clone button can make life easier even if you need to clone just once.",Ilmars Poikans
5454,Browse by more than one category,enhancement,0.11,osimons,new,2009-07-01T11:33:51+02:00,2020-05-01T06:51:13+02:00,"This plugin is very nice, but I need a little bit more:
It's good to have request such as:
{{{
/blog/category/News+Updates
}}}
To select items with both News and Updates category set[[BR]]
And to have the same in !BlogList macro, such as
{{{
[[BlogList(category=News+Updates)]]
}}}

Or, more common, to have request
{{{
/blog/view?categories=News+Updates&author=Paul,Alex
}}}
values, separated by + are AND combined, separed by comma are OR combined. And the same in !Bloglist. Is it good and possible?",Paul
6022,[Patch] Unnecessary whitespace from metainfo ul list should be removed,enhancement,0.11,osimons,new,2009-10-23T02:26:03+02:00,2009-11-06T06:33:19+01:00,Unnecessary whitespace from ''metainfo'' `ul` list should be removed as this whitespace is displayed if list is styled inline.,Mitar
6023,[Patch] For better styling posts should be marked with list or standalone class,enhancement,0.11,Ryan J Ollos,new,2009-10-23T02:33:32+02:00,2020-05-09T18:40:10+02:00,"For better styling posts should be marked with list or standalone class if they are rendered in a list context or in a standalone context, respectively.",Mitar
6653,move comment warnings where the user can see them,enhancement,0.11,Ryan J Ollos,new,2010-02-17T10:08:46+01:00,2020-05-09T18:40:41+02:00,"Currently, if a manipulator produces warning when the user submits a comment, the warning is shown on top of the page (as usual in Trac) and the page scrolls down to page preview. There's a ""(Warnings"") link added to the preview that points back to the warning box.

Unfortunately, this is quite hard to spot. This patch uses !JavaScript to move warnings box right on top of the offending comment's preview, so that the user can immediately see both ''that'' something is wrong and ''what'' it is.

It degrades gracefully in absence of !JavaScript, falling back to previous version.",Vaclav Slavik
6699,Trackback support,enhancement,0.11,osimons,new,2010-02-21T15:31:03+01:00,2010-02-23T13:24:34+01:00,It would be great if FullBlogPlugin would parse links in posts and use [http://en.wikipedia.org/wiki/Trackback Trackback] to notify linked blog of a link.,Mitar
7029,automatic blog post slug (aka shortname) creation,enhancement,0.11,lkraav,new,2010-04-26T17:04:30+02:00,2020-05-08T04:30:20+02:00,"this ticket tracks the development of [http://bitbucket.org/lkraav/automatic-slug-patch automatic-slug-patch] for FullBlogPlugin by lkraav. questions, comments, discussion here.",lkraav
7593,Allow comment to be added when version or post are deleted,enhancement,0.11,osimons,new,2010-08-31T07:13:01+02:00,2011-08-19T06:15:47+02:00,"This may seem like a strange request since the comment probably won't be stored in the database as the version or post is being deleted, however the comment would be useful for passing to the FullBlogNotificationPlugin so that the email that is sent on deletion can contain an explanation for the deletion.",Ryan J Ollos
9142,Show comments directly under blog entry in main view,enhancement,0.12,osimons,new,2011-08-31T15:42:07+02:00,2011-08-31T15:42:07+02:00,"In the main blog view, the small comment link/number is easy to overlook. Would be great if there were an option to have comments shown directly underneath each entry in the main blog view (so: blog post, comments, blog post, comments, blog post, ...). Probably wise to also add an option to restrict the number of comments shown in this way (i.e. on the last 3-4 comments).",ak@…
9237,"if category is not set, use default category defined in trac.ini",enhancement,0.12,osimons,new,2011-10-05T11:28:35+02:00,2011-12-01T08:29:17+01:00,"Usually, users forget to set a category when they post a new blog entry. This is bad since then it's not available or caught via the category survey.

This plugin could handle that by automatically setting a default category if none is set on posting. And I want to specify the default category in trac.ini.",falkb
11156,Filter 'about' post from BlogList macro output,enhancement,1.0,osimons,new,2013-06-09T19:10:35+02:00,2020-05-01T06:51:13+02:00,"The ''about'' blog post is special, and probably will often be set in the initial setup phase of a blog.

But if not, it is shown among all other posts, what is undesired IMHO. See current view in WikiStart. I do even expect it to descend according to its creation time as more blog posts appear. It should be hidden.",Steffen Hoffmann
11901,Add XML-RPC,enhancement,1.0,osimons,new,2014-08-04T16:25:20+02:00,2020-05-01T06:51:13+02:00,"Please find attached a plugin file that extends XmlRpcPlugin with 'get' methods to retrieve blog posts (in case it can be useful for some other Trac users).
  

It is based on the 'wiki' XML-RPC API and use the same method names (I did not find a 'standard' API for blog posts...).

I don't know how where to add that file in the FullBlogPlugin so that it can extend XmlRpcPlugin, so I just use it as a ""standalone plugin file"".

",sdegrande
12511,Effective-date attributes for blog posts,enhancement,,osimons,new,2015-09-09T22:04:58+02:00,2015-09-09T22:04:58+02:00,"We are using Trac for our Wiki and ticketing system, and we are evaluating the FullBlogPlugin as a tool that we can use to log significant events during the lifetime of a project.  As it exists now, it nearly covers all of our requirements, but one thing that would be useful is the addition of effective-date attributes for a blog post.  The date that a post is made is rarely going to be the effective date of a significant event in our case.  Usually a post is made days after a significant event occurs and there has been time to analyze its cause and effects.  For example, an anomaly on a spacecraft occurs and causes a 3-day data outage.  There could be some time between the event actually occurring and the time that the blog post would be made about it.  I had envisioned attributes such as eff_start_date and eff_end_date providing the ability to assign an effective date range for a blog post. Having effective-date attributes for the post would allow posts to be ordered and searched by effective date.  I realize not everyone has such a need, but i can see it being useful to many people.  Perhaps if the fields were not set they would just be ignored.",anonymous
13971,Better 'about' page handling,enhancement,,osimons,new,2021-03-06T18:10:43+01:00,2021-04-12T20:31:18+02:00,"Coming from some ancient version of this plugin, I don't have an 'about' blog post, and don't really want to add one since it will show up as the latest post.
The plugin used to put the blog_infotext where it now wants to put the 'about' post, and has moved the blog_infotext to the _bottom_ of the sidebar, which in my case, is way, way down the page.

I can see several possible approaches here, but I'd like to implement something that would be acceptable upstream.

Suggestion 1:
In the absence of an 'about' blog post, only show the ""This blog does not yet have an 'About' post."" message to those with BLOG_CREATE permissions, so it isn't an eye-sore when not created.
I think this change should be made independent of the later suggestions.

Suggestion 2a:
In the absence of an 'about' blog post, put the blog_infotext at the top of the sidebar.

Suggestion 2b:
Allow the use of an 'AboutBlog' wiki page instead of an 'about' blog post.  This avoids the 'about' page showing up in a random place in the blog history.

Suggestion 2c:
Replace the 'about' blog entry with blog_about, with a suggestion for those who want to use an 'about' blog entry to use the Include macro in the blog_about content to reference it.  (This approach would also allow referencing an 'AboutBlog' (or other) wiki page, so has more flexibility... but more implementation work, I expect.


Comments, discussion, etc. welcome.



",Eli Carter
8435,make blog gateway page more configurable,enhancement,0.11,osimons,new,2011-01-21T19:37:30+01:00,2011-01-22T09:22:21+01:00,"It seems that the only options for configuring the `/blog` page are the number of postings to display, the template for naming new posts, and some text for the sidebar. I would prefer to have more control, for example, the level of control from the !BlogList macro, //i.e.// the ability to set the format, the max size, etc.",shabbychef
9860,author page should have (optional) limited number of posts,enhancement,0.11,osimons,new,2012-02-28T02:16:48+01:00,2020-05-08T04:09:09+02:00,"Some of our blog authors have more than 200 blog posts. When visiting the 
{{{local.trac.install/trac/blog/author/the_users_name}}} author page, //all// of the hundreds of blog posts appear. This is an enormous web page, is slow to render, and is probably unnecessary for most users. As a result, the 'author' pages are never used. It would be nice if there were an optional configurable 'max posts' parameter that applied to the {{{blog/author/the_users_name}}} type pages.  ",shabbychef
14219,Macro BlogList() and macro TicketQuery(),defect,1.4,osimons,new,2023-04-06T14:14:46+02:00,2023-08-16T07:39:56+02:00,"If apply both macros in same wiki page then macro TicketQuery() not work correctly, progessbar not visible

Code of wiki Page

{{{
[[BlogList(recent=5, category=news)]]

[[TicketQuery(component^=TC., format=progress)]]
}}}

result
[[Image(2023-04-06 15_13_53-test – TeamСenter — Firefox Nightly.png, 100%​)]]

Result without BlogList macro
[[Image(""2023-04-06 15_14_35-test – TeamСenter — Firefox Nightly.png"", 100%)]]

If reorder all work fine
[[Image(""2023-04-06 15_19_03-test – TeamСenter — Firefox Nightly.png"",100%)]]",Alexey