include('customfields.php');

Now create a new file called customfields.php in the theme folder (the same folder as function.php) with the following contents:

<?php

function get_extra_profile_list() {
return Array(
/* Add your custom fields, here like follows:
'slug_of_the_field_here' => 'Field name for display',
 */
'address' => 'Address',
'favouritecolour' => 'Favourite Colour'
);
}

add_action( 'show_user_profile', 'extra_user_profile_fields' );
add_action( 'edit_user_profile', 'extra_user_profile_fields' );

function extra_user_profile_fields( $user ) { ?>
<h3><?php _e("Extra profile information", "blank"); ?></h3>

<table class="form-table">
<?php
foreach(get_extra_profile_list() as $key => $value) {
?>
<tr>
<th><label for="<?php echo $key; ?>"><?php _e($value); ?></label></th>
<td>
<input type="text" name="<?php echo $key; ?>" id="<?php echo $key; ?>" value="<?php echo esc_attr( get_the_author_meta( $key, $user->ID ) ); ?>" class="regular-text" /><br />
<span class="description"><?php _e("Please enter your $value."); ?></span>
</td>
</tr>
<?php
}
?>
</table>
<?php }

add_action( 'personal_options_update', 'save_extra_user_profile_fields' );
add_action( 'edit_user_profile_update', 'save_extra_user_profile_fields' );

function save_extra_user_profile_fields( $user_id ) {

if ( !current_user_can( 'edit_user', $user_id ) ) { return false; }

foreach(get_extra_profile_list() as $key => $value) {
update_usermeta( $user_id, $key, $_POST[$key] );
}
}
?>

Now if you go to “Users” under your administration and edit a user, the additional profile fields will show up at the bottom of the edit page.

See the plugin page on Compdigitec for more details and screenshots/downloads.

1. Posts are set to expire. If you select the option “Automatically close comments on articles older than x days” under Settings->Discussion, then posts will automatically close comments after x days.
2. Your blog is not set to enable commenting. Enable “Allow people to post comments on new articles” under Settings->Discussion.
3. The specific post is not allowing comments. Edit the post in question and under the “Discussion” section ensure both “Allow comments” and “Allow trackbacks and pingbacks on this page” are both selected.

If the above three steps still do not help, then you can run the following database queries to enable comments globally:

UPDATE wp_posts SET comment_status = REPLACE (comment_status, 'closed', 'open') WHERE post_status = 'publish' AND post_type = 'post';

UPDATE wp_options SET option_value = 0 WHERE option_name = 'close_comments_for_old_posts'

<?php
/*
 *      (C) Copyright 2011 Compdigitec. All rights reserved.
 *      Redistribution and use in source and binary forms, with or without
 *      modification, are permitted provided that the following conditions are
 *      met:
 *
 *      * Redistributions of source code must retain the above copyright
 *        notice, this list of conditions and the following disclaimer.
 *      * Redistributions in binary form must reproduce the above
 *        copyright notice, this list of conditions and the following disclaimer
 *        in the documentation and/or other materials provided with the
 *        distribution.
 *      * Neither the name of the Compdigitec nor the names of its
 *        contributors may be used to endorse or promote products derived from
 *        this software without specific prior written permission.
 *
 *      THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
 *      "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
 *      LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
 *      A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
 *      OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
 *      SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
 *      LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
 *      DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
 *      THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 *      (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 *      OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 */

/**
 * Gets the direct link of a URL with a given public Skydrive URL
 * @param string $liveurl The public SkyDrive URL
 * @return string|false The direct URL of the skydrive or false if error
 */
function get_skydrive_direct_link($liveurl) {
	$file = file_get_contents($liveurl);

	// find file loc
	$pos = strpos($file,'<a id="spPreviewLink" href="');
	if($pos === false) return false;
	$pos += strlen('<a id="spPreviewLink" href="');

	$buffer = "";
	while(substr($file,$pos,1) != '"') {
		$buffer .= substr($file,$pos,1);
		$pos++;
	}

	$buffer = html_entity_decode($buffer);

	$directlink = substr($buffer,0,strlen($buffer)-7);

	$host = parse_url($directlink,PHP_URL_HOST);
	if(strpos($host,"livefilestore.com") === false) {
		return false;
	}
	return $directlink;
}
?>

To use this function, feed it the public URL and it will return the direct link of the file:

$direct = get_skydrive_direct_link("http://cid-abcdef1234567890.office.live.com/self.aspx/FolderName/FileName.exe");
// Returns something like http://public.bay.livefilestore.com/y1pZwjyu-qfXUWjM-si2IeNs-juO0PjZE-Sk5EVvZxgeenjCxxv9vHiUy8q1RGafKnbaGSC2alqAoIbDvAYegznaZ/FileName.exe
$not_direct = get_skydrive_direct_link("http://not.skydrive.example.com/not/a/skydrive/FileName.exe");
// Returns FALSE (if it is not a SkyDrive upload)

You can use this script as part of an independent web service or as part of your existing PHP application under the BSD license. There is a link generator on this website available that you can use to try it out or use with your application without needing the script to be installed.

