WP-Twitter-Login

Who is this plugin for?

This plugin has been specially coded for intermediate to senior WordPress developers that want to develop a new web application using WordPress. The plugin can be configured easily and it has been coded to be very scalable. Users with no knowledge of PHP may find other solutions more helpful since this plugin doesn’t have any GUI. The main purpose of this plugin is to allow people to develop an app taking advantage of the high-converting one-click Twitter sign-up process and saving time in programming a User Authentication system.

How it works?

When a user accesses the URL ?tw=login in a WordPress website he is redirected to Twitter using Matt Harris’ OAuth library. Once authenticated, a new WordPress user is created picking all the information from the Twitter username. The WordPress username has a prefix (tw- by default) and his Twitter ID (the public username is not used here since it can be changed). The password is his Twitter ID with a custom salt. Extra information is stored in his user profile (nickname, full name, website, bio, etc.) as well as in custom user fields (oauth_token, oauth_token_secret, language, followers and friends count, profile image, etc.).

A caveat in WordPress is that it requires a valid and unique email address per user. Since Twitter does not provide you with the user’s email address, the plugin registers the user with an email address like tw-twitterid@domainname.com.

By default the plugin will not allow users to access WP-Admin which makes this plugin perfect for someone who will provide a service to registered users without ever showing the WordPress inner pages to them. You can enable access to WP-Admin changing a variable from true to false although you should disallow users from changing their password or they will not be able to log back in.

Download

Download the plugin from GitHub:

wp-twitter-login

License

This plugin is licensed under a MIT license. Feel free to use it in any commercial way.

Installation

1. Download the plugin and upload it to your plugins folder as you would do with any other WordPress plugin

2. Create a new app at Twitter here

3. Copy the Consumer Key and Consumer Secret and paste them in twitterlogin.php

4. Change the $salt variable to something long and complicated

5. Optionally, you can change the username prefix to something else to increase security

Retrieving user information

To see if a user is logged in through Twitter run is_user_logged_in() and then check if the username matches the Twitter prefix (tw- by default).

To retrieve the current user’s data do something like this:

global $current_user;
get_currentuserinfo();
echo 'Hello ' . $current_user->nickname;
echo 'User token: ' . $current_user->oauth_token;
echo '<img src="' . $current_user->profile_image_url . '" alt="" />';

To retrieve data from someone else do something like this:

$user_info = get_userdata($user_id);
echo 'Username: ' . $user_info->nickname;

Kohana’s official documentation is pretty complete and useful as well as well written. I have been studying it for a few days but wanted to read the tutorials also whenever I had no Internet connectivity. Searching on the Internet for PDFs or ePubs on Kohana didn’t really show much so I developed a little tool that extracts the official documentation and outputs it in one single file so you can read the official Kohana guide anywhere anytime.

You can download the documentation both in ePub, PDF and HTML formats. The ePub format does not have the images in it (I used an online tool and it removed them, there aren’t a lot anyway) but works great in the iPad, Kindle and Android tablets.

Kohana 3.2 Documentation in PDF format (mirror) (3.3MB)

Kohana 3.2 Documentation in ePub format (mirror) (240KB)

Kohana 3.2 Documentation in HTML format (mirror) (310KB)

I have done my best with the crawling tool but it hasn’t been 100% tested so some sections may have been skipped, please let me know in the comments if that’s the case.

Thanks to all the contributors to the Kohana Documentation, as I am still learning Kohana accept this as my little contribution to the framework :)

I mostly use the iPad for reading email, news and blogs although I am still perplexed at how few apps there are for actually doing some work. Well, to be honest, there are many apps to do some work. But I believe in platform-agnostic web-apps or SAAS to be the future of our world and the amount, variety and features of current web apps for web development is still quite scarce.

One of the big gaps that I found was regarding code editors. The lack of fast symbol typing in the keyboard is very frustrating and slow (you need to use iOS’s default keyboard and type 3 keys just to get a “<” sign, plus another one to get back). This is why I came up with a proof of concept on additional keyboard rows with extra keys for touch screen devices and added all symbols frequently used for coding and programming so you don’t need to keep switching from one keyboard set to another. It has been optimised for the iPad in portrait mode although with some responsive CSS queries and device detection it can be adapted anywhere.

