‘Cannot edit LocalServerPort:
Error writing the value’s new contents’

As usual, when something I don’t like happens on my computer or on other parts of my life, I ask my friend Google about it, the suggested solutions were :

• Open the Registry Editor using the command “Regedt32.exe”
• Set or review permissions (Edit->Permissions…)

Of course none of these worked for me, all I had to do is to close the anti-virus program, or to be more specific unload server/client security agent (lol).

I’m not much on Windows, so I can’t explain that behavior, if you know something about it, please share it on the comments section, I will be very pleased to add it here on this very same post.

# Prototype
# string get_current_url([boolean $ignore_port_80])

# Function
function get_current_url($ignore_port_80 = true) {
  $is_https = $_SERVER['HTTPS'] === 'on';
  $show_port = ($_SERVER['SERVER_PORT'] === '80') && !$ignore_port_80;

  $url = ''
    . 'http'
    . ($is_https ? 's' : '')
    . '://'
    . $_SERVER['SERVER_NAME']
    . ($show_port ? (':'.$_SERVER['SERVER_PORT']) : '')
    . $_SERVER['REQUEST_URI'];
    return $url;
}

# Examples
echo get_current_url();       # outputs http://www.kadimi.com/en/some-title-123
echo get_current_url(true);   # same
echo get_current_url(false);  # outputs http://www.kadimi.com:80/en/some-title-123

When I start vsftpd on my CentOs machine I get this error:

Starting vsftpd for vsftpd: 500 OOPS: unrecognised variable in config file:  anonymous_enable

How can I fix it?

Answer

The option “anonymous_enable” is a valid vsftpd option, but as you can see on the error message, there is an extra white space before the variable definition, I suspect that the line was there, commented, and that when you uncommented it you forgot to remove the white space after the “#”, check your vsftpd.conf file make sure that “anonymous_enable=YES” or “anonymous_enable=NO” stands on a single line without any preceding spaces then start vsftpd:

service vsftpd start

mysql > SELECT * FROM wp_links;
mysql > SELECT * FROM wp_links\g

Those are exactly the same, and will produce the same result, here is an example:

mysql> select * from wp_links \g
+---------+-----------------------+--------------+------------+-------------+---------------+------------------+--------------+------------+-------------+---------------------+----------+------------+-----------------------+
| link_id | link_url | link_name | link_image | link_target | link_category | link_description | link_visible | link_owner | link_rating | link_updated | link_rel | link_notes | link_rss |
+---------+-----------------------+--------------+------------+-------------+---------------+------------------+--------------+------------+-------------+---------------------+----------+------------+-----------------------+
| 1 | http://www.ar-wp.com/ | WP arabic | | | 0 | | Y | 1 | 0 | 0000-00-00 00:00:00 | | | http://www.ar-wp.com/ |
+---------+-----------------------+--------------+------------+-------------+---------------+------------------+--------------+------------+-------------+---------------------+----------+------------+-----------------------+
1 row in set (0.01 sec)


\G is another valid statement terminator, it tells MySQL to produce vertical output, this comes in handy when the result has too much columns, here is the same statement again but with the \G terminator:

mysql> select * from wp_links\G
*************************** 1. row ***************************
link_id: 1
link_url: http://www.ar-wp.com/
link_name: WP arabic
link_image:
link_target:
link_category: 0
link_description:
link_visible: Y
link_owner: 1
link_rating: 0
link_updated: 0000-00-00 00:00:00
link_rel:
link_notes:
link_rss: http://www.ar-wp.com/
1 row in set (0.00 sec)

As you can see this is a more user friendly fashion for displaying data.

include_path is a PHP core directive, it stores a directory path or a directories paths  list separated by colons “:” on Unix and MAC platforms or by semicolons “;” on Windows platforms.

When you use include(), include_once(), require(), require_once(), fopen(), file(), readfile() or file_get_contents() to load a file (let’s say my_file.inc.php), PHP will look if the file exists on the current working directory, if it doesn’t find it it will look on the directory list provided (by default) by the include_path directive, PHP will start by searching the first (leftmost) directory path on the list, and won’t stop until it finds the file to load (include, require, fopen.. ), if it doesn’t find the file on all directories of the list, it will issue a warning or two

In order to complete these steps faster, we will prefer using SSH to download or edit files and to create folder instead of using FTP, FTP will take a lot of time compared to SSH… Let’s start.

1 – Download and Install Symfony

Login to your account using SSH, if you are already logged in make sure your current working directory is your home directory (~), then create a “php” folder where you will download the symfony package, we will use the same directory structure used on the Symfony documentation, this will allow you to follow the documentation examples without changing directory names etc.

Before issuing the following commands, grab the link of the latest symfony version from Symfony website, for the purposes of this tutorial you will have to download the  source .tgz file, the text  written in red font will be different depending on the Symfony version:

