Forum Replies Created

Viewing 15 replies - 151 through 165 (of 350 total)
  • Thread Starter converting2wp

    (@converting2wp)

    Hmmm… A careful “export data from old site; drop table in new site; import data” didn’t fix the problem — but I copied and pasted from one PhpMyAdmin to another and things seem to be working now. Thanks.

    Thread Starter converting2wp

    (@converting2wp)

    Thanks. I’ll try exporting/importing the table because I did make some edits Contact Form section.

    Sometimes problems like this are due to an issue in the browser. Have you tried clearing the cache? Looking at it in a different browser?

    Despite the name, the plugin Sidebar Login works fine to put a login form on a page. Just

    1. create a template for the page,
    2. add code to the template to show the form or the content — probably using is_user_logged_in(), and
    3. use the template tag <?php sidebarlogin(); ?> to generate the form.

    The codex has a page on Roles and Capabilities

    [A characteristic of the forum is that some of the volunteers who respond don’t actually “live” here, so don’t take it personally when the responses trickle off.]

    The file above looks like comments.php – a file typically loaded only when a single post is being shown, so it doesn’t have anything to do with the “0 Comments” showing on your home page.

    In the Station 2.0.0 files, you will, however, find a file library/_post_footer.php. That file has the code

    <div class="left">
    <span><?php comments_number(0, 1, '%'); ?></span>
    <a href="<?php the_permalink(); ?>#comments" title="<?php _e('View Comments', TDOMAIN);?>">
    <?php _e('Comments',TDOMAIN)?></a>
    </div>

    That code is printing out the “0 Comments”. You can just delete those lines (or figure out what the correct conditional logic is, code that and return it to the theme developer). The same applies for the <div class=”right”> that generates the other part of the bar at the bottom of each post — you may want to take out the “Leave a Response” and just leave in the “Edit” post link.

    Since Station has a paid version, if you need additional help, that might be the way to go. It’s a fairly complex theme and if you want to be able to upgrade to get its new features, you would, I think, want the developer to know what your requirements are so that they can be included.

    wp_loginout: If people are logged out, they’ll see a “login” link. If logged in, they’ll see “logout”.

    wp_register: Shows a “Site Admin” link if the user is logged in. You don’t need the “if (…)” if you’ve turned off user registrations (see the link to the codex).

    Where you put the code depends on your theme. I often put it in the footer (out of the way unless you are looking for it). If you can find the code (in sidebar.php?) for

    However, some themes strongly encourage the use of widgets instead of changing the code in theme files. If you need this as a widget you might find a customizable Meta widget — custom-meta popped up in my search.

    There’s a related issue with the way the theme treats comments. If it doesn’t have a configuration option to turn off the “comments (#)” you’ll need to find the PHP file that generates that HTML and change it to generate what you want. If there’s a forum for the theme, someone else may have solved that problem and you might get a quicker response there.

    Here’s what I use for admin login/site admin when there’s no need for the “registration” and “subscribers” don’t need access to the backend.

    <ul>
    <li>
    <?php
    wp_loginout(); // can redirect to home page if appropriate
    ?>
    </li>
    <?php
    global $user_level;
    if (is_user_logged_in() && $user_level > 0) { wp_register( ); }
    ?>
    </ul>

    Or, simpler, what if you take out the “Categories” and the “UL” tags underneath it Doesn’t that give you your top level categories at the same level as “DU HQ”?

    But I may be completely missing your point.

    If your top-level categories don’t change often, you could put the text for them in the nav bar and then show just their children as in:

    http://codex.ww.wp.xz.cn/Template_Tags/wp_list_categories#Only_Show_Children_of_a_Category

    If you don’t want to worry about changing the menu when you add/delete a top-level category, you’ll need another loop in your menu code and you might use the get_categories and get_category_link functions.

    You’ll probably need to make sure the lists match up with what your theme/css is expecting, and decide whether a top level category with children is a link or not.

    TEMPLATEPATH and ABSPATH are WordPress symbolic constants which, as you’ve discovered, expand to the current theme directory and to the root of the WordPress install. If you don’t want to put your includes directory there, you need to change the path that you give to the PHP include function to be the path on the server to the directory. So maybe

    include ('/home/mylogin/public_html/includes/test-include.php');

    If you want to make the path “portable”, you can use one of the PHP variables for this:

    include($_SERVER['DOCUMENT_ROOT'].'/includes/test-include.php');

    Thanks! This was driving me crazy, but now that I’ve seen your comment it starts to make sense.

    converting2wp

    (@converting2wp)

    In the site you’re trying to mimic, there are three <div> sections in the footer, each styled with a class of footer_row (by which I think the author means “footer column”).

    #footer .footer_row {
      float:left;
      margin:0 10px 0 0;
      width:310px;
    }

    You need to make similar changes to your footer.php with the corresponding changes to your style.css.

    Now, how to get content into those sections? Well, you can hard code it in the footer.php, but if your content could be generated by a widget, you could also make each section its own “sidebar”. See the 2010 theme (default for WordPress 3.0) for an example of how this is done. You can also review the “Define Sidebars” section in the Codex for a brief overview.

    converting2wp

    (@converting2wp)

    This is a function of the theme.

    For instance, in my theme, the archive.php file has code that looks like

    <small><?php the_time('l, F jS, Y') ?></small>

    To delete the time stamp in your list of posts, simply delete that code from archive.php.

    the_time is a Template Tag and there are other tags that might be used to generate the date. If you look at the HTML code surrounding the date, you should be able to match it up with the PHP code in the theme files. [See this info on the template hierarchy for clues as to which files might be involved.]

    Note that the blog post may be displayed in several different contexts on the blog (in an archive, as a single post, on the front page of the blog), so there may be several different files in the theme that you’ll need to adjust to delete the date.

    Full disclosure: I run a few blogs where I don’t make frequent updates. I’ve come to terms with the fact that the “freshness” of the site is visible — and don’t mind the visitors seeing that things aren’t so new. If you use things like “archives by month” the visitors will have other ways to see how often you update the blog. If a frequency of once a week or a month or just “when there’s something to say” is what “works” for you, then I wouldn’t worry about making the post dates visible (though, of course, they can be deemphasized).

Viewing 15 replies - 151 through 165 (of 350 total)