Normally, when PHP scripts access the remote IP of a client through REMOTE_ADDR, it can only access the IP of the last client. Under most web hosting conditions this is perfectly normal, but in some corporate networks there is a reverse name-based proxy used to serve multiple servers through one IP. However, this messes up many scripts because to them it appears that all traffic is coming through one Intranet address, and this also messes up many spam protection filters because it appears to be an internal address.

Most proxy servers send the X-Forwarded-For header when contains the real IP that it is forwarding, but this cannot always be trusted, especially if your server is open both inside and outside the intranet. This means that when getting the real IP address, one must be careful that the request is coming from a trusted proxy server and not from a rouge spammer.

Since most scripts are not programmed by default to provide this kind of functionality, we have written a patch for WordPress 2.9 and Bad Behvaiour 2.0.38. However, this is not an efficient or elegant way to perform this kind of functionality, and instead recommend that Apache (or whatever your web server is) automatically rewrite REMOTE_ADDR instead. This way no unofficial patching is required, and it is compatible with more scripts.

For WordPress 2.9:

Open <blog path>/wp-includes/comment.php and scroll to line 1199, which reads “$commentdata['comment_author_IP'] = preg_replace( ‘/[^0-9a-fA-F:., ]/’, ”,$_SERVER['REMOTE_ADDR'] );“.

Now add the following code to it (replacing 111.222.233.144 with your trusted proxy server IP):

/** Begin X-Forwarded-For Patch **/
$headers = getallheaders();
if(isset($headers["X-Forwarded-For"])) {
	// forwarded proxy
	if($_SERVER['REMOTE_ADDR'] == "111.222.233.144") {
		// this is a trusted gateway
		$xff = $headers["X-Forwarded-For"];
		$xff_array = explode(",",$xff);
		$last_forwarded_host = trim($xff_array[count($xff_array)-1]);
		// remove port number, if needed
		if(strpos($last_forwarded_host,":") !== false) {
			$lfh_array = explode(":",$last_forwarded_host);
			unset($lfh_array[count($lfh_array)-1]);
			$last_forwarded_host = implode(":",$lfh_array);
		}
		// set real client IP as IP
		$commentdata['comment_author_IP'] = $last_forwarded_host;
	}
}
/** End X-Forwarded For Patch **/

Now comments should be attributed to their source IPs in the Comment administration panel.

For Bad Behaviour 2.0.38:

Open <bad behaviour path>/bad-behavior/core.inc.php to line 116 ($ip = $_SERVER['REMOTE_ADDR']).

Now add the following lines after a newline (replace 111.222.233.144 with your gateway IP):

/** Begin X-Forwarded-For Patch **/
if(isset($headers["X-Forwarded-For"])) {
	// forwarded proxy
	if($ip == "111.222.233.144") {
		// this is a trusted gateway
		$xff = $headers["X-Forwarded-For"];
		$xff_array = explode(",",$xff);
		$last_forwarded_host = trim($xff_array[count($xff_array)-1]);
		// remove port number, if needed
		if(strpos($last_forwarded_host,":") !== false) {
			$lfh_array = explode(":",$last_forwarded_host);
			unset($lfh_array[count($lfh_array)-1]);
			$last_forwarded_host = implode(":",$lfh_array);
		}
		// set real client IP as IP
		$ip = $last_forwarded_host;
		unset($headers["X-Forwarded-For"]);
		unset($headers_mixed["X-Forwarded-For"]);
	}
}
/** End X-Forwarded For Patch **/

Now Bad Behaviour will start functioning again, as by default any Intranet address is whitelisted by default.

Prerequisites

• Uninstall any old versions of Roadsend PHP and bigloo on your computer.
• Install the packages libgtk2.0-0, libpcre3, libfcgi, libmysqlclient15off and libsqlite3-0 like such:

  sudo apt-get install libgtk2.0-0 libpcre3 libfcgi libmysqlclient15off libsqlite3-0
  

• Install unofficial bigloo and set up the bigloo symlink like such:

  sudo ln -s / /z

Procedure

1. Download and install the Roadsend PHP binary package:
   • roadsend-php-unofficial.deb (4.8 MB)

   Note that the Roadsend PHP debugger (pdb) has been renamed to (roadsend-pdb) due to naming conflict with python.

2. Create a test PHP file with the following content, and save it as hello.php:

   <?php
   
   // Roadsend PHP testing program
   $words = Array("Hello", "World", "from", "Roadsend PHP!");
   $sentence = implode(" ",$words);
   echo $sentence . "\n";
   exit(0);
   
   ?>

3. Run:

   pcc hello.php

   to generate a hello executable. Test this executable by running:

   ./hello

   The output of the program should read:

   Hello World from Roadsend PHP!

4. Now we will test the MicroServer backend, which is a small embedded webserver that allows you to turn your PHP application into a stand-alone webserver:

   pcc -s hello-server --port 44444 hello.php

   to generate the hello-server webserver. Now, we will try to visit the MicroServer:

   ./hello-server

   The server should be up and running by this point. Now point your browser at http://127.0.0.1:44444/hello.php and watch your PHP turn itself into a webserver without Apache.

