Link: http://validator.w3.org/mobile/

First, the device must be identified so the correct content can be served.

An .htaccess file can be used, or these settings can be placed in httpd.conf (or an included .conf file). This is an Apache 1.3 version, 2.+ may be slightly different.

Code:

In this case, the page is a very simple page, to let people know that they need to use a browser to visit the page.

XML:

Validate the code using the link above to ensure it displays well in most devices.

Link: http://jetscripts.com/

Cool scripts that are worth buying. The purchase price is far less than the cost of the time you’d have to spend to write them yourself, and, in my case, the code’s much better, too.

http://jetscripts.com/sanitizer.htm - This is a much improved version of script that’s been shared and used by many people. It protects your code, data, and server. I’m using this on several systems.

http://jetscripts.com/geotool/ - This script allows you to prevent people from various locations from visiting your site. If your target market is the United States, and you don’t sell to or serve other people, there’s no need to serve pages to the rest of the world. You can customize the interface so the message.

http://jetscripts.com/captcha/ - Most people don’t like CAPTCHA forms - the images are difficult to read, and the code can be bothersome to integrate. This one’s easy to read and easy to work with.

http://jetscripts.com/jetbanners.htm - Awesome. Check it out.

This template makes a feedback form a little easier to use. It sets up the from and the subject out of the submitted content, and puts the message in as text.

Code:

Be sure to adjust your attribute names if necessary.

Link: http://httpd.apache.org/docs/2.2/mod/mod_headers.html

The question was whether the number of rewrite rules in .htaccess would have a significant impact on performance.

With the following set of rewrite rules:

Code:

The results were:

Received: t=1267660375832889 Duration: D=273652
Received: t=1267660761803171 Duration: D=297682
Received: t=1267660779066518 Duration: D=272959
Received: t=1267660804103095 Duration: D=292675
Received: t=1267660821137470 Duration: D=256268

This set of rewrite rules:

Code:

Yielded these results:

Received: t=1267660624947466 Duration: D=279933
Received: t=1267660660237894 Duration: D=289207
Received: t=1267660681578539 Duration: D=327192
Received: t=1267660701894745 Duration: D=254252
Received: t=1267660719493366 Duration: D=262131

This was a very informal test, just to see if there were any glaring differences, as you can see, the results were reasonably close.

A team member requested a list of users and email addresses from an eZ publish site, and I remembered seeing a file called ezcsvexport.com under php/bin.

After a few tries, I found the following sequence of commands worked really well.

CSV_EXPORT_BASE=~/tools/export
cd ~/public_html/ez
/usr/local/bin/php -C bin/php/ezcsvexport.php 12 –storage-dir=$CSV_EXPORT_BASE -smsite -q -l export -p password 2> /dev/null
rm $CSV_EXPORT_BASE/*.png 2> /dev/null
rm $CSV_EXPORT_BASE/*.jpg 2> /dev/null
rm $CSV_EXPORT_BASE/*.gif 2> /dev/null
rm $CSV_EXPORT_BASE/*.bmp 2> /dev/null
sed “s/\([^\;]*\);\([^\;]*\);[^\|]*[\|]\(\|[^\|]*\)[\|].*$/\1,\2,\3/” $CSV_EXPORT_BASE/user.csv | grep -v ‘;’ | grep ‘@’ | mail email@domain.com -s “eZ Guest Accounts”

This created a file called user.csv, which was delimited with semicolons and included all the information. The account information (username, email, etc) was serialized, meaning separated with vertical bars or piping characters. I used sed to replace the semicolons with commas, and find the second element of the user account data (the email address). Some people had added signatures, so one grep command was used to get only those lines with @s in them, since that indicates an email address. Finally the whole thing was piped through mail and sent to the requestor.

The export script saved me a lot of time.