Archive of BlogPluginDev Discussions

Please add new discussions to BlogPluginDev

This is the first beta release of the BlogPlugin. I am aware that there's documentation missing on the BlogUp TWikiApplication that comes with it. Here's the related entry in the bugs database: Bugs:Item840.

-- MichaelDaum - 24 Jan 2006

Thanks Micha for sharing this Plugin. This one is very important for TWikiAdvocacy

BTW, how about measuring and documenting the PluginBenchmarks numbers?

-- PeterThoeny - 08 Feb 2006

UTF-8

Does it support utf-8? I creat a blogpage with chinese content. I input the chinese char in the BlogEntryForm, It works fine when save the topic first time. But If you edit it again, some chinese char will display some thing like "#nnnn;" It works fine, when the same char display and edit in the WikiPage. I install the twiki(Dakar)on the redhat Linux AS4. Please check attached file for more information.

-- ZhengLingxiang - 05 Apr 2006

ZhengLingxiang, the configure.html that you attached shows one warning (CGI::Session not installed) You need to install that. (Maybe the configure script should be stricter as this is not a warning but an installation error. Hm.)

Most probably the issue that you reported is not related to the BlogPlugin. Please try to reproduce the error by simplifying your environment. Create a simple TWikiForm and attach it to a topic (see the docs on how to do that). Then try to edit the form adding utf-8 content. If the error does not show up enable plugins one by one and try again to edit utf-8 content in TWikiForms in each step.

-- MichaelDaum - 05 Apr 2006

I test a simple topic with TwikiForm and disabled all the plugins. The error still exist. When edit a page with chinese text in the form, some chinese chars may become "#nnnn;".

-- ZhengLingxiang - 05 Apr 2006

Ok, so that's an error in the current TWiki release (and not releated to the BlogPlugin). Next is to file a bug report. Moved to Bugs:Item2032.

-- MichaelDaum - 05 Apr 2006

SKIP in RenderBlogEntriesInCategory seems not work properly.

The parameters SKIP in RenderBlogEntriesInCategory seems not work properly. The hyperlink "next page" in a blog category page can not go to the next page. I check the code in RenderBlogEntriesInCategory and fixed it by changed the following line:

~~~ %IFDEFINED{"%SKIP%" then="SKIP=\"%SKIP%\"" glue="off"}% 
~~~ %IFDEFINED{"%LIMIT%" then="LIMIT=\"%LIMIT%\"" glue="off"}% 

to
~~~ %IFDEFINED{"%SKIP%" then="SKIP=\"%URLPARAM{"skip"}%\"" glue="off"}%
~~~ %IFDEFINED{"%LIMIT%" then="LIMIT=\"%URLPARAM{"limit"}%\"" glue="off"}% 

-- ZhengLingxiang - 29 Apr 2006

Thanks, ZhengLingxiang, for spotting this problem.

Hm your fix might have helped you for the moment, but the same issue persists in other places too. The point is that the URLPARAM expression should have been in the originating SubjectCategory being constructed using the SubjectCategoryTemplate. This template has an URLPARAM parameter in there but it is expanded with the current url parameters when constructing a new SubjectCategory See the SKIN=" 0" in there (sidenote: uh, the LIMIT="..." is missing completely).

Ok, I fixed that differently by doing a thing I wanted to do for other reasons already before: I moved the render functions into dedicated VIEW_TEMPLATEs thereby reducing redundancy, using a cleaner model-view separation and fixing the URLPARAM issue you reported, as the SubjectCategoryTemplate only sets the VIEW_TEMPALTE variable etc. The implementation is hidden away in the view template and even ?raw=on will not show details (which I like).

Will package that soon.

-- MichaelDaum - 29 Apr 2006

Fixed in latest release.

-- MichaelDaum - 05 May 2006

Using BlogPlugin with PatternSkin

A couple of questions and suggestions. I have now split up the long list - some things are observations and do not apply to pattern skin directly.

