Important Things 1999

I just copied and pasted the code from source php file,

// Add custom shortcuts
ed.addShortcut(‘alt+shift+c’, ed.getLang(‘justifycenter_desc’), ‘JustifyCenter’);
ed.addShortcut(‘alt+shift+r’, ed.getLang(‘justifyright_desc’), ‘JustifyRight’);
ed.addShortcut(‘alt+shift+l’, ed.getLang(‘justifyleft_desc’), ‘JustifyLeft’);
ed.addShortcut(‘alt+shift+j’, ed.getLang(‘justifyfull_desc’), ‘JustifyFull’);
ed.addShortcut(‘alt+shift+q’, ed.getLang(‘blockquote_desc’), ‘mceBlockQuote’);
ed.addShortcut(‘alt+shift+u’, ed.getLang(‘bullist_desc’), ‘InsertUnorderedList’);
ed.addShortcut(‘alt+shift+o’, ed.getLang(‘numlist_desc’), ‘InsertOrderedList’);
ed.addShortcut(‘alt+shift+d’, ed.getLang(‘striketrough_desc’), ‘Strikethrough’);
ed.addShortcut(‘alt+shift+n’, ed.getLang(‘spellchecker.desc’), ‘mceSpellCheck’);
ed.addShortcut(‘alt+shift+a’, ed.getLang(‘link_desc’), ‘mceLink’);
ed.addShortcut(‘alt+shift+s’, ed.getLang(‘unlink_desc’), ‘unlink’);
ed.addShortcut(‘alt+shift+m’, ed.getLang(‘image_desc’), ‘mceImage’);
ed.addShortcut(‘alt+shift+g’, ed.getLang(‘fullscreen.desc’), ‘mceFullScreen’);
ed.addShortcut(‘alt+shift+z’, ed.getLang(‘wp_adv_desc’), ‘WP_Adv’);
ed.addShortcut(‘alt+shift+h’, ed.getLang(‘help_desc’), ‘WP_Help’);
ed.addShortcut(‘alt+shift+t‘, ed.getLang(‘wp_more_desc’), ‘WP_More‘);
ed.addShortcut(‘alt+shift+p‘, ed.getLang(‘wp_page_desc’), ‘WP_Page‘);

if ( tinymce.isWebKit ) {
ed.addShortcut(‘alt+shift+b‘, ed.getLang(‘bold_desc’), ‘Bold‘);
ed.addShortcut(‘alt+shift+i‘, ed.getLang(‘italic_desc’), ‘Italic‘);
}

WordPress V2.7 released today.

But my upgrade failed. After upgraded from V2.6.5 to V2.7, the page cann’t be opened, it shows “Fatal error: Call to undefined function wp_remote_request()”.
So, return V2.6.5.
The newest is NOT the best!

I think this could be plugins or themes problem.

The result may be different, if deactivate all plugins and use default theme before upgrade.

Refer: http://wordpress.org/support/topic/224102

Today, tested WordPress database recover backuped by “WordPress Database Backup”

1. I have set up WordPress Database Backup to backup WordPress database daily and email to my gmail account

2. download the last database backup file .sql.gz from gmail

3. open phpMyAdmin, choose import, and select .gz file downloaded

4. apply.

Succeed!

My backup plan:

1. Plugin using auto-update, and download plugins and other directories to local by FTP

2. WordPress Database backuped by “WordPress Database Backup“, and email to Gmail daily.

3. local files backup to Mozy.com daily.

The original article is here: http://codex.wordpress.org/Revision_Management

Revision Management

Autosaves

There is only ever a maximum of one autosave for any given post. New autosaves overwrite old autosaves. This means that no, your tables do not grow by one row every 60 seconds.

Autosaves are enabled for all posts and pages but do not overwrite published content. Autosaves are stored as a special type of revision; they do not overwrite the actual post. In fact, if your browser does crash, when you go to edit that post, WP will toss up a warning that says something like “This post has an autosave which is more recent that the post itself. Would you like to see it?” With a link to the revision page from where it can be restored/ignored.
Revision Options

There are options, but they are hidden well :) There is a constant (not even filterable) that can be set by a plugin or in your wp-config.php file:

WP_POST_REVISIONS:

* true (default), -1: store every revision
* false, 0: do not store any revisions (except the one autosave per post)
* (int) > 0: store that many revisions (+1 autosave) per post. Old revisions are automatically deleted.

Read more…

After WordPress installation, please modify the wp-config.php in the root directory of WordPress, the original part is like:

// Change each KEY to a different unique phrase.  You won’t have to remember the phrases later,
// so make them long and complicated.  You can visit http://api.wordpress.org/secret-key/1.1/
// to get keys generated for you, or just make something up.  Each key should have a different phrase.
define(‘AUTH_KEY’, ‘put your unique phrase here’); // Change this to a unique phrase.
define(‘SECURE_AUTH_KEY’, ‘put your unique phrase here’); // Change this to a unique phrase.
define(‘LOGGED_IN_KEY’, ‘put your unique phrase here’); // Change this to a unique phrase.

According to the notes, visit http://api.wordpress.org/secret-key/1.1/

Get your unique key, maybe it looks like

define(‘AUTH_KEY’, ‘jbT[&w<@&0xCg3LC7Sy4OF-4F=Lr7}AO`B\’taCDYA1bXNG@Q_4^Fr[~)uX4′);
define(‘SECURE_AUTH_KEY’, ‘$n[\”P11E\’mxhSyNoPyS\”>SA|VRQ4dUOY;y;#NM*aN-xIv{.G+Sryw;AnGg|evUc~’);
define(‘LOGGED_IN_KEY’, ‘`f-1jets5W*Ou)XT+uD\’`#RFdTgk4GCK$U^Qp\”-_jPr p{Xy/O~ |0)3o9BLQoQ0′);

it’s very cool! Can you make so complicated string?

Then, modify your new wp-config.php with those string, upload it by ftp.

When you manage your WordPress site, you need login again because of those modification.