header.php footer.php index.php s i d e b a r . p h p WordPress Help Sheet. <?php bloginfo('name'); ?> <?php wp_title(); ?> <?php bloginfo('stylesheet_url'); ?> <?php bloginfo('pingback_url'); ?> <?php bloginfo('template_url'); ?> <?php bloginfo('version
header.php footer.php index.php s i d e b a r . p h p WordPress Help Sheet. <?php bloginfo('name'); ?> <?php wp_title(); ?> <?php bloginfo('stylesheet_url'); ?> <?php bloginfo('pingback_url'); ?> <?php bloginfo('template_url'); ?> <?php bloginfo('version'); ?> <?php bloginfo('atom_url'); ?> <?php bloginfo('rss2_url'); ?> <?php bloginfo('url'); ?> <?php bloginfo('name'); ?> <?php bloginfo('html_ty
WordPress 2.1.1 dangerous, Upgrade to 2.1.2
Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. Longer explanation: This morning we received a note to our security mailing address about unusual and highly exploitable code in WordPress. The issue was investigated, and it appeared that
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
