Forum Replies Created

Viewing 15 replies - 1 through 15 (of 43 total)
  • Thanks. I’m not sure that would work though if you just want to know if it’s a category archive with no particular category in mind. What weirded me out is it does know it’s an archive, it just doesn’t know what kind. Seems there was a conflict with Query Multiple Taxonomies plugin. But another problem’s cropped up having to do with custom taxonomies and custom post types but that’s another issue I guess with permalink flushing which doesn’t seem to solve it.

    ia

    (@sofimi)

    I tried to use <?php echo $album->name?> in a custom album template but it says “Album overview” instead of the name of the album. When I add

    $album = nggdb::find_album( get_query_var('album') );

    beforehand, the text goes blank. var_dump($album) gives bool(false).

    Is there any way to add the album title in the template without modifying the core code as advised by _ap_?

    Edit: Using WP 2.8.2 & NextGen Gallery 1.3.5.

    I’m having this same problem. I really hope the WordPress team would look into this. Perhaps we should raise this in the Ideas section too.

    Though my guess is that a database export-import (instead of the WXR/XML file upload) would fix this problem.

    This happens to me too (WordPress 2.3 and 2.6). Not sure if it’s exactly the same:

    I write a post, add a custom field. When I save or publish it, sometimes the value of the field isn’t saved so I have to edit at least one more time. But then when I finally publish it, meaning the Write Post page shows up, the value of the custom field which I added to the previous post shows up on that blank post.

    So what happens is the custom field gets filled in the “next” post, not in the “current”/”previous” post I wanted to publish.

    This is a bit different from my previous problem that produces multiple draft posts, which was resolved by 2.6 I think.

    ia

    (@sofimi)

    I have to pipe in too and say this happens to me always. I just upgraded to 2.6 and everything went smoothly except for this, exactly what db0 said.

    yeah, i do want to know how they got admin access as well. fyi, after i wrote about this security issue, the “WordPress” user appeared in the database(s) again. does this mean i’d have to generate new database passwords all over again? sigh.

    guys, i think somebody should “name” this vulnerability so it’s easier to remember. also, i wrote about it here.

    yep, it happened to me too. i first saw the version 2.5 string in the footer and was immediately suspicious, but at first i thought it was because i used the wpau plugin instead of the cpanel upgrade (which i used to install wp the first time around). turns out you have to trust your instincts. 🙂

    i’m also surprised all this happened on april 11 (mine on the 12th) as well.

    i’ve been watching this page and will continue to do so. i hope more people contribute because it was only a few days ago when i tried googling “wp-info.txt” and practically nothing came up.

    I agree with prairieprog. I’d rather have “draft hell” than wonder where the hell my drafts went. They should at least add a visible link either in the navigation menu beside Posts or at least above the list to the tune of “looking for your drafts? click here”.

    The improved drafts suggestion has been implemented in 2.3 but I say there’s still much to improve about it. Can we open a new thread in the Ideas section?

    I got the same thing. But I think I got a fix for it. Does the title of the feed you’re pulling have special characters in it? Like curly quotes or simply double quotes? Mine did and when I used the Blogroll manager to add the link first, and then edit the feed tied to it by going to the Syndicated link, it will work fine.

    The way I got it fixed was contacting the web host and asking them to fix the security issue (it seems that was the reason for the limit). It could be that for your case. 🙂

    Am having the same problem with Feedwordpress. I tried to add a new feed source and then it spewed this error:

    Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 147555 bytes) in /home/XXXXXX/XXXXXX/XXXXXX/wp-includes/wp-db.php on line 97

    Maybe it can’t handle too many feeds at the same time.

    just found this: http://fortes.com/projects/wordpress/top-level-cats/

    removes the “category” (or whatever string you used in place of it) before the category name in the permalink.

    In your Permalinks options, set your “Custom Structure” to

    /%category%/%postname%/

    and your “Category Base” to

    /.

    I’ve seen this solution on several threads here (e.g. link – closed but might prove useful), but the response to this is: does it work with paged archives, i.e., /%category%/page/2/? I’ve tried it (not in 2.1) and it doesn’t work. Just a heads-up. 🙂

    trent, even the browser wouldn’t detect the feed. i believe the page didn’t include the usual <link rel= etc to indicate that a feed was existent – perhaps it’s the template they used, u know how some blogger templates are like that. 🙂 thanks though.

    of greater concern for me though is still the blank content blogger feeds. any leads on that one?

    otto, either way, the blogger feeds aren’t working for feedwordpress for me. some blogger feeds aren’t even automatically detected by the software and i use the /feeds/posts/default (?) URL. i can’t figure why in heavens would feedwordpress be unable to support blogger feeds. 🙁

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