Frumph

okay let’s go a different route and use the pages-<authorname>.php then

let me show you how to do that

This is a common use of the authors link in your posts info:

$post_author = "<span class=\"post-author\">".__('by','easel')." <a href=\"".get_author_posts_url( $authordata->ID, $authordata->user_nicename )."\">".get_the_author()."</a></span>\r\n";

basically, creating your own link to the pages in question, using the function get_author_posts_url .. instead of get_author_posts_url you can just create your own markup for the link directing to the correct location.. since $authordata is global for the post

you add global $authordata; to the top of the place where your posts code

then you can use $authordata->user_nicename as the pagename

<a href="/authors/<?php echo $authordata->user_nicename; ?>">

sort of thing which will be the link to the page for the author, but you need to adjust your posts section of how it displays the current post author link and modify it so it links to that page in question

well, you can customize the author.php to have any loop you want inside of it, posts custom post types or whatever you want, it’s basically a template file…

Which, really would be a heck of a lot simpler. The information you get from each author can be edited in the authors preferences in the wp-admin in the users panel and you can just grab that information directly.

Here is my author.php from my theme: https://github.com/Frumph/easel/blob/master/author.php you could use for reference if you wanted, notice that you can ‘add’ any loop you want to it since it’s just a template, like you would do with the page-author .. but this is a single page that encompasses everyone, don’t really need to add individual ones for each author imo. not to mention clicking their name on links goes to the author pages already so no extra coding…

just a thought.

So I take it since your style.css file is in /css/style.css which means relative to the root and not inside the theme directory itself you setup some code that looks at that directory as a theme directory?

.. Things are relative ya know, especially paths to template files.

<link rel="stylesheet" href="/css/style.css">

If that is off your root installation location and not inside wp-content/themes/leakcraft/ .. I seriously can see why you are having issues.

Your theme needs to be reworked and made proper coding starting at the ground up.

http://codex.wordpress.org/Theme_Development#Anatomy_of_a_Theme

http://leakcraft.com/wp-content/themes/leakcraft/style.css does not exist, which is where the themes section references what theme this is. How did you get appearance -> themes to recognize that it’s a viable theme to use?

Did you change it with ?

http://codex.wordpress.org/Editing_wp-config.php#Moving_themes_folder

Need more context, it could be something in the position you placed the code. For example if you added the <?php in a section that already had <?php marker enabled, it would do that.

Also it depends on the fatal error. If you could give us that fatal error – which can be found on your hostings php error log or on the screen, contact your hosting on setting up an error log if you don’t have one.

^ that’s actually probably an ‘ownership’ not permission situation, ls (directory view) listing the directory structure and check if the ownership is the same as the rest of the directories in the wp-content folder

More then likely it’s not. Which means that the FTP user itself isn’t setup that the web daemon can read the files from it. The best way to verify this is to actually http://yoururl.com/wp-content/plugins/ease-digital-downloads/ to see if it brings you back an error of some sort or if you have indexes on the listing of the directory contents

Since you’re using a VPS, it probably means you know what you’re doing, just verify that the FTP user you’re using is in the owner’s group of that httpd section, or in the httpd’s group. (if that’s the case of the situation) .. I’ve seen quite a few times that people are putting the files in the wrong section of the directory structure that has the stuff there but not the right one that is being read by the httpd.