Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)
  • …and it’s gone again. 🙁

    JOY! The feed is functioning again! Once more I feel in touch with the World of WordPress!

    doves take to the air, choirs burst into song, marching bands fill the street, old people kiss, grown men weep with happiness

    Yup. Same behaviour pattern as me. Self-hosted, used the Release Candidates until 2.7 was released officially (as Coltrane… when will we see a ‘Mobley’, Matt??) and all good initially I think, then… [pfffft]

    [sobs] How will I know what’s happening n the World of WordPress? [sniff] I’m so lonely! [weeps uncontrollably]

    @ BernardBorealis

    Sorry, no dice. I inserted the link (and had the same thing suddenly drop down as an option to select… which I’d never inserted before… so *that’s* weird), selected [update] (or “enter”, or whatever the button that isn’t “cancel” or “close” says) and got the same result: no feed information, and the ‘configure’ panel when selected again says the plug-in could not find an RSS or ATOM feed at that URL.

    Dang.

    I feel so out of touch with WordPress…

    And I’ve got my “Other WordPress News” not displaying anything, but if I select [configure], then the RSS field is pre-filled with this:

    Error: could not find an RSS or ATOM feed at that URL.

    Which is weird, as I’ve not put anything in there for it to reject.

    …help?

    HUZZAH! Not only can the plug-in be installed successfully, I can even activate it as well!!! I even installed the “xrds-simple” plug-in while about the job! Woo-HOO!

    Thank you for your continuing efforts on everyone’s behalf, oh Leader and Knower of Powerful Code.

    “Blog break-down” = activating it may have been successful, but the blog broke before I could get a confirmation of it. Sadly, I didn’t copy the error message. My bad.

    Without looking at the permissions on those files, I’ve tried to install the version of the plug-in released yesterday, and the result was a complete blog break-down, with an error code rooted in the plug-in folder.

    Using WordPress 2.6.3 and OpenID 3.1.1 on my own server, here’s what I’m getting when I activate the plug-in:

    Warning: require_once(login.php) [function.require-once]: failed to open stream:
    No such file or directory in
    MY_DOMAIN/BLOG_FOLDER/wp-content/plugins/openid/openid.php on line 30
    
    Fatal error: require_once() [function.require]: Failed opening required 'login.php'
    (include_path='MY_DOMAIN/BLOG_FOLDER/wp-content/plugins/openid:.:/usr/share/pear')
    in MY_DOMAIN/BLOG_FOLDER/wp-content/plugins/openid/openid.php on line 30

    So… anyone have a thought?

    I had the same situation (new server, no uploads permitted, same error reported) and followed the [delete] [re-create] [assign permissions] process and it worked fine for me as well.

    I did it slightly more easily than copying and re-naming, though. I opened up File-Zilla, connected to the server that my blog is on, deleted the naughty [uploads] folder completly, re-uploded the folder from my local disk, then drilled down the most recent branches of the tree, setting permissions of 777 as I went.

    Pity it has to open the door so wide to the world though.

Viewing 10 replies - 1 through 10 (of 10 total)