Thanks to @BrianFegter comment, I was able to find and fix the problem. It was just a problem of case-sensitivity. My development environment, http://serverpress.com/products/desktopserver/ , doesn’t have a problem with finding the pdf when the file name was caps and the anchor tag link was in lower case. My hosting provider seems to be the … Read more
I kept on searching, and finally found something that fixed this issue. For those who are using CentOs 7 in combination with Plesk 12: The issue is with SELinux. When it’s used in Enforcing mode (which is the default), wp-content does not show itself via FTP. Switching it to Permissive mode or disabling SELinux altogether … Read more
You first need to ask yourself: Will this theme ever be maintained or used by other people than me? If so, read on, if not, you should only build code that will eventually make sense to you when getting back to this project after a few years. If you are creating a theme that will … Read more
WordPress have a Codex entry just for you: https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory
I’ve usually seen a .well-known folder associated with site ownership validation for SSL certificates. You may find the following link from Server Fault may assist in further understanding. Maybe you can convince the Client to have a different folder name?
There are no “folders” in the CMS as the content is stored in a set of database tables, unless your site is created with the content inside the templates and not the content editor. A parent -> child page structure is possible and easy to organize. Simply assign the second level pages to a common … Read more
If there is a need for custom files e.g. CSS that need to be called, should a custom directory e.g. css be created under wp-content e.g. wp-content/css? No, never. You should not do this under any circumstances. A themes assets belong in the theme. A plugins assets belong in that plugin. The only exception is … Read more
see if this plugin can work for you: http://wordpress.org/extend/plugins/quick-pagepost-redirect-plugin/
The easiest way to achieve this is to add, Options -Indexes ..to your .htaccess file. Specifically your .htaccess file should look like this, # BEGIN WordPress Options -Indexes …etc …etc # END WordPress This is one way and probably the most efficient way. This method will prevent any direct access outside of blog posts, pages, … Read more
You could do either pretty easily or you could create a custom post type within your current installation and then you wouldn’t have to do either and you would only have one installation to manage.