Announcing the first official Pligg CMS template that allows voting up and voting down stories!
By clicking on the up or down arrows in "The Standard" template, the number will increase or decrease by 1 vote. This means that it is possible for stories to receive either zero votes or a negative number of votes. In order for a story to become published it must reach the positive number specified in the Pligg admin panel (Admin > Configure > Voting > Votes to Publish). Once the displayed number reaches the Votes to Publish number it will move it to the published section and will remain there no matter how many negative votes are then cast. This means that stories will have a more difficult time reaching the front page and I recommend that users drop their Votes to Publish number to 3 or 4 rather than the default 5 if they choose to use this template or voting method. Read more about this template on the official blog post announcement.

I discovered a bit of a problem in how Pligg handles child comments, so editing story.php is needed for Pligg 1.0.0 sites to display child comments correctly. Directions for doing this simple edit can be found in the README.txt file included with the download.

I included a customized version of the sidebar comments module to change the design of the comments in the sidebar. I wanted to match the look of the story comments. Just overwrite the existing module that came with Pligg 1.0.0 and make sure that you have activated it from your Admin > Modules page.If you don't like blue color used in "The Standard", try out "Sunshine Standard". It's an addon .zip file that includes alternate images and CSS to change the color to an orange template. A screenshot of Sunshine can be seen below. I will not be updating this alternate style version so you will need to update Sunshine manually.

Mark this template as installed to receive support. I will only be providing limited support for this template, feel free to submit your own fixes and I'll add them to the SVN version of the template.

[Sjet]

I am currently modifying "The Standard" to my needs. Will it be ok to place adsense on it?

[Yankidank]

Originally Posted by Sjet

I am currently modifying "The Standard" to my needs. Will it be ok to place adsense on it?

Unless I specifically say otherwise for templates, it is fine to use my open source (free) templates and Pligg CMS for commercial websites.

[kandsgroup]

hi Yankidank

you done a grate job, "The Standard" is the really nice template ever i have seen. its very clean and simple.

i have used 2 commercial template before but i am not satisfy with that. because who visits the site using IE6 browsers they cant access the site. but in your template i don't have to worry about that. sure i will donate for your grate effort.

i need some help to modify the template. after adding some script there is a white space in the top & right side positions in the template. i cant find it in the css. please see the attached image and help me remove the spaces.

site

Thank you very much.

[gabs]

I loving it but got 2 problems in the hated IE7 grrrrrrrrr

JS error

PHP Code:

    <script>
    // This script makes the 2 columns match height
    function equalHeight(group) {
        tallest = 0;
        group.each(function() {
            thisHeight = $(this).height();
            if(thisHeight > tallest) {
                tallest = thisHeight;
            }
        });
        group.height(tallest);
    }
    $(document).ready(function() {
        equalHeight($(".column"));
    });
    </script> 


on this part:

PHP Code:

$(document).ready(function() { 


Yep IE is giving us an error but due to the number of categories I have the 2nd line of categories is being pushed into the page..

I have a feeling it might be the above JS but anyone else found a fix?

[gabs]

My fix for IE if you have to line of Cat's

find in categorues.css

PHP Code:

#categories {
width:980px;
height:35px;
} 


Change the height to 35xthe no of row e.g for 2 :

PHP Code:

#categories {
width:980px;
height:70px;
} 


Still working on some safari probs and the js error will update unless anyone else has a fix?

[Icon]

Yankidank,

I think there is a bug with submit step 2, if you have URL method 2 enabled, and don't insert a captcha comment, it rewrites the url to: http://www.example.com/submit.php?id=foo when you click the Back button.

I tested this on a clean version of the standard and my edited version. Double checked the .htaccess file and there doesn't seem to be a rule to deal with this.

I tried adding the rule:
RewriteRule ^submit/?$ submit.php?id=$1 [L]

But doesn't seem to be working.

It also loses all information that was typed prior to clicking submit. This may be an issue with the captcha module, but I haven't really dug in.

[DrHope]

I followed your instructions: Upload the templates and modules directories to the root of your Pligg site. Overwrite any files that may already exist. Then install the template from your Admin > Configure > Templates area by changing the default template name to "thestandard".

I get the message that 'thestandard' does not exist. In your template file I can find nothing that says 'thestandard.' I'm befuddled. What am I doing wrong?

[sloogy]

It seems like thestandard template doesnt work for pligg 1.1.1, is there going to be an update for this? it's a great template.

When "installing" (writing thestandard in the templates admin page) pligg doesn't save and apply the template, heck it doesn't even say that the template isn't supported in a text box. it just reverts back to the template it had.

[Yankidank]

You should see an error message that the template is not up to date with your version of Pligg. You may not be seeing this message because of missing language elements in your language file. Check the bottom most line in your language file, it should read as...

// End 1.1.1 Language File

It's a lot of extra time for me to maintain a template with each update. I have too much on my plate to try to maintain the 10 or so free templates that I have created. Anyone else is welcome to share their own updates.