Laughing Means A Lot To Me » WordPress

Disable update checking of WordPress 3

Tkjune — Sun, 14 Aug 2011 02:24:20 +0000

When you designing a website for client with WordPress, you may not want your client click the "Upgrade" button for any reasons (mostly, by curiosity). We all know that it may cause unusable of customized theme. Here's how to disable it. Open functions.php of your theme and add following lines.

add_filter('pre_site_transient_update_core', create_function('$a', "return null;")); // screening core update
add_filter('pre_site_transient_update_plugins', create_function('$a', "return null;")); // screening plugin update
add_filter('pre_site_transient_update_themes', create_function('$a', "return null;")); // screening theme update

remove_action('admin_init', '_maybe_update_core'); // forbid wp_version_check();
remove_action('admin_init', '_maybe_update_plugins'); // forbid wp_update_plugins();
remove_action('admin_init', '_maybe_update_themes'); // forbid wp_update_themes();

The second method is recommended that it removes the function in grain.

URL Rewriting for WordPress in IIS with wp_url_rewriting and patch

Tkjune — Wed, 04 May 2011 16:29:16 +0000

There are several ways to use URL rewriting for WordPress in IIS. I'm using wp_url_rewriting for my client. Recently, my client upgraded his WordPress to 3.1 which cause a problem that the page navigation does not work correctly.

Symptom: The page link in a category page, does not contain the category slug. Ex. in http://sampledomain/samplecate/, the page link should be http://sampledomain/samplecate/page/2, but it shows like http://sampledomain/page/2.

This does not happen on my Apache server. So I checked out wp_url_rewriting installation note and I found this:

3). Do a little hack to WordPress file ‘link-template.php’ to make paging works well for categories:(NOTE: You don’t need to do this step if you are using WordPress 2.3.0 or newer)

open file /wp-includes/link-template.php and find the following code:....

From 2.3.0 to 3.0.x, no need to do the hack. Since 3.1.0, it becomes a must again. The original hack does not working. It's been moved to another file. So do the hack as follows:

open file /wp-includes/functions.php and find following code:

function add_query_arg() {
$ret = '';
if ( is_array( func_get_arg(0) ) ) {
if ( @func_num_args() < 2 || false === @func_get_arg( 1 ) )
$uri = $_SERVER['REQUEST_URI'];
else
$uri = @func_get_arg( 1 );
} else {
if ( @func_num_args() < 3 || false === @func_get_arg( 2 ) )
$uri = $_SERVER['REQUEST_URI'];
else
$uri = @func_get_arg( 2 );
}

Replace the $_SERVER['REQUEST_URI'] with $_SERVER['PATH_INFO']

Then wp_url_rewriting will work again.

BTW, after fixing this, I found some updates of ISAPI_Rewrite. The lite version could work well for WordPress. I used that before. I remember there were some limitations for the lite version. Since this article was written on Feb 17th, 2010. I guess it should work fine. If so, this could be a better solution for there's no hack needed.

WordPress auto upgrade in Mac local environment

Tkjune — Sat, 17 Apr 2010 08:53:35 +0000

When I test WordPress in local Mac OS X, the auto upgrade function is not available. It shows up like below:

Here describes reasons and solution. But it doesn't work in my situation: Using XAMPP to set up the testing environment. Another solution were provided in comment 44 by Johan L. It works alright!

Do as follows:

To set up file ownership correctly:
In WP root directory
chown -R yourusername:apachegroupname *
In my case...
chown -R johan:apache *

find . -type d -exec chmod 770 {} ';'
find . -type f -exec chmod 660 {} ';'

WP 2.8: add
define('FS_METHOD', 'direct');
define('WP_TEMP_DIR', ABSPATH.'wp-content/tmp');
in wp-config.php
The function in file.php reads FS_METHOD and the tmp file creation test is never executed.
Make sure the wp-content/tmp directory exists and is writable by the apache user

Pre WP 2.8: well... you may need to patch the function in file.php by removing the if statement before $method='direct';
see comment #38 above
Only do this if you're sure you've setup file ownership correctly.

BTW the three numbers in chmod describe rights for "user", "group" and "others". read==4, write==2, execute==1. Sum of rights make up the number. Hence 777 means read, write and execute for user, group and others. 660 means read and write for user and group, no rights for others.

NEVER do a chmod 777 on any file or directory. NEVER recommend anyone to do it either!

Note that it's better to upgrade to 2.8 and above first.

The key is the two lines in wp-config.php.

Thanks Johan L.

PuSHPress

Tkjune — Thu, 04 Mar 2010 10:41:37 +0000

Just installed this new plugin. Try if it works well.

Simplified Chinese Language Pack for NextGEN Gallery

Tkjune — Mon, 13 Apr 2009 13:50:30 +0000

NextGEN Gallery is a very powerful plugin for WordPress that can manage the photo easily. It has many features and provides multiple language support. I've just made the Simplified Chinese language pack for the current version. Download: Simplified Chinese Language Pack for NextGEN Gallery ~~1.21~~ ~~1.33~~ 1.43 1.52 1.55 1.60 1.72 1.73 1.81 ~~1.83~~ 1.91

(Following bug has been fixed after 1.21)

There is a bug in this version when using other languages which will result in a notice's translation can not be shown. It a very small issue but if you are completist you can fix it in this way: Open this file [NextGEN plugin folder]/lib/core.php and find out line 419. Replace it with following code:

$result = sprintf( __( 'Note : Based on your server memory limit you should not upload larger images then <strong>%d x %d</strong> pixel', 'nggallery' ), $size['width'], $size['height']);

This notice appears in [Add Gallery / Images] -> [Upload a Zip-file] and similar pages. Well, in fact, there are two more bugs if you really want to fix... Open this file [NextGEN plugin folder]/admin/tinymce/window.php and find out line 29-30. Replace them with following code:

span>
 
<span style="text-decoration: line-through;">

Checkout what I did (very simple) with this wonderful plugin and know more about how to use it.

Coding standards

Tkjune — Mon, 13 Apr 2009 02:56:41 +0000

For a beginner of programing, it's a good habit of writing codes in standard format. There are different rules in different companies/teams. Better than form your own, follow a standard of a popular application could be easier and more acceptable by people. For example, the WordPress Coding Standards and Inline Documentation.
Some good approach I just learned from it:

When doing logical comparisons always put the variable on the right side.
I saw this in some codes, now I know why: If you forget an equal sign it'll throw a parse error instead of just evaluating true and executing the statement. It really takes no extra time to do, so if this saves one bug it's worth it.
Use real tabs and not spaces, as this allows the most flexibility across clients.
In some courses, it's suggested that using spaces instead of tabs. Either of they has their reasons. As mentioned above, using the standards of popular applications could be better. And I have already had the habit of using tabs, so I just follow WordPress here.
Tabs should be used at the beginning of the line and spaces should be used mid-line.
Exception for previous point: if you have a block of code that would be more readable if things aligned, use spaces.
Ternary operators are fine, but always have them test if the statement is true, not false. Otherwise it just gets confusing.
1. // GOOD example:
2. // (if statement is true) ? (do this) : (if false, do this);
3. $musictype = ( 'jazz' == $music ) ? 'cool' : 'blah';