• When using pattern skin, the login/logout links are not on the page. And without being logged in it is impossible to add entries. I've spent quite some time to discover that I should perhaps log in first.
  • Oh, IC. Let me clarify: the blog will look differently depending on your authorization. You may be an anonymous reader, a registered user or a registered user member of the BlogAuthorGroup. Only the latter will get to see the BlogAuthorTools in the sidebar. -- MD
  • In that case the default login/logout mechanism should be placed in the blog web left bar. -- AC
  • fixed in v0.95

• To have a more consistent button style, I would like to have the style twikiButton and twikiSubmit in buttons (for instance the "New Posting" button now has the classes blogSubmitButton blogEntryButton )
  • No. The rule is that the css namespace is divided up by tagging chunks of html prefixing a token that describes the unit it emitted it. In this case I use blog for all html generated by the BlogPlugin. twikiButton and twikiSubmit are reserved for html emitted by the core engine. If you want to customize html of a plugin a skin has to provide support for it. Skins have the last responsibility to decide on the css properties. They might want to style the "New Posting" button to look like ordinary twikiButtons or not. Note, however that the BlogPlugin comes with a USERSTYLE that already is added to the _BlogPlugin.WebPreferences trying to provide at least some more blog feeling using PatternSkin. -- MD
    • Generally, you are right. But we don't use the rule that strict: quite some topics that are distributed with TWiki have a twikiXxx css class. As I understand it, these can be considered as common ground classes. In this case, twikiButton and twikiSubmin are emitted by the core engine, but not on this page. But the skin should have defined a style for these classes. So yes, a skin can give support to plugin-emitted classes, and I have done that for TablePlugin classes. But buttons are so common you could as well make our lives simpler by using twikiButton class. --AC

• But with pattern skin I cannot edit BlogAbout. Perhaps because the topic actions are not displayed with pattern skin?
  • Right, that's a bug. I started to make use of VIEW_TEMPLATEs all over the place in the BlogPlugin some time ago, then twiki-4.0.3 came out with a revamped PatternSkin. Now the BlogPlugin must provide different VIEW_TEMPLATEs for both skins. Will fix that. -- MD
  • fixed in v0.95

• It is not clear how to delete an entry.
• It is also not possible to delete a category or author page.
  • Once the VIEW_TEMPLATEs are fixed you can use ordinary TWiki means. -- MD
  • fixed in v0.95

• The red dot does not appear red in pattern skin (in the h1 header) and also not in the left bar. An additional style is needed:

  h1 .redDot a:link,
  h1 .redDot a:visited,
  #patternLeftBarContents .redDot a:link,
  #patternLeftBarContents .redDot a:visited {
     color:#f00;
     font-size:110%;
  }
        

  • Thanks, will add this to the next release of the RedDotPlugin -- MD
    • Or should this be added to PatternSkin? --AC

• WebLeftBar inserts newlines. Better to put the includes on one line:

  %STARTINCLUDE%%DBCALL{"RenderSideBar"}%%STOPINCLUDE%

  • I tried to use the same call to RenderSideBar for both PatternSkin's WebLeftBar and NatSkin's WebSideBar. But now I see that there are more things that have to go into the WebLeftBar only as for example PatternSkin has no WebButtons (to tabs above the main area). So the links there have to be in the WebLeftBar. Same holds for the login stuff as noted above already -- MD
  • fixed in v0.95

Blog Rss Feed

Hi, blog developers and users, i wonder these two things:

• if Blog Rss Feed can use " $summary " to display part of contents in rss reader?
• if only one word allowed in $expand() ? so $expand(Progress) is right but $expand(Action Plan) is wrong?

Thanks very much !

-- ShashaLuan - 16 Aug 2006

e.g. when i subscribe WebRssTeaser, i will see the teaser contents from my rss reader. But is there a way to use variable $summary to limit characters.
I ask this because i create a new TopicType and form for myself in blog, so i want to read a summary content from my form. I revised the RenderRss.txt file, and add two line " ~~~    $expand(Progress) " " ~~~    $expand(Action Plan) " above the line " ~~~    $expand(Teaser) ". (" Progress " and " Action Plan " is fieldname in my form). I also write a new rss feed only for this TopicType. From rss reader i can get full content in Progress, but can not get content from "Action Plan"(Is this because there is a space between "Action" and "Plan" )

