$ yum install subversion
$ cd /var/www
$ mkdir django-src
$ cd django-src
$ svn co http://code.djangoproject.com/svn/django/trunk/
$ cd trunk
$ python setup.py install

Installing and Starting MySQL Server Here are commands needed to install and start MySQL:

$ yum install mysql-server
$ /etc/rc.d/init.d/mysqld start

Installing Python MySQL Support This is the trickiest part. Python talks to MySQL using software called MySQLdb. The version available in Centos via Yum is 1.2.1-1 and isn’t compatible with the most recent Django codebase. Because of this you must download and compile MySQLdb. Before compiling MySQLdb, enter the command below to make sure you have the necessary tools:

$ yum install python-devel mysql-devel gcc

Next, download the source tarball from SourceForge then follow these steps:

$ mv <name of MySQLdb tarball> ~
$ cd ~
$ tar zxvf <filename of MySQLdb tarball>
$ cd <name of resulting directory>
$ python setup.py build
$ python setup.py install

When these steps are completed you should be good to go.

What is Twitter Login?

Sign in with Twitter is the pattern of authentication that allows users to connect their Twitter account with third-party services in as little is one click. It utilizes OAuth and although the flow is very similar, the authorization URL and workflow differs slightly as described Here.

Why Twitter Login For Pligg?

• Easy Login
• No need to Register to Your System
• Increases Your pligg site’s user
• Oauth Authentication is Secure
• Less Spam
  

What do you Need ?

A Pligg Site, Twitter Api Key and Secret Key from your Twitter account

Demo:http://www.tweetrl.com

Buy Now Only Its Only  $25

Download and upload the following to your /js folder:

TwitterWidget

Open pligg.tpl, locate /body and add the following before:

{literal}
<script type=”text/javascript”><!–
var rpnetTwitAttrs = {
usernames: “enbeeone3,surfider”,
count: 5,
title: “Twitter Stream”,
showImages: true,
imageHeight: ‘48px’,
imageWidth: ‘48px’
};
// –></script>
<script type=”text/javascript” src=”http://www.domain.com/js/TwitterWidget.js”>
</script>
{/literal}

make sure you change the domain.com to whatever your url is.  The values for “username” can be changed to whatever Twitter id’s you want to display.

Open sidebar.tpl and add the following line where you want the stream to appear:

{if $pagename neq “story”}{assign var=sidebar_module value=”twitterstream”}{include file=$the_template_sidebar_modules.”/wrapper.tpl”}{/if}

Save and close.

Now, create a file called twitterstream.tpl and add the following to it:

<div>
<a id=”rpnet_twTitle” href=”#”>Twitter Stream</a></div>
<div id=”rpnet_twitterWidget”>

Get your username listed here by <a title=”Submit a tutorial” href=”http://www.domain.com/submit”>submitting tutorials</a></div>

Again, be sure to change domain.com to whatever your url is.

Save and upload to your sidebar_modules directory.

That’s it.

Notes:

Because of Twitter’s API limitations on the number of API calls in one hour, the stream may appear blank after a while, depending on the traffic to your site, if it does, you will need to wait until the hour is up.  I am hoping to have a cache feature added it to soon to prevent time outs.

Now you Make a Choice Again, Trade your $14.90 to your Own max, 10 Minutes of time

You can add a Retweet Button to your Own Website , http://tweetmeme.com/about/retweet_button

You Have a Choice whether you get it from http://www.pligg.com/pro/catalog/modules/ultimate-retweet-103.html , or spend just few minutes and add some codes to your Pligg site. You can Donate your $8.75 and Support Haiti , rather than Paying for the “ULTIMATE RETWEET” module that Pligg Pro shop is selling.

It’s actually quite simple.

Open, link_summary.tpl, add where you want the button to appear:

{literal}
<script type=”text/javascript”><!–mce:0–></script>
<script src=”http://tweetmeme.com/i/scripts/button.js” type=”text/javascript”><!–mce:1–></script>
{/literal}

