When you need to split your page or post into multiple pages then all you have to do is type.

<!--nextpage-->

into the HTML editor where you would like your page splits to appear.

After dealing with a lot of .htaccess files in connection with several websites. If you uncompress a .zip or transfer the file from a web server to your desktop via FTP, the file never shows up. Thus making very difficult to edit.

A file that starts with a period is one of the files that OS X hides by default so that you don’t accidentally delete and or alter it thus messing up your file system. However, there could be times that you want access to those hidden mac files. Strangely Apple has not made easy as toggling a menu item in the Finder.

Here is a simple and free solution for you to follow the following few steps. After writing a line or two of code you’ll be able to use Apple’s Automator software to create a plugin that you can use to toggle the view of hidden files from within Finder.

After opening Automator, select Automator from within the Applications Library on the left-hand side. You’ll now see a number of different built-in actions that are available to the Automator application.

Select Run Shell Script from the list of available actions, and drag it into your workflow.

Type (or paste in) the following code into the Run Shell Script text box:

defaults write com.apple.finder AppleShowAllFiles TRUE

killall Finder

What I’d wanted to do is display the comments without the viewer having to click “1 comment” or “2 comments” and take them to another page. Your theme has this code in some or all of these files: index.php, single.php, archives.php.

To display the full comment and option to reply instead of the “click for comments” link.

In the appropriate file, replace the code that looks something like this:

<p><?php the_tags(); ?><?php edit_post_link('Edit',' ',''); ?
> <br /><?php comments_popup_link ('Click here to Comment on this post',
'1 Comment- click to read', '% Comments - click to read'); ?> </p>

<?php
  $withcomments = "1";comments_template();
?>

I wanted to have a page that people could get to from a URL only and if you make the page private in the admin option then this will remove the page from the menu, and you will be able to access it by entering the URL. However take note that when you log out you will not be able to see the page contents. This also goes for you users.

So if you want to publish a page that public people can see full content from just hitting a URL then you need to publish it and then exclude it from the navigational function. Find your function.php and then modify the code. Wordpress creates the menu with this function: wp_list_pages();

You can either remove that function and add your own links, or add the “exclude” argument to wp_list_pages(); like this: wp_list_pages(‘exclude=1,2,39′);

The numbers are the page id’s. You can find the page id from the manage pages section of your wordpress blog admin. This method however did not work for me as my nav menu have a drop down ability. So I had to code it like this.

wp_list_pages(‘include=1,2,39&title_li=’);

You can read about all the options on this Wordpress Development Page

Good luck in coding your page.

In the settings tab you are allowed to change the home page URL. However this will break your wordpress site. It auto redirect both the front and back end pages. You can not log back and and fix it. You must go into your MySQL database and change the table field. You must go to the wp_options table and then the siteurl field and change it back.

Also on a side note if you want to make a sub page your blog page and not the home page you can also do this in the settings. Go to the reading tab and then create a page, it will be blank, then select it the post page field.

After adding a title to my index.php page I started to get this error.

Warning: Cannot modify header information – headers already sent by (output started at /Library/WebServer/Documents/ Websites/forestgumpsays/index.php:3) in /Library/WebServer/Documents/ Websites/forestgumpsays/wp-includes/pluggable.php on line 391

After looking at many similar error posts I figured out the problem. This is what it means. On index.php line3 there is an error indicated. However the problem is that the <?php tag hs a line space before it. Or the <? tag has a space after it. The odd part is that it was only showing an error when I hit the non www domain name. So check the file indicated in the first part of the error. The pluggable.php file is fine it is the one catching the error.

I also had a similar error problem on a new wordpress install in the config file. Turns out that there was an extra line at the end of the document. I hope this post helps the next person to quickly fix their similar php error problem.