-- ShashaLuan - 16 Aug 2006

Hi Shasha, have a look at the DBCachePlugin syntax description. There's a variable called $trunc(string,length) that will truncate string to length bytes. So try something like $trunc($encode(html),200) to get a similar result as with $summary which is only available in TWiki's SEARCH but not in DBQUERY.

Wrt Action Plan, try ActionPlan. To find out the real field name append ?raw=debug to an url to get to see the pure topic data. Or try DBDUMP{"topic"} to see what is stored in the web db by the DBCachePlugin.

-- MichaelDaum - 16 Aug 2006

Thanks Michael , I revise the RenderRss topic and use " ~~~          $trunc($expand(ActionPlan),130)

" , it works well, but when i add a new line " ~~~         $trunc($expand( Progress),100)

" under it, the new line( Progress ) doesn't work. i cannot read the summary of " Progress " from rss reader. This is part of code in RenderRss:

~~~          $expand(TopicDescription)
~~~          $percntFIDEFINED$percnt
~~~          $trunc($expand(ActionPlan),130)<p />
~~~          $trunc($expand(Progress),100)<p />
~~~          $expand(Teaser)
~~~          %IFDEFINED{"%TEASEONLY%" then=" " else="<p />$expand(Text)"}%) 

i can use $trunc(...) only once in a topic ?

-- ShashaLuan - 16 Aug 2006

Yea, that's an error in the DBCachePlugin. Will try to fix it. For now, here is a workaround:

~~~          $trunc($expand(ActionPlan and '<p/>' and Progress),235)<p />

-- MichaelDaum - 21 Aug 2006

Using $trunc problem in 22 Aug 2006

Hi, Michael, when i using

~~~          $trunc($expand(ActionPlan and '<p />' and Progress), 235)<p />

i found another problem. Now i want to get summary from ActionPlan and Progress. For each of them i want to get 235 characters summary.

1. if ActionPlan has less than 235 characters, yes, it works well, and i can get both summary from ActionPlan and Progress. (seems also calculate spaces, so limitation 235 can only read useful characters less than 235)
2. if ActionPlan has more than 235 characters, i cannot get summary from Progress, because it overflows.
3. for 235, i think it will check the ActionPlan first and calculate its charactors, and if there is surplus, less than 235 charators, then check Progress.

pls correct me if i'm wrong, thanks. -- ShashaLuan - 22 Aug 2006

Filed a Bugs:Item2810 and made a new release DBCachePlugin v1.23. Now try two $trunc()s again.

-- MichaelDaum - 23 Aug 2006

Thanks, it works well

-- ShashaLuan - 24 Aug 2006

How to update the BlogPlugin?

I have set up several blogs using BlogPlugin. The new version of BlogPlugin has released. I want to update it. But there is a problem I worry about. Those old blogs I had set up will not have the feature of the new BlogPlugin. I have to copy some templates file in the _BlogPlugin to blog's folder. So some configurations of user may be reset. How should I update the BlogPlugin?

-- ZhikunLiu - 26 May 2006

The answer depends on your needs and courage.

If you want to use the new code then you basically move aside the old webs, create new once and move in the net data.

So:

1. delete the old _BlogPlugin template web
2. move aside / backup Main.BlogAdminGroup and Main.BlogAuthorGroup
3. unzip the new BlogPlugin.zip file
4. move back / restore Main.BlogAdminGroup and Main.BlogAuthorGroup

For each blog web Blog do the following (more or less)

1. create a new blog called BlogNew using the new _BlogPlugin templat web you just installed
2. copy all Blog[Link|Entry|Comment|Page][0-9]*txt* files from the Blog web to a new BlogNew web
3. merge Blog.WebPreferences and BlogNew.WebPreferences
4. test
5. in case you customized any BlogUp parts, make those modifications in BlogNew
6. test
7. move Blog to _Blog (note the leading underscore) thus making it invisible
8. move BlogNew to Blog
9. test
10. write a "Hooray" posting

