By using get_userdatabylogin

$user = get_userdatabylogin('loginname');
if($user){
   echo $user->ID;
}

This is for static use (just one domain):

define('WP_HOME', 'http://onyou.ch');
define('WP_SITEURL', 'http://onyou.ch');

For more than one domain set these values dynamically:

define('WP_HOME', 'http://'.$_SERVER['HTTP_HOST']);
define('WP_SITEURL', 'http://'.$_SERVER['HTTP_HOST']);

UPDATE wp_posts SET guid = REPLACE (guid,'www.oldsite.com','www.newsite.com');
UPDATE wp_posts SET post_content = REPLACE (post_content, 'www.oldsite.com', 'www.newsite.com');
UPDATE wp_options SET option_value = replace(option_value,  'www.oldsite.com', 'www.newsite.com') WHERE option_name = 'home' OR option_name = 'siteurl';

You might also need to remove the entry “rewrite_rules” in your wp_options table.

Have fun!

This sample script is embedded directly in the html, but it could also be included in a js file.

<pre><code><script type="text/javascript">
    $(document).ready(function() {
        $("#hidden_link").fancybox().trigger('click');
    });
</script></code>

var encoded = "" ' & < >";
alert(encoded);
var decoded = $('<textarea />').html(encoded).val();
alert(decoded);

or

var decoded = $("<div/>").html(encoded).text();

Note that both parent and child need to include the jQuery postMessage javascript.

The parent frame code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

<script type="text/javascript" src="jquery.ba-postmessage.min.js"></script>
 
<div id="iframe"></div>
 
<script type="text/javascript">
(function ($) {
var if_height,
       src = 'http://childframeurl.com#' + encodeURIComponent( document.location.href ),
       iframe = $( '<iframe " src="' + src + '" width="700" height="1000" scrolling="no" frameborder="0"><\/iframe>' ).appendTo( '#iframe' );
 
       setInterval(function getHeight() {
             $.receiveMessage(function(e){
                    var h = Number( e.data.replace( /.*if_height=(\d+)(?:&|$)/, '$1' ) );
                    if ( !isNaN( h ) && h > 0 && h !== if_height ) {
                    // Height has changed, update the iframe.
                    iframe.height( if_height = h );
                    }
             } );
       }, 500);
})(jQuery);
</script>

The child frame code

1
2
3
4
5
6
7
8
9
10
11
12
13
14

<script type="text/javascript" src="jquery.ba-postmessage.min.js"></script>
<script type="text/javascript">
(function ($) {
       $(document).ready(function() {
             var parent_url = decodeURIComponent( document.location.hash.replace( /^#/, '' ) ),link;
 
             function setHeight() {
                    $.postMessage({ if_height: $('body').outerHeight( true ) }, parent_url, parent );
             };
             setHeight();
             setInterval(setHeight, 500);
       });
})(jQuery);
</script>

http://webdesign.onyou.ch/2010/12/26/absolute-and-relative-urls/

Relative URLs don’t contain all the components and are always considered with respect to a base URL. A relative URL is resolved to an absolute URL, with respect to the base URL. Typically, a relative URL contains the path components of a resource and allows related sets of resources to reference each other in a relative way. This allows path hierarchies to be readily changed without the need to change every URL embedded in a set of documents.

The following table shows several relative URLs and how they are resolved to the corresponding absolute URLs given the base URL http://onyou.ch/a/b/c.html?foo=bar.

• Robots.txt directives
• Nofollow attributes on links
• Meta noindex/nofollow directives
• X-Robots noindex/nofollow directives

..and so on. These directives all function in different ways, but they all serve the same basic purpose: control how Google crawls the various pages on your site. For example, you can use meta noindex to instruct Google not to index your sitemap, RSS feed, or any other page you wish. This level of control over which pages are crawled and indexed is helpful, but what if you need to control how Google crawls the contents of a specific page? Easy. Google enables us to do this with a set of googleon/googleoff tags.

ABOUT GOOGLEON AND GOOGLEOFF TAGS

Put simply, the googleon/googleoff tags tell Google Search Appliance when to start and stop indexing various parts of the web document. Consider the following example:

<p>This is normal (X)HTML content that will be indexed by Google.</p>
 
<!--googleoff: index-->
 
<p>This (X)HTML content will NOT be indexed by Google.</p>
 
<!--googleon: index-->

In this example, we see how the googleon/googleoff tags will prevent the second paragraph from being indexed by Google. Notice the “index” parameter, which may be set to any of the following:

• index – content surrounded by “googleoff: index” will not be indexed by Google
• anchor – anchor text for any links within a “googleoff: anchor” area will not be associated with the target page
• snippet – content surrounded by “googleoff: snippet” will not be used to create snippets for search results
• all – content surrounded by “googleoff: all” are treated with all attributes: index, anchor, and snippet

Cool, eh? Let’s have a look at a specific usage example..

USING GOOGLEON AND GOOGLEOFF TAGS

Let’s say your comment threads tend to stray into off-topic conversation. Keeping your pages as tightly focused on the subject at hand is a great way to improve the on-page relevancy of your targeted keywords while improving the accuracy of matching search queries. Thus, to keep the superfluous banter out of the Google index, you could add googleon/googleoff tags as follows:

<!--googleoff: all-->
 
<div id="comments">
 
   <p><strong>Nick Mason</strong> - August 2nd, 2009</p>
   <p>From Her Majesty the queen. His boots were very clean.</p>
 
   <p><strong>Rick Wright</strong> - August 3rd, 2009</p>
   <p>Every year is getting shorter, never seem to find the time.</p>
 
   <p><strong>David Gilmour</strong> - August 4th, 2009</p>
   <p>By the river holding hands roll me up and lay me down.</p>
 
   <p><strong>Roger Waters</strong> - August 5th, 2009</p>
   <p>And after a while, you can work on points for style.</p>
 
</div>
 
<!--googleon: all-->

We definitely don’t want to see such a mindless thread in Google, and it will be interesting to see if the <pre> example gets dropped from the index..

MAY THE FORCE BE WITH YOU

While using this method to control how Google indexes your on-page content, there are a couple of things you should keep in mind. First, there is a difference between indexing and crawling. Google may crawl portions of your page that are demarcated with googleon/googleoff tags. So in case you were thinking that this technique may be a way to deal with Google’s new nofollow policy, forget about it — PageRank will continue to flow through any links contained within a googleoff zone.

Besides this, also keep in mind that this is a proprietary technique supported exclusively by Google Search Appliance. If you have content that you want to keep out of the index of allsearch engines, then you will need to find another way to do it. Eventually, Yahoo! and MSN/Live/Bing/Whatever may create proprietary “on/off tags” of their own, but chances are slim to none that they will obey the proprietary technology of the mighty Google.

For more information about googleon/googleoff tags, check out Google’s official documentation.