Forum Replies Created

Viewing 15 replies - 31 through 45 (of 66 total)
  • Thread Starter doubledubs

    (@doubledubs)

    Thanks for the reply. I don’t get many replies here (I usually figure it out myself after 2 days of pure anguish) which is why I post my own solutions.

    My plug-in directory is set at 755 and the footnote plugin is also at 755.

    My intention is just to avoid mistagging my footnotes from here on out. ??

    Thread Starter doubledubs

    (@doubledubs)

    I’m going to leave this unresolved for now, but here’s what I think the problem is. If anyone else has experienced this, let me know. In the meantime, I’ll have this fully tested by April 16, 2006. Since it’s on a live blog, I can’t really run test posts.

    The very strange thing about this problem was that the plug-ins (subscribe2 with wp-cron) worked perfectly on my test site. When ported to the production site, it stopped working.

    Solution:
    It appears that future dated posts that were written prior to the installation of wp-cron will not be recognized by the susbscribe2 and wp-chron plug-ins for e-mail distribution. I can’t figure out why this would be, but when I create a new post or a new future dated post, each one e-mails shortly after the publish date/time. The exceptions are posts I wrote prior to the installation of subscribe2 and wp-cron.

    In order to get everything notifying subscribers by e-mail, I think if I edit each post (add a few words and re-save), those posts will then e-mail to the distribution list. I’ll let you all know next week.

    Thread Starter doubledubs

    (@doubledubs)

    OK – I figured it out. The problem was not a server error as I correctly assumed (the error logs made no sense).

    The problem was with the tagging of my footnotes plug-in that I still love. I left an open footnote tag that was improperly formatted (it’s supposed to be a double open paren to indicate the beginning of a new footnote – I put a single open paren). This apparrently caused both the individual post page and the index.php that it was sitting in to fail.

    Twolf:

    I’ve been having major problems with subscribe2. While it’s actually working for new posts, my blog needed wp-cron by the same plug-in author and I have not gotten it to work. I love using plug-ins, but when plug-in authors have decided not to support their work anymore, it’s probably time to move on.

    I’m about to start using feedblitz instead. Sorry I can’t help, but the feedblitz service should be much more reliable if you don’t mind the feedblitz logo on all e-mails.

    This may not be what you’re looking for, but you could use this plugin to create a series. You’d then be able to link to a post and with each post in the series have a list of all the other posts in cronological order. Just a thought.

    Thread Starter doubledubs

    (@doubledubs)

    Thanks Handy Solo. The .topnav at 100% doesn’t do it, but let me play around with the divs. I’ll let you know how that goes. (I really suck at CSS)

    Thread Starter doubledubs

    (@doubledubs)

    Well, I’m not one to bump my questions, but since only 3 of my last 10 questions have been answered, I’m gonna bump this one more time. I just can’t figure this one out.

    Thanks!!

    Thread Starter doubledubs

    (@doubledubs)

    I’m bumping this cus I figure someone around here knows and I’ve tried everything else already.

    Here’s the HTML

    /*
    <table>
    <tr valign=”top” bgcolor=”#ffffff”>
    <td>
    <ul class=”topnav”>
    <li <?php if(is_home()) { echo ‘class=”current_page_item”‘;} ?>>“>Home
    <?php wp_list_pages(‘title_li=’) ;?>

    </td>
    <td>
    <form method=”get” id=”sform” action=”<?php bloginfo(‘home’); ?>/”><input type=”text” id=”q” value=”<?php echo wp_specialchars($s, 1); ?>” name=”s” size=”15″ /><input type=”submit” name=”submit” value=”Search” /> </form>
    </td>
    </tr>
    </table>
    */
    And here’s the CSS
    /*
    #search input{
    width:175px;
    font-size: 0.85em;
    background:#fff;
    color:#963;
    margin-top:2px;
    }
    .topnav
    {
    list-style:none;
    margin:0px 0 0 0;
    padding:5px 0;
    text-align:left;
    width:60%;
    min-width:65em;
    max-width:65em;
    }
    .topnav li
    {
    list-style:none;
    margin:0;
    padding:0 5px;
    display:inline;
    }
    .topnav li a
    {
    color:#000031;
    padding:3px 0;
    text-decoration:none;
    }
    .topnav li a:hover, .topnav li.current_page_item a
    {
    color:#CE6531;
    padding:3px 0;
    text-decoration:none;
    border-bottom:#CE6531 2px solid;
    }
    */

    OK – I suppose what I’d do is put the code on page.php and edit out the 10 pages you don’t want it on. I’d help with exact code, but it’s all trial and error for me. I use the codex help. Thry this to see if it has what you’re looking for:

    https://codex.www.ads-software.com/Conditional_Tags

    You can add the conditional statement for each piece of html code you’re adding. I’d hate to manage 100 pages like that, perhaps someone else has a better way.

    I’m not sure how it is that you don’t have page.php. Are you talking about posts then? These should show on single.php I think. Either way, you should have both page.php and single.php.

    I think the confusion lies in the fact that you created all the pages in WP.

    Therefore, if you edit the page.php file, it will generally apply the HTML code to every page, not just one. To edit the html and have it display differently in each page, you’d have some massive if, else type statements that you’d manage on an ongoing basis.

    What everyone seems to be saying is that you created the page in WP, you can add that image in WP.

    There are a couple of plugins that might be out there that allow you to add an image based on the category of the post, but I’m not sure that’s quite what you want.

    If you’re willing to go into each page, it seems the best way is through the WYSIWYG page editor. If this is not what you’re looking for, please explain why.

    Jesse:

    I can’t answer your template question, but I am subscribed through bloglines. ??

    I use this theme on my blog with no issues (WP 2.0, not 2.02). I also have the pesky IE sidebar problem, but do a search on IE problems in the forums. You will see that this is an IE problem, not a problem with this particular theme (as far as I know).

    Thanks!!! Very helpful.

    Thread Starter doubledubs

    (@doubledubs)

    That’s what I thought. Thank you.

    Wonderful theme. In general it’s great looking. On the post pages I love how the comments sit on the right side of the page, not under the post.

    Well done. Just a couple of things:

    When viewed on 1280×1024 screen resolution, the content is pushed to the left half of the screen leaving over 50% of the real estate on the right side white. It’s a bit too much empty space for my taste. Then again, it is called “whitespace”

    I’m also not thrilled about the red lines down the left side of the screen (indicating content). I didn’t think it was necessary. However, perhaps something more subtle (instead of red over grey, perhaps two shades of grey?) But just my opinion…

Viewing 15 replies - 31 through 45 (of 66 total)