WP hooks navigation: Home/browse • Actions index • Filters index
To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).
The best way to understand what a hook does is to look at where it occurs in the source code.
do_action( "hook_name" )
apply_filters( "hook_name", "what_to_filter" )
.Remember, this hook may occur in more than one file. Moreover, the hook's context may change from version to version.
Line | Code |
---|---|
609 | delete_option('dccat2wpcat'); |
610 | delete_option('dcposts2wpposts'); |
611 | delete_option('dccm2wpcm'); |
612 | delete_option('dclinks2wplinks'); |
613 | delete_option('dcuser'); |
614 | delete_option('dcpass'); |
615 | delete_option('dcname'); |
616 | delete_option('dchost'); |
617 | delete_option('dccharset'); |
618 | do_action('import_done', 'dotclear'); |
619 | $this->tips(); |
620 | } |
621 |
|
622 | function tips() |
623 | { |
624 | echo '<p>'.__('Welcome to WordPress. We hope (and expect!) that you will find this platform incredibly rewarding! As a new WordPress user coming from DotClear, there are some things that we would like to point out. Hopefully, they will help your transition go as smoothly as possible.').'</p>'; |
625 | echo '<h3>'.__('Users').'</h3>'; |
626 | echo '<p>'.sprintf(__('You have already setup WordPress and have been assigned an administrative login and password. Forget it. You didn\'t have that login in DotClear, why should you have it here? Instead we have taken care to import all of your users into our system. Unfortunately there is one downside. Because both WordPress and DotClear uses a strong encryption hash with passwords, it is impossible to decrypt it and we are forced to assign temporary passwords to all your users. <strong>Every user has the same username, but their passwords are reset to password123.</strong> So <a href="%1$s">Login</a> and change it.'), '/wp-login.php').'</p>'; |
627 | echo '<h3>'.__('Preserving Authors').'</h3>'; |