you@yourdomain.com [/tmp]# cd
you@yourdomain.com [~]# mkdir php
you@yourdomain.com [~]# mkdir php/lib
you@yourdomain.com [~]# mkdir php/lib/vendor
you@yourdomain.com [~]# cd php/lib/vendor
you@yourdomain.com [~/vendor]# wget http://www.symfony-project.org/get/symfony-1.4.1.tgz
--06:15:44-- http://www.symfony-project.org/get/symfony-1.4.1.tgz
=> `symfony-1.4.1.tgz.2'
Resolving www.symfony-project.org... 217.174.222.79
Connecting to www.symfony-project.org|217.174.222.79|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3,210,838 (3.1M) [application/x-gzip]100%[===================================================================>] 3,210,838 1.34M/s
06:15:48 (1.34 MB/s) - `symfony-1.4.1.tgz.2' saved [3210838/3210838]
you@yourdomain.com [~/vendor]# tar zxpf symfony-1.4.1.tgz
you@yourdomain.com [~/vendor]# mv symfony-1.4.1 symfony
you@yourdomain.com [~/vendor]# rm -fr symfony-*


2 – Test your Symfony installation

You can test your installation and display the symfony version:

you@yourdomain.com [~]# php -q  php/lib/vendor/symfony/data/bin/symfony -V
symfony version 1.4.1 (/home/you/php/lib/vendor/symfony/lib)

3 – Tell PHP where to find Symfony files

Symfony files are now available in your server, but you still need to tell php where to find them easily. For that you need to modify your PHP include_path and add the “php” folder.

We need to know the php folder absolute path, for this we will “cd” to the “php” directory and issue the “pwd” command:

you@yourdomain.com [~]# cd ~/php
you@yourdomain.com [~]# pwd
/home3/you/php


-or-

you@yourdomain.com [~]# find ~/php -name php
/home3/you/php


There are different solutions for altering your PHP include_path, you will choose the one that meets your needs.
[See: How to modify PHP include_path]

In this tutorial, I will assume that you are relying on a global php.ini file .

Open you php.ini file for edit

you@yourdomain.com [~]# nano /x/y/z/php.ini


Look for the include_path directive setting, something like this:

include_path = ".:/usr/lib/php:/usr/local/lib/php"


you can find it easily by using nano’s search featrure:

• Press CTRL+W
• Type the search string and press RETURN, we are interested in the string include_path
• Press CTRL+W then RETURN until you find something that resembles the code above.

Add the php absolute path to your php include_path like this

include_path = ".:/usr/lib/php:/usr/local/lib/php:/home3/you/php"

Conclusion

At this point you can use symphony almost as if you installed it using the PEAR pear command. You can use the same method to install other PEAR packages. One more thing you can do is to alter your (most likely) shell PATH to add the symfony command:

Open .bash_profile add the following line AT THE END OF THE FILE:

PATH=$PATH:$HOME/php/lib/vendor/symfony/data/bin/
export PATH

Sending a crash report to complain about my issue won’t help me (specially), and won’t help Mozilla people too much, unless they know more about my system (OS, FF version, installed extensions, latest visited websites), so I’d better try to solve this issue by myself.

1st try

I restarted Firefox, it still crashes when i type the first letter of my search string…

2nd try

I rebooted my computer… I wasted 2 minutes for nothing.

3rd try

I scanned my computer using Avira Antivir Personal, nothing found as usual.

4th try, what I should have done from the beginning

I started firefox in safe mode and disabled all installed extensions (more than 15).
By the way, the command for starting Firefox in safe mode is:

firefox -safe-mode

Guess what, it worked now, I can use the search function again, but all my extensions are disabled, I enabled them 3 or 4 at a time, restarted Firefox, and tested the search function at each time until I spotted the bogus extensions which was nothing but YSlow 2.0.5.

So what?

Now I can send a descent report to Mozilla and be helpful, I will have to wait until YSlow is updated again or I will install the extension Google Speed which is very similar and even better than YSlow IMO.

Log in to your admin Dashboard and scroll to the bottom of the page, you’ll find your version number on the rightmost spot of the footer.

Or you can view the source of one of the pages of your blog and look for the meta generator tag:

<meta name="generator" content="WordPress 2.9.1" />

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 2516315 bytes) in /home/mydomain/public_html/blog/wp-includes/http.php on line 1370

This can happen at any line and with any file, not only http.php at line 1370!

Explanation

Don’t worry if you get this error, there is nothing wrong with your server or hosting plan etc. Whenever a new version of WordPress is released, new features are added, thus more calculations, so logically more memory is needed.
In older versions of WordPress (before 2.7… I think), the memory limit was set to 32M, if you are upgrading WordPress, you will probably get that error, you will have to edit the wp-settings.php file and set (I should say change) the constant WP_MEMORY_LIMIT value to 64M, giving PHP more memory to play with.

The solution

• Open the remote file wp-settings.php file located on the base directory where you installed your WP blog
• find this code (probably at line 13)
  

  define('WP_MEMORY_LIMIT', '32M');

• Replace with
  

  define('WP_MEMORY_LIMIT', '64M');

• Run the upgrade process again
• Enjoy your updated WP blog

• Download Opera 10.5 Alpha
• See the demonstration

The demonstration doesn’t show rotation, so the CSS for rotation under Opera is:

-o-transform:rotate(90deg);

FYI

When you install Opera 10.5 Alpha, your previous installation of Opera (Stable) is not removed, giving you the chance to test and compare…

Read

Find more about Crossbrowser CSS rotation at hakoniemi’s blog.