Forum Replies Created

Viewing 15 replies - 226 through 240 (of 406 total)
  • asechrest

    (@asechrest)

    Check to see if your theme is using edit_post_link().

    This function should automatically check to make sure 1) the user is logged in and 2) has the appropriate user permissions to edit the post.

    Forum: Fixing WordPress
    In reply to: Header Categories
    asechrest

    (@asechrest)

    I can guess that you’ve got code for a nav bar in your theme header.php file. Search for the applicable code and comment it out. It may utilize wp_list_pages(), so that could be a function for you to look for to find the section of code.

    This is just a best guess, since I don’t even have a link to your site.

    asechrest

    (@asechrest)

    You can take a look at Role Manager and/or Role Scoper plugins.

    asechrest

    (@asechrest)

    If you right click on your page and view source, you can see the line of code I mentioned toward the bottom. I was assuming that code was inserted into one of your theme files, and if so it has to be one of the theme files used on the home page because I don’t see that link on your other pages. I guess there’s a possiblility it’s not actually being inserted into the file, but it’s probably beyond my ability to troubleshoot if so.

    I’d download each of the main theme files one-by-one and search for a portion of that code in each to see if you can find it.

    asechrest

    (@asechrest)

    The code adding that “wp” link looks like this:

    <p style="color:#c0c0c0;font-size:10px"><a href="http://www.andreabaccega.com/category/wp-reciprocal-links/" title="Wordpress Seo plugin">wp</a></p>

    Looks like it’s probably inserted in your index.php. Or check footer.php. Remove the code.

    asechrest

    (@asechrest)

    @ L S

    I really think your expectations are based on a false premise – that the software can or should be designed with the absolute beginner in mind. Unfortunately, setting up a self-hosted WordPress blog requires a certain level of knowledge at the outset, and to attempt to design the software and documentation for all skill levels below that would be inefficient and unsuccessful.

    You would not expect for the owner’s manual of a Cessna to teach you how to fly, just as you should not expect the WordPress documentation to guide you through simple navigation of your server file system.

    Certainly the WordPress docs could outline what comes before /home/ in your server directory filestructure. But then we’re on a slippery slope. Should the docs drill down even further and explain what a filesystem is? Should they be suitable for someone who can barely open up a browser and navigate to WordPress.org? Or someone who doesn’t even know what a server is? I would suggest that the answer is probably no.

    Basic setup of a WordPress.org blog presupposes you have a certain level of skill. If you’re not at this level, you can certainly work up to it, but I don’t think it should be — or can be — the responsibility of the WordPress documentation to bring poeple of all skill levels below that up to speed.

    So if you’re willing, keep at it and understand that for a self-hosted blogging solution, WordPress really is “easy,” compared to other solutions on the market. If you can’t or don’t want to put in the time, as others have mentioned, Blogger or WordPress.com are better solutions for you.

    asechrest

    (@asechrest)

    If you don’t want to touch any PHP, you can try a plugin like List Category Posts.

    asechrest

    (@asechrest)

    Remember, once you add a widget to a sidebar, you need to hit the save button before clicking the edit link on the widget.

    asechrest

    (@asechrest)

    I tested that code outside the loop in my author.php and got nothing. Maybe paste the code where you say it’s working?

    Logically and per the codex, the_author() shouldn’t work unless you’re querying a post, so if you use it outside the Loop in an index.php, how does it know what author to display?

    asechrest

    (@asechrest)

    Not sure, you could use a pastebin to post the code for comparison and then link to it here. Myself or others could try taking a look.

    Let us know if that works for you.

    asechrest

    (@asechrest)

    As MichaelH mentioned, I don’t think the_author() works unless you use it within a WordPress loop. Yes, the retrieval of all posts by an author is a loop, but unless you use the_author() within that coded loop, it won’t work.

    I don’t think that second segment of code you posted is in a WordPress Loop. If it was, you’d get that display for every post listed. Which I’m sure is not what you want.

    What I think you want is something at the top of the page that displays the author’s name (i.e. outside the Loop). If so, try using something like this before the loop in the template that controls your author display:

    <?php
    			if(isset($_GET['author_name'])) :
    				$curauth = get_userdatabylogin($author_name);
    			else :
    				$curauth = get_userdata(intval($author));
    			endif;
    			?>
    			<?php $auth_ID = $curauth->ID; ?>
    			<div class="left_author">
    			<?php echo get_avatar($curauth->ID, '96' ); ?>
    			<h2>Author: <?php echo $curauth->nickname; ?></h2>
    ?>

    [EDIT] – Don’t cut and paste this code, it’s got my own div names and is probably missing some closing tags. You’ll be able to use most of it, though.

    asechrest

    (@asechrest)

    [EDITED] – For some reason I originally thought it hadn’t worked for you. Now I notice you posted back to say it worked.

    asechrest

    (@asechrest)

    Also, I assume this is actually the cause of the problem. If this doesn’t fix it, you can post back to see if myself or others have another idea.

    asechrest

    (@asechrest)

    It should be within that post. Go into the WP back end and edit that first post. Switch to HTML view in the write post editor and then close your image in the appropriate spot with an </img> tag.

    Don’t forget to double check each post’s content, not just the underlying code in the .php files.

    Also, many of these types of errors can be tracked down and fixed through site validation. It’s fairly common for a failure to close tags to cause layout errors.

    I wrote up a couple of posts (Part 1 and 2) here: How To: Validating Your Site the Easy Way.

    Hopefully that’ll help.

Viewing 15 replies - 226 through 240 (of 406 total)