That’s it.

When you’re doing one or two installations every so often, it’s no big, but for me it saves more time to tweak the installation files once so that I don’t need to worry about tweaking it on the backend later.

What are these tweaks?

• Custom admin username, admin display name, blog description, default category, and blog URL (I have a tendency of installing the WordPress files in their own directory separate from the blog’s home page)
• I’ve never been a huge fan of the phone home feature, so I’ve removed the blog address when checking for updates
• Although security by obscurity isn’t the greatest security defense, I still don’t feel comfortable advertising my blogging software and version, hence the WP generators have been removed from the head/RSS meta completely
• The default links and post/page/comment have been omitted because, frankly, I get tired of manually deleting them from every new installation
• Since the autosave/revision feature is overkill and DB bloat in most of my cases, I’ve added a line to the wp-config-sample.php file to disable it by default (of course, this only applies to installations that don’t already have an existing wp-config.php file handy)

Normally I don’t release these tweaks since they’re for my own personal use, but this time around, I figured why not?

Before downloading and using these WordPress files, please make sure you’re alright with the above—if not, don’t use them. Also, these files come with no warranties or guarantees—i.e. use at your own risk. If your server blows up or catches fire (highly unlikely), you’re on your own.

So, in this article I’ll run through 10 fairly straightforward ways that a beginning developer or blogger can customize their WordPress theme to ensure it doesn’t “look like a blog” — at least to a certain degree. Keep in mind that the goal here is not to hide the fact that a website is using WordPress — that’s quite difficult, if not impossible. The ultimate goal here is to help your website have a seamless, consistent, look and feel that does not necessarily scream “WordPress-driven” from the instant the home page loads up.

NOTE: These tips are for beginning WP developers who are coding themes for their own site, or experimenting with theme development. Most likely, these tips would not apply to custom downloaded themes that are pre-built and probably already have many of these customizations.

1. Customize Your Sidebar and Keep it Consistent

The sidebar in WordPress is a dead “giveaway” when a user visits your site. The sidebar will have default titles like “Blogroll”, “Categories” and “Archives”. You can easily change the text of these titles, and which sections are displayed, by editing the sidebar.php file in the theme directory. Also, WordPress displays a different sidebar depending on what page of the site you’re on, which can also be changed. I personally prefer to display virtually the same sidebar on all pages, to keep the site consistent.

Even if you’re not familiar with PHP, WordPress code is very developer-friendly, and easy to work with. A simple knowledge of how functions are called and how to open and close if statements is often more than enough to help you customize some of the sidebar code.

Also, you can easily duplicate and customize certain sidebar sections. Look at the sidebar here on Impressive Webs: You’ll notice there’s a list for “Articles” and “Tutorials”. This is done by duplicating the “categories” section and controlling what categories are displayed using parameters inside the function call for that particular section.

Check out the WordPress Codex for further information on customizing category listings.

2. Use “Decategorizer” Plugin for Cleaner URLs

One of the most obvious ways to customize the look of your blog’s urls is to use clean permalinks, rather than the default querystring driven url structure. But that’s an obvious one. No self-respecting blogger would fail to enable custom urls, which can be done easily through the WP dashboard.

But one thing you cannot do through the dashboard is remove the word “category” from links that point to specific categories on your site. That’s where Decategorizer comes in handy. This excellent plugin, which I’m using here on Impressive Webs, will strip the word “category” out of your WordPress urls, leaving a much cleaner experience, taking away the “blog” look and contributing to a more customized, branded feel for your website. Decategorizer will also automatically create 301 redirection for all your old category links, and works with subcategories.

The Decategorizer plugin had a few bugs, which have recently been corrected, and also requires that you install the Redirection plugin, for Decategorizer to work properly.

Be sure to read carefully the documentation and installation instructions for these plugins to ensure they are installed and functioning as expected.

3. Customize Metadata for Individual Posts