The code itself is basic HTML, CSS and a bit of JavaScript and jQuery. I’ve kept it simple to aid scalability and customisation. This is how it looks:

Demo and download

Click the following link to open the Code Editor. To test it properly you will need an iPad in portrait mode.

iPad web-based code editor with extra symbols keyboard

License

Public Domain, keeping the Internet open. You can use it commercially and distribute it as much as you want without being forced to credit the author.

Changelog

If you have developed it further send me an email and I will include it in the next release and you in the Credits.

8 February 2012 (v1.0)

• First release

If you haven’t seen my iPad HTML/CSS template you must see it now.

I’m currently developing a WordPress plugin that needs to show a virtual page generated by my plugin (such as a form or a message) and I wanted to avoid adding a new Page and modifying the current WordPress installation, so every plugin form, message or page had to be generated on the fly without touching the database.

Some WordPress plugins or themes create new pages in the website’s installation to add advanced functionalities. As an example, WooCommerce adds new pages to the wp_posts database that help set up the website to work with it. In my opinion this is a mess, if you already have a WordPress website running, installing this theme/plugin will mess with your current page structures and whenever you want to uninstall it or deactivate it you will need to manually remove those pages created previously by the plugin. I once wanted to test an advanced WordPress theme that deleted all the current pages I had… that was the most annoying thing ever, since I already had written the content for the website and lost it (yes, I should have backed up but, who would expect a theme to delete and install pages without even a warning?).

A few weeks ago I posted a question in WordPress StackExchange but couldn’t really get the answer I was looking for, there was this solution to create fake posts but I wanted generate unlimited pages with simple code as possible and using friendly URLs like: http://example.com/?plugin_page=myfakepage (I could then easily use mod_rewrite to make them look even better). Today I kept investigating and finally came with the solution.

Step by step guide

We will load the page at http://example.com/ but modify its title, content and select a blank theme template so it looks like a complete new page.

Custom page content

First of all we create a function that will overwrite the content:

function plugin_myown_content() {
  $return = '
<p>Fill in this form:</p>
<form action="?" method="post">
  <input type="text" name="foo" value="bar" />
  <input type="submit" value="Connect" />
</form>
';
  return $return;
}

Custom page title

Now we overwrite the title of the page with this function:

function plugin_myown_title() {
  return "On the fly foobar form";
}

Default page template

With this function we force WordPress to load the default page template of the current active theme:

function plugin_myown_template() {
  include(TEMPLATEPATH."/page.php");
  exit;
}

Hook actions and filters

Finally, we add a simple ifto check if the user is requesting the plugin’s fake page and run WordPress hooks to load the 3 functions mentioned before and force WordPress into displaying the virtual page we have just generated.

if ($_GET['plugin_page'] == "myfakepage") {
  add_filter('the_title','plugin_myown_title');
  add_filter('the_content','plugin_myown_content');
  add_action('template_redirect', 'plugin_myown_template');
}

The code is pretty basic, from here you can add your desired PHP code to make it do whatever you want. You can also add more hooks to customize the page even further. I hope you get the idea. This code has been tested with the latest version of WordPress (3.3.1).

This is a little compilation I’ve made of my most used code snippets every time I build a prototype, website or theme. By following these steps you can save 80% of coding time for any HTML/CSS website or WordPress theme. For some of my projects I use the Zen Coding plugin to develop the HTML. Most of the CSS itself is optimized already using short names and what some people call OOCSS (Object Oriented CSS).

1. CSS Reset and Minimal Grid

Yahoo CSS Reset

