Not signed in (Sign In)

Categories

Vanilla 1.1.5 is a product of Lussumo. More Information: Documentation, Community Support.

Help keep Vanilla free:
Welcome Guest!
Want to take part in these discussions? If you have an account, sign in now.
If you don't have an account, apply for one now.
    • CommentAuthorchanzero
    • CommentTimeMar 23rd 2007
     # 51
    alison: i think you're ok, but what you need to do is create a folder called Janine and put all the files from the unzipped Janine-1.1.0 folder (just the contents not the folder itself) in there

    michel: i think you missed the earlier discussion but squirrel was saying she had a new way for janine to work which i believe is incorporated into janine-1.1.0 -- that being, new vanilla discussions are not created upon publishing of a WP post -- instead discussions are created when someone clicks on the WP post's "post your comments" (which needs to be adjusted in your WP theme files per the readme)

    obviously squirrel can confirm officially
    • CommentAuthorchanzero
    • CommentTimeMar 23rd 2007 edited
     # 52
    hmm. i made the changes to my Single Post template to but something weird is going on with the html there. at the bottom of my page it says "41243 | Discussion >" where 41243 is my WPpost ID and Discussion is the following link:
    http://www.mysite.com/forums/extension.php?PostBackAction=GetBlogDiscussion&BlogPostID=

    EDIT: after reading the WP codex i believe the way the code is written will work correctly because the tag "the_ID" is only available during the Loop and thus BlogPostID will always be empty

    regardless, when i add the WPpostID manually to the end of the link thusly:
    http://www.mysite.com/forums/extension.php?PostBackAction=GetBlogDiscussion&BlogPostID=41243

    i get the following error:

    Parse error: parse error, unexpected '{' in /home/sites/buzzscope/users/buzz/public_html/forums/extensions/Janine/Janine.Control.JanineControl.php on line 185

    so now i'm sorta stumped. it's possible i did not upgrade janine correctly =/ will play around more when i get a chance.
  1.  # 53
    chanzerio, is the Janine-1.0.1 folder the updated one? It's got the wrong ReadMe, I'm pretty sure. What is the "Janine" folder? It's default file also says 1.0.1.

    quirrel was saying she had a new way for janine to work


    Squirrel is FEMALE? Not that it matters, but the forum is so male-heavy that I tend to just assume male.
    • CommentAuthorchanzero
    • CommentTimeMar 23rd 2007
     # 54
    alison: in your vanilla/extensions folder i believe you should have a folder called simply "Janine"; i think all newly unzipped files from janine 1.1.0 should go in there

    i am not sure the ReadMe is wrong. granted the version history only lists up to 1.0.4, however the information for changing WP files is new and seemingly correct

    i thought she was based on the line at the end of her readme's: "The alien looks like her father." but i could be wrong ^_^; not that it matters, as you said, but it is pretty cool if so
  2.  # 55
    OK, but just to be sure you understood, when I download the latest Janine 1.1.0, I get a folder called "Janine-2007-03-23 Folder" that has TWO folders in it, one called "Janine" and the other called "Janine-1.1.0." The FORMER has a read me that IS up-to-date, the latter doesn't. The more up-to-date ReadMe includes info on 1.1.0 and on upgrading from a previous version. The file NAMES within the two, inner folders are identical, but the ReadMe's are different. There are at least a few, minor differences in the code between the two sets of files, as well. For example:

    Line 185 in Janine.Control.JanineControl.php:

    return $this->GetDiscussionUrl($this->BlogPostData['BlogPostID']);
    return $this->GetDiscussionUrl($this->BlogPostData['BlogPostID']) {

    Are you saying that I should use the inner folder called "Janine-1.1.0"?
    • CommentAuthorchanzero
    • CommentTimeMar 23rd 2007
     # 56
    no i'm not definitely saying that -- in fact what you've pointed out seems like it would be what was wrong with mine. let me test and post results
    • CommentAuthorchanzero
    • CommentTimeMar 23rd 2007 edited
     # 57
    IT WORKED!!!!!!!!!!

    when i say that, i mean going to this link worked:
    http://www.mysite.com/forums/extension.php?PostBackAction=GetBlogDiscussion&BlogPostID=41243

    it created a new vanilla discussion with a link back to the WPpost! so that means i can go ahead and make the changes on my WP files :)

    try this:

    1) go into to settings and turn off Janine

    2) open Janine.Control.JanineControl.php from the Janine 1.1.0 folder and change line 185:
    from: return $this->GetDiscussionUrl($this->BlogPostData['BlogPostID']) {
    to: return $this->GetDiscussionUrl($this->BlogPostData['BlogPostID']);

    3) upload the files in Janine 1.1.0 into the vanilla/extensions/Janine/ folder, overwriting any existing files
    4) refresh settings page and turn on Janine
    5) pick a WP post with no comments and get its postID # and put at the end of this string (replace # sign with actual postID)
    http://www.yoursite.com/vanilla/extension.php?PostBackAction=GetBlogDiscussion&BlogPostID=#

    if all goes well, it should create the discussion -- and you'll be at the same happy spot where i currently am :)

    then just have to make changes to WP files as noted in 1.1.0 ReadMe

    *if all this doesn't work, try to run this link? not sure if necessary
    http://www.yoursite.com/forums/extensions/Janine/upgrade.php
  3.  # 58
    FYI, I just compared all the files in the two folders. The "Janine" folder has the CORRECT code. The "Janine-1.1.0" does not. If you use "Janine" you won't have to make the line 185 correction that chanzero gave above. (It also has the updated ReadMe.)

    I'll be uploading that and I'll let you know if I can get it to work.
  4.  # 59
    When it comes to your old blog posts created by Janine, you have three options:


    Is this referring to discussion posts created by Janine (since Janine doesn't create "blog posts")?

    **********

    Vanilla and WordPress must be using the same database, same username, same password.


    Neat Trick #1: If your blog and your Vanilla forum share the same users table, set this option to '0'. Janine will try to post the discussion using the same user ID that made the blog post.


    Aren't these referring to the same thing? If so, the "if" in the second quote doesn't make sense.

    **********

    JanineDiscUserID
    The user ID that Janine will use to post discussions, default is '1'.
    ...
    JanineDiscCategoryID
    The ID of the category where the new discussions will appear, default is '1'.


    Both of these categories have "0" as the default now.

    **********

    I did a fresh install of my theme as per the instructions "You will need to roll back any changes you made to your blog's theme for versions 1.0.X."

    It seems, however, that I really should have those changes, as per the "Adding a Discussion Link to the Blog" section in the docs. Were there other changes made that I forgot?

    *****

    I'll correct my previous post. It SEEMS as though the new version does not immediately create a new discussion upon blog post creation--UNLESS you have the ping thing going. (The ping thing, however, does not always work.)

    *******

    Alrightee. I'm off to do some coding. I'll check back in later.
  5.  # 60
    OK, good new and bad news.

    I changed my theme settings as per the instructions squirrel gave earlier for Mistylook. (Should they be different?)

    Then I created a new blog post. The post had NO "Discussion" link and NO discussion was created. (I did set the ping, so apparently the ping isn't working?)

    I ran the postbackaction as per chanzero's post. This DID create a disussion, but there is still no link on the blog TO the discussion.

    The links to the blog comments are gone on the main page and the single page, as they should be, but remain on the archive pages.

    I'm guessing that either the theme coding is wrong or I entered it wrong. Ideas?
    • CommentAuthorchanzero
    • CommentTimeMar 23rd 2007 edited
     # 61
    alison: sounds like janine is working but you have not changed your themes correctly
  6.  # 62
    Yea, it does. I just copied what squirrel had put in the thread earlier, but perhaps the new version requires different changes? I'll see if I can figure that out, but I'm not much at php.
    • CommentAuthorbflora
    • CommentTimeMar 23rd 2007
     # 63
    Everything seems to be working, after I followed the directions in this thread. Yeah, the two folders is a bit confusing.

    One weird thing though....the links that I'm generating for my wordpress templates (I'm using the code right out of the documentation) all start with the post # of whatever post the link is tied to. Where's this coming from and how do I get rid of it?

    So far this is really exciting! Its really going to force me to rethink how we run our blog.
    •  
      CommentAuthorsquirrel
    • CommentTimeMar 23rd 2007
     # 64
    The "Janine" folder has the CORRECT code. The "Janine-1.1.0" does not.

    This is correct. The "Janine-1.1.0" was an older working copy that shouldn't have been there. I should have been more careful but I was rushing.

    Neat Trick #1: If your blog and your Vanilla forum share the same users table, set this option to '0'. Janine will try to post the discussion using the same user ID that made the blog post.

    Aren't these referring to the same thing? If so, the "if" in the second quote doesn't make sense.


    They are not the same. Vanilla and WordPress can share the same database without sharing the same users table.

    Both of these categories have "0" as the default now.

    If so it's a bug, but one I haven't seen. When I install fresh both are '1'.

    I did a fresh install of my theme as per the instructions "You will need to roll back any changes you made to your blog's theme for versions 1.0.X."

    It seems, however, that I really should have those changes, as per the "Adding a Discussion Link to the Blog" section in the docs. Were there other changes made that I forgot?


    Nope, look carefully. The old instructions for 1.0.X relied on a custom field in your blog posts that Janine no longer bothers with. The earlier instructions I gave for Mistylook aren't valid for 1.1.0. Sorry about that.

    On top of that, chanzero is correct. I totally screwed up the 1.1.0 instructions for altering the blog template.

    I will fix the zip and the docs, roll the version up to 1.1.1 and post it soon. Again, sorry.
  7.  # 65
    Well I don't know I followed all the instructions to the letter and still it doesn't post. I know I have done everything right. So I am not so sure what I am doing wrong. is there any help that I could get for this. I have to be over looking something.
  8.  # 66
    Uploaded version 1.1.1 of Janine.
    •  
      CommentAuthorsquirrel
    • CommentTimeMar 24th 2007
     # 67
    This update fixes the archive and has better documentation to clear up the link problems seen by chanzero, michelbites, bflora, and others. I actually tested my WordPress changes this time, so I know they're right. As always, please let me know if you have problems. Thanks.
    • CommentAuthorchanzero
    • CommentTimeMar 24th 2007 edited
     # 68
    yay! everything is working quite nicely now :) thanks for your diligent work squirrel!

    only thing is, i am noticing a bunch of discussions have been started but no posts have been made on them. is it possible that google-type search bots are tripping the discussion creation links? i ask this because they were all created at like 3-5am EST on a weekend, and i'm thinking if there really was someone online on my site now and they bothered to click "leave a comment", i'd think they'd leave one?

    EDIT: ok, i really think this can't be humans -- i just woke up and i now have 85 new discussions with 0 new posts!
    • CommentAuthorxtc
    • CommentTimeMar 24th 2007
     # 69
    lol :D
  9.  # 70
    Thanks for the clarification, squirrel.

    When you first enable Janine it should automatically create some default settings in Vanilla's conf/settings.php file. If you are using WordPress 2.0.X or 2.1.X, the default settings should work just fine for you, though you will probably want to customize some of them. These settings are stored in Vanilla's conf/settings.php file.


    When I originally installed Janine, I changed the conf/settings.php to 0 to use the "neat tricks." When I did a fresh install of Janine, the code were both still 0. So, when I reinstalled and re-enabled Janine, I guess it didn't overwrite my changes?

    Ah, OK. So the earlier MistyLook changes don't work anymore. I'll reinstall a fresh copy of the theme. Any hints on how to modify the docs to fit Misty? Do I need to modify at all? (I'm not much on php, if you hadn't noticed.)
    • CommentAuthorbflora
    • CommentTimeMar 24th 2007
     # 71
    Hey guys, how do I create a token to add the first 100 words or so of a wordpress post content to what Janine posts? It can't be so hard right? I'm liking the post title and post link, but I'd also like a little "teaser" of the actual content itself without the whole article showing up in there.

    I just don't know any SQL in order to write the query. What would it be and where would it go?
    •  
      CommentAuthorsquirrel
    • CommentTimeMar 25th 2007
     # 72
    Hm. Interesting, and not difficult.

    Open the file 'extensions/Janine/Janine.Control.WordPress21.php'

    Find the line that looks like this:
    'BlogPostModified' => 'post_modified_gmt',
    Add the following line right after it:
    'BlogPostContent' => 'post_content',

    Find the line that looks like this:
    $SqlBuilder->AddSelect(array('BlogPostID', 'BlogPostUserID', 'BlogPostTitle', 'BlogPostComments', 'BlogPostLink'), 'bp');
    Replace it with this:
    $SqlBuilder->AddSelect(array('BlogPostID', 'BlogPostUserID', 'BlogPostTitle', 'BlogPostComments', 'BlogPostLink', 'BlogPostContent'), 'bp');

    Find the line that looks like this:
    // Attempt to get the category ID, nice but not necessary
    Add the following lines right BEFORE it:
    // Split the post content at the "more" tag
    $PostContent = explode('<!--more-->', $ReturnData['BlogPostContent'], 2);
    $ReturnData['BlogPostBeforeSplit'] = $PostContent[0];
    $ReturnData['BlogPostAfterSplit'] = ForceSet(@$PostContent[1], '');


    This will give you three new tokens: BlogPostContent, BlogPostBeforeSplit, and BlogPostAfterSplit. The first has the entire text of the blog post, the second has everything before the "more" tag (or everything, if there is no more tag), the third has everything after the "more" tag (or nothing, if there is no more tag).

    Does this help?
    • CommentAuthorchanzero
    • CommentTimeMar 25th 2007
     # 73
    squirrel: any clue about the mystery robot posts i mentioned? i now have 300+ discussions with 0 posts!

    but thanks for the "more" code, i needed that too.
    •  
      CommentAuthorsquirrel
    • CommentTimeMar 25th 2007
     # 74
    chanzero, you're probably right. They were probably created by a search engine spidering the links on your site. Janine creates the new discussion when the discussion link is accessed, so even a search engine could do that. I didn't consider that, or what it would do to a site with a lot of archives. Sorry about that.

    I should have advised you (and everyone else) to add rel="nofollow" to the comment links on your WordPress pages.
    • CommentAuthorcircuit
    • CommentTimeMar 25th 2007
     # 75
    i'm getting this error. i'm still trying to figure it out.

    A fatal, non-recoverable error has occurred
    Technical information (for support personel):

    Error Message
    The "JanineWordPress204" control referenced by "JanineWordPress204" does not appear to exist.
    Affected Elements
    ObjectFactory.CreateControl();
    • CommentAuthorcircuit
    • CommentTimeMar 25th 2007
     # 76
    i got it. i changed my wordpress version back to Wordpress21 in the settings.php file and it works. i actually have 2.0.4 but i guess the filename was coming up wrong.
    • CommentAuthorcircuit
    • CommentTimeMar 25th 2007
     # 77
    is there a way to retrieve the blog post's username as a token?
    • CommentAuthorbflora
    • CommentTimeMar 25th 2007
     # 78
    circuit, I'm guessing its done the same way as for the post content.

    Squirrel. Your steps worked like a charm! Janine's kicking some major ass. I'm going to add in an author token and date as well for a decent byline (I run a news blog so thats important).

    SWEET!
    • CommentAuthorcircuit
    • CommentTimeMar 25th 2007
     # 79
    one more little observation before i go to bed:
    this extension causes the blog post author to appear online in the 'who's online' extension, whether they are or not. not a problem for me really, but might be for someone.

    otherwise, i love it. thanks squirrel.
  10.  # 80
    Nevermind...
    • CommentAuthorbflora
    • CommentTimeMar 25th 2007
     # 81
    Hmmmm, actually, I'm not seeing an obvious solution, since display name is in a different table....how would that work?

    Something like this?

    if (!array_key_exists('JanineBlogUsers', $Context->DatabaseTables)) {
    $Context->DatabaseTables['JanineBlogUsers'] = 'users';
    $Context->DatabaseColumns['JanineBlogUsers'] = array(
    'BlogPostAuthor' => 'display_name WHERE ID=post_author',

    );
    • CommentAuthorcircuit
    • CommentTimeMar 25th 2007
     # 82
    This will give you three new tokens: BlogPostContent, BlogPostBeforeSplit, and BlogPostAfterSplit. The first has the entire text of the blog post, the second has everything before the "more" tag (or everything, if there is no more tag), the third has everything after the "more" tag (or nothing, if there is no more tag).

    Does this help?


    sorry, my millionth post :)
    it would be cool if this pulled the blog excerpt... i don't use the 'more' tag.
  11.  # 83
    I'm working on "Adding a Discussion Link to the Blog" for Mistylook myself.

    Followed step 3 and step 4.

    (FWIW, perhaps the docs could mention to replace the URL in the code with your OWN URL? I didn't read all the code (since I don't understand a lot of PHP anyway) and was surprised to end up at www.yoursite.com! :) )


    Did step five to single post, but I'm having a problem...
    • CommentAuthorbflora
    • CommentTimeMar 25th 2007
     # 84
    Another weird thing I'm noticing.....

    Sometimes the BlogPostLink token isn't picking up the Post Slug in the URL instead of the default title. I've got a post where the BlogPostLink gives you a 404 because the blog post was using a slug and the token link uses the posts full title in the URL. Why would that be? Why wouldn't it pick up the slug like on just about every other story I've tested so far?
    • CommentAuthorcircuit
    • CommentTimeMar 25th 2007
     # 85
    i'm not sure if this is an issue for anyone else, but my blog requires a user to be logged in to do anything except read. if you are logged out and click the 'add comment' link, the post is created in the forum, even though you're not permitted to reply to it. i fixed this by adding the following check in the wordpress template:


    <?php
    global $user_ID, $user_identity;
    get_currentuserinfo();
    if (!$user_ID):
    ?>

    // do something if the user is NOT logged in

    <?php
    else:
    ?>

    // do this if the user IS logged in

    <? endif; ?>
  12.  # 86
    Nevermind. Yea, I'm feeling like a php wiz about now...
    • CommentAuthorbflora
    • CommentTimeMar 25th 2007 edited
     # 87
    In addition to the slashes....how do I get my paragraph breaks in the post-content to show up when posted by Janine? My blog posts were written in the rich text editor. Markdown does the breaks just fine, but it doesn't pick up any of the image links or anything like that.

    Sorry to be a nag, this is just really exciting. I hope my questions help you make the extension even better.

    Also, style info doesn't show up when I give my paragraphs and links style="xxx:xxxxx;" commands in the conf/setteings.php file. Perhpas this is unavoidable...
    • CommentAuthorcircuit
    • CommentTimeMar 25th 2007
     # 88
    idea:
    maybe a new discussion should only be created if a comment is actually added in reply. otherwise users can needlessly create lots of blank discussions.
    i'm being a bit picky now :)
    time for bed!
  13.  # 89
    I'm attempting to add a token to create a link back to the article in the discussion. I'm using the HTML formatter extension on my Vanilla board (which seems to be the same that's used here. Here's what I tried:

    $Configuration['JanineDiscBody'] = 'Please join us to discuss [%BlogPostTitle%](%BlogPostLink%).';
    $Configuration['JanineDiscFormat'] = 'HTML';

    The text ends up like this:

    Please join us to discuss [Test the token](http://blog.mormonmomma.com/wordpress/2007/03/25/test-the-token/).

    What should I put instead of HTML to get this to work? Tried "Html" in case it was case sensitive. Didn't work either.
    • CommentAuthorbflora
    • CommentTimeMar 25th 2007
     # 90
    the syntax you're using is specifically for "Markdown."

    Try this instead for HTML. It's worked for me.

    $Configuration['JanineDiscBody'] = 'Please join to discuss <a href="%BlogPostLink%">%BlogPostTitle%</a>.';
    $Configuration['JanineDiscFormat'] = 'HTML';
  14.  # 91
    Thanks bflora. It still didn't work. It added the correct code, but it did NOT set it to HTML. When I look at the post, it's in text format. I can EDIT the post (manually changing the setting to HTML) and it works correctly, but this:

    $Configuration['JanineDiscFormat'] = 'HTML';

    doesn't seem to set it to HTML. Any ideas anyone?
    •  
      CommentAuthorsquirrel
    • CommentTimeMar 25th 2007
     # 92
    circuit: The "who's online" quirk is probably unavoidable because of how Janine works. If it doesn't bother you then it doesn't bother me. As for modifying Janine to prevent empty discussions, it's a good idea but it would take lots and lots of code. I'm afraid it's beyond the scope of my design for Janine but it you want to give it a shot I'll consider including it in a later release.

    bflora: Please show me an example of broken links in Janine. The post link is created by WordPress using the permalink structure set in the WP options. If your WP permalink works, the link in Janine should work (I think). About quotes, you're absolutely right, they're broken. Grr. I'm on it.

    bflora and circuit: Since it looks like I'll have to make yet another release to fix quote issues, I'll go ahead and include a bunch of new tokens in the WP control.

    Alison: The magic was in you all along.
    • CommentAuthorcircuit
    • CommentTimeMar 26th 2007 edited
     # 93
    overnight janine posted 20-30 posts on the forum by itself. the comment links have &rel=nofollow at the end, but it didnt stop it happening. is there anything i can do about this? i'm guessing it was caused by spiders, but the comment links are actually hidden unless you log in, so i'm not sure. maybe there are some spambots registered to our site. perhaps a simple confirmation screen would do the job?

    for now, i'm gonna add a javascript prompt to the link. i'm not sure if that will help.
  15.  # 94
    Apparently last time I tested the lower-case, I still had the Markdown code. The "Html" works with the good code on the token. :) I'm getting to be a very happy camper. :)

    Squirrel, thanks again for all your support for this extension.
    • CommentAuthorchanzero
    • CommentTimeMar 26th 2007 edited
     # 95
    is rel=nofollow supposed to be added at the end of the link (as circuit mentioned with the "&" sign) or like this
    <a rel=nofollow href=
    because i did the latter and still have the automatic postings

    alison: you go!
    •  
      CommentAuthorsquirrel
    • CommentTimeMar 26th 2007
     # 96
    chanzero: You want the latter, but don't forget to put in quotes like this:
    <a rel="nofollow" href="...

    It's not a perfect solution. Google and other search engines say that their spiders honor the "nofollow", but there are others that don't honor it. It only takes one badly behaved spider to suddenly trigger a bunch of Janine discussions.

    It's not hard to add an option to disallow anonymous users from triggering a new Janine discussion. If you turn it on, anonymous users will get bounced to the index if no Janine discussion has been created for that blog post. Only logged-in users will trigger a new Janine discussion. I'll go ahead and add that to 1.1.2.
    • CommentAuthorcircuit
    • CommentTimeMar 28th 2007
     # 97
    unfortunately i've had to disable janine due to abother 30 posts appearing on the forum overnight. the plugin is perfect except for that!
  16.  # 98
    circuit, if I understand what you are saying, it is that you have a ton of older blog entries that do NOT have discussions associated with them, and that the discussions are being created by a robot? (Sorry, reminds me of the old Saturday Night Live skit for robot insurance, "because robots are strong and they're made of metal.)

    Anyway, its seems the only NON-code solution would be to turn off discussions for the old blog entries, or CREATE them all yourself in a reasonable order so that the older ones drop to the bottom. (Another reason it would be great to be able to set the DATE on Vanilla entries like you can on WP entries.) I actually plan to do the latter. But I only have a few hundred articles that will be converted to the blog.
    • CommentAuthoralan
    • CommentTimeMar 29th 2007
     # 99
    Hey,

    I have a very specific issue with Janine, so specific that it's probably not going to be worth addressing, but in case it's an easy fix I thought I'd mention it.

    I'm using it on a blog where most of the posts will be hidden to any user not logged in (using this plugin - http://fortes.com/projects/wordpress/postlevels/). Unfortunately, when posts are hidden from users that aren't logged in, Janine won't create a discussion. The debug tool returns:

    Some problems were encountered
    Janine could not find the specified blog post.
    Janine will not create a discussion for this blog post because the post does not allow comments.

    (In case it affects a possible solution, Wordpress and Vanilla are set up to share a users table.) Is there any way to make Janine aware of the hidden posts?

    By the way, even if I have to work around this manually when I make a new post (make it public, follow the discussion link, edit the post to make it private), this plugin's still a fantastic and much appreciated help to the site. Lots and lots of thanks, Squirrel. You rule.

    All the best,
    Alan
    •  
      CommentAuthorsquirrel
    • CommentTimeMar 30th 2007
     # 100
    circuit: I don't think a javascript confirmation will help you out. I'll add code to 1.1.2 that gives you control over whether anonymous users can trigger Janine discussions. Now that I think about it, it also wouldn't be hard to add a "JanineStartDate" option that tells Janine to not create discussions for older posts. I'll add that too.

    alan: Please try this, open Janine.Control.WordPress21.php and find the following lines:
    // Get the most recent blog post
    $SqlBuilder->Clear();
    $SqlBuilder->SetMainTable('JanineBlogPosts', 'bp', $pre);
    $SqlBuilder->AddSelect(array('BlogPostID', 'BlogPostUserID', 'BlogPostTitle', 'BlogPostComments', 'BlogPostLink'), 'bp');
    $SqlBuilder->AddWhere('bp', 'BlogPostStatus', '', 'publish', 'like', 'and', '', '1', '1');
    $SqlBuilder->AddWhere('bp', 'BlogPostStatus', '', 'static', 'like', 'or');
    $SqlBuilder->EndWhereGroup();
    $SqlBuilder->AddOrderBy('BlogPostModified', 'bp', 'desc');
    $SqlBuilder->AddLimit(0, 1);
    if ($BlogPostID) {
    // If the post ID is specified, require it to match
    $SqlBuilder->AddWhere('bp', 'BlogPostID', '', ForceInt($BlogPostID, 0), '=', 'and', '', '0');
    }

    Replace them with these lines:
    // Get the blog post
    $SqlBuilder->Clear();
    $SqlBuilder->SetMainTable('JanineBlogPosts', 'bp', $pre);
    $SqlBuilder->AddSelect(array('BlogPostID', 'BlogPostUserID', 'BlogPostTitle', 'BlogPostComments', 'BlogPostLink'), 'bp');
    $SqlBuilder->AddLimit(0, 1);
    if ($BlogPostID) {
    // If the post ID is specified, require it to match
    $SqlBuilder->AddWhere('bp', 'BlogPostID', '', ForceInt($BlogPostID, 0), '=');
    }
    else {
    // If no post ID is specified, try to guess the most recent post
    $SqlBuilder->AddWhere('bp', 'BlogPostStatus', '', 'private', 'not like');
    $SqlBuilder->AddOrderBy('BlogPostModified', 'bp', 'desc');
    }

    This is probably another change I should put in 1.1.2.

    I promise I haven't forgotten about 1.1.2, but my job is crazy right now. It will be a little while before I can come back to coding and there are several bugs I'm chasing. Thanks for your patience.