Pro Socialgo > For web community software

Just playing around last night and made a few new actions for you to enjoy. These actions work best if the object effected is white, but, feel free to experiment. 

Instalation:  Goto your actions pallet and open the drop-down on the right corner, there you will see a option to "load Actions" navigate to the PSGsmokey action and load-er up. You can edit the action by double clicking on any of the options in the action, you might want to first copy it by dragging it to the new action button in the lower right of the pallet.

There are three actions to choose frome > Smokey glass > Smokey dark & Smokey fade. Good luck and let me know what you think. 

Download Photoshop Action Smokey








 

The problem with playing to much with individual page element styles, such as the "blog-post img" instead of broad site wide elements, such as just "img" is that your probably going to effect something somewhere you didn't want to. This is the case with our "img" style we did on the .blog entry in part 1 of this "tame your post" series.  If you jumped right in with our tutorial and have already styled your blog post images, you may not know it, but you have a problem. here it is:

 

When we styled our blog-entry images, we inadvertently styled the icons in our "comments view."

See the problem? When we styled our blog-entry images, we inadvertently styled the icons in our "comments view." Just click to comment on any of your posts and you will see the mess we have created in the individual post page. Hey don't get mad at me! I warned you at the end of the last tutorial.

We better fix this problem before your members see it. Here is how.
Each page in our socialgo templates has a individual body tag. Take our welcome page for instance, the individual body is "id=magazine." Wasn't that nice of them to do that for us. Now we can control each page with precise properties that only effect it's tag, and not the rest of the template. Don't go trying to do this all over the place just this minute, there are some problems with this especially in the forum and groups pages. I'll post on it later. for right now lets fix this image problem. 

To remove the styles from the icons above we will use the "body id="read" to zap the styles on the "h3 img" and the "p img" where the icons reside. 

It goes like this:


 

The code for the title and date looks something like this:

  Tame your post: part 1
  

   Published Saturday 24th January 2009 
  

The only place these icons show up is on the individual posts pages and the body id for these pages is "read." We're going to override or image styles that effect all images in a post by stylying all

's and the

.

We could just style the

's id of "entry-stats" But, I also don't want the image styles to effect andy inline images that might be in between

styles in the body of my blog.

Make two copies of the style we created for images in our posts... this one:

.blog-entry img {
        padding: 10px;
        
        background: #ebf1cf;
        border: 1px solid #e2e7b1;
}

In the first copy insert a h3:

.blog-entry h3 img {
        padding: 10px;
        
        background: #ebf1cf;
        border: 1px solid #e2e7b1;
}

In the second copy insert P:

.blog-entry p img {
        padding: 10px;
        
        background: #ebf1cf;
        border: 1px solid #e2e7b1;
}

Mow on both H3 and P styles change all values to zero or none, this will override the global "img" styles and tell just the h3 and p styles to zap the image styles. Here is the final product:

.blog-entry h3 img {
        padding: 0px;
        
        background: none;
        border: 0px solid #e2e7b1;
}

In the second copy insert P:

.blog-entry p img {
padding: 0px;
        
        background: none;
        border: 0px solid #e2e7b1;
}

With a comma, you could also do it in one declaration like so:

.blog-entry p img, .blog-entry p img {
padding: 0px;
        
        background: none;
        border: 0px solid #e2e7b1;
}

Next time we are going to look at the Comments link on our main blog page and see if we can make it a bit more noticeable.

<1 2 3 4