Most often, the error will appear if you use an exception handler combined with an error reporting to exception handler by converting it to an ErrorException, then there a suddenly a whole new magnitude of ways to throw errors within the exception handle, especially if E_NOTICE, E_STRICT and/or E_WARNING errors are converted. This form most often occurs when you use variables without first initializing them. This error may be preventable by wrapping the exception handler within a try/catch block.

A second form of this error occurs when you attempt to throw an exception in a destructor. This is well documented in the PHP manual, but this can still be triggered if you accidentally throw an exception:

• Manually - calling “throw new Exception(‘hello world’)’ in a destructor
• Implicitly - calling a function that throws an exception (e.g. calling function foo() which throws an exception)
• Error handler (ErrorException) - instating a user-defined function as an error handler which throws an ErrorException (which is still an error)

There is no exactly solid way to identify this type of error as you may not know exactly what your functions do. If you are throwing exceptions manually in your destructor, you need to go back to the PHP manually and read that it is not possible to throw exceptions within the destructor (as it lacks a stack frame). For the other two, you may need to comment out your destructors and manually uncomment parts until you reach the point where you find the error line as the error message produced by PHP is not too informative.

To parse a file:

<?php

// include simple template engine
include("tpl.class.php");

$tpl = new template();

$tpl->assign(Array('content'=>"Hello World from Simple Template Engine!"));

// If you want to display it directly
$tpl->display('example.tpl');

// If you want to send it to another function/class for more processing
some_function($tpl->parse('example.tpl'));

?>

example.tpl is:

<html><head><title>{content}</title></head><body><h1>{content}</h1></body></html>

If you found this article useful or helpful, please help Compdigitec spread the word. Don’t forget to subscribe to Compdigitec Labs for more useful and interesting articles!

• ext/gtk/gen_atk.c - patch, patched
• ext/gtk/gen_pango.c - patch, patched
• ext/gtk/gen_gdk.c - patch, patched
• ext/gtk/gen_gtk.c - patch, patched
• ext/scintilla/gen_scintilla.c - patch, patched
• main/php_gtk.c - patch, patched

This set of patches is incomplete because the build process will fail on

gcc -I/usr/dev/php-gtk-2.0.1/main -I. -I/usr/dev/php-gtk-2.0.1 -DPHP_ATOM_INC -I/usr/dev/php-gtk-2.0.1/include -I/usr/dev/php-gtk-2.0.1/main -I/usr/dev/php-gtk-2.0.1 -I/usr/include/php -I/usr/include/php/main -I/usr/include/php/TSRM -I/usr/include/php/Zend -I/usr/include/php/ext -I/usr/include/php/ext/date/lib -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/php -DHAVE_CONFIG_H -g -O0 -Wall -c /usr/dev/php-gtk-2.0.1/main/phpg_support.c  -fPIC -DPIC -o main/.libs/phpg_support.o

which it fails with the following output:

/usr/dev/php-gtk-2.0.1/main/phpg_support.c: In function ‘phpg_init_object’:
/usr/dev/php-gtk-2.0.1/main/phpg_support.c:275: error: incompatible type for argument 2 of ‘zend_hash_find’
/usr/dev/php-gtk-2.0.1/main/phpg_support.c: In function ‘phpg_register_class’:
/usr/dev/php-gtk-2.0.1/main/phpg_support.c:300: error: incompatible types in assignment
/usr/dev/php-gtk-2.0.1/main/phpg_support.c:328: error: incompatible type for argument 2 of ‘zend_hash_find’
/usr/dev/php-gtk-2.0.1/main/phpg_support.c:331: error: incompatible type for argument 2 of ‘_zend_hash_add_or_update’
/usr/dev/php-gtk-2.0.1/main/phpg_support.c: In function ‘phpg_register_interface’:
/usr/dev/php-gtk-2.0.1/main/phpg_support.c:353: error: incompatible types in assignment
/usr/dev/php-gtk-2.0.1/main/phpg_support.c: In function ‘unset_abstract_flag’:
/usr/dev/php-gtk-2.0.1/main/phpg_support.c:486: error: incompatible type for argument 2 of ‘zend_hash_quick_exists’
/usr/dev/php-gtk-2.0.1/main/phpg_support.c: In function ‘phpg_handler_marshal’:
/usr/dev/php-gtk-2.0.1/main/phpg_support.c:565: warning: passing argument 3 of ‘zend_is_callable’ from incompatible pointer type

If you found this article useful or helpful, please help Compdigitec spread the word. Don’t forget to subscribe to Compdigitec Labs for more useful or interesting articles!

‐‐prefix=/usr ‐‐enable-debug ‐‐with-openssl ‐‐with-zlib ‐‐with-curl ‐‐enable-ftp ‐‐with-gettext ‐‐with-mhash ‐‐with-mysql ‐‐enable-sockets ‐‐enable-soap ‐‐with-tidy ‐‐enable-zip ‐‐with-xsl ‐‐disable-cgi

If you found this article helpful or useful, please help Compdigitec spread the word. Don’t forget to subscribe to Compdigitec Labs for more useful or interesting articles!