Not signed in (Sign In)

Categories

Vanilla 1.1.4 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.

Add-ons: Janine

Bottom of Page

1 to 50 of 137

  1. <
  2. 1
  3. 2
  4. 3
  5. >
    •  
      CommentAuthorsquirrel
    • CommentTimeMar 5th 2007 edited
     # 1
    Janine is an extension to automatically create a new Vanilla discussion and associate it with a post on a blog. Right now Janine only supports recent versions of WordPress, but in theory it could be easily extended to work with just about any blog or content management system.
    •  
      CommentAuthorsquirrel
    • CommentTimeMar 5th 2007 edited
     # 2
    Please let me know if you have any trouble with Janine. Trying to integrate with another piece of software that you can't control is always delicate work, but I will do my best to fix breakages as quickly as possible.

    Known Issues

    1. Something is screwy with quote characters and/or slash characters, and using these characters in a blog post will make Janine fail to create a discussion. I don't know why yet, but I will. Target: This will be fixed in the next release.

    2. Right now Janine won't create discussions for private blog entries. A patch can be found here. Target: This patch will be in the next release.

    3. Consider this carefully before installing Janine on a blog with lots of old archived posts: If any user hits a Janine discussion link and no discussion exists for that post, Janine will create the discussion. The user does not have to leave a comment to trigger the new discussion. In fact, the user doesn't even have to be human, it could be a search engine spidering your site. If you have lots of old blog posts, your forums could be flooded with hundreds of new discussions overnight. I have two ideas to solve this: 1. A config option that disables discussion creation by anonymous users, 2. A config option that sets a "start date" and only creates discussions for blog entries made after that date. Each of these ideas has certain advantages. Target: Both of these solutions will be in the next release.

    4. There are some strange problems with Unicode characters. Janine might give you headaches if your blog is using non-Latin characters. I am looking into it, but Vanilla itself has some encoding quirks that are not fantastically well understood. Target: Hopefully I can fix this for the next release, but no promises.

    5. Janine does not open a new database connection to access the blog database. It simply uses the existing database connection opened by Vanilla. This means your Vanilla tables and your blog tables must be in the same database. Target: Sometime in the future. Not the next release.


    Items for the Next Release

    • Problems with quote and slash characters (issue #1 above). Status: Confirmed, but not yet understood.

    • No discussions created for private blog entries (issue #2 above). Status: Fix coded but not tested.

    • Web spiders causing havoc with large archives (issue #3 above). Status: Both fixes coded but not tested.

    • Problems with Unicode (issue #4 above). Status: Can't yet reproduce it myself.

    • Add some more tokens, such as BlogPostContent, BlogPostExcerpt, BlogPostBeforeSplit, BlogPostAfterSplit, BlogPostDate, BlogPostUsername, and anything else I can think of. Tokens for everyone! Status: Various stages of coding.
    • CommentAuthormahodder
    • CommentTimeMar 5th 2007
     # 3
    @squirrel: Have you had any experience integrating WP and Vanilla? I have integrated the two and included the Wordpress functions with my forum but have a issue with single and double quotes.

    It is explained here:

    http://lussumo.com/community/discussion/4818/wordpressvanilla-intergration-issue-with-single-quote/#Item_0

    Just wondering if you have come across this or may know why its happening, I can't figure it out.
    • CommentAuthorMark W
    • CommentTimeMar 6th 2007
     # 4
    It would rawk if Vanilla & WP comments synced. I've always wanted a community that was half blog half forum, so that the bloggers were interacting with the existing forum community and v.v. - it's a good way to bring fresh blood into the forum community and keep the community fresh.
    • CommentAuthorideve
    • CommentTimeMar 7th 2007 edited
     # 5
    Hi there Squirrel

    great job you did here really we needed this extension ('tell Swell get alive at least :( ).

    i was thinking about doing this but im not php'er ('tell now).

    here a small suggestion :

    your great extension will sync every post in the blog to vanilla that good enough but blogs usually have a personals , news ... any kind of post that doesn't need to be discussed for any kind of reasons such a personal posts.

    so what i was thinking of has two parts :

    1-part where you should work with wordpress : to add a "discuss this" button under each post to give the users the option for opening a discussion page @ Vanilla.

    2-part where you should work with vanilla : to modify or create plug in handle the post information that comes from part one.

    to be more specific the button will collect the post information and send them to vanilla. or you can simply just send the post id and let our plug in @ vanilla access the database gather the information and start a new discussion.

    it seems that your did the second part with a great job :) but having an option not to sync every post every thing to the forums and giving the user the choice to discuss or not will decrease the unwanted (undiscuss able posts) in the forums.

    also may one of yours community member comes with a great topic @ the forums and you want to blog that post you can reverse the two steps.

    finally its sad that I'm just talking here no code :( but not familiar with php myself and i don't have the time to be right now ( a full graduation semester :) )


    so i hope these ideas was useful for you guys. and thx again Squirrel for the great extension.
  6.  # 6
    Uploaded version 1.0.3 of Janine.
    •  
      CommentAuthorsquirrel
    • CommentTimeMar 7th 2007
     # 7
    /me kicks self, buries head in hands...

    Wow, I can't believe I missed this. One of the first requirements I set for Janine was that it should respect the WordPress "allow comments" setting for each post. Looking at my code, I can even see where Janine gets the 'comment_status' field from the WP tables... and then drops it on the floor. I just completely spaced out on hooking that up properly. Man. Wow.

    So... Yeah, that's fixed now. Version 1.0.3 is up with my apologies. Thanks for catching this, ideve!
    •  
      CommentAuthorsquirrel
    • CommentTimeMar 7th 2007 edited
     # 8
    A question from circuit, from an older Janine thread:
    is it possible to only create a forum post when a blog is posted in certain categories? no big deal if not, but it would make my life a bit easier!

    Can Janine do this automatically? Right now, no, and I'm not sure it should. There are some ways to fake this though...

    Idea #1: Use the "allow comments" checkbox (which now works properly) to tell Janine which posts should get new discussions.

    Idea #2: If you want "allow comments" to always be on (because you're also using WordPress comments maybe? I dunno) then create a blank "VanillaDiscussion" field in every post that should not get a discussion. If this field exists in the post, Janine will assume it already has a discussion and leave it alone.

    Hope this helps.
  9.  # 9
    Uploaded version 1.0.4 of Janine.
    •  
      CommentAuthorsquirrel
    • CommentTimeMar 19th 2007 edited
     # 10
    • Broke out lots of code into conditionally loaded include files.

    • Fixed several mistakes in the 'DEBUG' (postback) ping method.

    • Made warnings into proper dictionary entries (and made them more descriptive).

    • Additions and improvements to the documentation (there's more documentation than code now).

    If anyone else gets Janine to work on a live site, please let me know because I also have a dancing frog that you might be interested in.
  11.  # 11
    Installed 1.0.4. Went through every line item in the docs. Created two test posts (with "allow comments" on). No discussions were created. These posts also did not have the custom field that is supposed to be created.

    The really odd thing is that when I looked at the site or the first time today, there was a discussion in Vanilla for a blog entry I did YESTERDAY. The last time I looked at the board, it was completely empty. Now there is this one discussion. That discussion DOES have the custom field.

    Another thing is that I edited all my theme files as per your docs. But I still have the "no comments" link showing up on the new entry (perhaps your instructions don't remove that?). Of course there is also no "discussion" link to the discussion that doesn't exist.
    • CommentAuthorDetective
    • CommentTimeMar 19th 2007
     # 12

    If anyone else gets Janine to work on a live site, please let me know because I also have a dancing frog that you might be interested in.


    I use Janine. It works perfectly. I only have one problem but i think it's wordpress fault: when i edit some random old post, Janine gets pinged so it creates a new discussion... of course now i know that using this would avoid that:


    Idea #2: If you want "allow comments" to always be on (because you're also using WordPress comments maybe? I dunno) then create a blank "VanillaDiscussion" field in every post that should not get a discussion. If this field exists in the post, Janine will assume it already has a discussion and leave it alone.


    Thanks for such a great extension :)
  13.  # 13
    Detective is using WP 2.1.2, Vanilla 1.1.2. :/

    I looked at this site: http://www.ryuuko.cl/ and it has a blog, but the links go to WP comments, not to the board at http://www.ryuuko.cl/comunidad/.
  14.  # 14
    I need help installing this. I followed the instructions to the letter and double checked everything I can't seem to make this work. The only thing I can think of that is not letting this work together is that they are not sharing the same mysql data base. could that be the problem. HELP! Thanks...
  15.  # 15
    never mind i just read something else about another data base. i need to have them on the same database...
  16.  # 16
    Ok forget that... I just reinstalled Vanilla onto the same database. (fresh and clean install) and I still can't get it to work. So I still need help. Thank you...
    • CommentAuthorDetective
    • CommentTimeMar 19th 2007 edited
     # 17

    Detective is using WP 2.1.2, Vanilla 1.1.2. :/
    I looked at this site: http://www.ryuuko.cl/ and it has a blog, but the links go to WP comments, not to the board at http://www.ryuuko.cl/comunidad/.


    Check http://www.ryuuko.cl/2007/03/18/previa-de-hokuto-no-ken/ . Right after the article there's a link to "Discusión en la Comunidad".

    We're going to change our site template soon.... and WP comments won't appear ;) BTW, i followed Squirrel instructions: get the value for the custom field, add the link, and voilà! It works.
  18.  # 18
    I see, Detective...I think. So you have the link to the forum at the end of the FULL article (along with WP comments), but you have only a link to WP comments on the home page?

    BTW, i followed Squirrel instructions: get the value for the custom field, add the link, and voilà! It works.


    I'm not sure what you mean. What is it that you are making work this way. Are you doing it manually?
    •  
      CommentAuthorsquirrel
    • CommentTimeMar 19th 2007 edited
     # 19
    I believe Detective means that he read the instructions in the "Adding the Discussion Link" section of the README.html and adapted them for the theme he uses on his site.

    This is the most difficult part of the install because it's the part I can't provide step-by-step instructions for. Everyone's theme is going to be different. I gave instructions for the "WordPress Default" theme because everybody has it so that's the best way to demonstrate the technique you'll need.

    In your case, you are using the MistyLook theme. The example for that is slightly different.

    In "Main Index Template":

    Look for this:
    <?php comments_popup_link('(0)', '(1)','(%)')?> | <a href="<?php the_permalink(); ?>" title="Permalink: <?php echo wptexturize(strip_tags(stripslashes($post->post_title), '')); ?>" rel="bookmark">#</a> <?php edit_post_link('(edit)'); ?>
    Replace with this:
    <?php if (comments_open() && ($vanilla_link = get_post_meta($post->ID, 'VanillaDiscussion', true))) { echo ("<a href=\"{$vanilla_link}\">(D)</a> |"); } ?> <a href="<?php the_permalink(); ?>" title="Permalink: <?php echo wptexturize(strip_tags(stripslashes($post->post_title), '')); ?>" rel="bookmark">#</a> <?php edit_post_link('(edit)'); ?>

    Look for this:
    <p class="postmetadata">Posted in <?php the_category(', ') ?> | <?php comments_popup_link('No Comments &#187;', '1 Comment &#187;', '% Comments &#187;'); ?></p>
    Replace with this:
    <p class="postmetadata">Posted in <?php the_category(', ') ?><?php if (comments_open() && ($vanilla_link = get_post_meta($post->ID, 'VanillaDiscussion', true))) { echo (" | <a href=\"{$vanilla_link}\">Discussion &#187;</a>"); } ?></p>

    The next one is called "Archives". There are actually two of them, and let me send a big thank-you to the theme author for creating two templates with the same name. You want the first "Archives", the one that corresponds to archive.php:

    Look for this:
    Posted in <?php the_category(', ') ?> on <?php the_time('M jS, Y') ?> <?php edit_post_link('Edit', '', ' | '); ?> <?php comments_popup_link('No Comments &#187;', '1 Comment &#187;', '% Comments &#187;'); ?> </p>
    Replace with this:
    Posted in <?php the_category(', ') ?> on <?php the_time('M jS, Y') ?><?php edit_post_link('Edit', ' | ', ''); ?><?php if (comments_open() && ($vanilla_link = get_post_meta($post->ID, 'VanillaDiscussion', true))) { echo (" | <a href=\"{$vanilla_link}\">Discussion &#187;</a>"); } ?></p>

    In "Single Post":

    Look for this:
    <p class="postmetadata">Posted in <?php the_category(', ') ?> | <?php comments_number('No Comments', '1 Comment','% Comments')?></p>
    Replace with this:
    <p class="postmetadata">Posted in <?php the_category(', ') ?><?php if (comments_open() && ($vanilla_link = get_post_meta($post->ID, 'VanillaDiscussion', true))) { echo (" | <a href=\"{$vanilla_link}\">Discussion &#187;</a>"); } ?></p>

    Look for this and delete it:
    <?php comments_template(); ?>

    Finally, in "functions.php":

    Look for this:
    There are <?php global $numposts;echo $numposts; ?> Posts and <?php global $numcmnts;echo $numcmnts;?> Comments so far.
    Replace with this:
    There are <?php global $numposts;echo $numposts; ?> Posts so far.

    There might be more but I think that covers it. Here's what the result should look like.
  20.  # 20
    I read the ReadMe, too, and thought I implemented it correctly. :/

    So, I removed Mistylook from the server, and reinstalled a clean copy in case I had messed it up. Then I made the changes you suggested. It still didn't work.

    THEN I noticed the LITTLE TEEN UNOBTRUSIVE "If this file were writable you could edit it." So I had been editing the code, but the new code wasn't being saved. (That's really deceptive.) Auughhh! With the new install, forgot to CHMOD so that I could edit it from the Theme Editor.

    Made changes directly to the files....now it looks most lovely.

    Sheesh.

    OK, so, if I understand this correctly, it all seems to be working except that we have to log out and force the postback manually? Right?
    •  
      CommentAuthorsquirrel
    • CommentTimeMar 20th 2007
     # 21
    You shouldn't have to use the postback, that's the part that's really bothering me. I wish I had this problem on my setup, then at least I could debug it. It makes me fear that there's some quirk in your webserver config that causes the XML-RPC ping from WordPress to be delayed or skipped altogether. There is some precedent for this; I've read that previous versions of WP had problems with the ping, so... yeah. I just don't know how to even start looking for this. >:(

    There is another way, though.

    Janine needs some way to keep track of "did I already create a discussion for this blog post?". Right now I'm doing that by sticking a "VanillaDiscussion" field into WordPress. I chose this method because it meant I didn't have to alter the structure of any database tables. It's a bit more elegant from a coding perspective, but from the users' perspective dealing with the "VanillaDiscussion" field is a huge pain in the ass.

    BUT, I could just suck it up and add a `BlogPostID` field to the Vanilla discussion table. Now instead of looking for a special custom field in your blog post, all you have to do is put in a link to extension.php with the ID of your post, for example: http://yoursite.com/path/to/vanilla/extension.php?PostBackAction=JanineUpdate&BlogPostID=14. When a user clicks on this link, the following things would happen:

    1. Janine searches the discussions table for a record with BlogPostID equal to 14 (or whatever).

    2. If the discussion doesn't exist, Janine creates it.

    3. Janine automatically bounces the user to the correct discussion URL.

    So now you don't have to hassle with a "VanillaDiscussion" field, you don't even touch the WP database at all (which is nifty), you have a much more reliable way to know if the discussion already exists or not, the discussion isn't even created until someone actually wants to comment, you can use Janine with virtually any blog (not just XML-RPC enabled ones), and you don't have to wonder what's happening behind your back.

    Yeah, I'm steadily convincing myself that this is a good idea.

    There are two big disadvantages: 1. You have to either alter the discussions table or create a new table that maps discussions to blog posts (probably the second is better), and 2. The database is being modified by an HTTP GET request. Number 2 bothers me more because it's not good web programming practice, but I think the overall risk of abuse is low.

    So... high upside, low risk, and not too much work to add. I could even keep the XML-RPC functionality, no reason to lose it. Okay, I talked myself into it. Time to start coding Janine 1.1.0.
  22.  # 22
    Yea, squirrel, what you said. Most of it was entirely over my head, but you convinced me way back at, "hello."

    Is there a Superior Extension Support Award where I can put in a nomination?
    •  
      CommentAuthorsquirrel
    • CommentTimeMar 21st 2007
     # 23
    I just want it to work and work well. I'm not employed in a coding job right now, so I have to do stuff like this to stay in shape.

    Everything I described is now coded, but not tested. I doubt I'll get it done tonight, though, so thank you for being patient. Janine 1.1.0 should be up within 24 hours.
  24.  # 24
    Awesome. I'm waiting with bated (but ever-so-patient patient) breath.
    • CommentAuthorchanzero
    • CommentTimeMar 21st 2007 edited
     # 25
    i think i like this idea also :)

    on my site we have A LOT of posts but not a lot of feedback, so as it is now i would have a ton of empty discussions in the forum. i was even trying to think ahead of a way to put, say, all the press releases into a separate forum for that very reason -- they're just not the kind of thing that people usually comment on. so janine 1.1.0 would make for a much cleaner forum and database for a site like mine

    one downside is that you won't have people browsing the forum and finding an article via the auto-generated post, but that's i guess ok -- can always use add-ons like feedreader to get the latest blog posts in the sidebar

    i know alison and i haven't been able to get the current janine working so hopefully things go well with 1.1.0 for everyone :)
    • CommentAuthorxtc
    • CommentTimeMar 21st 2007
     # 26
    Hi, i ran into the same problem as most frustrater doods here. Janine just wouldn't work. I pinpointed the problem to a charset setting issue. I use UTF8 as the charset for wordpress, this makes the xml data, that is sent to the xml-rpc ping parser, be enconded in UTF8 thus non standard characters are enconded weirdly for Janine (which is written in some other enconding). Problem exactly happens in default.php at this line:

    if ( (strpos($RawData, '<?xml') === 0)

    the < is not a standard character, thus encoded diferently, thus making them not findable, so the xml-rpc ping works, it's just discarded by the extension.

    My solution was to encode that file (default.php) entirely to UTF8. I'll wait to see how this is solved.

    Posible Solutions:

    -Use regexps.

    -Use utf8_decode / utf8_encode and the functions to detect utf8 data.

    -Search for another string into de xml ping data.

    Contact me for anything you need. Hope to be helpfull
    • CommentAuthorxtc
    • CommentTimeMar 21st 2007
     # 27
    squirrel i can help right now. I have some hours devoted to this blog/forum for college and hope to get it done in less than 3 hours, so i could work helping you with thi snow ^^

    Gimme a call

    I'll got shower
    • CommentAuthorchanzero
    • CommentTimeMar 21st 2007
     # 28
    fyi, my encoding is ISO-8859-1. i chose that because i had some formatting problems with old content i had ported into WP
    • CommentAuthorxtc
    • CommentTimeMar 21st 2007 edited
     # 29
    chanzero but yours work right?
  30.  # 30
    Hey xtc, glad to have more input.

    My encoding is UTF-8.
    • CommentAuthorchanzero
    • CommentTimeMar 21st 2007
     # 31
    xtc: no, i have to do PostBackAction=JanineUpdate to force the update like alison
    • CommentAuthorxtc
    • CommentTimeMar 21st 2007
     # 32
    try looking for the solution in default.php here:

    if ($Context->SelfUrl == 'extension.php') {

    if (@$_SERVER['REQUEST_METHOD'] == 'POST') {
    $RawData = '';
    $RawData .= trim(@$GLOBALS['HTTP_RAW_POST_DATA']);
    if ( (strpos($RawData, '<?xml') === 0) && (strpos($RawData, 'weblogUpdates.ping') !== FALSE) ) {
    $JaninePingMethod = 'XML-RPC';
    }

    } else if (@$Context->Configuration['JanineAllowPostBack']) {
    if (ForceIncomingString('PostBackAction', '') == 'JanineUpdate') {
    $JaninePingMethod = 'DEBUG';
    }
    }

    }

    Janine wouldn't match any of the two options since i have PostBackAction = 0 and it wouldn't find the info it searches for in the xml-rpc data. I still think it is encoding problems, because the only weird behaviour happened when matching with strpos, maybe you are using latin iso charset and janine is written in come no latin ansi, maybe ascii, so it doesn't find the thing anyway.

    Let me know if i can help in any other way.

    btw, this is the site i'm deploying. Is for coordination for a college class. http://pub2.halles.cl/
    It's Vanilla + WP, trying to integrate as much as posible. Still working on it so you'll see a crippled forum :p
    • CommentAuthorxtc
    • CommentTimeMar 21st 2007
     # 33
    i know this is off topic but i need a quick help, is there a way to move the side bar to the right without making changes iun the theming sourcecode ?
  34.  # 34
    Nice integration xtc. I really like how you wrapped the forum to match the site. I've got to figure out how to do that.

    Did you search the rest of the forum for help with the sidebar issue? If you can't find anything there, start a new discussion. Those who can help will be more likely to see it.
    • CommentAuthorxtc
    • CommentTimeMar 21st 2007
     # 35
    i had to modify the theme structure source code to match the wordpress theme, and then applied the same stylesheet :p

    fo moving the sidebar to the right i just floated it to the right with css. Also i changed the position of the sidebar in the wordpress theme, so i could use the same stylesheet.

    If you need any help i'll be glad to provide.
    •  
      CommentAuthorsquirrel
    • CommentTimeMar 21st 2007
     # 36
    I don't get it.

    The first 128 characters of latin1 (ISO-8859-1) have exactly the same encoding in UTF-8. The '<' and '>' fall in this range so I don't know how they could be any more "standard". When I convert default.php to UTF-8 the two files are byte-for-byte identical. Also my WordPress encoding is UTF-8 the same as Alison and it's no trouble for me.

    I did find one possible problem in how Janine gets the raw post data. If your PHP has the register_globals option turned off then the $GLOBALS['HTTP_RAW_POST_DATA'] will be empty. To fix this in Janine, open the default.php and look for the following lines:
    $RawData = '';
    $RawData .= trim(@$GLOBALS['HTTP_RAW_POST_DATA']);
    Replace with the following line:
    $RawData = isset($HTTP_RAW_POST_DATA) ? trim($HTTP_RAW_POST_DATA) : trim(file_get_contents('php://input'));
    But this is the kind of thing that either works or it doesn't. It wouldn't account for the lone successful XML-RPC ping that Alison saw on her setup. Try it anyway if you have a mind to. I'll include this fix in Janine 1.1.0 just because it's more "correct".
  37.  # 37
    squirrel, I just made the changes you suggested. Then I made a new post, logged out, and forced the postback action. This is what I got:


    Some problems were encountered
    Janine says: Comments are not allowed for the most recent blog post.
    • CommentAuthorchanzero
    • CommentTimeMar 21st 2007
     # 38
    that didn't change anything for me. nothing posted and JanineUpdate still said i had to be logged out; and then when i was logged out JanineUpdate said it had posted the discussion for me.

    thanks for your continued work on this :)
    • CommentAuthorxtc
    • CommentTimeMar 22nd 2007
     # 39
    hm... i'll test this some more, maybe i can spot the weirdness.

    squirrel

    About the method you want to implement, on how Janine keeps track of Wp-posts that have plugin. AS i understood you would store all data in Janine's table (or whatever) so wp can't access it directly. I can help making a plugin for wordpress that would integrate this feature for theme usage.
    •  
      CommentAuthorsquirrel
    • CommentTimeMar 22nd 2007
     # 40
    Thanks, xtc, but no need for a WP plugin. If Janine keeps a record of posts-to-discussions then Janine can simply look up the discussion that matches the blog's post ID and redirect the user with a header bounce. It works quite well, I'm just finishing the debugging now.
    • CommentAuthorxtc
    • CommentTimeMar 22nd 2007
     # 41
    cool :) I suppose that the theme line for the linking will be based on *if_comments_are_open()* or something like that....

    btw, take a look at my thing, i think i won't do anything else for integrating, does the job i need.

    http://pub2.halles.cl/
    •  
      CommentAuthorsquirrel
    • CommentTimeMar 22nd 2007
     # 42
    I hit some snags in testing and they took longer to work out than I thought. It's going well, but I've gotta push 1.1.0 back until tomorrow. Sorry!
  43.  # 43
    Uploaded version 1.1.0 of Janine.
    •  
      CommentAuthorsquirrel
    • CommentTimeMar 23rd 2007
     # 44
    It's done and it works. It's more than twice as big, but over half of that is documentation. I highly recommend you read that documentation because it has everything you need to know to upgrade from versions 1.0.X.

    No more PHP, squirrel eat now...
    •  
      CommentAuthoralast
    • CommentTimeMar 23rd 2007 edited
     # 45
    thanks, great.

    BTW: in case anyone's inetersted, a bit of good news for mac-users. As some, perhaps, know already, there is a way of integrating Wordpress with Rapidweaver:

    http://nilrogsplace.se/webdesign/rapidweaver/tutorials/wordpress/index_en.html

    In case you've done that, there's no need to mess around with WP templates. You can insert all the necessary stuff right into your RW blog-page and cutomise it there according to your needs. Since everyone will be redirected from the original WP page to the one you create with RW, it doesn't really matter how the former looks like (unless you are a purist :))

    And, of course, most of the language customisation is then also done in RW. Unfortunately, encoding still doesn't work with the data extracted by Janine, though.
    •  
      CommentAuthoralast
    • CommentTimeMar 23rd 2007 edited
     # 46
    and still... some thoughts, squirrel, for after you've eaten.

    i was thinking about the interchangeability of commenting in the blog and discussing on the forum options. imagine a user who, through some deeper integration between Vanilla and Wordpress, by registering at the forum acquires also a WP account. you can also imagine this user wanting to integrate her WP-blog into a personal site, perhaps located on another server. it is also quite possible that she might want some of the posts on that blog to be starting new discussion threads on the forum but to have others commented upon separately on that personal site of hers, while not being visible to the forum at all. why not? in that case, i am not sure whether BOTH 'comment' and 'discuss' options should be present in each post, or should the user have an option of choosing which one (if any) to display...
    • CommentAuthorchanzero
    • CommentTimeMar 23rd 2007 edited
     # 47
    ok, i have installed the new janine and now when i do JanineUpdate i get no error so i assume it's working -- i still have to edit my WP pages to have the janine commenting links on there before i can test that. will report back shortly :)
  48.  # 48
    Sigh.

    I downloaded the new Janine, but ran into confusion. It's got two folders in the folder. One is called "Janine" and the ReadMe has info up through version 1.1.0. The other is called "Janine-1.1.0" but the ReadMe only has info up to 1.0.4.

    In other words, the FOLDER with the most up-do-date name SEEMS to have the OLD info. Which one do I use?

    Then, reading the seemingly newer ReadMe's "Upgrading from Versions 1.0.X, its seems I may have done something bad. Before reading anything (!) I disabled Janine in my test Vanilla and then deleted the old Janine from my server. Was that bad? Maybe not.

    FWIW, all the blog postings are dummies anyway, so I can just delete them all and start over...

    Any update chanzero?
  49.  # 49
    I can't get the new version to work at all. Just doesn't post anything in Vanilla. I did a complete removal of Janine from the database and everything. Then I installed it fresh and it still doesn't work. I am at a loss. I noticed I can't force the post either because there is no Allowed Post Back option anymore so I can't force it. Anyways I need guidance. Thank you.
  50.  # 50
    Michel, obviously I don't have this working either, so I may be off base, but if I understood correctly, this version will NOT automatically post a discussion. I think ??? that you have to click on the link in the post before it will make one.

    I think that explains chanzero's comment that it seemed to be working, but he wouldn't be sure until he added the Janine comment links to his theme. I think. Hope. Or something.

    Someone who knows something is free to correct me.

1 to 50 of 137

  1. <
  2. 1
  3. 2
  4. 3
  5. >