Every post has “metadata” contained inside of paragraph tags at the bottom of each blog post. This data is generated dynamically through the loop that pulls your content out of the database. You can easily edit, delete, or modify any of these pieces of data that are displayed with each entry, which can be found inside of the index.php file in your theme directory. The default look for the metadata section looks like this in WordPress 2.8.1:

<p class=“postmetadata”><?php the_tags(‘Tags: ’, ’, ’, ’<br />‘); ?> Posted in <?php the_category(‘, ’) ?> | <?php edit_post_link(‘Edit’, ”, ’ | ’); ?> <?php comments_popup_link(‘No Comments &#187;’, ’1 Comment &#187;’, ’% Comments &#187;’); ?></p>

By editing the above section of code, you can choose to display only comments and categories, and even alter the characters that are displayed. For example the » will display ». You have the option to remove those characters and use something more appropriate for your site’s look.

4. Disable Comments (Not Recommended)

This is not necessarily something I would recommend, since user-contributed comments are a huge part of the blogging world, however, it should definitely be pointed out that removing the “Post a Comment” section at the bottom of every post would be a sure-fire way to adjust your blog to ensure a more customized look and feel.

While this would contribute to a “non-blog” atmosphere on your website, it is highly recommended that you keep user comments open and instead customize the look of the comment area. Of course, if you’re using WordPress purely as a content management system for developing pages instead of “blog posts” then this would be an obvious choice, and would make more sense.

5. Don’t Use “Tags” or a “Tag Cloud” (Not Recommended)

Again, while this customization option is not necessarily recommended, it is certainly an effective way to customize your blog so that it does not resemble every other WordPress installation on the World Wide Web. “Tags” are keywords that you can add to individual posts in your WordPress dashboard. They are similar to categories, but provide a wider interrelationship between posts.

Tags associated with a particular post allow users to click on certain keywords to view more entries related to that keyword, similar to clicking on a specific category. Tags also provide SEO benefits, as they help Google and blog directories properly categorize your blog’s pages. So, while you do have the option to avoid using tags on your posts, thereby ensuring a cleaner look to your website, be aware of the drawbacks of doing so.

For simplicity, I personally do not use tags on Impressive Webs. I like each post to be associated with 1-3 categories, and nothing more. That’s just a personal preference to keep the content the primary focus. I prefer to attract users who will actually read the content, as opposed to the ones that are click-happy and bookmark everything.

6. Change the Default Display of the Title Bar Content

The header.php file in WordPress’s default theme has a title bar that is coded like this:

<title><?php wp_title(‘&laquo;’, true, ’right’); ?> <?php bloginfo(‘name’); ?></title>

Once again, you can see the « character that is highly overused in the web development industry. (Not to mention that it’s actually a left quotation mark for french text!) You can replace that character with a different one, and even change the way the page titles are displayed.

You’ll notice there’s a function called wp_title that holds 3 parameters (including the « character). The third parameter tells WordPress where to display the post title — to the left or to the right of your blog name.

You also have the option to remove the function that displays your blog’s name, and instead just manually enter a more keyword-friendly title. The blog name that displays in your Dashboard under “settings” will still display your official blog name on RSS readers.

7. Use the “Pages” Sidebar Section as Your Main Navigation

While I’ve already discussed a little bit about the sidebar, it’s worth mentioning separately that the “pages” section of the sidebar can easily serve as your main navigation bar. At first glance, nobody will even notice that this has been done.

In the default WP theme, here’s the code that generates the “pages” section of the sidebar, found in sidebar.php:

<?php wp_list_pages(‘title_li=<h2>Pages</h2>‘ ); ?>

Simply take that piece of code and place it wherever you want your main navigation to display. Of course, you’ll have to style it to your liking, in line with your theme’s look. And most likely you’ll want to remove the title of that section. You can do that by simply removing everything after the equals sign in the single parameter, so it will look like this:

<?php wp_list_pages(‘title_li=’ ); ?>

Use the WordPress Codex to see other ways to customize the look of the page list in the default wordpress theme.

8. Don’t Call Your Website a “Blog”

Okay, this is not really a WordPress tip, per se. It’s more of a marketing recommendation for the purpose of more effective branding in conjunction with a site that just happens to use WordPress as its engine. Serious websites that provide significant content are viewed as “communities” or “resources”, instead of “blogs”. The word “blog” nowadays is probably more appropriate for individuals who post thoughts and musings on various personal and professional topics.

If you have long-term plans for your website, and would like to expand it into a thriving online community that is respected and recognized in your industry, then you need to view it that way from the start, and communicate that atmosphere to your users — even if you are starting out small and really are just a single “blogger” posting thoughts and musings on relevant industry matters.

9. Remove or Customize Default Text and Title Attributes

While I’ve already touched on the customization of a few text elements of the default WordPress theme, there are other little text snippets that can be edited, removed, or appended to. An obvious example is the “Powered by WordPress” section in the footer. Your website’s footer seems simple, but it is potentially a significant part of your site’s look, feel, and overall image.

There are also title attributes that are embedded in anchor tags throughout the site. Here is one example, found in the index.php file:

<h2><a href=“<?php the_permalink() ?>” rel=“bookmark” title=“Permanent Link to <?php the_title_attribute(); ?>”><?php the_title(); ?></a></h2>

The code above is the section that will display the title of each post listed on your home page. The title attribute in the anchor tag has the super-obvious text of “Permanent link to …” and then the PHP function that spits out the title. You can modify this and other default text that appears throughout your WP theme.

10. Use “Nice Search” Plugin for Clean Search URLs

Nice Search is a very simple plugin that makes searches performed on your website look less “WordPress-y” and more like a custom search engine installed on your website. According to the author’s website:

“This is a really simple plugin that redirects your WordPress searches (?s=search-term) to the pretty-looking URI version: /search/search-term, and also converts spaces (%20) to plus symbols.”

Although this plugin has not been updated in some time, I do have it successfully running on WordPress 2.6.3 on another website, so it seems to be compatible with some of the more recent versions of WordPress.

Conclusion

I hope beginning WP theme developers, and possibly some intermediates, found these tips helpful. Most of this is compiled from my own personal, and somewhat limited experience with WordPress and PHP, so I’m sure there’s lots I’ve missed, and lots where I’ve simply stated the obvious.

I hope some of these tips will encourage “bloggers” to develop a more customized and branded look and feel to their site, allowing them to break free from blogging conformity.

Maybe you are looking at template companies demo and want to understand how they layed it out? Perhaps you are just a snoop.
Well it’s easy peasy to do this. Just add ?tp=1 to the end of a Joomla url, preferably a non SEF url.
You will then be able to see all the published modules on that page.

Here are a few examples.

• http://joomla.org?tp=1
• http://www.joomlajunkie.com?tp=1
• http://www.columbusgeek.com/?tp=1

While it is best to leave this message on your site as it helps spread the Joomla love, sometimes your clients do not want to partake in the love fest.

In Joomla 1.5.xx if you want to remove the footer, go to Extensions > Module Manager and unpublish the footer module. If you want to change the text, you need to get out your FTP client and do some changes.
Go to the language directory, go to the folder of the language you want to change, (in our case English), then find the mod_footer.ini. Search for “powered by” and change the text to whatever you want your text in the footer to be.

In some cases the template you are using might have it hard-coded in, or done differently. In this circumstance you should ask the developer of the template you are using.

Chances are, this wasn’t too high on your list, and you might overlook it until somebody mentions it to you in May.
There is no reason to have to do this yearly maintenance if you don’t mind doing a little cut and pasting.

First, find where your copyright is inserted. In Joomla, it is generally at the bottom of the templates index.php file. Depending on the template, it may be in a different location. Your mileage may vary.

Now, we will simply change the 2009 date, to this bit of php code:
(Remove the space after the < and before the >)

< ?php echo date('Y');? >

So it looks like this now.

Pretty sweet right?

We are pleased to announce that WordPress has won the Overall Best Open Source CMS Award in the 2009 Open Source CMS Awards. WordPress has won this Award for the first time in the past four years, earning itself a place in the Hall of Fame category for the Award next year.

While WordPress occupied the top spot in the Overall Award, the other two extremely popular finalists MODx and SilverStripe tied for the first runner up position. After Pixie and Pligg sharing a similar result for the Most Promising CMS category, this is the second time the combined opinion of judges and the public was evenly divided for two CMSes, awarding each of them a first runner up spot.

Here’s the distribution of the prize fund for this category:

WordPress: $4,000

MODx: $2,000

SilverStripe: $2,000

This final announcement marks the end of the 2009 Open Source CMS Award. The Award continued to be a great success with over 12,000 nominations and over 23,000 votes received across its five categories.

In addition to winning in the Overall Best Open Source CMS category, WordPress was named first runner-up in the Best Open Source PHP CMS category. This is significant because wordpress was not even in the top 5 last year, and now wordpress is #2, ahead of Joomla! As is stated on the Award site, “WordPress made its way into the top five for the first time. The fact that it was outranked by Drupal by a very slight margin indicates how popular it has become with users as well as developers over the past year.”

Every day thousands of new people are embracing WordPress to power not just their blogs but entire sites and communities without compromising on usability or scalability (as would be the case with a legacy CMS). Every member of the WordPress community, from core developer to beginning user, should be proud to be part of this momentum: congratulations to us all!

First of all, I think Drupal is a perfect match for President Barack Obama’s push for an open and transparent government — Drupal provides a great mix of traditional web content management features and social features that enable open communication and participation. This combination is what we refer to as social publishing and is why so many people use Drupal. Furthermore, I think Drupal is a great fit in terms of President Barack Obama’s desire to reduce cost and to act quickly. Drupal’s flexibility and modularity enables organizations to build sites quickly at lower cost than most other systems. In other words, Drupal is a great match for the U.S. government.

Second, this is a clear sign that governments realize that Open Source does not pose additional risks compared to proprietary software, and furthermore, that by moving away from proprietary software, they are not being locked into a particular technology, and that they can benefit from the innovation that is the result of thousands of developers collaborating on Drupal. It takes time to understand these things and to bring this change, so I congratulate the Obama administration for taking such an important leadership role in considering Open Source solutions.

Being one of the world’s largest consumers of computer software, the U.S. government is not new to Drupal. Several agencies, including the Department of Defense, the Department of Commerce, the Department of Education, and the General Service Administration have been using Drupal, for example. Drupal adoption is growing rapidly within the U.S. government. However, Whitehouse.gov switching to Drupal goes above and beyond any other Drupal installation within the U.S. government, and is a fantastic testament for Drupal and Open Source. It will raise awareness about Drupal across the U.S. government, and across all governments world-wide.

Personally, I’m thrilled by the idea that Drupal can help governments provide greater transparency, higher velocity, and more flexibility.

Feature are listed Below

• Easy to setup and configure

• Switch between 302 (temporary) and 301 (permanent) redirection

• Lists all your posts/pages/attachments with short links to each

• Shows the short link in the edit post/page form together with the text you can tweet out (trimmed to 140 characters) and a link to Twitter with the predefined text

• You can output the ShortURl in your themes using the `twitter_link()` function

• New function available: `permalink_to_twitter_link()` which takes a permalink as an argument and returns a Twitter Friendly Link (if exists)

• Compatible with Sociable, Twitter Tools, Tweet This, SexyBookmarks and AskApache Google 404 plugins

• Compatible with WordPress MU and BuddyPress

• Configurable linking relations (HTML and HTTP) for rel=shortlink, and rel=canonical

• Super easy tracking with Google Analytics! Destination links are Taggable!

• You can now switch to alphanumeric links for sexy links with numbers and letters like example.com/s2e7

• More coming up soon!

DOWNLOAD NOW!

• ImpressCMS :