Suddenly at start of Google Chrome (installed month’s ago) Windows 7 show the request UAC (User Access Control), indicating that this program will try to start with administrator rights. Probably due to update of Chrome or more likely one of his plugin, must have changed some parameters and Windows, rightly, he notice me a possible danger like a virus or trojan. Knowing that the version installed (and reinstalled for safety) is healthy, I tried a quick workaround. First I found the executable, which usually is not in the classic c:\Program Files but under your user account:

C:\Users\YOURUSERNAME\AppData\Local\Google\Chrome\Application\chrome.exe

So “classic” right click chrome.exe property. From the screen that comes out press on compatibility and then at the bottom you will find the button “change settings for all users“.
A new window appears, after all, de-select option “start this program as administrator“.
Give OK to close all windows, and the problem is finally solved.

Following the tutorial Simfony (known PHP Framework) to the preliminary pre-requisite, reflected the lack of XSL module under Apache and PHP. Specifically, the message I found was:

[[WARNING]] XSL module is installed: FAILED
*** Install the XSL module (recommended for Propel) ***

The workaround is to install apt-get the missing modules as follows:

sudo apt-get install libapache2-modxslt php5-xsl

then restart the instance of Apache2

sudo / etc/init.d/apache2 restart

Restarting the configuration check the error message should be gone.

WordPress born as blog platform for easy of use and many other features is becoming a CMS. However, it is possible that the site is only used internally at the enterprise level, not exposed to the Internet, this could be a problem for businesses that use a Proxy for browsing. In fact WordPress often requires “go to out” our LAN, example checking for plugin/core updates, or remove the options for your blogroll. From version 2.8 programmers have added a new use of the site behind a proxy.

A few parameters (manually entered) to config.php file is required
First we define our proxy and its port:

define ('WP_PROXY_HOST', '192 .168.1.1 ');
define ('WP_PROXY_PORT', '8080 ');

If the proxy requires authentication will also add:

define ('WP_PROXY_USERNAME', 'myuser');
define ('WP_PROXY_PASSWORD', 'mypassword');

Then if we needed the proxy is not used locally or at such other intranet sites, we will proceed with these parameters:

Define ('WP_PROXY_BYPASS_HOSTS', 'localhost, other.intranet');

Finally we can block all requests to sites that are potentially unsure, so you can compile a white list for those that we believe reliable:

define ('WP_HTTP_BLOCK_EXTERNAL', 'true');
define ('WP_ACCESSIBLE_HOSTS', 'api.wordpress.org, akismet.com');

WordPress is full of features and sometimes not fully known to the main public. Today we discover “Press This” a practical tool that provides quick access to creating a new article, while you are surfing through our browser, and pre-fill most of the fields of “New Post” in WordPress.

First, go in the administration under Tools - Tools. Find at bottom the link you’re going to drag (drag and drop) on your bookmark toolbar (tested under Internet Explorer, Mozilla Firefox and Google Chrome). Now when you navigate on the net, you can start writing an article very quickly.  Just select some text on source page, and press the button on the bookmark. Will open a new blog window with several pre-built camps.

If you need, you can create a custom button for bookmark with special needs. The call uses these parameters = http://myblog.com/wp-admin/press-this.php?u=&t=&s=

• u = the url of the current page in browser
• t = the title of the current page in browser
• s = the selected text on the page
• i = url of an image file if present

You could call checkmate of the forgetful, i mean not remember your blog administrator password. This happens  when creating new blog, or after a long time of inactivity. Before performing this procedure, which is irreversible, we recommend you use the special page designed by the creators of WordPress (just add the URL of your domain the following syntax /wp-login.php? Action=lostpassword)

So if you have not yet resolved, proceed with the “heavy weapons”  using phpMyAdmin Will change via an SQL the administrator password. Once in phpMyAdmin, press the button SQL  in the top left, under the logo of the program. Now you can write this command in the appropriate box

UPDATE ‘wp_users’ SET ‘user_pass’ = MD5(‘PASSWORD’) WHERE ‘user_login’ =’admin’ LIMIT 1;

Obviously your new password is .. PASSWORD, and of course we recommend you change immeditely at  first access the administrative area of the blog.

I ran into a stupid problem, by changing the settings for permalinks to a WordPress (switching the classic PHP request to URL SEO) i get a “404 error page not found”. After checking that my apache to have the mod_rewrite enabled and .htaccess file was been created by WordPress itself, i tried to investigate into the configuration of Apache.

Actually the configuration of the root directory report the value:
AllowOverride None
changed in:
AllowOverride All
The problem was solved, but have wasted me  lot of time …

Today, services like Twitter impose the use of short URL, certainly in the network there are several free services, but if we want something we can use custom WordPress to create a dedicated service to our blog. The trick is to exploit the demand for each item, calling for his ID stored in the database.

In part we can put this piece of HTML code to display a link to “short”.

<?php echo get_bloginfo('url')."/?p=".$post->ID; ?>

Google Buzz is now on everyone’s lips for being anti Facebook situation. It’s time to exploit this situation to your blog, because the service is heavily oriented social network. Technically Google Buzz is largely integrated into Google Reader, the aggregator of RSS feeds, so we can exploit this relationship to create an appropriate button. You only have to make sure that in your profile Buzz (above under the heading “connected sites”) has been added to Google Reader.

Obviously we must have a basic knowledge of PHP and WordPress system, but simply add a few lines in the right place, through the WordPress editor (in the Appearance -> Editor).

Here’s the code:

1
2

<a rel=”nofollow” target=”_blank” href=”http://www.google.com/reader/link?url=<?php echo get_permalink() ?>&title=<?php the_title();?>&snippet=<?php the_excerpt(); ?>&srcURL=<?php echo get_settings(‘home’); ?>” Title=”Share this via Google Buzz><img="<?php echo bloginfo('template_url');">/images/buzz-icon2.gif"/>
</a> Google Buzz

Also looking between the various utilities proposed in Google Reader you can add a small clip (bottom of the page under “Add a clip”) to your site, where “share” show your Buzz’s.

One of the nice features that the Ajax has brought with it, is surely the autosave. When we write a new article, a special javascript allows you to save, within a specified timeframe, the draft we have produced. For example we are writing and you lose connection, or for majeure force you must dedicate ourselves to something else, without this handy feature we will be with the “old” time-out page and we will have to rewrite everything from scratch. Despite its usefulness, however, there may have needs for which this function is counterproductive.

The developers of WordPress have a far-sighted thinking to specific functions of “changing the classification” of some PHP classes. So to disable autosaving you must add a specific function in the file functions.php present among the files of your theme.

1
2
3
4

function disableAutoSave()(wp_deregister_script
    ('autosave');)
 
add_action( 'wp_print_scripts', 'disableAutoSave');

Function wp_deregister precisely intercept the script and disable autosave. If we want to rehabilitate the function we need to delete the lines above.

From version 2.9 of WordPress you have a Recycle Bin for articles. Definitely a step forward that brings in the dimension of the WordPress as CMS. Trash is emptied automatically every 30 days, but if you want change this you can do a little touch to the wp-config.php file present in your web root.

Add the line:
define( 'EMPTY_TRASH_DAYS', 15 );
where the value 15 are the days that pass from the time when an article ends up in the trash when it is finally eliminated.
And if we want to completely disable the trash? We do this by inserting the value zero