-- MichaelDaum - 26 May 2006

Auto-linking in Blog Entries?

How do I turn on the auto-linking feature in blog entries? I played around with the NOAUTOLINK preference but that didn't help.

-- JamesTan - 15 Jun 2006

Edit RenderBlogEntry. There's a section "Format". Remove the <noautolink> and </noautolink> tags in the blogText div.

-- MichaelDaum - 15 Jun 2006

Thanks for the tip Michael. After some poking around, I realised that you have to remove the <noautolink> and </noautolink> in RenderDocNavigation and RenderFullTeaser as well, otherwise it won't work.

-- JamesTan - 19 Jun 2006

When do the "Red Dots" appear

Hi, I have some confusion with "Red Dot" in blog. Why some topics have "Red Dot" and some topics not. Especially in "News Feed". Currently in blog, only these types have "red dot": one is blog entry, and another is bloglink(exclude Rss Feed Bloglink). There are two questions:

• Why the Rss feed Bloglink don't have "red dot"?
• Why a bloglink(with url to another website) can not be deleted(don't have "move" button)?

is this a bug or something else? thanks

-- ShashaLuan - 14 Jul 2006

In general "Red Dots" are shown if you are authorized to edit the target topic (see the RedDotPlugin docu). In some cases the BlogPlugin deviates from this rule, like for BlogLinks. This one only gets a red dot (in the sidebar) if it contains and rss feed url. The reasoning behind is that you get a red dot link if you would leave the blog site otherwise as the link in the blogroll is pointing to an external site. If the BlogLink is containing an rss feed url then clicking on it will drive you to the aggregation section of your blog thus not leaving the site. This is helps to keep the number of red dots in the blogroll low. If you don't like that then change RenderBlogRoll TopicFuncion accordingly. Please, say if you need help with that.

In any case you can go to the BlogLink topic to get a list of all BlogLink topics there.

-- MichaelDaum - 17 Jul 2006

Customizing email notifications

I would send email notification by using webNotify on any update in one of blogs.However, in notification,BlogEnryX or BlogCommentX are listed there instead of headlines.Those will make reader confused to judge the exact info they have concerns. In code level,I find "mailnotify.tmpl" but change on the file will influence other webs.This is an urgent request.Thanks.

-- ZhiweiSun - 05 Jul 2006

More specific questions: 1.Can I get blog headline info by URL? 2. How to get blog headline info directly on code,I noticed "CITEBLOG" on front-end.

-- ZhiweiSun - 05 Jul 2006

As far as I understand you, the best is to forget about webnotify, as it is not customizable for TWiki applications. However, to get nicely formatted notifications you can use rss2email, a bridge between rss and email. As rss feeds are customized in a blog specific way emails created by rss2email will be also. You could create a cronjob that calls rss2email and sends the result to a mailing list.

-- MichaelDaum - 05 Jul 2006

The [[%ATTACHURL%/%TOPIC%.zip][Download]] link fails if this Plugin is installed; it works only here on TWiki.org. Better to write the full URL [[http://twiki.org/p/pub/Plugins/%TOPIC%/%TOPIC%.zip][Download]]. Actually I think it is better to keep the original text "Download the ZIP file from the Plugin web (see below)" (and fix the viewfile issue on TWiki.org.)

-- PeterThoeny - 05 Aug 2006

Blog Editing "Newline" Problem

Hi, when i writing in blog, i found a problem: "newline" dosen't work. take the BlogEntry as a case: I wrote this in the BlogEntry edit mode :

hi, 
the teaser, 
hello 
world

Then i will see this in the view mode :

hi, the teaser, hello world

So i need to use:

hi, 

the teaser, 

hello 

world

or

hi, <br>
the teaser,<br> 
hello <br>
world

to a new line. Is it a bug in Blog? Thanks for you help

-- ShashaLuan - 12 Sep 2006

This is normal wiki behavior. Create an arbitrary in Sandbox and have a look.

-- MichaelDaum - 12 Sep 2006

Thanks :), i see

-- ShashaLuan - 12 Sep 2006

Anonymous blogging

How do I grant everyone access to write a blog post? I understand I need to edit BlogAuthorGroup, but it would be great if I don't have to add every user to that group.

-- ArthurClemens - 18 Sep 2006

What happens if you add TWikiGuest to BlogAuthorGroup? Doesn't that grant everyone access?

• In that case non-logged in users get to see a "Write a new post" button, but once they log in the button is gone because they are not in the list of authors. -- ArthurClemens - 18 Sep 2006
• Hm, having unauthenticated users to write postings may be only an option in very controlled environments. This can be achieved with a few modifications to the related TopicTemplates taking out any CHANGEACCESS restrictions there in addtion to approriate settings in the WebPreferences. -- MichaelDaum - 23 Sep 2006
• It appears that my main problem is that post data are not passed on after the login screen. -- ArthurClemens - 21 Sep 2006
• This is not a BlogPlugin related problem and has been fixed in TWiki4-SVN recently to edit-save-login-continuesave even using TemplateLogin. I am not able to reproduce this problem any more.
  If you want to allow anonymous commenting then just remove the DENYCHANGEACCESS in the WebPreferences of your blog. -- MichaelDaum - 23 Sep 2006

-- FranzJosefSilli - 18 Sep 2006

BlogFactory

I just found out about BlogFactory. Really nice!

As I understand it, the user can only create a Weblog if he is included in ALLOWWEBMANAGE for TWiki, right?

I would like to enable all users to create their personal weblogs. Is there any way to do this?

-- MichaelRedinger - 20 Jul 2006

Even worse. Only a TWikiAdmin can create a new blog. That's hard-coded in several places in TWiki and the BlogPlugin.

-- MichaelDaum - 20 Jul 2006

But with added coding the TWiki could be set up to create a new web (based on _BlogWeb) for each user.

-- ArthurClemens - 20 Jul 2006

General remarks

• It is unfamiliar to have the form field labels at the right side of the input field.
• Then on some pages the submit button is at the left, before the input field.
  • Hm, I will check all cases and rethink usability and consistency. If you are addressing the fact that the field label "New TopicFunction" is the submit button in one, I'd rather say that it is quite fine concerning usability. -- MD
    • But you do have a problem with reading order, and thus with the natural flow. Because you need to fill in the field, and then go back and press the submit button. Note that on the small pop-up window the button is placed above the input field. --AC

• In the edit screen, what does "State" (enabled/disabled) mean? Something like public/hidden?
  • A BlogEntry can be in the state "enabled" or "disabled" and it does exactly what you said. A disabled blog entry is not published yet. So the state token "unpublished" might be more appropriate in fact. There are certain scenarios where you would like to defer to publish a posting you are about to write. Maybe you simply have not finished it yet. -- MD
    • Yes, I would prefer the label Published stated published/unpublished. -- AC
  • fixed in v0.95

• How do I retrieve a disabled entry?
  • Ah, in BlogEntry. -- AC
  • All unpublished postings of a blog author are listed in the sidebar of a BlogAuthor page right under the BlogAuthorTools. Surely, they are only visible there if this blog author has logged in. -- MD

• It is not so clear what the intention is to create entries for BlogAuthor.
  • Also, in adding a BlogAuthor, do I have to enter a name, a WikiName, or a Main.WikiName?
  • For example see my previous comment. Topics of type BlogAuthor serve some other purposes. For example in a multi-authored blog every BlogAuthor page lists the postings written by that author only. The BlogPlugin is detecting if a blog is single- or multi-authored by counting the BlogAuthor pages. A single-author blog will not display "by Frank N. Stone" displaying all blog entries as the blog is owned by him completely anyway. No reason to display his name all over again. On multi-authored blogs each BlogAuthor page may be used to describe each individual writer in more detail while the frontpage describes them as a group. And you may chose to name your BlogAuthor page differently from your WikiName using some fancy pseudonym. I also planned to add more formfields to the BlogAuthorForm to customize the comments written by that author, e.g. have a small avatar picture or a background color. -- MD

• Wouldn't it be better to use the blog title in the window title instead of the topic name?
  • Using NatSkin this in fact is the case for the WebHome. Other topics, i.e. blogentries use their headline in the window title. Most other topics in the BlogPlugin have at least a TopicDescription formfield that is used in the window title. -- MD

• The entry title inserts an extra space after the link and before the red dot. This is not in the left bar.
• It would be better if there is only one h1 header, and the left bar uses h2 headers.
• The comment email field says EMail instead of E-mail.
• How can I add an image to an entry?
  • Lates versions of the BlogPlugin have a "Upload Image" BlogAuthorTool to manage all image material on a page called BlogImages. More info there -- MD

• Topic WebSearch is missing from _BlogPlugin data dir
  • Oh IC, will add it back. Again a victim of my natskin-centric view. NatSkin has natsearch customized for the BlogUp application. That is it renders links and summaries making use of blog specific topic properties. -- MD
  • fixed in v0.95

• I find the link headers Chron.   Cat.  Tag.   Lex. quite cryptic.
  • See the sidebar. The blog archive displays a precise definition of these modes there. -- MD

• I get a few validation errors when for instance authors are not defined: the bullet list starts with ul = but has no =li in it.
  • You mean there is no BlogAuthor page defined? Which list is empty then? -- MD

• After replying, I get this line in the entry page: Arthur Clemens replied 6 hours, 47 minutes after the incident. What is the incident? Suggestion for other word "Incident" is the referd entity. In case of this application it is a posting or a comment on it being commented on again -- MD

• I find the big number at the right (indicating the number or comments) very enigmatic. I would prefer to have the text "1 comment" in small type.
  • I studdied a lot of other "real" blogging software and picked out those parts I liked most. Have a look at WordPress, which I studdied in most detail, i.e the Kubrick style. In general I tried to remove as many strings from the view as possible while retaining usability. There are lots of things in a blogging software and on each blog site that you need to "learn" and "understand". The balance of demanding that effort vs being too verbose is a matter of taste actually. However, as you may hover over the number you get the crucial helping tooltip that explains the elements. Hovering gui elements to learn about them is taken for granted. -- MD
  • But I do understand this for the left side bar
  • On our intranet I have changed this to show the comments below the post (in RenderFullTeaser):

    ~~~    $formfield(Text)
    ~~~    <div class=\"commentCount\">   <= Start insert
    ~~~    $percntCOUNTCOMMENTS{\"$web.$topic\" hidenull=\"on\"
    ~~~     format=\"<img src=\\"%ICONURL{bubble}%\\" width=\\"16\\" height=\\"16\\" alt=\\"Comments\\" border=\\"0\\" /> <a
    href=\\"$dollarpercntSCRIPTURL{\\"view\\"}$dollarpercnt/
    *~~        $web/$topic#topComment\\"
    ~~~        title=\\"comments on <nop>$topic\\">reacties</a> ($dollarcount)\"
    ~~~    }$percnt
    ~~~    </div>
          

• There are some styles 'hard-coded' in topic templates (for instance <h3 style="margin-bottom:0px;padding-bottom:0px">). I would be nice if there are classes for this.

Unfortunately I cannot include my Weblog home topic with INCLUDE in another web (I tried it in Sandbox), because I get the error: ERROR: DBCALL can't find topic RenderFrontPage in Sandbox.

• I manage to get the first entries now by putting this in the other web:

%~~ DBCALL{"Weblog.RenderFrontPage" 
~~~   SKIP="%URLPARAM{"skip"}%" 
~~~   LIMIT="%URLPARAM{"limit"}%" 
~~~   CAT="%URLPARAM{"cat"}%" 
~~~   AUTHOR="%URLPARAM{"author" default=".*"}%" 
~~~ }%

This generates (urls modified):

---

There are a couple of things here:

• there is no category defined (should I?), so xx minutes ago in by looks strange (in should not be there)
• the entry has a h1 header
• the author is referenced as AuthorName, so there should be either a nop or Main.AuthorName
  • I see now that the author name is a link if the author is set as one of the authors (as topic type). In that case I think the interface could be a bit more helpful: in the edit screen for instance, and on the pop-up when clicked on BlogAuthor (the submit button is at the wrong side!).
  • I've added a couple of author names. Now the author name is not a link in the entry page, but it is on the category page with accumulated posts.

---

• The paging mechanism does not work when the front page is included in another web. In the above example the first 5 items render fine, adding comments works, but the paging not.
  • Solution: to include the blog in another topic in another web, change this in WebHome:

%STARTINCLUDE%  <= change 1
%~~ DBCALL{"%WEB%.RenderFrontPage"   <= %WEB% = change 2
~~~   SKIP="%URLPARAM{"skip"}%" 
~~~   LIMIT="%URLPARAM{"limit"}%" 
~~~   CAT="%URLPARAM{"cat"}%" 
~~~   AUTHOR="%URLPARAM{"author" default=".*"}%" 
~~~ }%
%STOPINCLUDE%  <= change 3

Then in the topic simply call %INCLUDE{Weblog.WebHome}%

• • fixed in v0.95

• In my side bar I get an unresolved variable: %IFSKINSTATETHEN{searchbox="pos2"}% (from SVN).
  • fixed in v0.95
• BlogPlugin is liberally sprinkling p tags which makes design a bit difficult. For instance I have a link "Weblog archive" straight after the list of latest entries. In the html source I get:

<p />
 <!--
<p />
-->
<div class="blogNavigation">
<table border="0" cellpadding="0" cellspacing="0"><tr>
<td class="blogPrev"> <a style="display:none" href="?skip=0;limit=5">&#171;&nbsp;previous page </a>
</td>
<td class="blogNext"> <a style="display:none" href="?skip=5;limit=5">next page&nbsp;&#187; </a>
</td>

</tr></table>
</div>
<p />
Weblog archive link here

So instead of the normal div margin of the entry I get the margin plus a couple of newlines before the link. blogNavigation could be hidden altogether if there is no blogPrev and blogNext.

• • fixed in v0.95

• There is no common css class for the "place comment" link. It would be nice to get a overall style, in teasers and in posting pages.

-- ArthurClemens - 19-23 Jun 2006

Arthur you probably should try using BlogPlugin with NatSkin instead - it works and looks a lot better that way! The IFSKINSTATETHEN variable is in NatSkin plugin.

• Not possible. Our TWiki intranet uses a derivation of pattern skin, and the weblog is an integrated part of it. -- AC

-- JamesTan - 20 Jun 2006

I think that PlogPlugin is pretty much designed to use NatSkin, so I'm not sure it's feasible to try and get it to work with PatternSkin. It's really meant to be part of the BlogUp package, I believe.

OTOH, it would be nice if the two primary skin authors got together and worked out some skin basics.

-- MeredithLesly - 21 Jun 2006

I understand not all is working well at the moment, but I would like to see BlogPlugin work better with pattern skin (or the way around). Actually there are not so many skin issues, but on the usability front some things can be improved.

-- ArthurClemens - 22 Jun 2006

I wouldn't mind to help Michael to sort out the details/issues I have described above (not only pattern skin things).

-- ArthurClemens - 23 Jun 2006

Thanks, a lot for the detailed feedback, Arthur. I really appreciate that as well as any helping hand. First, let me commented on your above questions inline.

• My comments in red. -- ArthurClemens - 06 Jul 2006
• Added some more replies on your feedback. Will study and incorporate the other suggestions when working on the next release. -- MichaelDaum - 08 Jul 2006

-- MichaelDaum - 06 Jul 2006