Forum Replies Created

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

    (@chrish)

    I’m afraid not. I just went back to using local comments.

    ChrisH

    (@chrish)

    I would love to see this, also.

    Thread Starter ChrisH

    (@chrish)

    Hm. I’m not entirely sure how to apply those fixes to my page. Like the first one says, I did change the height of all the parent elements to 100%, and that gives the wrapper box some height, but not enough.

    Thread Starter ChrisH

    (@chrish)

    Yes, I did.

    Thread Starter ChrisH

    (@chrish)

    Well, it was just downloaded off the official Mozilla site yesterday, so it should be.

    Thread Starter ChrisH

    (@chrish)

    Update: Again, thanks for the help. It turns out, though, that it was neither of these issues. The template I was using was a variation of K2 (TripleK2); apparently it was mucking up the script, presumably because of the conflict between Sidebar Modules and the new integration of widgets into the core. I’m using the default layout now, and I’ll have to play with the template a bit before I can get back to normal.

    Thread Starter ChrisH

    (@chrish)

    Thanks very much, iscifi. I’ll check it out. Even if it doesn’t work, thank you. At least I don’t feel crazy now.

    Thread Starter ChrisH

    (@chrish)

    No, it tells me nothing. When I run the page, all I get is a big blank page.

    Actually, 2.1 is a significant improvement from the 2.0 series, and works incredibly well.

    Of course, if you’re having issues, you really should post what those issues are instead of complaining in an entirely useless manner.

    Otto: you keep saying this in every thread I’ve seen, and really, it just pisses me off. It’s not constructive. It’s dissmissive and patronizing, and sounds suspiciously like the old Microsoft approach: “It’s not a bug, it’s a feature.” A lot of people have raised legitimate concerns, and your approach is to imply that if we don’t understand that the new way of doing X is better, then we’re idiots.

    The blogroll is a particular problem to me, philosophically as well as practically. I was delighted when widgets came along and I no longer had to manually insert and reorder clusters of code for each category of link every time I wanted to modify my sidebar. Well, guess what? No more. Now I have to go back to manually working out code, as well as keeping in mind that the link category “books” is actually category “8” or something. In short, WordPress is now incapable of providing users with something that they could even get on Blogger, which is a very tangible step backward. Even worse, although I can work out the PHP, tedious as it may be, there are lots of people who can’t. A viable piece of open-source blogging software shouldn’t just brush off people who don’t know how to hand-code their links. The success of WP lies in the fact that it’s managed to be something more than just a toy for the geeks. I’ve been a prosyletizer for WordPress; I’ve been trying to get as many people away from Blogspot as I can, and although I’ll still do that, it has to be with the caveat that they’re better off using Blogrolling.com to maintain their links.

    ChrisH

    (@chrish)

    Let me add my voice to those dissenting. I’m going to be spending days getting my template to show my blogroll properly again, and am considering deep-sixing the whole damn thing and just going back to maintaining my lists on Blogrolling. The previous setup wasn’t perfect, but it was intuitive and easy to use, and you didn’t have to work out PHP code in order to modify each individual segment.

    I think what bothers me most is how condescending and dismissive Otto has consistently been about peoples’ concerns about this particular issue. In this thread and others, I get the feeling that he wants us to quit our damn whining and suck it up. That’s really the most frustrating thing, to see that kind of obliviousness to people’s concerns coming from a representative of a project that’s been such a great alternative to the top-down management of the big software projects. Now, we’re expected to adapt our needs to the WP way of doing things, rather than vice-versa.

    ChrisH

    (@chrish)

    I’m having problems with K2 also; has no one else found this, or addressed it?

    ChrisH

    (@chrish)

    I’d like to heartily recommend Ady’s plugin; it seems really well put-together, and I think that most people will find that it’s exactly what they’re looking for.

    I’m running into a problem, though, because of an odd idiosyncrisy of the blog I’m trying to import. Maybe someone here can make some suggestions about how I can work around it. What it boils down to is that the Post Title is linked differently in the RSS feed and in the actual post.

    First of all, the blog is a metablog; the format is that each post shows an excerpt from a post or article of interest elsewhere and then provides a link to the original.

    In the posts on Blogspot, this link is the Post Title. In short, the Post Title, instead of being an internal permalink, is an external link. In the feed, it’s a regular permalink. Thus, what I wind up with is a bunch of posts with excerpts with no reference back to the original. It’s as though someone had scissored the endnotes out of a reference work.

    I’ve been able to figure out that the layout feature responsible for this is that the template has been set up so that the contents of the “Link Field” are wrapped around the Post Title. Unfortunately, the help file for this feature seems to have been written for the Old Blogger. Any idea how I could map these links and tranfer them, or does anyone know how to change that template feature in the New Blogger lingo?

    Does anyone have any more insights on why this happens in Firefox? I don’t have the Tiger Admin plugin, but I still get the greyed-out boxes when using Firefox.

    Interesting. I’m having this same problem, and I was about to write about it. However, I don’t have the Tiger Admin plugin.

    My Firefox version is 1.5.0.3 (Mac). I haven’t tried it in IE, but it does work in Safari.

    Forum: Fixing WordPress
    In reply to: Blogging via Email

    Email posting is one of the most important features to me, and I’d really like to get some clarification on what it can and can’t do. It seems that there’s very little written in the codex about the proper uses and limits of email posts, and I was wondering if some people could help me work it out.

    * First: I understand that the emails should be in text format. That’s fine, and sensible.

    * However, text emails have caused some serious problems for me with line breaks, and I often find myself going back when I get home to adjust them. Often, I find that each line is ended with an ‘=’ sign, which is a pain in the butt to remove from each and every line. This seems to depend on whether I’m using Yahoo, Gmail, or my own server mail.

    * Is it possible to include codes other than simple text in the emails? If so, what codes are and aren’t allowed? This is where one of the major problems with the odd line breaks comes in; if I have a particularly long URL and it breaks between lines, it causes gibberish. Yesterday, I was able to post using blockquote tags, but the other stuff didn’t come through formatted as I would have liked it.

    * Is there any way of putting some kind of code in the email body to tell WP to put the post in a category other than the default?

    Thanks much.

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