/* Copyright (c) 2011, Yahoo! Inc. All rights reserved.
Code licensed under the BSD License:

http://developer.yahoo.com/yui/license.html

version: 2.9.0 */
html{color:#000;background:#FFF}body,div,dl,dt,dd,ul,ol,li,h1,h2,h3,h4,h5,h6,pre,code,form,fieldset,legend,input,button,textarea,select,p,blockquote,th,td{margin:0;padding:0}table{border-collapse:collapse;border-spacing:0}fieldset,img{border:0}address,button,caption,cite,code,dfn,em,input,optgroup,option,select,strong,textarea,th,var{font:inherit}del,ins{text-decoration:none}li{list-style:none}caption,th{text-align:left}h1,h2,h3,h4,h5,h6{font-size:100%;font-weight:normal}q:before,q:after{content:''}abbr,acronym{border:0;font-variant:normal}sup{vertical-align:baseline}sub{vertical-align:baseline}legend{color:#000}

960px Grid (12 cols, 60px width, 20px gutter)

/* Minimal Grid */
.g1{width:60px;}.g2{width:140px;}.g3{width:220px;}.g4{width:300px;}.g5{width:380px;}.g6{width:460px;}.g7{width:540px;}.g8{width:620px;}.g9{width:700px;}.g10{width:780px;}.g11{width:860px;}.g12{width:940px;}.g1,.g2,.g3,.g4,.g5,.g6,.g7,.g8,.g9,.g10,.g11,.g12{overflow:hidden;float:left;display:inline;margin:0 10px;}.r{width:960px;overflow:hidden;margin:0 auto;}.r .r{width:auto;display:inline-block;margin:0 -10px;}

CSS 100% box model

Padding, borders, margins and width equals 100%:

* {-webkit-box-sizing:border-box;-moz-box-sizing:border-box;box-sizing: border-box;}

Common CSS

/* Common CSS */
html {}body {font-family:Arial,sans-serif;font-size:14px;}
a{color:#0085d5;text-decoration:none}a:hover{}
li{display:inline}
h1,h2,h3,h4,h5,h6 {}
strong,.strong {font-weight:900}em,.em {font-style:italic}
.right{text-align:right}.center {text-align:center}
.fright{float:right}.fleft{float:left}
.hide{display:none}

Sprite map

/* Sprite */
#logo,.button,
.sprite{background:transparent url('images/sprite.jpg') no-repeat;}
.ico {display:inline-block;height:16px;width:16px}
.ico.aa {background-position:-px -px}

Forms and buttons

.button{background:#eee;border:1px solid #ccc;cursor:pointer;font-weight:900;padding:5px 10px;text-decoration:none}

CSS for the coming HTML template

/* Main structure */
#wrap {}
#header {}
 #logo {}
  #logo span {display:none}
 #s {}
#topnav {}
 #nav {}
  #nav li {display:inline}
#container {}
 #container a {text-decoration:underline}
 #container li {display:list-item}
 .main {}
 .main h1 {}
 .main h2 {}
 .main p {}

 .side {}
  .side h4 {}
  .side h5 {}
  .side p {}

#footer {}
 #footer p {}
 #footer p a {}

Overlap design watermark for pixel perfect CSS

    <style>
        #watermark {position:fixed;top:0;left:0;width:100%;background:url(images/watermark.jpg) top center;height:5px;opacity:0.2}
        #watermark:hover {height:1000px;opacity:0.5}
    </style>
    <div id="watermark"></div>

2. HTML Zen Coding shortcuts

Typical HTML website structure

With the power of Zen Coding, I can code a full HTML website in one line of code, then press the shortcut (Ctrl+, in Dreamweaver) and voila, there you have all the HTML ready:

html:xt>(div#wrap>(div#header.r>(div.g6>p#logo>span)+(div.g6>form#search>input[type=text]#s+input[type=submit].hide))+(div#topnav.r>div.g12>ul.nav>li*5>a)+(div#container.r>(div.main.g8>div.post>h1+p+img[src=http://dummyimage.com/150x150])+(div.side.g4>h4+p>ul>li*5>a))+(div#footer.r>(div.g6>p>a*1)+(div.g6>p>a*4)))

Here’s the fragmented HTML:

html:xt
div#wrap
div#header.r>div.g6*2
div#header.r>(div.g6>p#logo>span)+(div.g6>form#search>input[type=text]#s+input[type=submit].hide)
div#topnav.r>div.g12>ul.nav>li*5>a
div#container.r>(div.main.g8>div.post>h1+p+img[src=http://dummyimage.com/150x150])+(div.side.g4>h4+p>ul>li*5>a)
div#footer.r>(div.g6>p>a*1)+(div.g6>p>a*4)

Forms and tables

form>label+input:text+input:submit
select#items>option[value=item-$]*3
table>(tr>th*2)+(tr>td*2)

Listings

div.list-vert>(img[src=http://dummyimage.com/100x100]+h3+p.brand+span.rating-5+p.price+(p>a.button-m))

3. WordPress theme

1. Download the Starter Theme
2. Add TimThumb
3. Then grab snippets from WP Snippets
4. Start coding and customizing

4. WordPress customization

In the functions.php

date_default_timezone_set('Europe/Madrid');
date_default_timezone_set('Europe/London');

TimThumb shortcut

function timthumb($src, $w, $h, $q=90, $zc=1) {
    return get_bloginfo('template_url').'/thumb.php?src='.$src.'&w='.$w.'&h='.$h.'&q='.$q.'&zc='.$zc;
}

Custom field shortcut

function customfield($name, $id="") {
    $value = get_post_custom_values($name, $id);
    return $value[0];
}

Extract images of a post

function catch_that_image() {
    global $post, $posts;
    $first_img = '';
    ob_start();
    ob_end_clean();
    $output = preg_match_all('/<img.+src=[\'"]([^\'"]+)[\'"].*>/i', $post->post_content, $matches);
    $first_img = $matches [1] [0];

    if(empty($first_img)){ $first_img = "/images/default.jpg"; }
    return $first_img;
}

Nice excerpts

/* This function will trim text without
cutting it in the middle of the word and
adding … if longer
*/
function trimtext($text, $length) {
    $words = explode(" ", strip_tags($text));
    $newtext = "";
    $addhellip = "";
    foreach ($words as $word) {
        if (strlen($newtext." ".$word) < $length) {
            $newtext .= " ".$word;
        }else{
            $addhellip = 1;
            break;
        }
    }
    if ($addhellip) {$newtext .= "…";}
    return $newtext;
}

Get exact current page URL

function curPageURL() {
 $pageURL = 'http';
 if ($_SERVER["HTTPS"] == "on") {$pageURL .= "s";}
 $pageURL .= "://";
 if ($_SERVER["SERVER_PORT"] != "80") {
  $pageURL .= $_SERVER["SERVER_NAME"].":".$_SERVER["SERVER_PORT"].$_SERVER["REQUEST_URI"];
 } else {
  $pageURL .= $_SERVER["SERVER_NAME"].$_SERVER["REQUEST_URI"];
 }
 return $pageURL;
}

Optimize WYSIWYG editor for SEO

if (isset($wp_version)) {
    add_filter("mce_buttons", "extended_editor_mce_buttons", 0);
    add_filter("mce_buttons_2", "extended_editor_mce_buttons_2", 0);
    add_filter('tiny_mce_before_init', 'extended_editor_change_mce_buttons', 0);
}

function extended_editor_mce_buttons($buttons) {
    return array(
        "formatselect", "separator",
        "bold", "italic", "separator",
        "bullist", "numlist", "blockquote", "separator",
        "link", "unlink", "separator",
        "charmap", "separator",
        "pasteword", "separator",
        "fullscreen", "separator",
    );
}

function extended_editor_mce_buttons_2($buttons) {
// the second toolbar line
return array();
}

function extended_editor_change_mce_buttons( $initArray ) {
    $initArray['theme_advanced_blockformats'] = 'p,h2,h3,h4,h5,h6,pre';
    return $initArray;
}

In the wp-config.php

Disable/limit revisions

# Maximum 5 revisions
define('WP_POST_REVISIONS', 5);
# Disable revisions
define('WP_POST_REVISIONS', false);

 5. WordPress must-have plugins

• Admin Helper
• All-in-one SEO
• Google XML Sitemap
• HTML Sitemap

Related posts

• WordPress code snippets, tricks and cheat sheet
• WordPress Performance

Photo by CoffeGeek

About a year ago I created a one-page document for content writers in my team to write better online articles. I am now releasing it so you can print it and have it close to you while writing. These are the most basic and important SEO tips you need to know if you want your posts to succeed. You will find a link to download the one-page PDF at the bottom of the article.

1. The most important tip is to create quality content

Posts that are bookmarked, shared, linked, commented or thanked. That should be the purpose of every post and should either be:

1. Useful (people reference to them)
2. Interesting (people bookmark them)
3. Funny or entertaining (people share them)

Here’s a good article extending this concept on writing with a purpose.

2. User goes always first

Keep the post readable and attractive to humans. Google is secondary. Ensuring you write for your users will have long-term SEO benefits.

3. Use Headings to split the content

Heading 1 is always the page title and it is the most important title. Headings to use in the content must start from Heading 2 to a max depth of H6. Use headings instead of bolding or formatting the text yourself.

4. Use eye-catching titles but keep them short

Don’t be just informative, get the user’s attention.

1. Windows tricks -> Top 10 coolest tricks for Windows!
2. London party places -> Best secret places to party in London

5. First paragraphs are the most important ones

Search Engines give more importance to the first part of the posts. In fact, really large posts are usually not indexed completely.

6. Be descriptive by adding keywords whenever possible

All headings should have keywords in them:

1. What I like -> What I like about the HP Pavilion laptop
2. My trip -> My awesome trip to Barcelona this summer

7. Use synonyms

Don’t repeat keywords you are not targeting for, use a lot of synonyms instead.

1. What I like about Acer -> Review about Acer computers / My opinion on Acer laptops

This way, users searching for “acer review”, “acer opinion” or “acer laptop” will find our page.

8. Rich formatting increases SEO

Eases Search Engines to identify the content.

• Using lists (and differentiating between ordered and unordered lists),
• bold and italic words or sentences,
• blockquote paragraphs when quoting or pasting literal text

9. Add both inbound and outbound links

Links to authority webs like Flickr, Wikipedia or YouTube can be frequent (you don’t lose any PageRank juice). But don’t link too much to other websites (one or two per paragraph). Always describe the links:

1. Download the Flash player by clicking here. -> Download the Flash player.

10. Format posts inside WordPress

Text editors like Microsoft Word may add irrelevant or invalid code into posts. If the text is in Word, paste it in Notepad so it looses all formatting, then copy and paste into WordPress and format it there using Headings, lists, bold, italic, etc.

Download the 10 SEO tips for WordPress PDF file

10 SEO tips for WordPress PDF file
If you have any doubts feel free to ask them in the comments. Also, share this article with your team, friends and colleagues for increased results and better blogging.

This is how you can get how deep a page is compared to the root/home page in WordPress, works for both the current page or any page by providing its ID. Copy this script and paste it in your functions.php file:

function get_depth($postid) {
  $depth = ($postid==get_option('page_on_front')) ? -1 : 0;
  while ($postid > 0) {
    $postid = get_post_ancestors($postid);
    $postid = $postid[0];
    $depth++;
  }
  return $depth;
}

Now paste this anywhere in a loop:

echo get_depth($post->ID);

Other solutions I’ve found on the Internet where 50 lines long or even 100 and they where full of loops and slow, that’s why I decided to code this one.

The home page will return 0, direct childs will return 1, childs of childs will return 2, etc.

One line Alternative

You can also use this one:

echo count($post->ancestors);

Although it will not differentiate between the home page and level 1 pages (will output 0).

That’s it, easy as pie! If you maintain WordPress sites or are a theme developer see this post on advanced tips to improve performance and gain space in WordPress.

The plugin is extremely lightweight and is an essential tool for WordPress theme developers.

Admin Helper is hidden and does not show unless you are logged in. Once logged in it appears unobtrusively like this:

So it is not as annoying as the default Admin Bar that comes with WordPress yet it provides everything you need while developing the WordPress theme in a mouse move or click.

Login square: While you are not connected, a 5×5 invisible square at the bottom right of the page will link you to the Login page.

You can download the plugin by following the link below:

Admin helper WordPress Plugin v1.2

This is a list of actions and tips to take in order to make your WordPress website faster and improve its performance. You should follow these steps at least once every 3-6 months depending on your website’s activity in order to keep it clean and to increase its performance to a top level. If you have been using WordPress for a while and have never cleaned it you may be surprised at how much database space you can save up, the last cleaning I did to a client saved 82% of space going from 132MB to 23MB.

Before running any queries in the database take backups of everything and make sure no one is editing any post or page while cleaning WordPress.

The database

1. Delete post revisions

Create a backup of the revisions first by selecting and exporting them:

SELECT * FROM wp_posts WHERE post_type = 'revision'

Then delete them and be amazed at the big space savings:

DELETE FROM wp_posts WHERE post_type = 'revision'

2. Limit post revision

By default, WordPress saves every revision of a post. This can make your wp_posts table 2 to 10 times bigger than necessary. In your wp-config.php file, add this:

define('WP_POST_REVISIONS', no_of_revisions);

Leaving number of revisions to 10 is more than enough, if your blog is used by 1 or 2 people then 5 may be even better.

3. Disabling post revision

You can disable post revision completely (although I would personally leave it just in case). To do that:

define('WP_POST_REVISIONS', false);

4. Deleting spam comments

If you don’t use Akismet or any other effective spam control service, spam messages can bloat your database waiting to be approved or deleted. You can either go to the WordPress Administration Panel > Comments and delete them or just head to MySQL and execute this:

DELETE FROM `wp_comments` WHERE `comment_approved` NOT LIKE '1'

This query will delete both spam, pending and trashed comments.

5. Disable comments in all your WordPress blog posts

Some WordPress sites get loads of real comments every day but some don’t. If your website just receives spammy comments and you guess one in a million will be real, I may suggest you to consider disabling them, not only will this save you time and loads of database space but will also increase the performance and loading speed of your pages. You can install Disqus which allows people to post comments through several ways (Twitter, Facebook, manually, etc.) and has very effective spam protection. If you don’t get many comments and performance/SEO is a must then add a link to a Contact Us page next to the post and encourage people to contact you that way.
To disable comments go to Settings > Discussion and disable these two checkboxes:

• Allow link notifications from other blogs (pingbacks and trackbacks.)
• Allow people to post comments on new articles

This will disable comments only in the new posts you create from now on. To disable comments (and pings) in your existing blog posts execute this query in your MySQL:

UPDATE `wp_posts` SET `comment_status` = 'closed', `ping_status` = 'closed';

6. Delete plugin log tables

Some plugins store log files in your database but these can sometimes get way too big if the plugin developer hasn’t set a limit. Check your database tables and look for big tables or tables containing log in their name.

7. Delete old plugin tables

Some WordPress plugins create tables in your database and when you delete them, the tables are still there to keep your configuration if you ever install the plugin again. If you do not intend to install them anymore, have a quick look at your database tables and see if you find any remains of those plugins.

8. Delete old plugin option parameters

Some WordPress plugins also store information in the wp_options table.

9. Optimize, analyze, check and repair your tables

After deleting so many records, it is good to optimize your tables again to remove any over-heading data.

10. Check your WordPress table’s Primary and Index Keys

It’s not just about size what makes a database run slower but the way it is indexed. Once you have cleaned your database, it is time to check that MySQL is indexing everything properly. phpMyAdmin is a very powerful tool and may also warn you about it or suggest better ways. I suggest you read more about MySQL and how it works to understand how queries are made, how to index properly and how a database works on the background.

The server

11. Remove old plugins completely

Connect with your FTP and remove any old plugins you are not using anymore. Don’t bother to remove Hello Dolly as it will get installed again in the next update.

12. Search for the upgrade folder

Sometimes (usually on failed WordPress automatic upgrades) an upgrade folder is created which contains some temporary files that you can remove.

13. Search for old backups

Delete old backups from the web server and store them locally, also search inside your plugins in case any of them stores backups there.

14. Search for cache files

If you use TimThumb or any other file caching system it is a good idea to, once in a while, clean the complete cache folder to remove items not used in a long time.

WordPress settings

You’ve now cleaned the database and the server files and probably made the server much quicker. You can now tweak your WordPress installation to make it work even faster.

15. Upgrade to the latest version

Seems quite obvious but it really makes a difference and protects you from any bugs.

16. Empty the posts/pages trash

The trash is emptied every 30 days by default. You can change that time by adding this function to your functions.php file:

//empty WordPress trash once a week
define('EMPTY_TRASH_DAYS', 7);

Or change the number to 0 to disable automatically emptying the trash at all.

17. WordPress permalinks

One of the biggest neglected performance hits by advanced users is the way you set up your permalinks. There has been much discussion and it has been demonstrated that you should not just use /%postname%/ as your Permalink structure. I personally use /%post_id%/%postname%/ as it’s the fastest query (the Post ID is a primary key in MySQL).

18. Remove non-changing dynamic code

PHP functions such as <?php bloginfo('title'); ?> or <?php if ( function_exists('my_plugin') ) ?> nearly always output the same value so it doesn’t make sense to request it all the time increasing server load. Replacing those with its static content will decrease avoidable queries. To see how many queries a page load does you can use this code: <?php echo get_num_queries();?> .

19. Enable the default WordPress Object Cache

If you are using a cache plugin such as WP Super Cache, W3 Total Cache or WP-Cache you should ignore this step.

Since WordPress 2.0 there is a feature called Object Cache which is not enabled by default. To enable it follow these steps:

• Open wp-config.php in your WordPress root folder
• Add the following code:

  define('ENABLE_CACHE', TRUE);

• Create a new folder called cache to store all the cached files in wp-content
• Change the cache folder permission to 755 or 777

You can set an expiration time to keep it clean, to do this add this line too (time is in seconds):

define('CACHE_EXPIRATION_TIME', 3600); // 1 hour

20. Move your WordPress installation to a subdirectory

It will help keep the web server root folder cleaner. To do this you will need to do some tweaks in your website’s administration panel or in Apache so that the destination of your domain points to the /wordpress/ folder.

21. Fix PHP notices and warnings

The plugins and theme you are using work fine, if not you would disable them. But occasionally some of them are not coded a 100% correctly. One of the most common issues is not defining variables in PHP, this is not just a bad coding practice but it also makes the PHP engine go a bit crazy and take extra time to process the code. It is very easy to fix and any beginner programmer should be able to manage this. Once you are done, notify the plugin/theme authors of these so they fix the warnings and notices on the next release. Enable WP_DEBUG in your wp-config.php file and read this article on PHP error suppression performance.

Further tips

22. Change your hosting provider

One of the main reasons why websites load slowly and sluggish is because of the hosting provider. Some hostings such as GoDaddy have really bad reputation and you should move to somewhere else like HostGator, you may spend £2-10 more per month but both your users and Google will compensate you.

Final notes

Here we’ve just covered optimizing a WordPress installation although you can keep optimizing the PHP code, MySQL queries, use less HTML, optimize the CSS selectors and use a sprite map, tailor Apache to your needs, enable Gzip compression to your files or use a Content Delivery Network amongst many others.

UserCake és un sistema senzill de gestió d’usuaris desenvolupat en PHP. Hi ha molts sistemes d’usuari a Internet i una gran quantitat de tutorials també. Lamentablement molts són complicats, mal programats o insegurs. L’objectiu d’UserCake és proporcionar als programadors amb una base per a construir aplicacions per a l’usuari sense tots els problemes. UserCake està clarament escrit i ben documentat en el codi base. Desenvolupar amb UserCake és senzill i ràpid.

Pots descarregar el pack d’idioma traduït al català des d’aquí:

ca.php (UserCake 1.4)

Per a instalar-lo renombra l’arxiu de dalt a ca.php i guarda’l a usercake/models/lang/. Modifica la variable $langauge a ca de l’arxiu usercake/models/settings.php.

Web oficial: UserCake