number_format — Format a number with grouped thousands.

number_format ( float $number [, int $decimals ] )
number_format ( float $number  , int $decimals  , string $dec_point  , string $thousands_sep  )

• $number: Required. The number to be formatted. If no other parameters are set, the number will be formatted without decimals and with comma (,) as the thousands separator.
• $decimals: Optional. Specifies how many decimals. If this parameter is set, the number will be formatted with a dot (.) as decimal point.
• $dec_point: Optional. Specifies what string to use for decimal point.
• $thousands_sep: Optional. Specifies what string to use for thousands separator. Only the first character of separator is used. For example, “xxx” will give the same output as “x”. ( If this parameter is given, all other parameters are required as well. )

Note: This function supports one, two, or four parameters (not three).

Example:

echo number_format("1000000");
echo "<br />";
echo number_format("1000000",2);
echo "<br />";
echo number_format("1000000",2,",",".");

Results:

1,000,000
1,000,000.00
1.000.000,00

Tehnologies: Macromedia Flash.

UPDATE tablename SET tablefield = replace(tablefield, "findstring", "replacestring");

You can also tack on a WHERE statement, if you like.

Example:

UPDATE node SET body1 = replace(body1,'cat','dog'), body2 =  replace(body2,'cat','dog')

Try:

<?php
     mysql_query("SET CHARACTER SET 'utf8'", $connection);
?>

Links:
http://dev.mysql.com/doc/refman/5.1/en/charset-connection.html

Global $oMyError = ObjEvent("AutoIt.Error", "COMError")
InetGet("http://thottbot.com/?s=", @ScriptDir & "\html.html")
$sSource = FileRead(@ScriptDir & "\html.html")
$sPlainText = _HTML_StripTags($sSource)
ConsoleWrite($sPlainText & @CRLF)
Func _HTML_StripTags($sHTML)
    If Not StringStripWS($sHTML, 8 ) Then Return SetError(1, 0, "")
    Local $oHTML = ObjCreate("HTMLFILE")
    If @error Then Return SetError(2, 0, "")
    $oHTML.Open()
    $oHTML.Write($sHTML)
    If Not $oHTML.Body.InnerText Then Return SetError(3, 0, "")
    Return SetError(0, 0, $oHTML.Body.InnerText)
EndFunc   ;==>_HTML_StripTags
Func COMError()
    MsgBox(16, "AutoItCOM Test", "We intercepted a COM Error !" & @CRLF & @CRLF & _
            "err.description is: " & @TAB & $oMyError.description & @CRLF & _
            "err.windescription:" & @TAB & $oMyError.windescription & @CRLF & _
            "err.number is: " & @TAB & Hex($oMyError.number, 8) & @CRLF & _
            "err.lastdllerror is: " & @TAB & $oMyError.lastdllerror & @CRLF & _
            "err.scriptline is: " & @TAB & $oMyError.scriptline & @CRLF & _
            "err.source is: " & @TAB & $oMyError.source & @CRLF & _
            "err.helpfile is: " & @TAB & $oMyError.helpfile & @CRLF & _
            "err.helpcontext is: " & @TAB & $oMyError.helpcontext _
            )
    SetError(1)
EndFunc   ;==>COMError

I’ve never been one too keen Grey’s css min-height hack, mainly because of the bulky workaround in your html. Sure hacks can cause bulkier CSS, but I’m ok with that. The problem with Grey’s is that it’s not only a ‘CSS‘ hack (which I’m totally fine with), but it also involves changing your html. I’m none too delighted that you need to add two separate empty div elements just to get this working correctly. Nevermind the matter, he thought of this ages ago when I was still learning how to count to twelve on sesame street. Ok so I learned that like last year, I’m catching on.

#minheight {
     min-height:400px;
     display:table;
     height: auto !important; /* for modern browsers */
     *display: block; /* for IE5.x and IE6 */ 
     _height: 400px; /* for IE5.x and IE6 */
}

Assuming IE6 will not fix the correct implementation for the !important declaration and assuming that if IE7 does, they’ll also implement min-height correctly since at the pace they’re going they’re fixing CSS like mad crazy cows.

The above snippet of CSS works like a charm in IE6, Mozilla/Firefox/Gecko, Opera 7.x+, Safari1.2

Description

Retrieve post object by post name.

Usage

<?php get_post_by_slug( $post_name ) ?>

Parameters

$post_name
(string) (required) The post name.
Default: None

Return Values

(object)
Post data object

Examples

<?php
     function get_post_by_slug($post_name, $output = OBJECT)
     {
         global $wpdb;
         $post = $wpdb->get_var( $wpdb->prepare( "SELECT ID FROM $wpdb->posts WHERE post_name = %s AND post_type='post'", $post_name ));
         if ( $post )
             return get_post($post, $output);

         return null;
     }
?>

Related

Function Reference / get_category_by_slug()

Tehnologies: Template Design (Layout, CSS, HTML), Macromedia Flash and XML.

Tehnologies: Template Design (Layout, CSS, HTML), Macromedia Flash and XML.

Using Magento by iClickNetwork team.

Tags:

Since IE 6 and 7 support pointer, there’s no more reason to use hand, except when older IEs are part of your target audience. In that case, the only cross-browser syntax is:

element {
      cursor: pointer;
      cursor: hand;
}

Then you need the “cursor: pointer” rule to have the clickable mouse icon show up.

In CSS, the following rule is used to display an clickable cursor icon:

cursor: pointer;

However, you sometimes will see code that uses …

cursor: hand;

So should one use “pointer” or “hand”?

All “modern” browsers will support “pointer” and that is the W3C standard. As you can see from the W3C specs, “hand” is not a valid valid for the “cursor” property. Also, Firefox and Safari does not support the “hand” value and requires “pointer”. The “hand” value is only needed by Internet Explorer 5.5 and below. You can see which browser support which values in this table at Quirksmode.

With Internet Explorer 7.0 out at the time of this writing, Internet Explorer 5.5 is somewhat obsolete. Hence, I would just use “cursor: pointer”.

However, if you want to support lower Internet Explorer browsers, put both property values with the “pointer” listed last…

cursor: hand;
cursor: pointer;

But note that having “cursor: hand” in your CSS will fail W3C validation when you put your URL into W3C validator.