Caleb left a comment last month. He was having problems creating protected blog posts (posts that can be read only by certain people who have the right password to access the posts). He had tried some Javascript but it hadn’t worked. So I decided to look into the problem.

As far as Blogsome is concerned, it’s easy to protect your posts. There’s no need to use any Javascript at all. When you write a post, there is a password box on the right hand side of the dashboard. Here’s one I filled in earlier over on a test blog. Notice the password field has been completed with the password ‘roger_rabbit’. If you decided to protect a post, do try to pick a better password than that.

Next time someone comes to your blog, this is what they will see.

I tried putting the wrong password in, as if I was a nosy visitor who was trying to guess it, but I was only allowed to read the post when I put the correct password in the box.

I tested this in Firefox 2.0 and Internet Explorer 6 and it worked ok in both browsers.

Updates: Password protection does seem to stop anyone from reading your protected post in an RSS feed reader. Have checked this in Google Reader and Bloglines. All you see for the protected entry is the line “There is no excerpt because this is a protected post”.

There is also a way to make your entire Blogsome blog private. No Javascript required. Matt Schinckel has the solution.

Next time you’re writing a post, scroll down toward the bottom of the ‘Write post’ page before you hit ‘publish’, and you will find the ‘Custom fields’ section.

Using the custom fields is easy. But what are they for? Well, let’s say I’ve just done my main post but I also want to mention what I’m reading at the moment or what television programmes I’m watching. That’s exactly the sort of thing that the Custom Fields section is for. Here’s an example of how to fill in the boxes:

As you can see, the ‘Key’ box is where you put what you’re doing (reading, listening to or watching something, or whatever). And the ‘Value’ box is where you give a little bit more information. It looks as if my secret is out, doesn’t it? According to the custom fields in the picture, I’m listening to Greenday.

After you have used the custom fields once or twice, the things that you enter in the ‘Key’ box will appear in a handy drop-down select box. Just choose the option you want. It’s as easy as that!

the_meta

There’s just one more thing you have to do though, before your custom field information will show up on the page.

Go to Manage>Files on your dashboard, and choose Posts. This will take you to where you can edit your post.html template.

Choose where you want your custom fields to show, and write {the_meta} in the file, as shown below. A good place to put custom fields is at the end of a post.

Styling custom fields

A quick look at the source code will show that custom fields are generated as an unordered list with the class of ‘post-meta’. Information entered in the ‘Key’ box is a span with the class of ‘post-meta-key’. If you are confident with CSS, custom fields can be styled just like any other element.

• Currently listening to: BBC News

There are lots of different ways to protect your email address from spammers and email harvesters. The safest way of all is not to put your email details on your website at all. Turning your email address into an image is another way, although that also means that your visitors can’t click on the image to send you a message: they have to copy the address from the image instead.

You can also use Javascript or hex values to encode your address, but it can take a while to find a suitable code snippet to use.

Blogsome users have another option: Smarty code. It’s easy, and here’s how to do it. Let’s suppose your real email address is **me@example.com**. Choose from one of the following:

Firstly, there’s this:

{mailto address="me@example.com" encode="javascript"}

Anyone looking at your blog source code will see this:

<script type="text/javascript">eval(unescape('%64%6f%63%75%6d%65%6e%74%2e%77%72%69%74%65%28%27%3c%61%20%68%72%65%66%3d%22%6d%61%69%6c%74%6f%3a%6d%65%40%65%78%61%6d%70%6c%65%2e%63%6f%6d%22%20%3e%6d%65%40%65%78%61%6d%70%6c%65%2e%63%6f%6d%3c%2f%61%3e%27%29%3b'))</script>

Or you could try doing this:

{mailto address="me@example.com" encode="hex"}

which looks like this:

<a href="&#109;&#97;&#105;&#108;&#116;&#111;&#58;%6d%65@%65%78%61%6d%70%6c%65.%63%6f%6d" >&#x6d;&#x65;&#x40;&#x65;&#x78;&#x61;&#x6d;&#x70;&#x6c;&#x65;&#x2e;&#x63;&#x6f;&#x6d;</a>

And finally there’s this:

{mailto address="me@example.com" encode="javascript_charcode"}

which returns this in the source code:

<script type="text/javascript" language="javascript">
<!--
{document.write(String.fromCharCode(60,97,32,104,114,101,102,61,34,109,97,105,108,116,111,58,109,101,64,101,120,97,109,112,108,101,46,99,111,109,34,32,62,109,101,64,101,120,97,109,112,108,101,46,99,111,109,60,47,97,62))}
//-->
</script>

Whenever someone leaves a comment on your Blogsome blog, the link usually includes the ‘nofollow’ attribute. This means that Google and other search engines don’t count it as a proper link. If you wish to reward your regular commenters with backlinks that Google does count, then go to your comments.html file and follow these simple steps:

1. Find the bit that says something like this: <cite>{comment_author_link}{_e text=" said"}:<br /></cite>.
2. Change it to: <cite><a href="{comment_author_url}">{comment_author}</a>
{_e text=" said"}:<br /></cite>.
3. Then find this: {comment_text},
4. And change it to this: {capture name='text_comment'}{comment_text}{/capture}
{$smarty.capture.text_comment|replace:'rel="nofollow"':''|replace:"rel='nofollow'":""}.

Have a look at the source code for any comments that have been left on your blog. If the changes have worked, you will not see ‘nofollow’ on any of the comments.

As always when making changes, remember to save a copy of your original comments.html file so that you can put it back in your template if, for any reason, the alterations don’t work for you.

source: http://standalone.blogsome.com/