Forum Replies Created

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

    (@greghaspants)

    Archive.org is an excellent resource, but I don’t think they do their cacheing as often as Google does. Google had already cached an entry from a few days ago, whereas archive.org… well, I don’t know. They aren’t cacheing my site at all.
    As for feedster, I wish I had thought of that before. See, the problem I had with google cache is that it really screws up the HTML, if you choose to download the “just text” version. This is what I did. And it took a long time to fix, but now the site is back up and running. Still, feedster’s cache interface does not get in the way, and manages to do so without capitalizing every HTML tag. Sigh.

    Thread Starter greghaspants

    (@greghaspants)

    Okay, crisis averted. I managed to cull together most of the posts from Google’s cache. I do appreciate everyone’s kind words and help. Thanks for calming me down. 🙂

    Thread Starter greghaspants

    (@greghaspants)

    Scott: OH my goodness. I didn’t even think of that! I don’t think my post count has gone over even 40, so that’s a great way. I appreciate the suggestion.

    Thread Starter greghaspants

    (@greghaspants)

    It’s possible, but unlikely. Their main server had a hardware failure a couple of days ago, and I’ve only been on the temporary server for three days or so. I’ve fired off an email, just in case.

    The only differences I can spot between yours and mine are the following:

    • The “ifmodule” thing, which as you mentioned, is necessary.
    • The “/wp” at the beginning of every URL.

    So, I don’t really know what to say. It may be that your hosting provider doesn’t allow rewrite rules, but that would seem a bit silly to me.
    I’m probably miles off.
    The only thing I could possibly suggest is to use the permalink rewriting that does not use .htaccess. That’s where you have index.php between your site’s URL and the permalink path. Instructions are somewhere within the software, I think. But other that, I don’t know.

    Hmm. What does your .htaccess file look like?

    Forum: Plugins
    In reply to: Question re: the API
    Thread Starter greghaspants

    (@greghaspants)

    “Source code will be posted shortly.”
    Here you go: http://stuffandthings.org/pretend/stuff.txt
    Two ammendments to my post, if I may.

    1. The code as posted did not actually work when looking at the actual blog pages. Originally, instead of assigning different items to $to_return, I had a bunch of print statements. I lost that version. But, both versions cause the same problem anyway.
    2. I apologize for the loose formatting. I’m normally really really strict about that, but I’m just not feeling that tonight. It’s unprofessional, I am aware.

    Again, thanks in advance.

    Forum: Fixing WordPress
    In reply to: RSS, Atom, etc.

    Correct me if I’m wrong, but I think WordPress by default provides a number of feeds:

    • RSS 2
    • RSS 1
    • RSS .92
    • Atom .3

    Any more?

    Forum: Themes and Templates
    In reply to: menu alignment

    Hmm. It certainly does look much better on FF now.
    I’m not sure if you made the changes to the blockquote style definition. If not, add this between the <style> and </style> towards the top of the page:
    blockquote { margin: 0 !important; padding: 0 !important; }
    I’ll be crossing my fingers that it works, as I can’t experiment any more today.
    If this doesn’t fix it, then the problem likely has to do with the textarea box at the bottom of the page (ie, where a user would enter his/her comments) being too wide.

    I’m not sure you entirely understand WordPress. Three things that will probably help you:

    1. One installation of WordPress = One Weblog. In other words, one installation of WordPress is not meant to administer more than one weblog at a time.
    2. One installation of WordPress = One Directory. That is, unless you’re willing to hunt around the files and what-not to change a bunch of files names.
    3. WordPress’ registration feature is only to let multiple people post to the same weblog. It does not give them the ability to create another weblog, which is impossible anyway.

    Opensourcecms.com has a bunch of different content mgmt. systems you can try out, and last time I checked, some of them let users sign up for their own journal-type-things.

    Forum: Themes and Templates
    In reply to: menu alignment

    Oh, and another thing. I also shortened the comment box at the bottom to 40 columns; by itself, it didn’t fix anything, but you may want to shorten it anyway because padding in forms can be finnicky.

    Forum: Themes and Templates
    In reply to: menu alignment

    I was able to alleviate the problem by adding two items to

    ‘s style definition:
    margin: 0 !important;
    padding: 0 !important;
    For whatever reason, it’s now aligned on the left side of the containing div, but otherwise it looks just the same.
    Also, the design as it is doesn’t show correctly in Mozilla, with the menu overlapping the main column. I’d investigate why, but I’m tired and don’t feel like doing any work. 🙂
    Hope this helps!

    And, more mistakes. Bugger.
    Basically, anytime you see “$” you should put a dollar sign in it’s place. Apparently, the filter likes to decode special symbols and what-not.
    Sorry for the confusion, and the wasted space.

    Woops! Replace the second line of the first code snippet with the following:
    $blog = 1;
    (that should read: dollar-sign, then “blog” (no quotes), then ” = 1;” (no quotes again.)

    I don’t know too much about this, but I think you do.
    At the very least, at the top of any page you want to use with wordpress, you need to include the following header:
    <?php
    $blog = 1;
    require('wp-blog-header.php');
    ?>
    …but only if the new page is in the same folder as the main index template. If not, you have to replace wp-blog-header.php with the full address (i.e., http://theurlofyourwebsite.com/wp-blog-header.php).
    The other thing you may have to implement is the main loop, if you’re using the page to show a bunch of entries. That is,
    <?php if ($posts) { foreach ($posts as $post) { start_wp(); ?>
    (Insert code for what you want to show for each post – title, content, etc.)
    <?php } } else { // end foreach, end if any posts ?>
    (Insert what you want to show when no posts match the passed criteria)
    <?php } ?>
    Hope this helps!

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