Forum Replies Created

Viewing 15 replies - 1 through 15 (of 20 total)
  • Thread Starter bitwisemcgee

    (@bitwisemcgee)

    Alright gang, 1.0.0 is released, you can get it here: https://nymb.us/?page_id=45

    Thanks to all the people that tested on my sight, it helped a lot ??

    Let me know of any issues, and I’ll fix em!

    Thread Starter bitwisemcgee

    (@bitwisemcgee)

    That’s a great idea sphagum, I’ll definitely add that. It will most likely be something like
    CSS:
    content div: [text input]
    author link: [text input]

    etc.

    Thread Starter bitwisemcgee

    (@bitwisemcgee)

    I haven’t tested with trackbacks/pingbacks, so I’ll have to get to work on that. Also, the css was set to what the default comments had in the kubrick theme. You can look at the function ‘handleAsyncRet’ in expand-comments.js to see what the classNames are set to. I’ll be working on documentation for that sort of thing this weekend.

    Thread Starter bitwisemcgee

    (@bitwisemcgee)

    https://nymb.us/?page_id=45

    New version 0.6:
    No longer gets data from RSS, communicates to exp-com.php which talks to the sql server. This provides loads more functionality, plus a bit more straightforwardness.

    If you have 0.5 working, I highly suggest you hold on to it. If you want this one (for things like comment author links) then keep the two installs seperate, and follow the directions for 0.6. then turn off 0.5, and turn on 0.6 and see if it works. if something breaks, let me know, and revert. I’ll be watching this thread and the one on my site for problems.

    google / look at wp_list_cats, namely: https://wiki.www.ads-software.com/wp_list_cats and notice the “exclude” option. maybe not as fancy as you’d like, but that would work.

    Thread Starter bitwisemcgee

    (@bitwisemcgee)

    Good News! 0.5 is out, and I believe it will fix most if not all of the issues people are having.

    The problem was in the javascript that would find the div for the comments. I had it based on the default theme, which was rather silly of me. I now have it changed to a much more universal way, which just so happens to be faster/cleaner code. huzzah!

    anyway, download it and let me know if there are any issues ??

    Thread Starter bitwisemcgee

    (@bitwisemcgee)

    I just put version 0.4 up, big changes include:

    +Now has an options page for intro/outro (non-link text before and after link), expand/collapse text, and no-javascript text
    +new file exp-com.php: copy exp-com.php to the ROOT directory of your website and enable the fetch via exp-com.php option. This fixes the issue of rss feeds being on external sites. This is only partially tested with my setup, so let me know how this works for people.

    Thread Starter bitwisemcgee

    (@bitwisemcgee)

    well, I know that error is caused by a redirect error. I’m unfamiliar with what feedburner redirect does, but if it causes rss requests to be redirected to a different site, that would cause that error

    edit: okay, just looked at the feedburner stuff. If you have the feedburner cache on some other server, then yes, when the javascript requests the feed, it will be redirected. currently I’m debating using the feed anymore, since it might just be easier to make my own database queries for the comments.

    Thread Starter bitwisemcgee

    (@bitwisemcgee)

    BigDog, that’s a relatively easy fix. This is in the readme, but that error is from the browser not letting the javascript try and get data from a remote page. This is a security feature so js on pages don’t download stuff that could be ‘untrustworthy’.

    I had this issue when users would go to my site as https://www.nymb.us and click an expand link. For my setup, wordpress builds the rss links as https://nymb.us… so when the javascript would try and download the rss, firefox felt it was going to a different site (since, technically, https://www.nymb.us and nymb.us could be two different sites). My fix was to redirect all requests to https://www.nymb.us back to nymb.us

    also, 0.3 is up, with only minor changes until I get more information on the errors people are having. if you do have problems, try this one anwyway.

    Thread Starter bitwisemcgee

    (@bitwisemcgee)

    there was a problem with expand-comments.js being loaded via relativue url (/wp-content/plugins/expand-comments/expand-comments.js) but Viper’s install dir was different. version 0.2 should fix this. If you are using firefox, open the javascript console and click the link. If you get the error ‘makeAjaxRequest not defined’, that means the expand-comments.js file wasn’t sourced. could you post the link to the blog where the problem is?

    Thread Starter bitwisemcgee

    (@bitwisemcgee)

    no worries, hopefully the solution will pop up soon ??

    Most likely I’ll get to the other enhancements this weekend, namely:
    User defined link title (passed to the function)
    User defined ‘intro’ and ‘outro’ (non link items displayed before and after link)
    div is added only if comments exist

    if there are any other ideas, speak up!

    Thread Starter bitwisemcgee

    (@bitwisemcgee)

    odd, my guess is that it might be a result of some other errors on your page. Try adding some ‘alert(“got here”)’ type of stuff to see where the code is bombing out. If you don’t want to do that, try cleaning up the site until it validates, hopefully that will fix it.

    also, I’ve only tested this stuff in IE and FF, so other browsers might have issues. If you know it works for a certain browser, please let me know

    Thread Starter bitwisemcgee

    (@bitwisemcgee)

    hm, well, the js is working, and so is the ajax (since ‘Loading…’ is replaced, which is done by ajax) My first guess is that the js can’t find the div to put the comments into. do you know javascript? you can try and edit the expand-comments.php file so that the javascript inside there will do an ‘alert()’ with some debug info in it, namely, what it thinks appendDiv is in line 88. Perhaps just add ‘alert(appendDiv.id);’ after that line, and see what the alert says when you click the link

    Thread Starter bitwisemcgee

    (@bitwisemcgee)

    hm, I think you’re having a similar problem as viper, if I try and use the Expand Comments it says that makeAjaxRequest isn’t found (which lives in expand-comments.js). On your site, where is the plugin directory located? ie, I can browse directly to expand-comments.js by the following:
    https://nymb.us/wp-content/plugins/expand-comments/expand-comments.js
    but your is a 404, so I guess its a bit different for you.

    most likely I need to get the wp setting for plugin locations, rather than have it hard coded like I do. see if you can find how to browse to the javascript file, and post the url for it here

    thanks, and sorry for the trouble

    Thread Starter bitwisemcgee

    (@bitwisemcgee)

    there’s also an issue with the nature of AJAX that’s noted in the readme, namely, if a person is on your site at, say, https://www.site.com, and the wordpress install and all the links are at site.com (no www.) then the browser security will stop ajax from retrieving anything. Basically browsers think that you don’t want it to get data from anywhere but where you’re currently browsing.

    I haven’t had time to look into it too much, but my ‘quick fix’ is to redirect requests to https://www.nymb.us to nymb.us, and all works.

    where are you trying to get this to work at?

    edit: to clarify, if your RSS link is, say, https://nymb.us/?feed=rss2&p=39 but the user is at https://www.nymb.us, when they click the link, the ajax request is made to https://nymb.us/?feed=rss2&p=39, and NOT https://www.nymb.us/?feed=rss2&p=39. since technically these represent different sites to the browser, it fails, and the RSS is displayed instead.

Viewing 15 replies - 1 through 15 (of 20 total)