HelpHub

custom_field_example

atachibana — Sat, 27 Feb 2016 17:00:02 +0000

managepages-enV4.4.2

atachibana — Tue, 08 Mar 2016 00:57:17 +0000

add-new-post

normalize — Tue, 15 Mar 2016 02:29:29 +0000

add-new-post-options

normalize — Tue, 15 Mar 2016 02:33:11 +0000

Pages-AddNew-4.3

greensteph — Tue, 15 Mar 2016 13:47:40 +0000

menu-screen1

normalize — Sat, 19 Mar 2016 01:28:26 +0000

menu-screen2

normalize — Sat, 19 Mar 2016 01:28:27 +0000

menu-screen3

normalize — Sat, 19 Mar 2016 01:28:27 +0000

menu-screen4

normalize — Sat, 19 Mar 2016 01:28:27 +0000

menu-screen5

normalize — Sat, 19 Mar 2016 01:28:28 +0000

menu-screen6

normalize — Sat, 19 Mar 2016 01:28:28 +0000

howdyuser

atachibana — Sun, 27 Mar 2016 09:47:29 +0000

screenoptions

atachibana — Sun, 27 Mar 2016 09:48:49 +0000

appearance-customize-widgets

atachibana — Sun, 10 Apr 2016 14:40:00 +0000

designwidget

atachibana — Sun, 10 Apr 2016 14:41:07 +0000

writepage

atachibana — Sun, 10 Apr 2016 14:59:28 +0000

phpmyadmin_top

atachibana — Sat, 23 Apr 2016 08:47:45 +0000

phpmyadmin_dbtop

atachibana — Sat, 23 Apr 2016 08:52:31 +0000

phpmyadmin_quick_export

atachibana — Sat, 23 Apr 2016 08:53:30 +0000

phpmyadmin_custom_export

atachibana — Sat, 23 Apr 2016 09:04:48 +0000

phpmyadmin_export_output

atachibana — Sat, 23 Apr 2016 09:18:01 +0000

phpmyadmin_export_formatspecific

atachibana — Sat, 23 Apr 2016 09:18:51 +0000

phpmyadmin_export_object

atachibana — Sat, 23 Apr 2016 09:19:40 +0000

phpmyadmin_export_data

atachibana — Sat, 23 Apr 2016 09:20:18 +0000

mysql_workbench_top

atachibana — Sat, 23 Apr 2016 09:20:59 +0000

mysql_workbench_export

atachibana — Sat, 23 Apr 2016 09:21:45 +0000

mysql_workbench_export2

atachibana — Sat, 23 Apr 2016 09:22:25 +0000

mysql_workbench_import

atachibana — Sat, 23 Apr 2016 09:23:00 +0000

wp-db-backup_table

atachibana — Sat, 23 Apr 2016 09:23:36 +0000

wp-db-backup_settings

atachibana — Sat, 23 Apr 2016 09:24:14 +0000

podz_filezilla_1

atachibana — Sat, 23 Apr 2016 12:55:03 +0000

podz_filezilla_3

atachibana — Sat, 23 Apr 2016 12:57:49 +0000

Adding items to menu

bellaratmelia — Mon, 25 Apr 2016 07:08:41 +0000

Adding menu to site

bellaratmelia — Mon, 25 Apr 2016 07:08:43 +0000

Creating a menu

bellaratmelia — Mon, 25 Apr 2016 07:08:48 +0000

Deleting a menu item

bellaratmelia — Mon, 25 Apr 2016 07:08:49 +0000

Creating sub items 3.13.39 pm

bellaratmelia — Mon, 25 Apr 2016 07:14:09 +0000

managefiles

atachibana — Fri, 29 Apr 2016 04:18:31 +0000

attachedfile-detail

atachibana — Fri, 29 Apr 2016 04:19:15 +0000

medialibrary_listview

atachibana — Fri, 29 Apr 2016 04:20:33 +0000

find-posts-or-pages

atachibana — Fri, 29 Apr 2016 04:21:10 +0000

manageposts

atachibana — Fri, 29 Apr 2016 04:33:25 +0000

designwidget

atachibana — Fri, 29 Apr 2016 05:06:54 +0000

designwidget

atachibana — Fri, 29 Apr 2016 05:13:23 +0000

options-permalinks

atachibana — Fri, 29 Apr 2016 05:46:36 +0000

cpanel-dbwizardicon

atachibana — Fri, 29 Apr 2016 05:53:53 +0000

cpanel-createdb-step1

atachibana — Fri, 29 Apr 2016 05:54:23 +0000

cpanel-createdb-step2

atachibana — Fri, 29 Apr 2016 05:54:54 +0000

cpanel-createdb-step3

atachibana — Fri, 29 Apr 2016 05:55:47 +0000

cpanel-createdb-step4

atachibana — Fri, 29 Apr 2016 05:56:38 +0000

posts-bulk-edit-screen

atachibana — Fri, 29 Apr 2016 06:10:55 +0000

wp_db_bu3

atachibana — Sun, 08 May 2016 13:14:39 +0000

wp_db_bu

atachibana — Sun, 08 May 2016 13:15:25 +0000

wp_db_bu2

atachibana — Sun, 08 May 2016 13:18:10 +0000

cpanel1

atachibana — Sun, 08 May 2016 13:22:15 +0000

cpanel2

atachibana — Sun, 08 May 2016 13:23:24 +0000

direct1

atachibana — Sun, 08 May 2016 13:25:36 +0000

direct2

atachibana — Sun, 08 May 2016 13:26:11 +0000

ensim1

atachibana — Sun, 08 May 2016 13:30:31 +0000

ensim2

atachibana — Sun, 08 May 2016 13:30:58 +0000

vdeck1

atachibana — Sun, 08 May 2016 13:31:34 +0000

vdeck1-2

atachibana — Sun, 08 May 2016 13:32:37 +0000

vdeck2

atachibana — Sun, 08 May 2016 13:32:53 +0000

ferozo-backup

atachibana — Sun, 08 May 2016 13:34:34 +0000

phpmyadmin_top_dbindicated

atachibana — Sun, 08 May 2016 13:35:46 +0000

customizer-siteicon

atachibana — Sat, 21 May 2016 16:41:55 +0000

posteditor_more_button_text

atachibana — Sun, 29 May 2016 14:05:36 +0000

leaf

atachibana — Sun, 29 May 2016 14:26:38 +0000

css_display_original

geoffreyshilling — Mon, 30 May 2016 19:32:14 +0000

internalservererror2

atachibana — Sun, 19 Jun 2016 14:11:11 +0000

dberror1

atachibana — Sun, 19 Jun 2016 14:12:05 +0000

maintenancemode1

atachibana — Sun, 19 Jun 2016 14:13:13 +0000

menu-screen1

normalize — Mon, 27 Jun 2016 00:40:27 +0000

menu-screen2

normalize — Mon, 27 Jun 2016 00:40:27 +0000

menu-screen3

normalize — Mon, 27 Jun 2016 00:40:28 +0000

menu-screen4

normalize — Mon, 27 Jun 2016 00:40:28 +0000

menu-screen5

normalize — Mon, 27 Jun 2016 00:40:29 +0000

menu-screen6

normalize — Mon, 27 Jun 2016 00:40:29 +0000

leaf

normalize — Mon, 27 Jun 2016 00:56:13 +0000

rssfeed

atachibana — Sun, 03 Jul 2016 13:36:44 +0000

icon_smile

atachibana — Sun, 10 Jul 2016 14:03:11 +0000

icon_wink

atachibana — Sun, 10 Jul 2016 14:04:23 +0000

icon_sad

atachibana — Sun, 10 Jul 2016 14:05:35 +0000

icon_confused

atachibana — Sun, 10 Jul 2016 14:06:03 +0000

icon_redface

atachibana — Sun, 10 Jul 2016 14:17:22 +0000

icon_rolleyes

atachibana — Sun, 10 Jul 2016 14:18:06 +0000

icon_eek

atachibana — Sun, 10 Jul 2016 14:18:40 +0000

645px-2016_Comment_form

normalize — Mon, 11 Jul 2016 15:34:08 +0000

discussion_checked

normalize — Mon, 11 Jul 2016 15:35:08 +0000

quick_edit_link

normalize — Mon, 11 Jul 2016 15:35:39 +0000

bulk_action_allow_comments

normalize — Mon, 11 Jul 2016 15:36:04 +0000

recent_comments_dashboard

normalize — Mon, 11 Jul 2016 15:36:23 +0000

comment_pending_numbered_smaller

normalize — Mon, 11 Jul 2016 15:36:45 +0000

bulk_approve_comments

normalize — Mon, 11 Jul 2016 15:37:12 +0000

visibility

normalize — Mon, 11 Jul 2016 15:40:56 +0000

expanded_visibility

normalize — Mon, 11 Jul 2016 15:41:30 +0000

protected_post

normalize — Mon, 11 Jul 2016 15:41:58 +0000

private_visibility

normalize — Mon, 11 Jul 2016 15:42:28 +0000

Managing_links_add_link

normalize — Mon, 11 Jul 2016 15:49:51 +0000

Managing_links_links_screen

normalize — Mon, 11 Jul 2016 15:50:53 +0000

Managing_links_link_order

normalize — Mon, 11 Jul 2016 15:51:21 +0000

Managing_links_add_link (1)

normalize — Mon, 11 Jul 2016 15:51:49 +0000

Managing_links_add_link_screen

normalize — Mon, 11 Jul 2016 15:52:09 +0000

Managing_links_add_link_save

normalize — Mon, 11 Jul 2016 15:52:41 +0000

Managing_links_edit_link

normalize — Mon, 11 Jul 2016 15:53:01 +0000

Managing_links_edit_link (1)

normalize — Mon, 11 Jul 2016 15:53:30 +0000

Managing_links_delete_link_sure_box

normalize — Mon, 11 Jul 2016 15:53:56 +0000

Managing_links_delete_links

normalize — Mon, 11 Jul 2016 15:54:21 +0000

links_categories_2

normalize — Mon, 11 Jul 2016 15:55:01 +0000

Managing_links_add_link (2)

normalize — Mon, 11 Jul 2016 15:55:26 +0000

links_categories_1

normalize — Mon, 11 Jul 2016 15:55:52 +0000

published-gallery

atachibana — Mon, 11 Jul 2016 16:16:39 +0000

gallery-place-cursor

atachibana — Mon, 11 Jul 2016 16:20:53 +0000

gallery-add-media-button

atachibana — Mon, 11 Jul 2016 16:21:33 +0000

drag-to-start-gallery

atachibana — Mon, 11 Jul 2016 16:24:37 +0000

create-gallery

atachibana — Mon, 11 Jul 2016 16:25:06 +0000

edit-gallery-drag

atachibana — Mon, 11 Jul 2016 16:25:57 +0000

gallery-in-visual-editor

atachibana — Mon, 11 Jul 2016 16:26:29 +0000

edit-gallery

atachibana — Mon, 11 Jul 2016 16:26:58 +0000

profile

atachibana — Tue, 12 Jul 2016 14:02:02 +0000

profile-colors

atachibana — Tue, 12 Jul 2016 14:04:10 +0000

device-preview

atachibana — Tue, 12 Jul 2016 22:15:34 +0000

theme-logo-support

atachibana — Tue, 12 Jul 2016 22:16:06 +0000

inline-link-editing

atachibana — Tue, 12 Jul 2016 22:16:36 +0000

moderate_comment_v4.5

atachibana — Tue, 12 Jul 2016 22:17:38 +0000

protected_edit

atachibana — Thu, 14 Jul 2016 22:11:24 +0000

protected_password

atachibana — Thu, 14 Jul 2016 22:12:14 +0000

protected_content

atachibana — Thu, 14 Jul 2016 22:13:56 +0000

error_console

atachibana — Sat, 16 Jul 2016 10:44:54 +0000

ie_console1

atachibana — Sat, 16 Jul 2016 10:45:53 +0000

ie_console2

atachibana — Sat, 16 Jul 2016 10:46:23 +0000

chrome_console

atachibana — Sat, 16 Jul 2016 10:47:06 +0000

debug_safari

atachibana — Sat, 16 Jul 2016 12:22:24 +0000

debug_safari4

atachibana — Sat, 16 Jul 2016 12:22:53 +0000

debug_safari3

atachibana — Sat, 16 Jul 2016 12:23:21 +0000

opera_console

atachibana — Sat, 16 Jul 2016 12:23:51 +0000

hovercard

atachibana — Sat, 16 Jul 2016 13:14:51 +0000

new_default_avatar_comment

atachibana — Sat, 16 Jul 2016 13:14:52 +0000

new_default_avatar_list

atachibana — Sat, 16 Jul 2016 13:14:53 +0000

gravatar_example

atachibana — Sat, 16 Jul 2016 13:14:53 +0000

browseruploader2

atachibana — Sat, 16 Jul 2016 14:17:13 +0000

addnewpage

atachibana — Sat, 16 Jul 2016 14:17:14 +0000

760px-options-general

atachibana — Sat, 16 Jul 2016 14:24:38 +0000

MS-Web-Matrix-5_Browser-localhost

atachibana — Sun, 17 Jul 2016 00:31:00 +0000

MS-Web-Matrix-3_Select-Site-tab

atachibana — Sun, 17 Jul 2016 00:31:01 +0000

MS-Web-Matrix-2_Launch-My-Sites

atachibana — Sun, 17 Jul 2016 00:31:01 +0000

MS-Web-Matrix-1_Launch-Web-Matrix

atachibana — Sun, 17 Jul 2016 00:31:02 +0000

Permalink_settings

atachibana — Sun, 17 Jul 2016 00:31:02 +0000

Settings

atachibana — Sun, 17 Jul 2016 00:31:03 +0000

WordPress_Dashboard_menu

atachibana — Sun, 17 Jul 2016 00:31:03 +0000

WordPress_login

atachibana — Sun, 17 Jul 2016 00:31:04 +0000

WordPress_Site_Configuration_completed

atachibana — Sun, 17 Jul 2016 00:31:04 +0000

WordPress_Site_Configuration_continued

atachibana — Sun, 17 Jul 2016 00:31:05 +0000

WordPress_site_configuration

atachibana — Sun, 17 Jul 2016 00:31:05 +0000

WebPI_Installing_WordPress_WebMatrixSite

atachibana — Sun, 17 Jul 2016 00:31:05 +0000

WebPI5_Installing_WordPress_Step7

atachibana — Sun, 17 Jul 2016 00:31:06 +0000

WebPI5_Step5B_Example-Security-Keys

atachibana — Sun, 17 Jul 2016 00:31:06 +0000

WebPI5_Installing_WordPress_Step6

atachibana — Sun, 17 Jul 2016 00:31:07 +0000

WebPI_Installing_WordPress_Step5

atachibana — Sun, 17 Jul 2016 00:31:07 +0000

WebPI_Installing_WordPress_Step4

atachibana — Sun, 17 Jul 2016 00:31:08 +0000

WebPI_Installing_WordPress_Step3

atachibana — Sun, 17 Jul 2016 00:31:08 +0000

WebPI_Installing_WordPress_Step2

atachibana — Sun, 17 Jul 2016 00:31:09 +0000

WebPI_Installing_WordPress_Step1

atachibana — Sun, 17 Jul 2016 00:31:09 +0000

Microsoft_Web_Platform_install_5-0_WebPage

atachibana — Sun, 17 Jul 2016 01:51:06 +0000

File_Download_Security_Warning_1

atachibana — Sun, 17 Jul 2016 01:53:46 +0000

Internet_Explorer_Security_Warning_2

atachibana — Sun, 17 Jul 2016 01:55:39 +0000

MS-Web-Matrix-4_Launch-Site-URL

atachibana — Sun, 17 Jul 2016 02:34:50 +0000

no-www

atachibana — Sun, 17 Jul 2016 03:04:50 +0000

sites-edit-site

atachibana — Sun, 17 Jul 2016 03:04:51 +0000

750px-Twenty_Fifteen_Social_Icons_Manage_Menu

atachibana — Sun, 17 Jul 2016 04:10:44 +0000

Twenty_Fifteen_Menu_Descriptions

atachibana — Sun, 17 Jul 2016 04:10:45 +0000

750px-Twenty_Fifteen_Screen_Options

atachibana — Sun, 17 Jul 2016 04:10:46 +0000

Twenty_Fifteen_Menu

atachibana — Sun, 17 Jul 2016 04:10:46 +0000

Twenty_Fifteen_Customize_Color_Schemes

atachibana — Sun, 17 Jul 2016 04:10:47 +0000

750px-Twenty_Fifteen_Colors

atachibana — Sun, 17 Jul 2016 04:10:48 +0000

750px-Responsive_Twenty_Fifteen

atachibana — Sun, 17 Jul 2016 04:10:48 +0000

podz_filezilla_11

atachibana — Sun, 17 Jul 2016 04:41:49 +0000

podz_filezilla_10

atachibana — Sun, 17 Jul 2016 04:41:50 +0000

podz_filezilla_9

atachibana — Sun, 17 Jul 2016 04:41:51 +0000

podz_filezilla_8

atachibana — Sun, 17 Jul 2016 04:41:51 +0000

podz_filezilla_7

atachibana — Sun, 17 Jul 2016 04:41:51 +0000

podz_filezilla_6

atachibana — Sun, 17 Jul 2016 04:41:52 +0000

300px-podz_filezilla_5

atachibana — Sun, 17 Jul 2016 04:41:52 +0000

300px-podz_filezilla_4

atachibana — Sun, 17 Jul 2016 04:41:53 +0000

phpmyadmin-sql-tab

atachibana — Sun, 17 Jul 2016 15:19:21 +0000

phpmyadmin-import-successful

atachibana — Sun, 17 Jul 2016 15:19:22 +0000

phpmyadmin-export-screen

atachibana — Sun, 17 Jul 2016 15:19:22 +0000

phpmyadmin-export-tab

atachibana — Sun, 17 Jul 2016 15:19:23 +0000

phpmyadmin-choose-database

atachibana — Sun, 17 Jul 2016 15:19:23 +0000

add-image-insert-cursor

juhisaxena — Mon, 18 Jul 2016 05:59:08 +0000

add-media-button

juhisaxena — Mon, 18 Jul 2016 06:01:30 +0000

media-uploader

juhisaxena — Mon, 18 Jul 2016 06:02:57 +0000

edit-image

juhisaxena — Mon, 18 Jul 2016 06:05:30 +0000

attachement-details

juhisaxena — Mon, 18 Jul 2016 06:07:08 +0000

attachment-display-settings

juhisaxena — Mon, 18 Jul 2016 06:08:58 +0000

750px-image-alignment-4up

juhisaxena — Mon, 18 Jul 2016 06:10:34 +0000

750px-image-sizes-3up

juhisaxena — Mon, 18 Jul 2016 06:11:48 +0000

400px-re-edit-image

juhisaxena — Mon, 18 Jul 2016 06:21:27 +0000

reverbnation_embed

atachibana — Mon, 18 Jul 2016 09:07:06 +0000

wp_embed_preview

atachibana — Mon, 18 Jul 2016 09:07:07 +0000

responsive-devices-desktop-1x

atachibana — Mon, 18 Jul 2016 09:07:07 +0000

twenty-sixteen-white-desktop-1x

atachibana — Mon, 18 Jul 2016 09:07:08 +0000

500px-dashboard

ankitguptaindia — Tue, 26 Jul 2016 08:48:55 +0000

700px-screenoptions

ankitguptaindia — Tue, 26 Jul 2016 08:50:13 +0000

manage-blogroll-defaults

atachibana — Tue, 02 Aug 2016 08:27:20 +0000

new-default-blogroll

atachibana — Tue, 02 Aug 2016 08:27:20 +0000

visual-advanced-toolbar

atachibana — Tue, 02 Aug 2016 08:27:21 +0000

visual-advanced-buttons

atachibana — Tue, 02 Aug 2016 08:27:22 +0000

new-pending-review-post-status

atachibana — Tue, 02 Aug 2016 08:27:24 +0000

manage-post-filters

atachibana — Tue, 02 Aug 2016 08:27:24 +0000

plugin-update-notification

atachibana — Tue, 02 Aug 2016 08:27:25 +0000

wordpress-update-notification

atachibana — Tue, 02 Aug 2016 08:27:25 +0000

new-post-with-tag-field

atachibana — Tue, 02 Aug 2016 08:27:26 +0000

800px-whatIsABlog

juhisaxena — Tue, 02 Aug 2016 10:46:59 +0000

header-img

juhisaxena — Fri, 19 Aug 2016 07:15:56 +0000

post-avatar

juhisaxena — Fri, 19 Aug 2016 07:17:21 +0000

125px-stepOneRead

ankitguptaindia — Thu, 25 Aug 2016 13:35:53 +0000

Dragmedia

maced0507 — Thu, 20 Oct 2016 20:59:57 +0000

character-entities-slash

normalize — Tue, 01 Nov 2016 13:42:00 +0000

character-entities

normalize — Tue, 01 Nov 2016 13:44:02 +0000

custom_search_page_2

atachibana — Sun, 13 Nov 2016 14:16:43 +0000

custom_search_page_1

atachibana — Sun, 13 Nov 2016 14:16:44 +0000

quotes-auto-correction-01

normalize — Tue, 15 Nov 2016 14:40:00 +0000

quotes-auto-correction-02

normalize — Tue, 15 Nov 2016 14:40:18 +0000

Pages-AddNew-4.3

normalize — Mon, 28 Nov 2016 16:13:48 +0000

css-hunt-inspecttool

artemitos — Sun, 04 Dec 2016 15:59:23 +0000

WordPress Login

artemitos — Sun, 04 Dec 2016 16:37:28 +0000

Preview your site

artemitos — Sun, 04 Dec 2016 16:46:53 +0000

Admin dashboard

artemitos — Sun, 04 Dec 2016 16:47:55 +0000

profile

artemitos — Sun, 04 Dec 2016 16:49:12 +0000

themes

artemitos — Sun, 04 Dec 2016 16:50:30 +0000

writepost

artemitos — Sun, 04 Dec 2016 16:50:49 +0000

Create and manage categories

artemitos — Sun, 04 Dec 2016 16:52:34 +0000

Admin Posts

artemitos — Sun, 04 Dec 2016 16:53:03 +0000

Plugins page

artemitos — Sun, 04 Dec 2016 16:53:38 +0000

Plugins ‹ Valet — WordPress 2016-12-04 11-53-33

masonjames — Sun, 04 Dec 2016 16:53:51 +0000

Add Plugins — WordPress

masonjames — Sun, 04 Dec 2016 17:09:54 +0000

Upload a plugin via FTP

masonjames — Sun, 04 Dec 2016 17:15:38 +0000

Add Favorite Plugins - WordPress

masonjames — Sun, 04 Dec 2016 17:24:31 +0000

Favorite Plugins — WordPress Plugin Repo

masonjames — Sun, 04 Dec 2016 17:27:12 +0000

protected_edit_4.7

atachibana — Tue, 13 Dec 2016 07:32:39 +0000

protected_password_4.7

atachibana — Tue, 13 Dec 2016 07:32:41 +0000

protected_content_4.7

atachibana — Tue, 13 Dec 2016 07:32:43 +0000

sites-edit-site_4.7

atachibana — Thu, 15 Dec 2016 12:22:11 +0000

Screen Shot 2016-12-16 at 11.23.29 AM

juhisaxena — Fri, 16 Dec 2016 05:53:56 +0000

phpMyAdmin_create_database_4.4

atachibana — Sun, 08 Jan 2017 08:24:49 +0000

phpMyAdmin_server_info_4.4

atachibana — Sun, 08 Jan 2017 08:29:01 +0000

install-step3_v47

atachibana — Sun, 08 Jan 2017 08:32:43 +0000

install-step5_v47

atachibana — Sun, 08 Jan 2017 08:32:45 +0000

static_front_page_setting

atachibana — Sat, 18 Feb 2017 12:51:04 +0000

Formatting Date and Time

Milana — Tue, 21 Feb 2017 21:20:42 +0000

changepw7

atachibana — Sun, 26 Feb 2017 14:50:19 +0000

changepw6

atachibana — Sun, 26 Feb 2017 14:50:22 +0000

changepw3

atachibana — Sun, 26 Feb 2017 14:50:24 +0000

changepw2

atachibana — Sun, 26 Feb 2017 14:50:27 +0000

Template Hierarchy

Milana — Thu, 16 Mar 2017 22:07:20 +0000

wordpress-loginpage

dolgelukkig — Fri, 17 Mar 2017 11:00:55 +0000

Dashboard ‹ Your Website — WordPress

dolgelukkig — Fri, 17 Mar 2017 11:46:52 +0000

Your Website preview

dolgelukkig — Fri, 17 Mar 2017 12:26:42 +0000

Profile ‹ Your Website — WordPress

dolgelukkig — Fri, 17 Mar 2017 13:01:47 +0000

Manage Themes ‹ Your Website — WordPress

dolgelukkig — Fri, 17 Mar 2017 14:18:15 +0000

Add a New Post ‹ Your Website — WordPress

dolgelukkig — Fri, 17 Mar 2017 14:35:29 +0000

General Settings ‹ Your Website — WordPress

dolgelukkig — Fri, 17 Mar 2017 15:25:18 +0000

General Settings ‹ Your Website — WordPress

dolgelukkig — Fri, 17 Mar 2017 15:27:16 +0000

Permalink Settings ‹ Your Website — WordPress

dolgelukkig — Fri, 17 Mar 2017 15:33:09 +0000

network-admin-link

atachibana — Sat, 18 Mar 2017 07:28:00 +0000

tools-network-created

atachibana — Sat, 18 Mar 2017 07:28:03 +0000

network-create

atachibana — Sat, 18 Mar 2017 07:28:05 +0000

Themes Administration Screen - Installed Themes

Milana — Thu, 23 Mar 2017 19:22:05 +0000

Themes Directory - Feature Filter

Milana — Thu, 23 Mar 2017 19:48:52 +0000

Theme Info Page

Milana — Thu, 23 Mar 2017 19:58:46 +0000

Install New Theme - Administration Panels

Milana — Thu, 23 Mar 2017 20:27:21 +0000

cPanel - File Manager

Milana — Sat, 25 Mar 2017 14:41:17 +0000

cPanel - Themes Directory

Milana — Sat, 25 Mar 2017 14:41:23 +0000

cPanel - Upload File

Milana — Sat, 25 Mar 2017 14:41:25 +0000

cPanel - Extract Archive

Milana — Sat, 25 Mar 2017 14:41:26 +0000

Broken Theme

Milana — Sat, 25 Mar 2017 21:36:59 +0000

Activated Theme Notice

Milana — Sun, 26 Mar 2017 18:17:29 +0000

login_form

atachibana — Sun, 28 May 2017 08:00:09 +0000

WordPress Excerpt editor

corwinstar — Thu, 15 Jun 2017 13:52:10 +0000

skitch6

davidmlentz — Fri, 08 Sep 2017 21:37:51 +0000

skitch

davidmlentz — Fri, 08 Sep 2017 21:38:59 +0000

skitch5

davidmlentz — Fri, 08 Sep 2017 21:39:54 +0000

skitch4

davidmlentz — Fri, 08 Sep 2017 21:40:04 +0000

twenty-seventeen-1058

chetan200891 — Mon, 12 Feb 2018 10:56:34 +0000

video-headers

chetan200891 — Mon, 12 Feb 2018 10:59:23 +0000

front-page

chetan200891 — Mon, 12 Feb 2018 11:06:18 +0000

theme-options

chetan200891 — Mon, 12 Feb 2018 11:06:39 +0000

blog

chetan200891 — Mon, 12 Feb 2018 11:06:59 +0000

colours-screenshot

chetan200891 — Mon, 12 Feb 2018 11:08:23 +0000

one-column

chetan200891 — Mon, 12 Feb 2018 11:13:17 +0000

two-column

chetan200891 — Mon, 12 Feb 2018 11:13:19 +0000

two-column-option

chetan200891 — Mon, 12 Feb 2018 11:13:24 +0000

pullquotes

chetan200891 — Mon, 12 Feb 2018 11:16:51 +0000

customizer4_9-menu

atachibana — Sat, 24 Feb 2018 06:33:45 +0000

800px-customizer4_9-theme

atachibana — Sat, 24 Feb 2018 06:33:47 +0000

text-widget-with-media

atachibana — Sat, 24 Feb 2018 06:33:48 +0000

gallery-widget

atachibana — Sat, 24 Feb 2018 06:33:50 +0000

customizer4_9-autosave

atachibana — Sat, 24 Feb 2018 06:33:51 +0000

customizer4_9-schedule

atachibana — Sat, 24 Feb 2018 06:33:52 +0000

400px-events-widget

atachibana — Sat, 24 Feb 2018 07:00:27 +0000

800px-link_boundaries

atachibana — Sat, 24 Feb 2018 07:00:29 +0000

800px-widgets-with-all-four

atachibana — Sat, 24 Feb 2018 07:00:30 +0000

twenty-sixteen-customized

atachibana — Sat, 24 Feb 2018 07:52:28 +0000

twenty-sixteen-colorscheme

atachibana — Sat, 24 Feb 2018 07:52:29 +0000

twentysixteen-pull-quotes

atachibana — Sat, 24 Feb 2018 07:52:30 +0000

twentysixteen-overhanging-image

atachibana — Sat, 24 Feb 2018 07:52:32 +0000

twentysixteen-content-bottom-widgets1

atachibana — Sat, 24 Feb 2018 07:52:33 +0000

twentysixteen-no-sidebar

atachibana — Sat, 24 Feb 2018 07:52:35 +0000

twentysixteen-device

atachibana — Sat, 24 Feb 2018 07:52:36 +0000

twetysixteen-featured-image

atachibana — Sat, 24 Feb 2018 07:52:37 +0000

options-writing

chetan200891 — Tue, 06 Mar 2018 10:14:52 +0000

320px-options-discussion1

juhisaxena — Wed, 07 Mar 2018 06:42:21 +0000

image

juhisaxena — Wed, 07 Mar 2018 06:42:21 +0000

settings-writing-4_9_4

atachibana — Sat, 10 Mar 2018 15:25:29 +0000

installing_multiple_wordpresses

atachibana — Sun, 11 Mar 2018 12:51:08 +0000

media-setting

kafleg — Sun, 18 Mar 2018 07:35:06 +0000

administrations_screen_4.9.4_with_note

atachibana — Sat, 31 Mar 2018 05:44:43 +0000

administrations_screen_4.9.4-about

atachibana — Sat, 31 Mar 2018 07:04:13 +0000

bbPress Public Forum

Clorith — Sun, 03 Nov 2013 05:43:53 +0000

bbPress Public Forum Description

bbPress Private Forum

Clorith — Sun, 03 Nov 2013 05:45:14 +0000

bbPress Private Forum Description

bbPress Forums Category

Clorith — Sun, 03 Nov 2013 05:49:35 +0000

bbPress Forums Category Description

bbPress Closed Forum

Clorith — Sun, 03 Nov 2013 05:52:47 +0000

bbPress Closed Forum Description

Suits

Clorith — Fri, 17 Jan 2014 07:19:34 +0000

Suits (Category)

bbPress Hidden Forum

Clorith — Sun, 03 Nov 2013 05:45:40 +0000

bbPress Hidden Forum Description

Clothing

Clorith — Fri, 17 Jan 2014 07:17:05 +0000

Clothing (Category)

Women's

Clorith — Fri, 17 Jan 2014 07:17:57 +0000

Women's (Category)

Men's

Clorith — Fri, 17 Jan 2014 07:18:32 +0000

Men's (Category)

Ties

Clorith — Fri, 17 Jan 2014 07:20:01 +0000

Ties (Forum)

permalink_settings_4.9.5

atachibana — Sat, 07 Apr 2018 13:02:14 +0000

w-mark

mapk — Tue, 17 Apr 2018 15:21:38 +0000

PrivacySettingsTool_4.9.6

lunaluna_dev — Thu, 14 Jun 2018 13:33:28 +0000

PrivacySettingsTool_Editor_4.9.6

lunaluna_dev — Thu, 14 Jun 2018 13:38:40 +0000

PrivacySettingsTool_4.9.6_login

lunaluna_dev — Thu, 14 Jun 2018 13:39:49 +0000

File_PrivacySettingsTool_TwentySeventeen_4.9.6

lunaluna_dev — Thu, 14 Jun 2018 13:41:27 +0000

PrivacySettingsTool_TwentySeventeen_4.9.6

lunaluna_dev — Thu, 14 Jun 2018 13:46:21 +0000

twenty-seventeen-top

audrasjb — Tue, 31 Jul 2018 11:53:58 +0000

600px-v47_editor-toolbars

audrasjb — Tue, 31 Jul 2018 11:59:54 +0000

600px-v47_editor-shortcuts-1

audrasjb — Tue, 31 Jul 2018 12:00:23 +0000

Hello world!

Clorith — Sun, 03 Nov 2013 02:56:30 +0000

Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!

Jackets

Clorith — Fri, 17 Jan 2014 07:20:49 +0000

Jackets (Forum)

Skirts

Clorith — Fri, 17 Jan 2014 07:21:52 +0000

Skirts (Forum)

Restoring Your Database From Backup

Mon, 11 Jul 2016 22:11:29 +0000

Using phpMyAdmin

phpMyAdmin is a program used to manipulate databases remotely through a web interface. A good hosting package will have this included. For information on backing up your WordPress database, see Backing Up Your Database. Information here has been tested using phpMyAdmin 4.0.5 running on Unix. The following instructions will replace your current database with the backup, reverting your database to the state it was in when you backed up.

Restore Process

Using phpMyAdmin, follow the steps below to restore a MySQL/MariaDB database.

Login to phpMyAdmin.
Click "Databases" and select the database that you will be importing your data into.
You will then see either a list of tables already inside that database or a screen that says no tables exist. This depends on your setup.
Across the top of the screen will be a row of tabs. Click the Import tab.
On the next screen will be a location of text file box, and next to that a button named Browse.
Click Browse. Locate the backup file stored on your computer.
Make sure SQL is selected in the Format drop-down menu.
Click the Go button.

Now grab a coffee. This bit takes a while. Eventually you will see a success screen. If you get an error message, your best bet is to post to the WordPress support forums to get help.

Using MySQL/MariaDB Commands

The restore process consists of unarchiving your archived database dump, and importing it into your MySQL/MariaDB database. Assuming your backup is a .bz2 file, created using instructions similar to those given for Backing up your database using MySQL/MariaDB commands, the following steps will guide you through restoring your database: 1. Unzip your .bz2 file:

[code language="php"]user@linux:~/files/blog&gt; bzip2 -d blog.bak.sql.bz2[/code]

Note: If your database backup was a .tar.gz file called blog.bak.sql.tar.gz, then

[code language="php"]tar -zxvf blog.bak.sql.tar.gz[/code]

is the command that should be used instead of the above. 2. Put the backed-up SQL back into MySQL/MariaDB:

[code language="php"]
user@linux:~/files/blog&gt; mysql -h mysqlhostserver -u mysqlusername -p databasename &lt; blog.bak.sql

Enter password: (enter your mysql password)
user@linux~/files/blog:&gt;
[/code]

Changing File Permissions

ankitguptaindia — Thu, 25 Aug 2016 13:43:23 +0000

On computer filesystems, different files and directories have permissions that specify who and what can read, write, modify and access them. This is important because WordPress may need access to write to files in your wp-content directory to enable certain functions.

Permission Modes

  7       5     5
 user   group  world
 r+w+x  r+x    r+x
 4+2+1  4+0+1  4+0+1  = 755

The permission mode is computed by adding up the following values for the user, the file group, and for everyone else. The diagram shows how.

Read 4 - Allowed to read files
Write 2 - Allowed to write/modify files
eXecute1 - Read/write/delete/modify/directory

  7       4      4
 user   group  world
 r+w+x    r      r
 4+2+1  4+0+0  4+0+0  = 744

Example Permission Modes

|- style="width:99%; margin:0 auto;" border="0" cellpadding="3" cellspacing="1" align="center" bgcolor="#eee" color="000" border="1"

! Mode !! Str Perms !! Explanation

| 0477 ||-r--rwxrwx|| owner has read only (4), other and group has rwx (7)

| 0677 || -rw-rwxrwx||owner has rw only(6), other and group has rwx (7)

| 0444 || -r--r--r--||all have read only (4)

| 0666 || -rw-rw-rw-||all have rw only (6)

| 0400 || -r--------||owner has read only(4), group and others have no permission(0)

| 0600 || -rw-------||owner has rw only, group and others have no permission

| 0470 || -r--rwx---||owner has read only, group has rwx, others have no permission

| 0407 || -r-----rwx||owner has read only, other has rwx, group has no permission

| 0670 || -rw-rwx---||owner has rw only, group has rwx, others have no permission

| 0607 || -rw----rwx||owner has rw only, group has no permission and others have rwx

|+See full list 0000 to 0777.

SSL in WordPress

janr — Thu, 15 Jun 2017 13:20:41 +0000

Having an SSL certificate is the de-facto standard nowadays. An SSL certificate, or TLS which superseded SSL, encrypts communication transferred between client and server. Despite SSL being superseded by TLS, we often still speak of SSL, and will do so in this article.

Encryption and trust provided by SSL

An SSL certificate does more than encrypting the communication between client and server. Because the client and server swap out cryptographic certificates, you are guaranteed to only communicate with that particular server and site. Therefore, an SSL certificate also provides trust. Having an SSL certificate does not make your website automatically more secure. It has nothing to do with website security, see Hardening WordPress for more information on this subject.

Moving to SSL in WordPress

When an SSL certificate is installed for your website, you'll need to change the WordPress address to the HTTPS URL, e.g from http://www.example.com to https://www.example.com. To do this you go to your WordPress dashboard and then click: Settings > General, and then amend the 'WordPress Address (URL), and 'Site Address (URL)' fields.

Standard Post

Clorith — Sun, 08 Dec 2013 22:28:32 +0000

Standard Post

Slacks

Clorith — Fri, 17 Jan 2014 07:20:31 +0000

Slacks (Forum)

Blouses

Clorith — Fri, 17 Jan 2014 07:22:11 +0000

Blouses (Forum)

Dresses

Clorith — Fri, 17 Jan 2014 07:22:33 +0000

Dresses (Category)

Evening Gowns

Clorith — Fri, 17 Jan 2014 07:22:54 +0000

Evening Gowns (Forum)

Sun Dresses

Clorith — Fri, 17 Jan 2014 07:23:17 +0000

Sun Dresses (Forum)

Aside Post

Clorith — Sun, 08 Dec 2013 22:29:01 +0000

Aside Post

Audio Post

Clorith — Sun, 08 Dec 2013 22:29:24 +0000

Audio Post

Chat Post

Clorith — Sun, 08 Dec 2013 22:29:50 +0000

Chat Post

Gallery Post

Clorith — Sun, 08 Dec 2013 22:30:17 +0000

Gallery Post

Image Post

Clorith — Sun, 08 Dec 2013 22:30:46 +0000

Image Post

Link Post

Clorith — Sun, 08 Dec 2013 22:31:09 +0000

Link Post

Quote Post

Clorith — Sun, 08 Dec 2013 22:31:36 +0000

Quote Post

Settings Privacy Screen

lunaluna_dev — Mon, 30 Nov -0001 00:00:00 +0000

WordPress 4.9.6 included a Privacy Settings tool. Administrator can create new page or specify existing one as Privacy Policy page of the site.

Note: The new page will include help and suggestions for your privacy policy. However, it is your responsibility to use those resources correctly, to provide the information that your privacy policy requires, and to keep that information current and accurate.

Using Privacy Settings tool

1. Select Settings -> Privacy from Administration Screens.

2. Click Create New Page to generate a Privacy Policy Page. Or, Select an existing page which you want to use from dropdown box and click Use This Page.

3. If you click Create New Page, then template page titled Privacy Policy will be opened. Modify the contents and click Publish.

Hint: If you need help, click the link of 'Check out our guide' for recommendations on what content to include.

Where is the Privacy Policy page displayed?

The Privacy Policy page will be shown on your login and registration pages. Notice the bottom Link 'Privacy Policy'.

It is your responsibility to create a link to the Privacy Policy page to every page on your site. But theme will support such function soon. For example, Twenty Seventeen adds the link to the Privacy Policy page at the bottom.

To Theme Developers

For users convenience, you should refer these new functions.

get_privacy_policy_url() - Retrieves the URL to the privacy policy page.
the_privacy_policy_link() - Displays the privacy policy link with formatting, when applicable.
get_the_privacy_policy_link() - Returns the privacy policy link with formatting, when applicable.

This is the example from Twenty Seventeen (twentyseventeen/template-parts/footer/site-info.php)

if ( function_exists( 'the_privacy_policy_link' ) ) {
    the_privacy_policy_link( '', '' );
}

Reference

Changelog

4.9.6 : Privacy Settings tool
3.5 : Screen deprecated, Search Engine Visibility option moved to Settings Reading Screen
3.0 : Site visibility
2.1 : New Screen

How to install WordPress

paaljoachim — Tue, 16 Feb 2016 15:29:58 +0000

WordPress is well-known for its ease of installation. Under most circumstances, installing WordPress is a very simple process and takes less than five minutes to complete. Many web hosts now offer tools (e.g. Fantastico) to automatically install WordPress for you. However, if you wish to install WordPress yourself, the following guide will help.

Things to Know Before Installing WordPress

Before you begin the install, there are a few things you need to have and do. Refer the article Before You Install.
If you need multiple WordPress instances, refer Installing Multiple WordPress.

Basic Instructions

Here's the quick version of the instructions for those who are already comfortable with performing such installations. More detailed instructions follow.

Download and unzip the WordPress package if you haven't already.
Create a database for WordPress on your web server, as well as a MySQL (or MariaDB) user who has all privileges for accessing and modifying it.
(Optional) Find and rename wp-config-sample.php to wp-config.php, then edit the file (see Editing wp-config.php) and add your database information.
Note: If you are not comfortable with renaming files, step 3 is optional and you can skip it as the install program will create the wp-config.php file for you.
Upload the WordPress files to the desired location on your web server:
- If you want to integrate WordPress into the root of your domain (e.g. http://example.com/), move or upload all contents of the unzipped WordPress directory (excluding the WordPress directory itself) into the root directory of your web server.
- If you want to have your WordPress installation in its own subdirectory on your website (e.g. http://example.com/blog/), create the blog directory on your server and upload the contents of the unzipped WordPress package to the directory via FTP.
- Note: If your FTP client has an option to convert file names to lower case, make sure it's disabled.
Run the WordPress installation script by accessing the URL in a web browser. This should be the URL where you uploaded the WordPress files.
- If you installed WordPress in the root directory, you should visit: http://example.com/
- If you installed WordPress in its own subdirectory called blog, for example, you should visit: http://example.com/blog/

That's it! WordPress should now be installed.

Detailed Instructions

Step 1: Download and Extract

Download and unzip the WordPress package from https://wordpress.org/download/.

If you will be uploading WordPress to a remote web server, download the WordPress package to your computer with a web browser and unzip the package.
If you will be using FTP, skip to the next step - uploading files is covered later.
If you have shell access to your web server, and are comfortable using console-based tools, you may wish to download WordPress directly to your web server using wget (or lynx or another console-based web browser) if you want to avoid FTPing:
- wget https://wordpress.org/latest.tar.gz
- Then unzip the package using:
  tar -xzvf latest.tar.gz
  
  The WordPress package will extract into a folder called wordpress in the same directory that you downloadedlatest.tar.gz.

Step 2: Create the Database and a User

If you are using a hosting provider, you may already have a WordPress database set up for you, or there may be an automated setup solution to do so. Check your hosting provider's support pages or your control panel for clues about whether or not you'll need to create one manually.

If you determine that you’ll need to create one manually, follow the instructions for Using phpMyAdmin below to create your WordPress username and database. For other tools such as Plesk, cPanel and Using the MySQL Client, refer the article Creating Database for WordPress.

If you have only one database and it is already in use, you can install WordPress in it - just make sure to have a distinctive prefix for your tables to avoid over-writing any existing database tables.

Using phpMyAdmin

If your web server has phpMyAdmin installed, you may follow these instructions to create your WordPress username and database. If you work on your own computer, on most Linux distributions you can install PhpMyAdmin automatically.

Note: These instructions are written for phpMyAdmin 4.4; the phpMyAdmin user interface can vary slightly between versions.

If a database relating to WordPress does not already exist in the Database dropdown on the left, create one:
1. Choose a name for your WordPress database: 'wordpress' or 'blog' are good, but most hosting services (especially shared hosting) will require a name beginning with your username and an underscore, so, even if you work on your own computer, we advise that you check your hosting service requirements so that you can follow them on your own server and be able to transfer your database without modification. Enter the chosen database name in the Create database field and choose the best collation for your language and encoding. In most cases it's better to choose in the "utf8_" series and, if you don't find your language, to choose "utf8mb4_general_ci" (Reference: [1]).
Click the phpMyAdmin icon in the upper left to return to the main page, then click the Users tab. If a user relating to WordPress does not already exist in the list of users, create one:
1. Click Add user.
2. Choose a username for WordPress ('wordpress' is good) and enter it in the User name field. (Be sure Use text field: is selected from the dropdown.)
3. Choose a secure password (ideally containing a combination of upper- and lower-case letters, numbers, and symbols), and enter it in the Password field. (Be sure Use text field: is selected from the dropdown.) Re-enter the password in the Re-typefield.
4. Write down the username and password you chose.
5. Leave all options under Global privileges at their defaults.
6. Click Go.
7. # Return to the Users screen and click the Edit privileges icon on the user you've just created for WordPress.
8. # In the Database-specific privileges section, select the database you've just created for WordPress under the Add privileges to the following database dropdown, and click Go.
9. # The page will refresh with privileges for that database. Click Check All to select all privileges, and click Go.
10. # On the resulting page, make note of the host name listed after Server: at the top of the page. (This will usually be localhost.)

Step 3: Set up wp-config.php

You can either create and edit the wp-config.php file yourself, or you can skip this step and let WordPress try to do this itself when you run the installation script (step 5). (you’ll still need to tell WordPress your database information).

(For more extensive details, and step by step instructions for creating the configuration file and your secret key for password security, please see Editing wp-config.php.)

Return to where you extracted the WordPress package in Step 1, rename the file wp-config-sample.php to wp-config.php, and open it in a text editor.

Enter your database information under the section labeled

 // ** MySQL settings - You can get this info from your web host ** //

DB_NAME: The name of the database you created for WordPress in Step 2.
DB_USER: The username you created for WordPress in Step 2.
DB_PASSWORD: The password you chose for the WordPress username in Step 2.
DB_HOST: The hostname you determined in Step 2 (usually localhost, but not always; see some possible DB_HOST values). If a port, socket, or pipe is necessary, append a colon (:) and then the relevant information to the hostname.
DB_CHARSET: The database character set, normally should not be changed (see Editing wp-config.php).
DB_COLLATE: The database collation should normally be left blank (see Editing wp-config.php).

Enter your secret key values under the section labeled

  * Authentication Unique Keys and Salts.

Save the wp-config.php file.

Step 4: Upload the files

Now you will need to decide where on your domain you'd like your WordPress-powered site to appear:

In the root directory of your website. (For example, http://example.com/)
In a subdirectory of your website. (For example, http://example.com/blog/)

Note: The location of your root web directory in the filesystem on your web server will vary across hosting providers and operating systems. Check with your hosting provider or system administrator if you do not know where this is.

In the Root Directory

If you need to upload your files to your web server, use an FTP client to upload all the contents of the wordpress directory (but not the directory itself) into the root directory of your website.
If your files are already on your web server, and you are using shell access to install WordPress, move all of the contents of the wordpress directory (but not the directory itself) into the root directory of your website.

In a Subdirectory

If you need to upload your files to your web server, rename the wordpress directory to your desired name, then use an FTP client to upload the directory to your desired location within the root directory of your website.
If your files are already on your web server, and you are using shell access to install WordPress, move the wordpress directory to your desired location within the root directory of your website, and rename the directory to your desired name.

Step 5: Run the Install Script

Point a web browser to start the installation script.

If you placed the WordPress files in the root directory, you should visit: http://example.com/wp-admin/install.php
If you placed the WordPress files in a subdirectory called blog, for example, you should visit: http://example.com/blog/wp-admin/install.php

Setup configuration file

If WordPress can't find the wp-config.php file, it will tell you and offer to try to create and edit the file itself. (You can also do this directly by loading wp-admin/setup-config.php in your web browser.) WordPress will ask you the database details and write them to a new wp-config.php file. If this works, you can go ahead with the installation; otherwise, go back and create, edit, and upload the wp-config.php file yourself (step 3).

Finishing installation

The following screenshots show how the installation progresses. Notice that in entering the details screen, you enter your site title, your desired user name, your choice of a password (twice), and your e-mail address. Also displayed is a check-box asking if you would like your blog to appear in search engines like Google and Technorati. Leave the box checked if you would like your blog to be visible to everyone, including search engines, and uncheck the box if you want to block search engines, but allow normal visitors. Note all this information can be changed later in your Administration Screen.

If you successfully install the WordPress, login prompt will be displayed.

Install script troubleshooting

If you get an error about the database when you run the install script:
- Go back to Step 2 and Step 3, and make sure you entered all the correct database information into wp-config.php.
- Make sure you granted your WordPress user permission to access your WordPress database in Step 3.
- Make sure the database server is running.

Common Installation Problems

The following are some of the most common installation problems. For more information and troubleshooting for problems with your WordPress installation, check out FAQ Installation and FAQ Troubleshooting.

I see a directory listing rather than a web page.

The web server needs to be told to view index.php by default. In Apache, use the DirectoryIndex index.php directive. The simplest option is to create a file named .htaccess in the installed directory and place the directive there. Another option is to add the directive to the web server's configuration files.

I see lots of Headers already sent errors. How do I fix this?

You probably introduced a syntax error in editing wp-config.php.

Download wp-config.php (if you don't have shell access).
Open it in a text editor.
Check that the first line contains nothing but , and that there is no text before it (not even whitespace).

Check that the last line contains nothing but ?>, and that there is no text after it (not even whitespace). If your text editor saves as Unicode, make sure it adds no byte order mark (BOM). Most Unicode-enabled text editors do not inform the user whether or not it adds a BOM to files; if so, try using a different text editor. Save the file, upload it again if necessary, and reload the page in your browser.

My page comes out gibberish. When I look at the source I see a lot of "" tags. If the tags are being sent to the browser, it means your PHP is not working properly. All PHP code is supposed to be executed before the server sends the resulting HTML to your web browser. (That's why it's called a preprocessor.) Make sure your web server meets the requirements to run WordPress, that PHP is installed and configured properly, or contact your hosting provider or system administrator for assistance. I keep getting an Error connecting to database message but I'm sure my configuration is correct. Try resetting your MySQL password manually. If you have access to MySQL via shell, try issuing: SET PASSWORD FOR 'wordpressusername'@'hostname' = OLD_PASSWORD('password'); If you do not have shell access, you should be able to simply enter the above into an SQL query in phpMyAdmin. Failing that, you may need to use your host's control panel to reset the password for your database user. I keep getting an Your PHP installation appears to be missing the MySQL extension which is required by WordPress message but I'm sure my configuration is correct. Check to make sure that your configuration of your web-server is correct and that the MySQL plugin is getting loaded correctly by your web-server program. Sometimes this issue requires everything in the path all the way from the web-server down to the MySQL installation to be checked and verified to be fully operational. Incorrect configuration files or settings are often the cause of this issue. My image/MP3 uploads aren't working. If you use the Rich Text Editor on a blog that's installed in a subdirectory, and drag a newly uploaded image into the editor field, the image may vanish a couple seconds later. This is due to a problem with TinyMCE (the rich text editor) not getting enough information during the drag operation to construct the path to the image or other file correctly. The solution is to NOT drag uploaded images into the editor. Instead, click and hold on the image and select Send to Editor.

Hosting Company	DB_HOST Value Guess
1and1	`db12345678`
A2 Hosting	`localhost`
AN Hosting	`localhost`
Aruba.it	`localhost` or real IP provided with activation mail.
A Small Orange	`localhost`
AT&T	`xxxxxxxx.carrierzone.com` full server name found in PHP MyAdmin.
BlueHost	`localhost`
DreamHost	`mysql.example.com`
GoDaddy - Shared and 4GH Hosting	In the Databases menu go to MySQL. To the right of the database name click on Actions and Details. The hostname is at the bottom of the window.
GoDaddy - cPanel Hosting	`localhost`
GoDaddy - Plesk Hosting	Use the IP address shown in the Databases Section in Plesk. Do not include :3306
HostGator	`localhost`
ICDSoft	`localhost:/tmp/mysql5.sock`
Infomaniak Network	`mysql.yourdomain`
InMotion Hosting	`localhost`
iPage	`username.ipagemysql.com`
IPower	`username.ipowermysql.com`
Laughing Squid	`localhost`
MediaTemple Grid	`internal-db.s00000.gridserver.com` - (Replace "00000" with the actual site number)
MediaTemple DV	`localhost`
MegaHost	`localhost`
NearlyFreeSpeech.Net	`username.db`
NetworkSolutions	`mysqlv5`
one.com	`example.com.mysql`
pair Networks	`dbnnnx.pair.com`
QTH.com	`localhost`
Rackspace Cloud	`localhost` for unmanaged servers, variable for Cloud Sites like `mysqlXY-AB.wcN.dfQ.stabletransit.com` where X,Y,A,B,N,Q are variables
SysFix.eu Power Hosting	`datapower.sysfix.eu`
Site5	`localhost`
Yahoo	`mysql`
Hosts with cPanel	`localhost`
Hosts with Plesk	`localhost`
Hosts with DirectAdmin	`localhost`
Tophost.it	`sql.your-domain-name.it`

Name	OS (Paid edition)	OS (Free edition)	Notes
MySQL Workbench	Windows/Mac/Linux	Windows/Mac/Linux	See above
EMS SQL Management Studio for MySQL	Windows	-
Aqua Data Studio	Windows/Mac/Linux	Windows/Mac/Linux (14 days trial)	Available in 9 languages
Navicat for MySQL	Windows/Mac/Linux	Windows/Mac/Linux (14 days trial)	Available in 8 languages
SQLyog	Windows	-
Toad for MySQL	-	Windows
HeidiSQL	-	Windows
Sequel Pro		Mac	CocoaMySQL successor
Querious	-	Mac

icon	text	text	full text	icon	full text
:smile:	`:)`	`:-)`	`:smile:`	:lol:	`:lol:`
:grin:	`:D`	`:-D`	`:grin:`	:oops:	`:oops:`
:sad:	`:(`	`:-(`	`:sad:`	:cry:	`:cry:`
:eek:	`:o`	`:-o`	`:eek:`	:evil:	`:evil:`
:shock:	`8O`	`8-O`	`:shock:`	:twisted:	`:twisted:`
:???:	`:?`	`:-?`	`:???:`	:roll:	`:roll:`
:cool:	`8)`	`8-)`	`:cool:`	:!:	`:!:`
:mad:	`:x`	`:-x`	`:mad:`	:?:	`:?:`

:razz:	`:P`	`:-P`	`:razz:`	:idea:	`:idea:`
:neutral:	`:\|`	`:-\|`	`:neutral:`	:arrow:	`:arrow:`
:wink:	`;)`	`;-)`	`:wink:`	:mrgreen:	`:mrgreen:`

Capability	Super Admin	Administrator	Editor	Author	Contributor	Subscriber
create_sites	Y
delete_sites	Y
manage_network	Y
manage_sites	Y
manage_network_users	Y
manage_network_plugins	Y
manage_network_themes	Y
manage_network_options	Y
upload_plugins	Y
upload_themes	Y
upgrade_network	Y
setup_network	Y
Capability	Super Admin	Administrator	Editor	Author	Contributor	Subscriber
activate_plugins	Y	Y (single site or enabled by network setting)
create_users	Y	Y (single site)
delete_plugins	Y	Y (single site)
delete_themes	Y	Y (single site)
delete_users	Y	Y (single site)
edit_files	Y	Y (single site)
edit_plugins	Y	Y (single site)
edit_theme_options	Y	Y
edit_themes	Y	Y (single site)
edit_users	Y	Y (single site)
export	Y	Y
import	Y	Y
Capability	Super Admin	Administrator	Editor	Author	Contributor	Subscriber
install_plugins	Y	Y (single site)
install_themes	Y	Y (single site)
list_users	Y	Y
manage_options	Y	Y
promote_users	Y	Y
remove_users	Y	Y
switch_themes	Y	Y
update_core	Y	Y (single site)
update_plugins	Y	Y (single site)
update_themes	Y	Y (single site)
edit_dashboard	Y	Y
customize	Y	Y
delete_site	Y	Y
Capability	Super Admin	Administrator	Editor	Author	Contributor	Subscriber
moderate_comments	Y	Y	Y
manage_categories	Y	Y	Y
manage_links	Y	Y	Y
edit_others_posts	Y	Y	Y
edit_pages	Y	Y	Y
edit_others_pages	Y	Y	Y
edit_published_pages	Y	Y	Y
publish_pages	Y	Y	Y
delete_pages	Y	Y	Y
delete_others_pages	Y	Y	Y
delete_published_pages	Y	Y	Y
delete_others_posts	Y	Y	Y
delete_private_posts	Y	Y	Y
edit_private_posts	Y	Y	Y
read_private_posts	Y	Y	Y
delete_private_pages	Y	Y	Y
edit_private_pages	Y	Y	Y
read_private_pages	Y	Y	Y
unfiltered_html	Y	Y (single site)	Y (single site)
unfiltered_html	Y	Y	Y
Capability	Super Admin	Administrator	Editor	Author	Contributor	Subscriber
edit_published_posts	Y	Y	Y	Y
upload_files	Y	Y	Y	Y
publish_posts	Y	Y	Y	Y
delete_published_posts	Y	Y	Y	Y
edit_posts	Y	Y	Y	Y	Y
delete_posts	Y	Y	Y	Y	Y
Capability	Super Admin	Administrator	Editor	Author	Contributor	Subscriber
read	Y	Y	Y	Y	Y	Y

Day of Month
`d`	Numeric, with leading zeros	01–31
`j`	Numeric, without leading zeros	1–31
`S`	The English suffix for the day of the month	st, nd or th in the 1st, 2nd or 15th.
Weekday
`l`	Full name (lowercase 'L')	Sunday – Saturday
`D`	Three letter name	Mon – Sun
Month
`m`	Numeric, with leading zeros	01–12
`n`	Numeric, without leading zeros	1–12
`F`	Textual full	January – December
`M`	Textual three letters	Jan - Dec
Year
`Y`	Numeric, 4 digits	Eg., 1999, 2003
`y`	Numeric, 2 digits	Eg., 99, 03
Time
`a`	Lowercase	am, pm
`A`	Uppercase	AM, PM
`g`	Hour, 12-hour, without leading zeros	1–12
`h`	Hour, 12-hour, with leading zeros	01–12
`G`	Hour, 24-hour, without leading zeros	0-23
`H`	Hour, 24-hour, with leading zeros	00-23
`i`	Minutes, with leading zeros	00-59
`s`	Seconds, with leading zeros	00-59
`T`	Timezone abbreviation	Eg., EST, MDT ...
Full Date/Time
`c`	ISO 8601	2004-02-12T15:19:21+00:00
`r`	RFC 2822	Thu, 21 Dec 2000 16:01:07 +0200
`U`	Unix timestamp (seconds since Unix Epoch)	1455880176

Service	Embed Type	Since
Animoto	Videos	WordPress 4.0
Blip	Videos	WordPress 2.9
Cloudup	Videos, Galleries, Images	WordPress 4.4
CollegeHumor	Videos	WordPress 4.0
DailyMotion	Videos	WordPress 2.9
Facebook	post, activity, photo, video, media, question, note	WordPress 4.7
Flickr	Videos & Images	WordPress 2.9
FunnyOrDie.com	Videos	WordPress 3.0
Hulu	Videos	WordPress 2.9
Imgur	Images	WordPress 3.9
Instagram	Images	WordPress 3.5
Issuu	Documents	WordPress 4.0
Kickstarter	Projects	WordPress 4.2
Meetup.com	Various	WordPress 3.9
Mixcloud	Music	WordPress 4.0
Photobucket	Images	WordPress 2.9
PollDaddy	Polls & Surveys	WordPress 3.0
Reddit	Posts & Comments	WordPress 4.4
ReverbNation	Music	WordPress 4.4
Scribd	Documents	WordPress 2.9
SlideShare	Presentation slideshows	WordPress 3.5
SmugMug	Various	WordPress 3.0
SoundCloud	Music	WordPress 3.5
Speaker Deck	Presentation slideshows	WordPress 4.4
Spotify	Music	WordPress 3.6
TED	Videos	WordPress 4.0
Tumblr	Various	WordPress 4.2
Twitter	Tweet, profile, list, collection, likes, Moment	WordPress 3.4
VideoPress	Videos	WordPress 4.4
Vimeo	Videos	WordPress 2.9
Vine	Videos	WordPress 4.1
WordPress plugin directory	Plugins	WordPress 4.4
WordPress.tv	Videos	WordPress 2.9
YouTube	Videos	WordPress 2.9

Editing wp-config.php jon_bossenger — Mon, 22 Feb 2016 14:58:57 +0000 One of the most important files in your WordPress installation is the wp-config.phpfile. This file is located in the root of your WordPress file directory and contains your website's base configuration details, such as database connection information. When you first download WordPress, the wp-config.php file isn’t included. The WordPress setup process will create a wp-config.php file for you based on the information you provide. You can manually create a wp-config.php file by locating the sample file named "wp-config-sample.php" (located in the root install-directory), editing it as required, and then saving it as wp-config.php. Note: The contents of the wp-config-sample.php file are in a very specific order. The order matters. If you already have awp-config.php file, rearranging the contents of the file may create errors on your blog. To change the wp-config.php file for your installation, you will need this information: Database Name Database Name used by WordPress Database Username Username used to access Database Database Password Password used by Username to access Database Database Host The hostname of your Database Server. A port number, Unix socket file path or pipe may be needed as well. If your hosting provider installed WordPress for you, get the information from them. If you manage your own web server or hosting account, you will have this information as a result of creating the database and user. Configure Database Settings Important: Never use a word processor like Microsoft Word for editing WordPress files! Locate the file wp-config-sample.php in the base directory of your WordPress directory and open in a text editor. Note: Since Version 2.6, wp-config.php file can be moved to the directory directly above the WordPress install directory. Default wp-config-sample.php Note: This is an example of a default wp-config-sample.php. The values here are examples to show you what to do. Do not change these details here by editing this page, change them on your web server. If you make changes here by using the edit button, they will not work and you will be showing your password details to the world. // ** MySQL settings - You can get this info from your web host ** // /** The name of the database for WordPress */ define( 'DB_NAME', 'database_name_here' ); /** MySQL database username */ define( 'DB_USER', 'username_here' ); /** MySQL database password */ define( 'DB_PASSWORD', 'password_here' ); /** MySQL hostname */ define( 'DB_HOST', 'localhost' ); Note: Text inside /* */ are comments, for information purposes only. Set Database Name Replace 'database_name_here', with the name of your database, e.g. MyDatabaseName. define( 'DB_NAME', 'MyDatabaseName' ); // Example MySQL database name Set Database User Replace 'username_here', with the name of your username e.g. MyUserName. define( 'DB_USER', 'MyUserName' ); // Example MySQL username Set Database Password Replace 'password_here', with the your password, e.g. MyPassWord. define( 'DB_PASSWORD', 'MyPassWord' ); // Example MySQL password Set Database Host Replace 'localhost', with the name of your database host, e.g. MyDatabaseHost. A port number or Unix socket file path may be needed as well. define( 'DB_HOST', 'MyDatabaseHost' ); // Example MySQL Database host Note: There is a good chance you will NOT have to change it. If you are unsure, try installing with the default value of'localhost' and see if it works. If the install fails, contact your web hosting provider. MySQL Alternate Port If your host uses an alternate port number for your database you'll need to change the DB_HOST value in the wp-config.php file to reflect the alternate port provided by your host. For localhost: define( 'DB_HOST', '127.0.0.1:3307' ); or in some cases: define( 'DB_HOST', 'localhost:3307' ); For specified server: define( 'DB_HOST', 'mysql.example.com:3307' ); Replace 3307 with whatever port number your host gives you. MySQL Sockets or Pipes If your host uses Unix sockets or pipes, adjust the DB_HOST value in the wp-config.php file accordingly. define( 'DB_HOST', '127.0.0.1:/var/run/mysqld/mysqld.sock' ); // or define( 'DB_HOST', 'localhost:/var/run/mysqld/mysqld.sock' ); // or define( 'DB_HOST', 'example.tld:/var/run/mysqld/mysqld.sock' ); Replace /var/run/mysqld/mysqld.sock with the socket or pipe information provided by your host. Possible DB_HOST values Different hosting companies use different network settings for their mysql databases. If your hosting company is listed below in the left column, the value on the right is similar to the correct value for DB_HOST. Contact your tech support and/or search your hosting companies online Documentation to be sure. Hosting Company DB_HOST Value Guess 1and1 db12345678 A2 Hosting localhost AN Hosting localhost Aruba.it localhost or real IP provided with activation mail. A Small Orange localhost AT&T xxxxxxxx.carrierzone.com full server name found in PHP MyAdmin. BlueHost localhost DreamHost mysql.example.com GoDaddy - Shared and 4GH Hosting In the Databases menu go to MySQL. To the right of the database name click on Actions and Details. The hostname is at the bottom of the window. GoDaddy - cPanel Hosting localhost GoDaddy - Plesk Hosting Use the IP address shown in the Databases Section in Plesk. Do not include :3306 HostGator localhost ICDSoft localhost:/tmp/mysql5.sock Infomaniak Network mysql.yourdomain InMotion Hosting localhost iPage username.ipagemysql.com IPower username.ipowermysql.com Laughing Squid localhost MediaTemple Grid internal-db.s00000.gridserver.com - (Replace "00000" with the actual site number) MediaTemple DV localhost MegaHost localhost NearlyFreeSpeech.Net username.db NetworkSolutions mysqlv5 one.com example.com.mysql pair Networks dbnnnx.pair.com QTH.com localhost Rackspace Cloud localhost for unmanaged servers, variable for Cloud Sites like mysqlXY-AB.wcN.dfQ.stabletransit.com where X,Y,A,B,N,Q are variables SysFix.eu Power Hosting datapower.sysfix.eu Site5 localhost Yahoo mysql Hosts with cPanel localhost Hosts with Plesk localhost Hosts with DirectAdmin localhost Tophost.it sql.your-domain-name.it Database character set As of WordPress Version 2.2, DB_CHARSET was made available to allow designation of the database character set (e.g. tis620 for TIS620 Thai) to be used when defining the MySQL database tables. The default value of utf8 (Unicode UTF-8) is almost always the best option. UTF-8 supports any language, so you typically want to leave DB_CHARSET at utf8 and use the DB_COLLATE value for your language instead. This example shows utf8 which is considered the WordPress default value: define( 'DB_CHARSET', 'utf8' ); WARNING: Those performing new installations There usually should be no reason to change the default value of DB_CHARSET. If your blog needs a different character set, please read Character Sets and Collations MySQL Supports for valid DB_CHARSET values. WARNING: Those performing upgrades (especially blogs that existed before 2.2) If DB_CHARSET and DB_COLLATE do not exist in your wp-config.php file, DO NOT add either definition to yourwp-config.php file unless you read and understand Converting Database Character Sets. Adding DB_CHARSET and DB_COLLATE to the wp-config.php file, for an existing blog, can cause major problems. Database collation As of WordPress Version 2.2, DB_COLLATE was made available to allow designation of the database collation (i.e. the sort order of the character set). In most cases, this value should be left blank (null) so the database collation will be automatically assigned by MySQL based on the database character set specified by DB_CHARSET. An example of when you may need to set '''DB_COLLATE''' to one of the UTF-8 values defined in UTF-8 character sets for most Western European languages would be when a different language in which the characters that you entered are not the same as what is being displayed. The WordPress default DB_COLLATE value: define( 'DB_COLLATE', '' ); UTF-8 Unicode General collation define( 'DB_COLLATE', 'utf8_general_ci' ); UTF-8 Unicode Turkish collation define( 'DB_COLLATE', 'utf8_turkish_ci' ); WARNING: Those performing new installations There usually should be no reason to change the default value of DB_COLLATE. Leaving the value blank (null) will insure the collation is automatically assigned by MySQL when the database tables are created. WARNING: Those performing upgrades (especially blogs that existed before 2.2) If DB_COLLATE and DB_CHARSET do not exist in your wp-config.php file, DO NOT add either definition to yourwp-config.php file unless you read and understand Converting Database Character Sets. And you may be in need of a WordPress upgrade. Security Keys In Version 2.6, three (3) security keys, AUTH_KEY, SECURE_AUTH_KEY, and LOGGED_IN_KEY, were added to ensure better encryption of information stored in the user's cookies. (These collectively replaced a single key introduced in Version 2.5.) In Version 2.7 a fourth key, NONCE_KEY, was added to this group. When each key was added, corresponding salts were added: AUTH_SALT,SECURE_AUTH_SALT, LOGGED_IN_SALT, and NONCE_SALT. You don't have to remember the keys, just make them long, random and complicated -- or better yet, use the online generator. You can change these at any point in time to invalidate all existing cookies. This does mean that all users will have to login again. Example (don't use these!): define( 'AUTH_KEY', 't`DK%X:>xy|e-Z(BXb/f(Ur`8#~UzUQG-^_Cs_GHs5U-&Wb?pgn^p8(2@}IcnCa|' ); define( 'SECURE_AUTH_KEY', 'D&ovlU#|CvJ##uNq}bel+^MFtT&.b9{UvR]g%ixsXhGlRJ7q!h}XWdEC[BOKXssj' ); define( 'LOGGED_IN_KEY', 'MGKi8Br(&{H*~&0s;{k0(hdXW|0M=X={we6;Mpvtg+V.o<$|#_}qG(GaVDEsn,~*4i' ); define( 'NONCE_SALT', 'a|#h{c5|P &xWs4IZ20c2&%4!c(/uG}W:mAvy A secret key makes your site harder to successfully attack by adding random elements to the password. In simple terms, a secret key is a password with elements that make it harder to generate enough options to break through your security barriers. A password like "password" or "test" is simple and easily broken. A random, long password which uses no dictionary words, such as "88a7da62429ba6ad3cb3c76a09641fc" would take a brute force attacker millions of hours to crack. A 'salt is used to further enhance the security of the generated result. The four keys are required for the enhanced security. The four salts are recommended, but are not required, because WordPress will generate salts for you if none are provided. They are included in wp-config.php by default for inclusiveness. For more information on the technical background and breakdown of secret keys and secure passwords, see: Ryan Boren - SSL and Cookies in WordPress 2.6 WordPress Support Forum - HOWTO: Set up secret keys in WordPress 2.6+ Wikipedia's explanation of Password Cracking Lorelle VanFossen - Protect Your Blog With a Solid Password Instructables - Security Password Tips Huffington Post - 17 Tips You Can Do Today to Protect Your Online Passwords Advanced Options The following sections may contain advanced information and some changes might result in unforeseen issues. Please make sure you practice regular backups and know how to restore them before modifying these settings. table_prefix The $table_prefix is the value placed in the front of your database tables. Change the value if you want to use something other than wp_ for your database prefix. Typically this is changed if you are installing multiple WordPress blogs in the same database, as is done with the multisite feature. It is possible to have multiple installations in one database if you give each a unique prefix. Keep security in mind if you choose to do this. $table_prefix = 'r235_'; // Only numbers, letters, and underscores please! WP_SITEURL WP_SITEURL, defined since WordPress Version 2.2, allows the WordPress address (URL) to be defined. The value defined is the address where your WordPress core files reside. It should include the http:// part too. Do not put a slash "/" at the end. Setting this value in wp-config.php overrides the wp_options table value for siteurl. Adding this in can reduce the number of database calls when loading your site. Note: This will 'not' change the database stored value. The url will revert to the old database value if this line is ever removed from wp-config. Use the RELOCATE constant to change the siteurl value in the database. If WordPress is installed into a directory called "wordpress" for the domain example.com, define WP_SITEURL like this: define( 'WP_SITEURL', 'http://example.com/wordpress' ); Dynamically set WP_SITEURL based on $_SERVER['HTTP_HOST'] define( 'WP_SITEURL', 'http://' . $_SERVER['HTTP_HOST'] . '/path/to/wordpress' ); Note: HTTP_HOST is created dynamically by php based on the value of the HTTP HOST Header in the request, thus possibly allowing for file inclusion vulnerabilities. SERVER_NAME may also be created dynamically. However, when Apache is configured as UseCanonicalName "on", SERVER_NAME is set by the server configuration, instead of dynamically. In that case, it is safer to user SERVER_NAME than HTTP_HOST. Dynamically set WP_SITEURL based on $_SERVER['SERVER_NAME'] define( 'WP_SITEURL', 'http://' . $_SERVER['SERVER_NAME'] . '/path/to/wordpress' ); Blog address (URL) WP_HOME is another wp-config.php option added in WordPress Version 2.2. Similar to WP_SITEURL, WP_HOME overrides thewp_options table value for home but does not change it in the database. home is the address you want people to type in their browser to reach your WordPress blog. It should include the http:// part and should not have a slash "/" at the end. Adding this in can reduce the number of database calls when loading your site. define( 'WP_HOME', 'http://example.com/wordpress' ); If you are using the technique described in Giving WordPress Its Own Directory then follow the example below. Remember, you will also be placing an index.php in your web-root directory if you use a setting like this. define( 'WP_HOME', 'http://example.com' ); Dynamically set WP_HOME based on $_SERVER['HTTP_HOST'] define( 'WP_HOME', 'http://' . $_SERVER['HTTP_HOST'] . '/path/to/wordpress' ); Moving wp-content folder Since Version 2.6, you can move the wp-content directory, which holds your themes, plugins, and uploads, outside of the WordPress application directory. Set WP_CONTENT_DIR to the full local path of this directory (no trailing slash), e.g. define( 'WP_CONTENT_DIR', dirname(__FILE__) . '/blog/wp-content' ); Set WP_CONTENT_URL to the full URL of this directory (no trailing slash), e.g. define( 'WP_CONTENT_URL', 'http://example/blog/wp-content' ); Moving plugin folder Set WP_PLUGIN_DIR to the full local path of this directory (no trailing slash), e.g. define( 'WP_PLUGIN_DIR', dirname(__FILE__) . '/blog/wp-content/plugins' ); Set WP_PLUGIN_URL to the full URI of this directory (no trailing slash), e.g. define( 'WP_PLUGIN_URL', 'http://example/blog/wp-content/plugins' ); If you have compability issues with plugins Set PLUGINDIR to the full local path of this directory (no trailing slash), e.g. define( 'PLUGINDIR', dirname(__FILE__) . '/blog/wp-content/plugins' ); Moving themes folder You cannot move the themes folder because its path is hardcoded relative to the wp-content folder: $theme_root = WP_CONTENT_DIR . '/themes'; However, you can register additional theme directories using register_theme_directory. See how to move the wp-content folder. For more details how the themes folder is determined, see wp-includes/theme.php. Moving uploads folder Set UPLOADS to : define( 'UPLOADS', 'blog/wp-content/uploads' ); This path can not be absolute. It is always relative to ABSPATH, therefore does not require a leading slash. Modify AutoSave Interval When editing a post, WordPress uses Ajax to auto-save revisions to the post as you edit. You may want to increase this setting for longer delays in between auto-saves, or decrease the setting to make sure you never lose changes. The default is 60 seconds. define( 'AUTOSAVE_INTERVAL', 160 ); // Seconds Post Revisions WordPress, by default, will save copies of each edit made to a post or page, allowing the possibility of reverting to a previous version of that post or page. The saving of revisions can be disabled, or a maximum number of revisions per post or page can be specified. Disable Post Revisions If you do not set this value, WordPress defaults WP_POST_REVISIONS to true (enable post revisions). If you want to disable the awesome revisions feature, use this setting: define( 'WP_POST_REVISIONS', false ); Note: Some users could not get this to function until moving the command to the first line under the initial block comment in config.php. Specify the Number of Post Revisions If you want to specify a maximum number of revisions that WordPress stores, change false to an integer/number (e.g., 3 or 12). define( 'WP_POST_REVISIONS', 3 ); Note: Some users could not get this to function until moving the command to the first line under the initial block comment in config.php. Set Cookie Domain The domain set in the cookies for WordPress can be specified for those with unusual domain setups. For example, if subdomains are used to serve static content, you can set the cookie domain to only your non-static domain to prevent WordPress cookies from being sent with each request to static content on your subdomain . define( 'COOKIE_DOMAIN', 'www.example.com' ); Enable Multisite / Network Ability WP_ALLOW_MULTISITE is a feature introduced in WordPress Version 3.0 to enable multisite functionality previously achieved through WordPress MU. If this setting is absent from wp-config.php it defaults to false. define( 'WP_ALLOW_MULTISITE', true ); Redirect Nonexistent Blogs NOBLOGREDIRECT can be used to redirect the browser if the visitor tries to access a nonexistent subdomain or a subfolder. E.g., http://nonexistent.example.com or http://example.com/nonexistent/. define( 'NOBLOGREDIRECT', 'http://example.com' ); WP_Debug The WP_DEBUG option, added in WordPress Version 2.3.1, controls the reporting of some errors and warnings and enables use of theWP_DEBUG_DISPLAY and WP_DEBUG_LOG settings. The default boolean value is false. define( 'WP_DEBUG', true ); In WordPress versions since 2.3.2, database errors are printed only if WP_DEBUG is set to true. In earlier versions, database errors were always printed. (Database errors are handled by the wpdb class and are not affected by PHP's error settings.) In WordPress version 2.5, setting WP_DEBUG to true also raises the error reporting level to E_ALL and activates warnings when deprecated functions or files are used; otherwise, WordPress sets the error reporting level to E_ALL ^ E_NOTICE ^ E_USER_NOTICE. SCRIPT_DEBUG SCRIPT_DEBUG is a related constant that will force WordPress to use the "dev" versions of scripts and stylesheets in wp-includes/js, wp-includes/css, wp-admin/js, and wp-admin/css will be loaded instead of the .min.css and .min.js versions.. If you are planning on modifying some of WordPress' built-in JavaScript or Cascading Style Sheets, you should add the following code to your config file: define( 'SCRIPT_DEBUG', true ); Disable Javascript Concatenation To result in faster administration screens, all Javascript files are concatenated into one URL. If Javascript is failing to work in an administration screen, you can try disabling this feature: define( 'CONCATENATE_SCRIPTS', false ); Configure Error Logging Configuring error logging can be a bit tricky. First of all, default PHP error log and display settings are set in the php.ini file, which you may or may not have access to. If you do, they should be set to the desired settings for live PHP pages served to the public. It's strongly recommended that no error messages are displayed to the public and instead routed to an error log. Further more, error logs should not be located in the publicly accessible portion of your server. Sample recommended php.ini error settings: error_reporting = 4339 display_errors = Off display_startup_errors = Off log_errors = On error_log = /home/example.com/logs/php_error.log log_errors_max_len = 1024 ignore_repeated_errors = On ignore_repeated_source = Off html_errors = Off About Error Reporting 4339 This is a custom value that only logs issues that affect the functioning of your site, and ignores things like notices that may not even be errors. See PHP Error Constants for the meaning of each binary position for 1000011110011, which is the binary number equal to 4339. The far left 1 means report any E_RECOVERABLE_ERROR. The next 0 means do not report E_STRICT, (which is thrown when sloppy but functional coding is used) and so on. Feel free to determine your own custom error reporting number to use in place of 4339. Obviously, you will want different settings for your development environment. If your staging copy is on the same server, or you don't have access to php.ini, you will need to override the default settings at run time. It's a matter of personal preference whether you prefer errors to go to a log file, or you prefer to be notified immediately of any error, or perhaps both. Here's an example that reports all errors immediately that you could insert into your wp-config.php file: @ini_set( 'log_errors', 'Off' ); @ini_set( 'display_errors', 'On' ); define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', false ); define( 'WP_DEBUG_DISPLAY', true ); Because wp-config.php is loaded for every page view not loaded from a cache file, it is an excellent location to set php.ini settings that control your php installation. This is useful if you don't have access to a php.ini file, or if you just want to change some settings on the fly. One exception is 'error_reporting'. When WP_DEBUG is defined as true, 'error_reporting' will be set to E_ALL by WordPress regardless of anything you try to set in wp-config.php. If you really have a need to set 'error_reporting' to something else, it must be done after wp-settings.php is loaded, such as in a plugin file. If you turn on error logging, remember to delete the file afterwards, as it will often be in a publicly accessible location, where anyone could gain access to your log. Here is an example that turns php error_logging on and logs them to a specific file. If WP_DEBUG is defined to true, the errors will also be saved to this file. Just place this above any require_once or include commands. @ini_set( 'log_errors', 'On' ); @ini_set( 'display_errors', 'Off' ); @ini_set( 'error_log', '/home/example.com/logs/php_error.log' ); /* That's all, stop editing! Happy blogging. */ Another example of logging errors, as suggested by Mike Little on the wp-hackers email list: /** * This will log all errors notices and warnings to a file called debug.log in * wp-content (if Apache does not have write permission, you may need to create * the file first and set the appropriate permissions (i.e. use 666) ) */ define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', false ); @ini_set( 'display_errors', 0 ); A refined version from Mike Little on the Manchester WordPress User Group: /** * This will log all errors notices and warnings to a file called debug.log in * wp-content only when WP_DEBUG is true. if Apache does not have write permission, * you may need to create the file first and set the appropriate permissions (i.e. use 666). */ define( 'WP_DEBUG', true ); // Or false if ( WP_DEBUG ) { define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', false ); @ini_set( 'display_errors', 0 ); } Confusing the issue is that WordPress has three (3) constants that look like they could do the same thing. First off, remember that ifWP_DEBUG is false, it and the other two WordPress DEBUG constants do not do anything. The PHP directives, whatever they are, will prevail. Except for 'error_reporting', WordPress will set this to 4983 if WP_DEBUG is defined as false. Second, even if WP_DEBUG is true, the other constants only do something if they too are set to true. If they are set to false, the PHP directives remain unchanged. For example, if your php.ini file has the directive ('display_errors' = 'On'); but you have the statement define( 'WP_DEBUG_DISPLAY', false ); in your wp-config.php file, errors will still be displayed on screen even though you tried to prevent it by setting WP_DEBUG_DISPLAY to false because that is the PHP configured behavior. This is why it's very important to set the PHP directives to what you need in case any of the related WP constants are set to false. To be safe, explicitly set/define both types. More detailed descriptions of the WP constants is available at Debugging in WordPress. For your public, production WordPress installation, you might consider placing the following in your wp-config.php file, even though it may be partly redundant: @ini_set( 'log_errors', 'On' ); @ini_set( 'display_errors', 'Off' ); define( 'WP_DEBUG', false ); define( 'WP_DEBUG_LOG', false ); define( 'WP_DEBUG_DISPLAY', false ); The default debug log file is /wp-content/debug.log. Placing error logs in publicly accessible locations is a security risk. Ideally, your log files should be placed above you site's public root directory. If you can't do this, at the very least, set the log file permissions to 600 and add this entry to the .htaccess file in the root directory of your WordPress installation: Order allow,deny Deny from all This prevents anyone from accessing the file via HTTP. You can always view the log file by retrieving it from your server via FTP. Increasing memory allocated to PHP Also released with Version 2.5, the WP_MEMORY_LIMIT option allows you to specify the maximum amount of memory that can be consumed by PHP. This setting may be necessary in the event you receive a message such as "Allowed memory size of xxxxxx bytes exhausted". This setting increases PHP Memory only for WordPress, not other applications. By default, WordPress will attempt to increase memory allocated to PHP to 40MB (code is at the beginning of /wp-includes/default-constants.php) for single site and 64MB for multisite, so the setting in wp-config.php should reflect something higher than 40MB or 64MB depending on your setup. WordPress will automatically check if PHP has been allocated less memory than the entered value before utilizing this function. For example, if PHP has been allocated 64MB, there is no need to set this value to 64M as WordPress will automatically use all 64MB if need be. Note: Some hosts do not allow for increasing the PHP memory limit automatically. In that event, contact your host to increase the PHP memory limit. Also, many hosts set the PHP limit at 8MB. Increase PHP Memory to 64MB define( 'WP_MEMORY_LIMIT', '64M' ); Increase PHP Memory to 96MB define( 'WP_MEMORY_LIMIT', '96M' ); Administration tasks require much memory than usual operation. When in the administration area, the memory can be increased or decreased from the WP_MEMORY_LIMIT by defining WP_MAX_MEMORY_LIMIT. define( 'WP_MAX_MEMORY_LIMIT', '256M' ); Note: this has to be put before wp-settings.php inclusion. Cache The WP_CACHE setting, if true, includes the wp-content/advanced-cache.php script, when executing wp-settings.php. See this document for more information define( 'WP_CACHE', true ); Custom User and Usermeta Tables CUSTOM_USER_TABLE and CUSTOM_USER_META_TABLE are used to designate that the user and usermeta tables normally utilized by WordPress are not used, instead these values/tables are used to store your user information. define( 'CUSTOM_USER_TABLE', $table_prefix.'my_users' ); define( 'CUSTOM_USER_META_TABLE', $table_prefix.'my_usermeta' ); Note: Even if 'CUSTOM_USER_META_TABLE' is manually set, a usermeta table is still created for each database with the corresponding permissions for each instance. By default, the WordPress installer will add permissions for the first user (ID #1). You also need to manage permissions to each of the site via a plugin or custom function. If this isn't setup you will experience permission errors and log-in issues. CUSTOM_USER_TABLE is easiest to adopt during initial Setup your first instance of WordPress. The define statements of the wp-config.php on the first instance point to where wp_users data will be stored by default. After the first site setup, copying the working wp-config.php to your next instance will only require a change the $table_prefix variable. Do not use an e-mail address that is already in use by your original install. Once you have finished the setup process log in with the auto generated admin account and password. Next, promote your normal account to the administrator level and Log out of admin. Log back in as yourself, delete the admin account and promote the other user accounts as is needed. Language and Language Directory WordPress Version 4.0 allows you to change the language in your WordPress Administration Screens. To change the language in the admin settings screen. Go to Settings > General and select Site Language. WordPress v3.9.6 and below WPLANG defines the name of the language translation (.mo) file. WP_LANG_DIR defines what directory the WPLANG .mo file resides. If WP_LANG_DIR is not defined WordPress looks first to wp-content/languages and then wp-includes/languages for the .mo defined by WPLANG file. define( 'WPLANG', 'de_DE' ); define( 'WP_LANG_DIR', dirname(__FILE__) . 'wordpress/languages' ); To find out the WPLANG language code, please refer here. The code in WP Local column is what you need. Save queries for analysis The SAVEQUERIES definition saves the database queries to an array and that array can be displayed to help analyze those queries. The information saves each query, what function called it, and how long that query took to execute. Note: This will have a performance impact on your site, so make sure to turn this off when you aren't debugging. First, add this to the wp-config.php file: define( 'SAVEQUERIES', true ); Then in the footer of your theme put this: "; print_r( $wpdb->queries ); echo ""; } ?> Override of default file permissions The FS_CHMOD_DIR and FS_CHMOD_FILE define statements allow override of default file permissions. These two variables were developed in response to the problem of the core update function failing with hosts running under suexec. If a host uses restrictive file permissions (e.g. 400) for all user files, and refuses to access files which have group or world permissions set, these definitions could solve the problem. define( 'FS_CHMOD_DIR', ( 0755 & ~ umask() ) ); define( 'FS_CHMOD_FILE', ( 0644 & ~ umask() ) ); Example to provide setgid: define( 'FS_CHMOD_DIR', ( 02755 & ~umask() ) ); Note: '0755' and '02755' are octal values. Octal values must be prefixed with a 0 and are not delineated with single quotes ('). See Also: Changing File Permissions WordPress Upgrade Constants Note: Define as few of the below constants as needed to correct your update issues. The most common causes of needing to define these are: Host running with a special installation setup involving symlinks. You may need to define the path-related constants (FTP_BASE, FTP_CONTENT_DIR, and FTP_PLUGIN_DIR). Often defining simply the base will be enough. Certain PHP installations shipped with a PHP FTP extension which is incompatible with certain FTP servers. Under these rare situations, you may need to define FS_METHOD to "ftpsockets". The following are valid constants for WordPress updates: FS_METHOD forces the filesystem method. It should only be "direct", "ssh2", "ftpext", or "ftpsockets". Generally, you should only change this if you are experiencing update problems. If you change it and it doesn't help, change it back/remove it. Under most circumstances, setting it to 'ftpsockets' will work if the automatically chosen method does not. (Primary Preference) "direct" forces it to use Direct File I/O requests from within PHP, this is fraught with opening up security issues on poorly configured hosts, This is chosen automatically when appropriate. (Secondary Preference) "ssh2" is to force the usage of the SSH PHP Extension if installed (3rd Preference) "ftpext" is to force the usage of the FTP PHP Extension for FTP Access, and finally (4th Preference) "ftpsockets" utilises the PHP Sockets Class for FTP Access. FTP_BASE is the full path to the "base"(ABSPATH) folder of the WordPress installation. FTP_CONTENT_DIR is the full path to the wp-content folder of the WordPress installation. FTP_PLUGIN_DIR is the full path to the plugins folder of the WordPress installation. FTP_PUBKEY is the full path to your SSH public key. FTP_PRIKEY is the full path to your SSH private key. FTP_USER is either user FTP or SSH username. Most likely these are the same, but use the appropriate one for the type of update you wish to do. FTP_PASS is the password for the username entered for FTP_USER. If you are using SSH public key authentication this can be omitted. FTP_HOST is the hostname:port combination for your SSH/FTP server. The default FTP port is 21 and the default SSH port is 22. These do not need to be mentioned. FTP_SSL TRUE for SSL-connection if supported by the underlying transport (not available on all servers). This is for "Secure FTP" not for SSH SFTP. define( 'FS_METHOD', 'ftpext' ); define( 'FTP_BASE', '/path/to/wordpress/' ); define( 'FTP_CONTENT_DIR', '/path/to/wordpress/wp-content/' ); define( 'FTP_PLUGIN_DIR ', '/path/to/wordpress/wp-content/plugins/' ); define( 'FTP_PUBKEY', '/home/username/.ssh/id_rsa.pub' ); define( 'FTP_PRIKEY', '/home/username/.ssh/id_rsa' ); define( 'FTP_USER', 'username' ); define( 'FTP_PASS', 'password' ); define( 'FTP_HOST', 'ftp.example.org' ); define( 'FTP_SSL', false ); Some configurations should set FTP_HOST to localhost to avoid 503 problems when trying to update plugins or WP itself. Enabling SSH Upgrade Access There are two ways to upgrade using SSH2. The first is to use the SSH SFTP Updater Support plugin. The second is to use the built-in SSH2 upgrader, which requires the pecl SSH2 extension be installed. To install the pecl SSH2 extension you will need to issue a command similar to the following or talk to your web hosting provider to get this installed: pecl install ssh2 After installing the pecl ssh2 extension you will need to modify your php configuration to automatically load this extension. pecl is provided by the pear package in most linux distributions. To install pecl in Redhat/Fedora/CentOS: yum -y install php-pear To install pecl in Debian/Ubuntu: apt-get install php-pear It is recommended to use a private key that is not pass-phrase protected. There have been numerous reports that pass phrase protected private keys do not work properly. If you decide to try a pass phrase protected private key you will need to enter the pass phrase for the private key as FTP_PASS, or entering it in the "Password" field in the presented credential field when installing updates. Alternative Cron There might be reason to use an alternative Cron with WP. Most commonly this is done if scheduled posts are not getting published as predicted. This alternative method uses a redirection approach. The users' browser get a redirect when the cron needs to run, so that they come back to the site immediately while cron continues to run in the connection they just dropped. This method has certain risks, since it depends on a non-native WordPress service. define( 'ALTERNATE_WP_CRON', true ); Disable Cron and Cron Timeout Disable cron entirely by setting DISABLE_WP_CRON to true. define( 'DISABLE_WP_CRON', true ); Make sure a cron process cannot run more than once every WP_CRON_LOCK_TIMEOUT seconds. define( 'WP_CRON_LOCK_TIMEOUT', 60 ); Additional Defined Constants Here are additional constants that can be defined. These probably shouldn't be set unless other methodologies have been attempted first. The Cookie definitions can be particularly useful if you have an unusual domain setup. define( 'COOKIEPATH', preg_replace( '|https?://[^/]+|i', '', get_option( 'home' ) . '/' ) ); define( 'SITECOOKIEPATH', preg_replace( '|https?://[^/]+|i', '', get_option( 'siteurl' ) . '/' ) ); define( 'ADMIN_COOKIE_PATH', SITECOOKIEPATH . 'wp-admin' ); define( 'PLUGINS_COOKIE_PATH', preg_replace( '|https?://[^/]+|i', '', WP_PLUGIN_URL ) ); define( 'TEMPLATEPATH', get_template_directory() ); define( 'STYLESHEETPATH', get_stylesheet_directory() ); Empty Trash Added with Version 2.9, this constant controls the number of days before WordPress permanently deletes posts, pages, attachments, and comments, from the trash bin. The default is 30 days: define( 'EMPTY_TRASH_DAYS', 30 ); // 30 days To disable trash set the number of days to zero. define( 'EMPTY_TRASH_DAYS', 0 ); // Zero days Note: WordPress will not ask for confirmation when someone clicks on "Delete Permanently" using this setting. Automatic Database Optimizing Added with Version 2.9, there is automatic database repair support, which you can enable by adding the following define to your wp-config.php file. Note: This should only be enabled if needed and disabled once the issue is solved. When enabled, a user does not need to be logged in to access the functionality, since its main intent is to repair a corrupted database and users can often not login when the database is corrupt. define( 'WP_ALLOW_REPAIR', true ); The script can be found at {$your_site}/wp-admin/maint/repair.php DO_NOT_UPGRADE_GLOBAL_TABLES A DO_NOT_UPGRADE_GLOBAL_TABLES define prevents dbDelta() and the upgrade functions from doing expensive queries against global tables. Sites that have large global tables (particularly users and usermeta), as well as sites that share user tables with bbPress and other WordPress installs, can prevent the upgrade from changing those tables during upgrade by defining DO_NOT_UPGRADE_GLOBAL_TABLES to true. Since an ALTER, or an unbounded DELETE or UPDATE, can take a long time to complete, large sites usually want to avoid these being run as part of the upgrade so they can handle it themselves. Further, if installations are sharing user tables between multiple bbPress and WordPress installs you may to want one site to be the upgrade master. define( 'DO_NOT_UPGRADE_GLOBAL_TABLES', true ); View All Defined Constants PHP has a function that returns an array of all the currently defined constants with their values. print_r( @get_defined_constants() ); Disable the Plugin and Theme Editor Occasionally you may wish to disable the plugin or theme editor to prevent overzealous users from being able to edit sensitive files and potentially crash the site. Disabling these also provides an additional layer of security if a hacker gains access to a well-privileged user account. define( 'DISALLOW_FILE_EDIT', true ); Note: The functionality of some plugins may be affected by the use of current_user_can('edit_plugins') in their code. Plugin authors should avoid checking for this capability, or at least check if this constant is set and display an appropriate error message. Be aware that if a plugin is not working this may be the cause. Disable Plugin and Theme Update and Installation This will block users being able to use the plugin and theme installation/update functionality from the WordPress admin area. Setting this constant also disables the Plugin and Theme editor (i.e. you don't need to set DISALLOW_FILE_MODS and DISALLOW_FILE_EDIT, as on its own DISALLOW_FILE_MODS will have the same effect). define( 'DISALLOW_FILE_MODS', true ); Require SSL for Admin and Logins Note: WordPress Version 4.0 deprecated FORCE_SSL_LOGIN. Please use FORCE_SSL_ADMIN. FORCE_SSL_ADMIN is for when you want to secure logins and the admin area so that both passwords and cookies are never sent in the clear. See also Administration_Over_SSL for more details. define( 'FORCE_SSL_ADMIN', true ); Block External URL Requests Block external URL requests by defining WP_HTTP_BLOCK_EXTERNAL as true and this will only allow localhost and your blog to make requests. The constant WP_ACCESSIBLE_HOSTS will allow additional hosts to go through for requests. The format of the WP_ACCESSIBLE_HOSTS constant is a comma separated list of hostnames to allow, wildcard domains are supported, eg *.wordpress.org will allow for all subdomains of wordpress.org to be contacted. define( 'WP_HTTP_BLOCK_EXTERNAL', true ); define( 'WP_ACCESSIBLE_HOSTS', 'api.wordpress.org,*.github.com' ); Disable WordPress Auto Updates There might be reason for a site to not auto-update, such as customizations or host supplied updates. It can also be done before a major release to allow time for testing on a development or staging environment before allowing the update on a production site. define( 'AUTOMATIC_UPDATER_DISABLED', true ); Disable WordPress Core Updates The easiest way to manipulate core updates is with the WP_AUTO_UPDATE_CORE constant: # Disable all core updates: define( 'WP_AUTO_UPDATE_CORE', false ); # Enable all core updates, including minor and major: define( 'WP_AUTO_UPDATE_CORE', true ); # Enable core updates for minor releases (default): define( 'WP_AUTO_UPDATE_CORE', 'minor' ); Reference: Disabling Auto Updates in WordPress 3.7 Cleanup Image Edits By default, WordPress creates a new set of images every time you edit an image and when you restore the original, it leaves all the edits on the server. Defining IMAGE_EDIT_OVERWRITE as true changes this behaviour. Only one set of image edits are ever created and when you restore the original, the edits are removed from the server. define( 'IMAGE_EDIT_OVERWRITE', true ); Double Check Before Saving Be sure to check for leading and/or trailing spaces around any of the above values you entered, and DON'T delete the single quotes! Before you save the file, be sure to double-check that you have not accidentally deleted any of the single quotes around the parameter values. Be sure there is nothing after the closing PHP tag in the file. The last thing in the file should be ?> and nothing else. No spaces. To save the file, choose File > Save As > wp-config.php and save the file in the root of your WordPress install. Upload the file to your web server and you're ready to install WordPress! Cookies mikevanlohuizen — Wed, 24 Feb 2016 10:54:12 +0000 [codex_languages en="Cookies" ja_codex="Cookies" ptbr_codex="Cookies"] WordPress uses cookies for authentication. That means that in order to log in to your WordPress site, you must have cookies enabled in your browser. Enable Cookies in Your Browser Google Chrome https://support.google.com/chrome/answer/95647 Mozilla Firefox https://support.mozilla.org/en-US/kb/enable-and-disable-cookies-website-preferences Internet Explorer https://support.microsoft.com/en-us/help/17442/windows-internet-explorer-delete-manage-cookies Safari https://support.apple.com/kb/PH21411 Opera http://www.opera.com/help/tutorials/security/cookies/ Unexpected Output / Headers Already Sent? If you are seeing these errors, please see the Troubleshooting FAQ. Debugging in WordPress juhisaxena — Sat, 27 Feb 2016 05:41:44 +0000 Debugging PHP code is part of any project, but WordPress comes with specific debug systems designed to simplify the process as well as standardize code across the core, plugins and themes. This page describes the various debugging tools in WordPress and how to be more productive in your coding as well as increasing the overall quality and interoperativity of your code. [info]NOTE: While it is not mandatory to account for WP_DEBUG in plugins and themes it is highly recommended that plugin and theme developers use WP_DEBUG mode while working on code they plan to release publicly. If your plugin or theme is not compatible then the errors, notices and warnings it throws will make it impossible for other developers to use your plugin/theme while they have WP_DEBUG enabled and your theme will not be eligible for promotion via the official WordPress tools.[/info] WP_DEBUG WP_DEBUG is a PHP constant (a permanent global variable) that can be used to trigger the "debug" mode throughout WordPress. It is assumed to be false by default and is usually set to true in the wp-config.php file on development copies of WordPress. define( 'WP_DEBUG', true ); define( 'WP_DEBUG', false ); [alert]Note: The true and false values in the example are not surrounded by apostrophes (') because they are boolean (true/false) values. If you set constants to 'false', they will be interpreted as true because the quotes make it a string rather than a boolean.[/alert] It is not recommended to use WP_DEBUG or the other debug tools on live sites; they are meant for local testing and staging installs. PHP Errors, Warnings, and Notices Enabling WP_DEBUG will cause all PHP errors, notices and warnings to be displayed. This is likely to modify the default behavior of PHP which only displays fatal errors and/or shows a white screen of death when errors are reached. Showing all PHP notices and warnings often results in error messages for things that don't seem broken, but do not follow proper data validation conventions inside PHP. These warnings are easy to fix once the relevant code has been identified, and the resulting code is almost always more bug-resistant and easier to maintain. Deprecated Functions and Arguments Enabling WP_DEBUG will also cause notices about deprecated functions and arguments within WordPress that are being used on your site. These are functions or function arguments that have not been removed from the core code yet but are slated for deletion in the near future. Deprecation notices often indicate the new function that should be used instead. WP_DEBUG_LOG WP_DEBUG_LOG is a companion to WP_DEBUG that causes all errors to also be saved to a debug.log log file inside the /wp-content/ directory. This is useful if you want to review all notices later or need to view notices generated off-screen (e.g. during an AJAX request or wp-cron run). Note that this allows you to write to /wp-content/debug.log using PHP's built in error_log() function, which can be useful for instance when debugging AJAX events. define( 'WP_DEBUG_LOG', true ); [info]Note: for WP_DEBUG_LOG to do anything, WP_DEBUG must be enabled (true). Remember you can turn off WP_DEBUG_DISPLAY independently.[/info] WP_DEBUG_DISPLAY WP_DEBUG_DISPLAY is another companion to WP_DEBUG that controls whether debug messages are shown inside the HTML of pages or not. The default is 'true' which shows errors and warnings as they are generated. Setting this to false will hide all errors. This should be used in conjunction with WP_DEBUG_LOG so that errors can be reviewed later. define( 'WP_DEBUG_DISPLAY', false ); [info]Note: for WP_DEBUG_DISPLAY to do anything, WP_DEBUG must be enabled (true). Remember you can control WP_DEBUG_LOG independently.[/info] SCRIPT_DEBUG SCRIPT_DEBUG is a related constant that will force WordPress to use the "dev" versions of core CSS and JavaScript files rather than the minified versions that are normally loaded. This is useful when you are testing modifications to any built-in .js or .css files. Default is false. define( 'SCRIPT_DEBUG', true ); SAVEQUERIES The SAVEQUERIES definition saves the database queries to an array and that array can be displayed to help analyze those queries. The constant defined as true causes each query to be saved, how long that query took to execute, and what function called it. define( 'SAVEQUERIES', true ); The array is stored in the global $wpdb->queries. [alert]NOTE: This will have a performance impact on your site, so make sure to turn this off when you aren't debugging.[/alert] Example wp-config.php for Debugging The following code, inserted in your wp-config.php file, will log all errors, notices, and warnings to a file called debug.log in the wp-content directory. It will also hide the errors so they do not interrupt page generation. // Enable WP_DEBUG mode define( 'WP_DEBUG', true ); // Enable Debug logging to the /wp-content/debug.log file define( 'WP_DEBUG_LOG', true ); // Disable display of errors and warnings define( 'WP_DEBUG_DISPLAY', false ); @ini_set( 'display_errors', 0 ); // Use dev versions of core JS and CSS files (only needed if you are modifying these core files) define( 'SCRIPT_DEBUG', true ); [warning]NOTE: You must insert this BEFORE /* That's all, stop editing! Happy blogging. */ in the wp-config.php file.[/warning] Debugging Plugins There are many debugging plugins for WordPress that show more information about the internals, either for a specific component or in general. Here are some examples: Query Monitor Debug Bar Log Deprecated Notices External Resources WordPress 'wp-config.php' file Generator 'No White Screen' plugin: Display the error instead of a white screen Custom Fields atachibana — Sun, 28 Feb 2016 05:54:58 +0000 WordPress has the ability to allow post authors to assign custom fields to a post. This arbitrary extra information is known as meta-data. This meta-data can include bits of information such as: Mood: Happy Currently Reading: Cinderella Listening To: Rock Around the Clock Weather: Hot and humid With some extra coding, it is possible to achieve more complex actions, such as using the metadata to store an expiration date for a post. Meta-data is handled with key/value pairs. The key is the name of the meta-data element. The value is the information that will appear in the meta-data list on each individual post that the information is associated with. Keys can be used more than once per post. For example, if you were reading two different books (perhaps a technical book at work and a fiction at home), you could create a "reading" key and use it twice on the same post, once for each book. Here is an example of what this information might look like on your post: Currently Reading: Calvin and Hobbes Today's Mood: Jolly and Happy Usage Based upon our example above, let's add two custom fields, one called "Currently Reading" and the other "Today's Mood". Please follow below steps to to add this information to a post using Custom Fields. After you have written your post, scroll down to the area titled Custom Fields. Note: Some screen options on the Post & Page edit Administration Screens are hidden by default. Custom Fields are hidden by default if they have not been used before. To create a new Custom Field called "Currently Reading", enter the text "Currently Reading" (without the quotes) in the text entry field titled Name. The newly created Key ("Currently Reading") should now be assigned a Value, which in our case is the name of the book currently being read, "Calvin and Hobbes". Type "Calvin and Hobbes" in the Value field, again without the quotes. Click Add Custom Field button to save this custom information for that post. To add your "Today's Mood", repeat the process and add "Today's Mood" to the key and a description of your mood in the value text boxes and click Add Custom Field to save this information with the post. On your next post, you can add a new book and mood to your meta-data. In the Custom Fields section, the Key will now feature a pull down list with the previously entered Custom Fields. Choose "Currently Reading" and then enter the new book you are reading in the value. Click Add Custom Field and then repeat the process to add "Today's Mood". You only need to create a new "KEY" once, after which you can assign a value to that key for every post, if you so desire. You can also assign more than one Value to a key, for a post. This will come in handy for people who read more than one book at a time. Displaying Custom Fields To display the Custom Fields for each post, you have to use template tag that customizes your theme. For more detail about it, please refer WordPress Theme Developers Handbook. You may install Plugin that manages custom fields. Meta Box plugin - Plugin that allows you to create custom meta boxes and custom fields. Piklist - Plugin that allows you to create custom meta boxes and fields everywhere in WordPress. htaccess atachibana — Tue, 01 Mar 2016 17:40:17 +0000 The .htaccess is a distributed configuration file, and is how Apache handles configuration changes on a per-directory basis. WordPress uses this file to manipulate how Apache serves files from its root directory, and subdirectories thereof. Most notably, WP modifies this file to be able to handle pretty permalinks. This page may be used to restore a corrupted .htaccess file (e.g. a misbehaving plugin). Basic WP # BEGIN WordPress RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] # END WordPress Multisite WordPress 3.5 and up If you activated Multisite on WordPress 3.5 or later, use one of these. Subfolder Example RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] # add a trailing slash to /wp-admin RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L] RewriteCond %{REQUEST_FILENAME} -f [OR] RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^ - [L] RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L] RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L] RewriteRule . index.php [L] SubDomain Example RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] # add a trailing slash to /wp-admin RewriteRule ^wp-admin$ wp-admin/ [R=301,L] RewriteCond %{REQUEST_FILENAME} -f [OR] RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^ - [L] RewriteRule ^(wp-(content|admin|includes).*) $1 [L] RewriteRule ^(.*\.php)$ $1 [L] RewriteRule . index.php [L] WordPress 3.4 and below If you originally installed WordPress with 3.4 or older and activated Multisite then, you need to use one of these: SubFolder Example WordPress 3.0 through 3.4.2 # BEGIN WordPress RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] # uploaded files RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L] # add a trailing slash to /wp-admin RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L] RewriteCond %{REQUEST_FILENAME} -f [OR] RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^ - [L] RewriteRule ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L] RewriteRule ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L] RewriteRule . index.php [L] # END WordPress SubDomain Example # BEGIN WordPress RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] # uploaded files RewriteRule ^files/(.+) wp-includes/ms-files.php?file=$1 [L] RewriteCond %{REQUEST_FILENAME} -f [OR] RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^ - [L] RewriteRule . index.php [L] # END WordPress WordPress MU If you started using WordPress with WordPress MU (WPMU) and then migrated to a newer version of WordPress multisite, the .htaccess rules are more complex: SubFolder Example RewriteEngine On RewriteBase / # BEGIN WordPress #uploaded files RewriteRule ^(.*/)?files/$ index.php [L] RewriteCond %{REQUEST_URI} !.*wp-content/plugins.* RewriteRule ^(.*/)?files/(.*) wp-includes/ms-files.php?file=$2 [L] # add a trailing slash to /wp-admin RewriteCond %{REQUEST_URI} ^.*/wp-admin$ RewriteRule ^(.+)$ $1/ [R=301,L] RewriteCond %{REQUEST_FILENAME} -f [OR] RewriteCond %{REQUEST_FILENAME} -d RewriteRule . - [L] RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-.*) $2 [L] RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L] RewriteRule . index.php [L] # END WordPress General Examples Options Any options preceded by a + are added to the options currently in force, and any options preceded by a - are removed from the options currently in force. Possible values for the Options directive are any combination of: None All options are turned off. All All options except for MultiViews. This is the default setting. ExecCGI Execution of CGI scripts using mod_cgi is permitted. FollowSymLinks The server will follow symbolic links in this directory. Includes Server-side includes provided by mod_include are permitted. IncludesNOEXEC Server-side includes are permitted, but the #exec cmd and #exec cgi are disabled. Indexes URL maps to a directory, and no DirectoryIndex, a formatted listing of the directory. MultiViews Content negotiated "MultiViews" are allowed using mod_negotiation. SymLinksIfOwnerMatch Only follow symbolic links where target is owned by the same user id as the link. This will disable all options, and then only enable FollowSymLinks, which is necessary for mod_rewrite. Options None Options FollowSymLinks DirectoryIndex DirectoryIndex sets the file that Apache will serve if a directory is requested. Several URLs may be given, in which case the server will return the first one that it finds. DirectoryIndex index.php index.html /index.php DefaultLanguage DefaultLanguage will cause all files that do not already have a specific language tag associated with it will use this. DefaultLanguage en Default Charset Set the default character encoding sent in the HTTP header. See: Setting charset information in .htaccess AddDefaultCharset UTF-8 Set Charset for Specific Files AddType 'text/html; charset=UTF-8' .html Set for specific files AddCharset UTF-8 .html ServerSignature The ServerSignature directive allows the configuration of a trailing footer line under server-generated documents. Optionally add a line containing the server version and virtual host name to server-generated pages (internal error documents, FTP directory listings, mod_status and mod_info output etc., but not CGI generated documents or custom error documents). On adds a line with the server version number and ServerName of the serving virtual host Off suppresses the footer line Email creates a "mailto:" reference to the ServerAdmin of the referenced document SetEnv SERVER_ADMIN admin@site.com ServerSignature Email Force Files to be Downloaded The below will cause any requests for files ending in the specified extensions to not be displayed in the browser but instead force a "Save As" dialog so the client can download. AddType application/octet-stream .avi .mpg .mov .pdf .xls .mp4 HTTP Compression The AddOutputFilter directive maps the filename extension extension to the filters which will process responses from the server before they are sent to the client. This is in addition to any filters defined elsewhere, including SetOutputFilter and AddOutputFilterByType. This mapping is merged over any already in force, overriding any mappings that already exist for the same extension. See also: https://developers.google.com/speed/docs/insights/EnableCompression AddOutputFilterByType DEFLATE text/html text/plain text/xml application/xml application/xhtml+xml text/javascript text/css application/x-javascript BrowserMatch ^Mozilla/4 gzip-only-text/html BrowserMatch ^Mozilla/4\.0[678] no-gzip BrowserMatch \bMSIE !no-gzip !gzip-only-text/html Force Compression for certain files SetOutputFilter DEFLATE Send Custom HTTP Headers The Header directive lets you send HTTP headers for every request, or just specific files. You can view a sites HTTP Headers using Firebug, Chrome Dev Tools, Wireshark or an online tool. Header set X-Pingback "http://www.askapache.com/xmlrpc.php" Header set Content-Language "en-US" Unset HTTP Headers This will unset HTTP headers, using always will try extra hard to remove them. Header unset Pragma Header always unset WP-Super-Cache Header always unset X-Pingback Password Protect Login This is very useful for protecting the wp-login.php file. You can use this htpasswd generator. Basic Authentication AuthType Basic AuthName "Password Protected" AuthUserFile /full/path/to/.htpasswd Require valid-user Satisfy All Digest Authentication AuthType Digest AuthName "Password Protected" AuthDigestDomain /wp-login.php https://www.askapache.com/wp-login.php AuthUserFile /full/path/to/.htpasswd Require valid-user Satisfy All Require Specific IP This is a way to only allow certain IP addresses to be allowed access. ErrorDocument 401 default ErrorDocument 403 default Order deny,allow Deny from all Allow from 198.101.159.98 localhost Protect Sensitive Files This denies all web access to your wp-config file, error_logs, php.ini, and htaccess/htpasswds. Order deny,allow Deny from all Require SSL This will force SSL, and require the exact hostname or else it will redirect to the SSL version. Useful in a /wp-admin/.htaccess file. SSLOptions +StrictRequire SSLRequireSSL SSLRequire %{HTTP_HOST} eq "www.wordpress.com" ErrorDocument 403 https://www.wordpress.com External Resources Official Apache HTTP Server Tutorial: .htaccess files Official Htaccess Directive Quick Reference Htaccess Tutorial Google PageSpeed for Developers Stupid Htaccess Tricks Advanced Mod_Rewrite See also htaccess for subdirectories Using Permalinks Changing File Permissions UNIX Shell Skills Rewrite API Navigation Menus atachibana — Wed, 02 Mar 2016 12:39:47 +0000 [codex_languages en="Navigation Menus" ja_codex="Navigation Menus" sk_codex="Navigačné menu" zhcn_codex="导航菜单"] Navigation Menu is a theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for introducing customised navigation menus into a theme. In order to incorporate menu support into your theme, you need to add a few code segments to your theme files. Function Reference Register Navigation Menu register_nav_menus() register_nav_menu() unregister_nav_menu() Show Navigation Menu has_nav_menu() wp_nav_menu() Register Menus First, in your theme's functions.php, you need to write a function to register the names of your menus. (This is how they will appear in the Appearance -> Menus admin screen.) As an example, this menu would appear in the "Theme Locations" box as "Header Menu". function register_my_menu() { register_nav_menu('header-menu',__( 'Header Menu' )); } add_action( 'init', 'register_my_menu' ); And this would make two menu options appear, header menu and extra menu - function register_my_menus() { register_nav_menus( array( 'header-menu' => __( 'Header Menu' ), 'extra-menu' => __( 'Extra Menu' ) ) ); } add_action( 'init', 'register_my_menus' ); Display Menus on Theme Once you've done that, your theme will be almost ready. The last preparation step is to tell the theme where you want the menus to show up. You do this in the relevant theme file. So, for example, we might want our header menu to be in header.php. So open up that file in the theme editor, and decide where you want to put your menu. The code to use here is wp_nav_menu which we will need once for each menu location. So, add this code - 'header-menu' ) ); ?> All you need to ensure is that the theme_location points to the name you provided for your menu in the functions.php code above. (Note that it's the header-menu being used here rather than Header Menu without a hyphen. header-menu is the name that the code understands, Header Menu is the human-readable version that you see in the admin page.) To complete the code, you can put your extra menu someplace else. Maybe you want a menu on one of your pages, for example, and you might even want it to be jazzed up a little with a containing DIV of a certain class - wp_nav_menu( array( 'theme_location' => 'extra-menu', 'container_class' => 'my_extra_menu_class' ) ); So you'd put the above into your Page template, and not only would the menu show up wherever you put it, it'd be styled as my_extra_menu_class so that you can work with that in CSS. Menus Panel That's all the background work. To finish, you would simply visit the Appearance -> Menus panel in your site admin. Now, instead of seeing some text suggesting that your theme doesn't natively support menus, you'll see some Theme Location options. You can now use the GUI menu creator on this admin panel to put your menu(s) together. Give them each a name, and then assign a menu to a location with the pull-down options. (You will see your new navigation choices when you Add a New Menu.) External Resources Goodbye, headaches. Hello, menus! - Reasonable tutorial by Justin Tadlock which has more detail around the options available WordPress Navigation Menu Generator Related FTP Clients ankitguptaindia — Wed, 02 Mar 2016 12:39:37 +0000 There are two ways of getting files onto your site, and once there, changing them: By using the file manager provided in your host's control panel. Popular file managers: cPanel, DirectAdmin, Plesk By using an FTP or SFTP client. This guide will show you how to use FileZilla. FTP or "File Transfer Protocol" has been the most widely used transfer protocol for over thirty years. Use SFTP or "Secure File Transfer Protocol" if your host supports it. This transfers your files and your password over a secured connection, and should therefore be used instead of FTP whenever possible. Sometimes you have to contact your host to have SFTP enabled on your account. Why use FileZilla? Because, like WordPress, it is released under the GPL. So, it is not just free, it is staying that way, too. FileZilla is also a stable client that works on all flavors of Windows. Need an FTP or SFTP client for your Mac? Try Cyberduck, which is also free and released under the GPL. The following pages will show you how to setup and use Filezilla: Setting up FileZilla for Your Website How to Upload Files and Folders Setting Permissions Making Hidden Files Visible Want to try a different FTP or SFTP client? Find more on Wikipedia. Post Formats pansotdev — Thu, 03 Mar 2016 22:20:55 +0000 Intro Post Formats is a theme feature introduced with Version 3.1. A Post Format is a piece of meta information that can be used by a theme to customize its presentation of a post. The Post Formats feature provides a standardized list of formats that are available to all themes that support the feature. Themes are not required to support every format on the list. New formats cannot be introduced by themes or even plugins. The standardization of this list provides both compatibility between numerous themes and an avenue for external blogging tools to access this feature in a consistent fashion. In short, with a theme that supports Post Formats, a blogger can change how each post looks by choosing a Post Format from a radio-button list. Using Asides as an example, in the past, a category called Asides was created, and posts were assigned that category, and then displayed differently based on styling rules from post_class() or from in_category('asides'). With Post Formats, the new approach allows a theme to add support for a Post Format (e.g. add_theme_support('post-formats', array('aside'))), and then the post format can be selected in the Publish meta box when saving the post. A function call of get_post_format($post->ID) can be used to determine the format, andpost_class() will also create the "format-asides" class, for pure-css styling. Supported Formats The following Post Formats are available for users to choose from, if the theme enables support for them. Note that while the actual post content entry won't change, the theme can use this user choice to display the post differently based on the format chosen. For example, a theme could leave off the display of the title for a "Status" post. How things are displayed is entirely up to the theme, but here are some general guidelines. aside - Typically styled without a title. Similar to a Facebook note update. gallery - A gallery of images. Post will likely contain a gallery shortcode and will have image attachments. link - A link to another site. Themes may wish to use the first tag in the post content as the external link for that post. An alternative approach could be if the post consists only of a URL, then that will be the URL and the title (post_title) will be the name attached to the anchor for it. image - A single image. The first tag in the post could be considered the image. Alternatively, if the post consists only of a URL, that will be the image URL and the title of the post (post_title) will be the title attribute for the image. quote - A quotation. Probably will contain a blockquote holding the quote content. Alternatively, the quote may be just the content, with the source/author being the title. status - A short status update, similar to a Twitter status update. video - A single video or video playlist. The first tag or object/embed in the post content could be considered the video. Alternatively, if the post consists only of a URL, that will be the video URL. May also contain the video as an attachment to the post, if video support is enabled on the blog (like via a plugin). audio - An audio file or playlist. Could be used for Podcasting. chat - A chat transcript, like so: John: foo Mary: bar John: foo 2 Note: When writing or editing a Post, Standard is used to designate that no Post Format is specified. Also if a format is specified that is invalid then standard (no format) will be used. Function Reference Main Functions set_post_format() get_post_format() has_post_format() Other Functions get_post_format_link() get_post_format_string() Adding Theme Support Themes need to use add_theme_support() in the functions.php file to tell WordPress which post formats to support by passing an array of formats like so: add_theme_support( 'post-formats', array( 'aside', 'gallery' ) ); Note that you must call this before the init hook gets called! A good hook to use is the after_setup_theme hook. Adding Post Type Support Post Types need to use add_post_type_support() in the functions.php file to tell WordPress which post formats to support: // add post-formats to post_type 'page' add_post_type_support( 'page', 'post-formats' ); Next example registers custom post type 'my_custom_post_type', and add Post Formats. // register custom post type 'my_custom_post_type' add_action( 'init', 'create_my_post_type' ); function create_my_post_type() { register_post_type( 'my_custom_post_type', array( 'labels' => array( 'name' => __( 'Products' ) ), 'public' => true ) ); } //add post-formats to post_type 'my_custom_post_type' add_post_type_support( 'my_custom_post_type', 'post-formats' ); Or in the function register_post_type(), add 'post-formats', in 'supports' parameter array. Next example is equivalent to above one. // register custom post type 'my_custom_post_type' with 'supports' parameter add_action( 'init', 'create_my_post_type' ); function create_my_post_type() { register_post_type( 'my_custom_post_type', array( 'labels' => array( 'name' => __( 'Products' ) ), 'public' => true, 'supports' => array('title', 'editor', 'post-formats') ) ); } Using Formats In the theme, make use of get_post_format() to check the format for a post, and change its presentation accordingly. Note that posts with the default format will return a value of FALSE. Or make use of the has_post_format() conditional tag: if ( has_post_format( 'video' )) { echo 'this is the video format'; } An alternate way to use formats is through styling rules. Themes should use the post_class() function in the wrapper code that surrounds the post to add dynamic styling classes. Post formats will cause extra classes to be added in this manner, using the "format-foo" name. For example, one could hide post titles from status format posts by putting this in your theme's stylesheet: .format-status .post-title { display:none; } Suggested Styling Although you can style and design your formats to be displayed any way you see fit, each of the formats lends itself to a certain type of "style", as dictated by modern usage. It is well to keep in mind the intended usage for each format, as this will lend them towards being easily recognized as a specific type of thing visually by readers. For example, the aside, link, and status formats will typically be displayed without title or author information. They are simple, short, and minor. The aside could contain perhaps a paragraph or two, while the link would probably be only a sentence with a link to some URL in it. Both the link and aside might have a link to the single post page (using the_permalink()) and would thus allow comments, but the status format very likely would not have such a link. An image post, on the other hand, would typically just contain a single image, with or without a caption/text to go along with it. An audio/video post would be the same but with audio/video added in. Any of these three could use either plugins or standard Embeds to display their content. Titles and authorship might not be displayed for them either, as the content could be self-explanatory. The quote format is especially well suited to posting a simple quote from a person with no extra information. If you were to put the quote into the post content alone, and put the quoted person's name into the title of the post, then you could style the post so as to display the_content() by itself but restyled into a blockquote format, and use the_title() to display the quoted person's name as the byline. A chat in particular will probably tend towards a monospaced type display, in many cases. With some styling on the .format-chat, you can make it display the content of the post using a monospaced font, perhaps inside a gray background div or similar, thus distinguishing it visually as a chat session. Formats in a Child Theme Child Themes inherit the post formats defined by the parent theme. Calling add_theme_support() for post formats in a child theme must be done at a later priority than that of the parent theme and will override the existing list, not add to it. add_action( 'after_setup_theme', 'childtheme_formats', 11 ); function childtheme_formats(){ add_theme_support( 'post-formats', array( 'aside', 'gallery', 'link' ) ); } Calling remove_theme_support('post-formats') will remove it all together. Backwards Compatibility If your plugin or theme needs to be compatible with earlier versions of WordPress, you need to add terms named post-format-$format to the "post_format" taxonomy. For example, wp_insert_term( 'post-format-aside', 'post_format' ); You must also register the post_format taxonomy with register_taxonomy(). Source File wp-includes/post-formats.php External Resources Styling Chat Transcript with WordPress Custom Post Format by Narga Post Types and Formats and Taxonomies, oh my! by Otto On standardized Post Formats by Andrew Nacin Post Formats vs. Post Types by Mark Jaquith WordPress 3.1 Post Formats Reference by Lisa Sabin-Wilson Smarter Post Formats? by Dougal Campbell WordPress Theme Support Generator Pages Screen atachibana — Tue, 08 Mar 2016 01:08:25 +0000 Pages → Pages The Pages Screen provides the facility to manage all the Pages in a blog. Via this Screen, Pages can be edited, deleted, and viewed. Filtering, and searching, also makes it easy to quickly find Pages matching certain criteria. Several powerful features allow Pages to be edited in bulk (en masse) allowing fields such as Author, Parent, Template, Comments Allowed, Status, and Pings Allowed, to be changed for a whole batch of Pages. In addition, a Quick Edit feature provides an easy method to change a multitude of values, such as Title, Slug, Date, and Author, for a given Page. Back to Administration Screens. Pages Screen Table of Pages A table lists all of your Pages, by row. The Pages are listed with the newest Page first. The table of Pages contains the following columns: [ ] – This checkbox, when clicked (checked), 'selects' that particular Page to be processed by a Bulk Action. Title - This is the Page's Title displayed as a link. Click the Title link to allow this Page to be edited in the Edit Page screen. Next to the Title, if a Page is of a Draft, Pending, or Password Protected nature, text will display showing that. "ID" - This is not a column in the Table, but by hovering the mouse over the Page Title, the Page ID is revealed as part of the URL displayed in the browser status bar (in Firefox the status bar is displayed at the bottom of the screen). A Page's ID number is the unique number WordPress' database uses to identify individual Pages. Author - Displayed in the form of a link, this is the author who wrote the Page. Clicking the author link causes all the Pages authored by that user to be displayed in the Table of Pages (thus allowing a Bulk Action to be applied to all Pages for a given author). comment bubble - A comment bubble is the column heading, and each Page row has comment bubble with the number of comments for that Page. If a Pages has any comments, then the number comments is displayed in a blue bubble. Clicking on a blue comment bubble causes the Comments Screen to be displayed to allow moderation of those comments. Date - The Date column for each Page shows the Date 'Published' for Published Pages and the Date 'Last Modified' for other Pages. Sortable Columns Some column headings, such as the Title, Author, and Date, can be clicked to sort the Table of Pages in ascending or descending order. Hover over the column title, for example Title, to see the up-arrow or down-arrow. Click the heading to change the sort order. Page Navigation Under the Screen Options, the number of Pages displayed per page is determined. If more then one page of Pages is available, two double-arrow boxes to move to the first and last page are provided. Also two single-arrow boxes are displayed to move one page backward or forward. Finally, a box showing the current page number can be used to enter a page to directly display. Screen Options The Screen Options allow you to choose which columns are displayed, or not displayed, in the underlying Table. Clicking on the Screen Options tab shows a list of the columns with a check-box next to each column. Check the box for each column you want displayed in the Table, or uncheck the box to not display that column. In addition, the number of Pages per page can be set. Click the Screen Options tab again to close the Screen Options. Search Above the Table, to the right, is a search box where you can enter a word, or series of words, and click the "Search Pages" button to search and display all the Pages meeting your search words. Filtering Options At the top of this Screen are links such as All, Published, Pending Review, Draft, Private, that when clicked, will cause just the Pages of that type to be displayed in the underlying Table. Below that, and to the right of the Bulk Actions Apply button, are one other filter option: Show all dates This dropdown allows you to select, by date, which Pages are displayed in the Table of Pages. By default, "Show all dates" is selected and all of your Posts are displayed. Filter Clicking this button applies the settings you select in the dropdowns. Using Selection, Actions, and Apply Selection This Screen allows Bulk Actions to be performed on one or more Pages selected in the Table. For Bulk Actions to be performed on multiple Pages at once, those Pages must be first selected via one of these methods: Select one Page at a time - To select a Page, the checkbox to the left of the Page entry must be checked (clicked). It is possible to keep selecting more Pages by checking their respective checkbox. Select all Pages in given Table - All Pages in a given table can be selected by checking the checkbox in the Table's title, or footer bar. Of course, unchecking the header or footer title bar checkbox will cause all entries in that Table to be unchecked (NOT selected). Reverse Selection - A Reverse Selection means checked items become unchecked, and unchecked items become checked. A Reverse Selection is accomplished by holding the Shift key on the keyboard and clicking the header or footer title bar checkbox. Actions Actions describe the process to be performed on particular Pages. There are two styles of Actions that will be referred to as Bulk Actions and Immediate Actions. The following describes these Actions: Bulk Actions - These Actions can be performed on one, or more Pages, at one time, if those Pages have been previously selected. Bulk Actions are available, when appropriate, as choices in the Bulk Actions pulldown box, above the Table. The only Bulk Actions allowed are Edit and Delete. Immediate Actions - Immediate Actions are performed Immediately, on an individual Page. Hovering the mouse cursor over the Page row reveals the Edit, Quick Edit, Delete, and View options under the Title column, in that Page's row. Clicking on a Page Name will also initiate the Edit Action. The available Actions are described below: Edit - This Action can be either an "Immediate Action" or a "Bulk Action". The Immediate Action, initiated by click on the Title or clicking on the Edit option just below the Title, causes the Edit Pages screen to display. Edit is also available as a Bulk Action for the selected Pages, so see the Bulk Edit section for details on the Bulk Editing process. Quick Edit - Quick Edit is an "Immediate Action" that allows a quick in-line edit of certain fields related to a Page. See the Quick Edit section for details on this Action. Delete - This Action deletes the Pages. Delete is available both as a Bulk Action, and an Immediate Action. View - This Action presents the Page as it appears in a single Page view on your blog. View is available only as an Immediate Action. Bulk Edit The Bulk Edit Pages 'screen' is displayed below the Table Of Pages header once, one, or more, Pages have been selected, and the Bulk Action of Edit is Applied. Bulk Edit allows the fields Author, Parent, Template, Comments Allowed, Status, and Pings Allowed, to be changed for all the selected Pages. Cancel - Click Cancel to cancel and abort the Bulk Edit of these Pages. Update - Click Update to save the Bulk Edits made to these Pages. Quick Edit Quick Edit is an Immediate Action performed on one Page by clicking the Quick Edit link under the Page Title in the Table of Pages. Quick Edit is just an in-line edit that allows you to change the following items--Title, Slug, Date, Author, Password or Private page box, Parent, Order, Template, Allow Comments, Allow Pings, Status. Cancel - Click Cancel to cancel and abort the Edit of this Page. Update - Click Update to save the Edits made to this Page. Editing Individual Pages This mode is essentially the same as the Pages Add New Screen so see that Screen for the specific details of writing a Page. The only difference is that the button to save your work is called "Update" instead of "Publish". Apply After one or more Pages are selected, and after a Bulk Action is specified, the Apply button performs the given Action on the selected Pages. Apply - Click the Apply button to execute the Bulk Action, specified in the Actions pulldown, on the selected Pages. Remember, prior to executing Actions, one or more Pages must be selected, as described before. Hardening WordPress atachibana — Sat, 12 Mar 2016 02:48:39 +0000 Security in WordPress is taken very seriously, but as with any other system there are potential security issues that may arise if some basic security precautions aren't taken. This article will go through some common forms of vulnerabilities, and the things you can do to help keep your WordPress installation secure. This article is not the ultimate quick fix to your security concerns. If you have specific security concerns or doubts, you should discuss them with people whom you trust to have sufficient knowledge of computer security and WordPress. What is Security? Fundamentally, security is not about perfectly secure systems. Such a thing might well be impractical, or impossible to find and/or maintain. What security is though is risk reduction, not risk elimination. It's about employing all the appropriate controls available to you, within reason, that allow you to improve your overall posture reducing the odds of making yourself a target, subsequently getting hacked. Website Hosts Often, a good place to start when it comes to website security is your hosting environment. Today, there are a number of options available to you, and while hosts offer security to a certain level, it's important to understand where their responsibility ends and yours begins. Here is a good article explaining the complicated dynamic between web hosts and the security of your website. A secure server protects the privacy, integrity, and availability of the resources under the server administrator's control. Qualities of a trusted web host might include: Readily discusses your security concerns and which security features and processes they offer with their hosting. Provides the most recent stable versions of all server software. Provides reliable methods for backup and recovery. Decide which security you need on your server by determining the software and data that needs to be secured. The rest of this guide will help you with this. Website Applications It's easy to look at web hosts and pass the responsibility of security to them, but there is a tremendous amount of security that lies on the website owner as well. Web hosts are often responsible for the infrastructure on which your website sits, they are not responsible for the application you choose to install. To understand where and why this is important you must understand how websites get hacked, Rarely is it attributed to the infrastructure, and most often attributed to the application itself (i.e., the environment you are responsible for). Security Themes Keep in mind some general ideas while considering security for each aspect of your system: Limiting access Making smart choices that reduce possible entry points available to a malicious person. Containment Your system should be configured to minimize the amount of damage that can be done in the event that it is compromised. Preparation and knowledge Keeping backups and knowing the state of your WordPress installation at regular intervals. Having a plan to backup and recover your installation in the case of catastrophe can help you get back online faster in the case of a problem. Trusted Sources Do not get plugins/themes from untrusted sources. Restrict yourself to the WordPress.org repository or well known companies. Trying to get plugins/themes from the outside may lead to issues. Vulnerabilities on Your Computer Make sure the computers you use are free of spyware, malware, and virus infections. No amount of security in WordPress or on your web server will make the slightest difference if there is a keylogger on your computer. Always keep your operating system and the software on it, especially your web browser, up to date to protect you from security vulnerabilities. If you are browsing untrusted sites, we also recommend using tools like no-script (or disabling javascript/flash/java) in your browser. Vulnerabilities in WordPress Like many modern software packages, WordPress is updated regularly to address new security issues that may arise. Improving software security is always an ongoing concern, and to that end you should always keep up to date with the latest version of WordPress. Older versions of WordPress are not maintained with security updates. Updating WordPress Main article: Updating WordPress. The latest version of WordPress is always available from the main WordPress website at https://wordpress.org. Official releases are not available from other sites -- never download or install WordPress from any website other than https://wordpress.org. Since version 3.7, WordPress has featured automatic updates. Use this functionality to ease the process of keeping up to date. You can also use the WordPress Dashboard to keep informed about updates. Read the entry in the Dashboard or the WordPress Developer Blog to determine what steps you must take to update and remain secure. If a vulnerability is discovered in WordPress and a new version is released to address the issue, the information required to exploit the vulnerability is almost certainly in the public domain. This makes old versions more open to attack, and is one of the primary reasons you should always keep WordPress up to date. If you are an administrator in charge of more than one WordPress installation, consider using Subversion to make management easier. Reporting Security Issues If you think you have found a security flaw in WordPress, you can help by reporting the issue. See the Security FAQ for information on how to report security issues. If you think you have found a bug, report it. See Submitting Bugs for how to do this. You might have uncovered a vulnerability, or a bug that could lead to one. Web Server Vulnerabilities The web server running WordPress, and the software on it, can have vulnerabilities. Therefore, make sure you are running secure, stable versions of your web server and the software on it, or make sure you are using a trusted host that takes care of these things for you. If you're on a shared server (one that hosts other websites besides your own) and a website on the same server is compromised, your website can potentially be compromised too even if you follow everything in this guide. Be sure to ask your web host what security precautions they take. Network Vulnerabilities The network on both ends -- the WordPress server side and the client network side -- should be trusted. That means updating firewall rules on your home router and being careful about what networks you work from. An Internet cafe where you are sending passwords over an unencrypted connection, wireless or otherwise, is not a trusted network. Your web host should be making sure that their network is not compromised by attackers, and you should do the same. Network vulnerabilities can allow passwords and other sensitive information to be intercepted. Passwords Many potential vulnerabilities can be avoided with good security habits. A strong password is an important aspect of this. The goal with your password is to make it hard for other people to guess and hard for a brute force attack to succeed. Many automatic password generators are available that can be used to create secure passwords. WordPress also features a password strength meter which is shown when changing your password in WordPress. Use this when changing your password to ensure its strength is adequate. Things to avoid when choosing a password: Any permutation of your own real name, username, company name, or name of your website. A word from a dictionary, in any language. A short password. Any numeric-only or alphabetic-only password (a mixture of both is best). A strong password is necessary not just to protect your blog content. A hacker who gains access to your administrator account is able to install malicious scripts that can potentially compromise your entire server. In addition to using a strong password, it's a good idea to enable two-step authentication as an additional security measure. FTP When connecting to your server you should use SFTP encryption if your web host provides it. If you are unsure if your web host provides SFTP or not, just ask them. Using SFTP is the same as FTP, except your password and other data is encrypted as it is transmitted between your computer and your website. This means your password is never sent in the clear and cannot be intercepted by an attacker. File Permissions Some neat features of WordPress come from allowing various files to be writable by the web server. However, allowing write access to your files is potentially dangerous, particularly in a shared hosting environment. It is best to lock down your file permissions as much as possible and to loosen those restrictions on the occasions that you need to allow write access, or to create specific folders with less restrictions for the purpose of doing things like uploading files. Here is one possible permission scheme. All files should be owned by your user account, and should be writable by you. Any file that needs write access from WordPress should be writable by the web server, if your hosting set up requires it, that may mean those files need to be group-owned by the user account used by the web server process. / The root WordPress directory: all files should be writable only by your user account, except .htaccess if you want WordPress to automatically generate rewrite rules for you. /wp-admin/ The WordPress administration area: all files should be writable only by your user account. /wp-includes/ The bulk of WordPress application logic: all files should be writable only by your user account. /wp-content/ User-supplied content: intended to be writable by your user account and the web server process. Within /wp-content/ you will find: /wp-content/themes/ Theme files. If you want to use the built-in theme editor, all files need to be writable by the web server process. If you do not want to use the built-in theme editor, all files can be writable only by your user account. /wp-content/plugins/ Plugin files: all files should be writable only by your user account. Other directories that may be present with /wp-content/ should be documented by whichever plugin or theme requires them. Permissions may vary. Changing file permissions If you have shell access to your server, you can change file permissions recursively with the following command: For Directories: find /path/to/your/wordpress/install/ -type d -exec chmod 755 {} \; For Files: find /path/to/your/wordpress/install/ -type f -exec chmod 644 {} \; Regarding Automatic Updates When you tell WordPress to perform an automatic update, all file operations are performed as the user that owns the files, not as the web server's user. All files are set to 0644 and all directories are set to 0755, and writable by only the user and readable by everyone else, including the web server. Database Security If you run multiple blogs on the same server, it is wise to consider keeping them in separate databases each managed by a different user. This is best accomplished when performing the initial WordPress installation. This is a containment strategy: if an intruder successfully cracks one WordPress installation, this makes it that much harder to alter your other blogs. If you administer MySQL yourself, ensure that you understand your MySQL configuration and that unneeded features (such as accepting remote TCP connections) are disabled. See Secure MySQL Database Design for a nice introduction. Restricting Database User Privileges For normal WordPress operations, such as posting blog posts, uploading media files, posting comments, creating new WordPress users and installing WordPress plugins, the MySQL database user only needs data read and data write privileges to the MySQL database; SELECT, INSERT, UPDATE and DELETE. Therefore any other database structure and administration privileges, such as DROP, ALTER and GRANT can be revoked. By revoking such privileges you are also improving the containment policies. Note: Some plugins, themes and major WordPress updates might require to make database structural changes, such as add new tables or change the schema. In such case, before installing the plugin or updating a software, you will need to temporarily allow the database user the required privileges. WARNING: Attempting updates without having these privileges can cause problems when database schema changes occur. Thus, it is NOT recommended to revoke these privileges. If you do feel the need to do this for security reasons, then please make sure that you have a solid backup plan in place first, with regular whole database backups which you have tested are valid and that can be easily restored. A failed database upgrade can usually be solved by restoring the database back to an old version, granting the proper permissions, and then letting WordPress try the database update again. Restoring the database will return it back to that old version and the WordPress administration screens will then detect the old version and allow you to run the necessary SQL commands on it. Most WordPress upgrades do not change the schema, but some do. Only major point upgrades (3.7 to 3.8, for example) will alter the schema. Minor upgrades (3.8 to 3.8.1) will generally not. Nevertheless, keep a regular backup. Securing wp-admin Adding server-side password protection (such as BasicAuth) to /wp-admin/ adds a second layer of protection around your blog's admin area, the login screen, and your files. This forces an attacker or bot to attack this second layer of protection instead of your actual admin files. Many WordPress attacks are carried out autonomously by malicious software bots. Simply securing the wp-admin/ directory might also break some WordPress functionality, such as the AJAX handler at wp-admin/admin-ajax.php. See the Resources section for more documentation on how to password protect your wp-admin/ directory properly. The most common attacks against a WordPress blog usually fall into two categories. Sending specially-crafted HTTP requests to your server with specific exploit payloads for specific vulnerabilities. These include old/outdated plugins and software. Attempting to gain access to your blog by using "brute-force" password guessing. The ultimate implementation of this "second layer" password protection is to require an HTTPS SSL encrypted connection for administration, so that all communication and sensitive data is encrypted. See Administration Over SSL. Securing wp-includes A second layer of protection can be added where scripts are generally not intended to be accessed by any user. One way to do that is to block those scripts using mod_rewrite in the .htaccess file. Note: to ensure the code below is not overwritten by WordPress, place it outside the # BEGIN WordPress and # END WordPress tags in the .htaccess file. WordPress can overwrite anything between these tags. # Block the include-only files. RewriteEngine On RewriteBase / RewriteRule ^wp-admin/includes/ - [F,L] RewriteRule !^wp-includes/ - [S=3] RewriteRule ^wp-includes/[^/]+\.php$ - [F,L] RewriteRule ^wp-includes/js/tinymce/langs/.+\.php - [F,L] RewriteRule ^wp-includes/theme-compat/ - [F,L] # BEGIN WordPress Note that this won't work well on Multisite, as RewriteRule ^wp-includes/[^/]+\.php$ - [F,L] would prevent the ms-files.php file from generating images. Omitting that line will allow the code to work, but offers less security. Securing wp-config.php You can move the wp-config.php file to the directory above your WordPress install. This means for a site installed in the root of your webspace, you can store wp-config.php outside the web-root folder. Note: Some people assert that moving wp-config.php has minimal security benefits and, if not done carefully, may actually introduce serious vulnerabilities. Others disagree. Note that wp-config.php can be stored ONE directory level above the WordPress (where wp-includes resides) installation. Also, make sure that only you (and the web server) can read this file (it generally means a 400 or 440 permission). If you use a server with .htaccess, you can put this in that file (at the very top) to deny access to anyone surfing for it: order allow,deny deny from all Disable File Editing The WordPress Dashboard by default allows administrators to edit PHP files, such as plugin and theme files. This is often the first tool an attacker will use if able to login, since it allows code execution. WordPress has a constant to disable editing from Dashboard. Placing this line in wp-config.php is equivalent to removing the 'edit_themes', 'edit_plugins' and 'edit_files' capabilities of all users: define('DISALLOW_FILE_EDIT', true); This will not prevent an attacker from uploading malicious files to your site, but might stop some attacks. Plugins First of all, make sure your plugins are always updated. Also, if you are not using a specific plugin, delete it from the system. Firewall There are many plugins and services that can act as a firewall for your website. Some of them work by modifying your .htaccess file and restricting some access at the Apache level, before it is processed by WordPress. A good example is iThemes Security or All in One WP Security. Some firewall plugins act at the WordPress level, like WordFence and Shield, and try to filter attacks as WordPress is loading, but before it is fully processed. Besides plugins, you can also install a WAF (web firewall) at your web server to filter content before it is processed by WordPress. The most popular open source WAF is ModSecurity. A website firewall can also be added as intermediary between the traffic from the internet and your hosting server. These services all function as reverse proxies, in which they accept the initial requests and reroute them to your server, stripping it of all malicious requests. They accomplish this by modifying your DNS records, via an A record or full DNS swap, allowing all traffic to pass through the new network first. This causes all traffic to be filtered by the firewall before reaching your site. A few companies offer such service, like CloudFlare, Sucuri and Incapsula. Additionally, these third parties service providers function as Content Distribution Network (CDNs) by default, introducing performance optimization and global reach. Plugins that need write access If a plugin wants write access to your WordPress files and directories, please read the code to make sure it is legit or check with someone you trust. Possible places to check are the Support Forums and IRC Channel. Code execution plugins As we said, part of the goal of hardening WordPress is containing the damage done if there is a successful attack. Plugins which allow arbitrary PHP or other code to execute from entries in a database effectively magnify the possibility of damage in the event of a successful attack. A way to avoid using such a plugin is to use custom page templates that call the function. Part of the security this affords is active only when you disallow file editing within WordPress. Security through obscurity Security through obscurity is generally an unsound primary strategy. However, there are areas in WordPress where obscuring information might help with security: Rename the administrative account: When creating an administrative account, avoid easily guessed terms such as admin or webmaster as usernames because they are typically subject to attacks first. On an existing WordPress install you may rename the existing account in the MySQL command-line client with a command like UPDATE wp_users SET user_login = 'newuser' WHERE user_login = 'admin';, or by using a MySQL frontend like phpMyAdmin. Change the table_prefix: Many published WordPress-specific SQL-injection attacks make the assumption that the table_prefix is wp_, the default. Changing this can block at least some SQL injection attacks. Data Backups Back up your data regularly, including your MySQL databases. See the main article: Backing Up Your Database. Data integrity is critical for trusted backups. Encrypting the backup, keeping an independent record of MD5 hashes for each backup file, and/or placing backups on read-only media increases your confidence that your data has not been tampered with. A sound backup strategy could include keeping a set of regularly-timed snapshots of your entire WordPress installation (including WordPress core files and your database) in a trusted location. Imagine a site that makes weekly snapshots. Such a strategy means that if a site is compromised on May 1st but the compromise is not detected until May 12th, the site owner will have pre-compromise backups that can help in rebuilding the site and possibly even post-compromise backups which will aid in determining how the site was compromised. Logging Logs are your best friend when it comes to understanding what is happening with your website, especially if you're trying to perform forensics. Contrary to popular beliefs, logs allow you to see what was done and by who and when. Unfortunately the logs will not tell you who, username, logged in, but it will allow you to identify the IP and time and more importantly, the actions the attacker might have taken. You will be able to see any of these attacks via the logs - Cross Site Scripting (XSS), Remote File Inclusion (RFI), Local File Inclusion (LFI) and Directory Traversal attempts. You will also be able to see brute force attempts. There are various examples and tutorials available to help guide you through the process of parsing and analyzing your raw logs. If you get more comfortable with your logs you'll be able to see things like, when the theme and plugin editors are being used, when someone updates your widgets and when posts and pages are added. All key elements when doing forensic work on your web server. The are a few WordPress Security plugins that assist you with this as well, like the Sucuri Auditing tool or the Audit Trail plugin. There are two key open-source solutions you'll want on your web server from a security perspective, this is a layered approach to security. OSSEC can run on any NIX distribution and will also run on Windows. When configured correctly its very powerful. The idea is correlate and aggregate all the logs. You have to be sure to configure it to capture all access_logs and error_logs and if you have multiple websites on the server account for that. You'll also want to be sure to filter out the noise. By default you'll see a lot of noise and you'll want to configure it to be really effective. Monitoring Sometimes prevention is not enough and you may still be hacked. That's why intrusion detection/monitoring is very important. It will allow you to react faster, find out what happened and recover your site. Monitoring your logs If you are on a dedicated or virtual private server, in which you have the luxury of root access, you have the ability easily configure things so that you can see what's going on. OSSEC easily facilitates this and here is a little write up that might help you out OSSEC for Website Security - Part I. Monitoring your files for changes When an attack happens, it always leave traces. Either on the logs or on the file system (new files, modified files, etc). If you are using OSSEC for example, it will monitor your files and alert you when they change. Goals The goals of file system tracking include: Monitor changed and added files Log changes and additions Ability to revert granular changes Automated alerts General approaches Administrators can monitor file system via general technologies such as: System utilities Revision control OS/kernel level monitoring Specific tools Options for file system monitoring include: diff - build clean test copy of your site and compare against production Git - source code management inotify and incron - OS kernel level file monitoring service that can run commands on filesystem events Watcher - Python inotify library OSSEC - Open Source Host-based Intrusion Detection System that performs log analysis, file integrity checking, policy monitoring, rootkit detection, real-time alerting and active response. Considerations When configuring a file based monitoring strategy, there are many considerations, including the following. Run the monitoring script/service as root This would make it hard for attackers to disable or modify your file system monitoring solution. Disable monitoring during scheduled maintenance/upgrades This would prevent unnecessary notifications when you are performing regular maintenance on the site. Monitor only executable filetypes It may be reasonably safe to monitor only executable file types, such as .php files, etc.. Filtering out non-executable files may reduce unnecessary log entries and alerts. Use strict file system permissions Read about securing file permissions and ownership. In general, avoid allowing execute and write permissions to the extent possible. Monitoring your web server externally If the attacker tries to deface your site or add malware, you can also detect these changes by using a web-based integrity monitor solution. This comes in many forms today, use your favorite search engine and look for Web Malware Detection and Remediation and you'll likely get a long list of service providers. Resources How to Improve WordPress Security (Infographic) Security Plugins WordPress Security Cutting Through the BS e-Book: Locking Down WordPress wpsecure.net has a few guides on how to lock down WordPress. A Beginners Guide to Hardening WordPress Brad Williams: Lock it Up (Video) 21 Ways to Secure Your WordPress Site Official docs on how to password protect directories with an .htaccess file Simple tutorial on how to password protect the WordPress admin area and fix the 404 error AskApache Password Protection plugin for wp-admin/ and other directories Caution: Installing the AskApache Password Protection plugin may lock you out of your WordPress Admin panel. See the comments under the author's plugin home page to read other users' experiences with this plugin. See Also Security FAQ FAQ - My site was hacked Brute Force Attacks WordPress Security Whitepaper Site Design and Layout atachibana — Sat, 12 Mar 2016 02:59:36 +0000 [codex_languages en="Blog Design and Layout" es_codex="Blog Design and Layout" id_codex="Desain dan Tata Letak Blog" ja_codex="Blog Design and Layout" ko_codex="블로그 디자인과 레이아웃" pl_codex="Układ i Projekt Witryny" ru_codex="Дизайн и раскладка блога" th_codex="Blog Design and Layout" zhcn_codex="博客的设计和布局" zhtw_codex="部落格的設計和佈局"] Basics of WordPress Theme Design First Steps With WordPress Using WordPress Themes Theme Development FAQ Themes, Layout and Design WordPress Lessons Lessons: Designing Your WordPress Site Lessons: Customizing Template Files WordPress Site Reviews Theme Design Adding Navigation Menu support to a theme Developing a Colour Scheme Designing Headers CSS Horizontal Menus Dynamic Menu Highlighting Good Navigation Links Next and Previous Links Styling for Print Styling for Mobile Designing Your Post Meta Data Section Separating Categories in your Post Meta Data Section Using Custom Fields with Post-Meta Customizing the Read More Customizing the Login Form Adding Administration Menus Formatting Date and Time Styling Lists with CSS Designing Headings Playing With Fonts Using Images Wrapping Text Around Images Fun Character Entities Smilies How to Use Gravatars in WordPress Adding Asides Protecting Your Email Address from Harvesters Theme Development Theme Review Theme Functions File Explained WordPress and CSS CSS - Overview of CSS within WordPress, and list of resources related to CSS and WordPress Know Your Sources - External resources on HTML, PHP, and CSS in general CSS Coding Standards - Best practices for coding CSS CSS Troubleshooting - Examining and debugging CSS Right-to-Left Language Support - Working with RTL text using CSS Themes, Templates, and Customization Using Themes - Best starting point for learning about Themes Templates - Comprehensive list of theme and template resources Plugins - Comprehensive list of plugin resources WordPress Plugins and Customization - Other resources related to customizing WordPress Menu User Guide normalize — Tue, 22 Mar 2016 02:39:12 +0000 [codex_languages en="WordPress_Menu_User_Guide" ja_codex="WordPress_Menu_User_Guide"] This guide to the WordPress Menu system covers the basic tasks a user may carry out when using the built-in menu editor. Defining a Menu You must define a menu before you can add items to it. Login to the WordPress Dashboard. From the 'Appearance' menu on the left-hand side of the Dashboard, select the 'Menus' option to bring up the Menu Editor. Select Create a new menu at the top of the page Enter a name for your new menu in the Menu Name box Click the Create Menu button. Your new custom menu has now been defined. Adding Items to a Menu You can add different link types into your menu, these are split between panes left of the menu you\'re currently editing. Locate the pane entitled Pages. Within this pane, select the View All link to bring up a list of all the currently published Pages on your site. Select the Pages that you want to add by clicking the checkbox next to each Page\'s title. Click the Add to Menu button located at the bottom of this pane to add your selection(s) to the menu that you created in the previous step. Click the Save Menu button once you\'ve added all the menu items you want. Your custom menu has now been saved. Note The Screen Options allow you to choose which items you can use to add to a menu. Certain items, like Tags are hidden by default. Deleting a Menu Item Locate the menu item that you want to remove in the menu editor window Click on the arrow icon in the top right-hand corner of the menu item/box to expand it. Click on the Remove link. The menu item/box will be immediately removed. Click the Save Menu button to save your changes. Customizing Menu Items Navigation Label This field specifies the title of the item on your custom menu. This is what your visitors will see when they visit your site/blog. Original A link to the original source of the menu item (e.g. a link to view the post or page). Following items are hidden by default. Use Screen Options to show the required fields. Title Attribute This field specifies the Alternative ('Alt') text for the menu item. This text will be displayed when a user\'s mouse hovers over a menu item. Link Target Select "Same window or tab" or "New window or tab" from the pulldown. CSS Classes Optional CSS Classes for this menu item Link Relationship (XFN) Allows for the generation of XFN attributes automatically so you can show how you are related to the authors/owners of site to which you are linking. Description Description for this link. The description will be displayed in the menu if the current theme supports it. Click on the arrow in the top right-hand corner of the menu item to expand it. Enter the values for the required fields that you want to assign to the item. Click the Save Menu button to save your changes. Creating Multi-level Menus When planning the structure of your menu, it helps to think of each menu item as a heading in a formal report document. In a formal report, main section headings (Level 1 headings) are the nearest to the left of the page; sub-section headings (Level 2 headings) are indented slightly further to the right; any other subordinate headings (Level 3, 4, etc) within the same section are indented even further to the right. The WordPress menu editor allows you to create multi-level menus using a simple 'drag and drop' interface. Drag menu items up or down to change their order of appearance in the menu. Drag menu items left or right in order to create sub-levels within your menu. To make one menu item a subordinate of another, you need to position the 'child' underneath its 'parent' and then drag it slightly to the right. Position the mouse over the 'child' menu item. Whilst holding the left mouse button, drag it to the right. Release the mouse button. Repeat these steps for each sub-menu item. Click the Save Menu button in the Menu Editor to save your changes. Adding Your Menu to Your Site If your current theme supports custom menus, you will be able to add your new menu to one of the Theme Locations. Scroll to the bottom of the menu editor window. In the section titled Theme locations, click the check box for the location where you want your menu to appear. Click Save menu once you\'ve made your selection. If your current theme does not support custom menus, you will need to add your new menu via the Custom Menu widget in the Appearance Widgets Screen. Congratulations! Your new custom menu has now been added to your site. Pages greensteph — Tue, 15 Mar 2016 13:44:35 +0000 In WordPress, you can put content on your site as either a "post" or a "page". When you're writing a regular blog entry, you write a post. Posts, in a default setup, appear in reverse chronological order on your blog's home page. In contrast, pages are for non-hierarchical content: pages like "About" or "Contact" would be common examples. Pages live outside of the normal blog chronology, and are often used to present timeless information about yourself or your site -- information that is always relevant. You can use Pages to organize and manage the structure of your website content. In addition to the common "About" and "Contact" pages, other examples include "Copyright", "Disclosure", "Legal Information", "Reprint Permissions", "Company Information" or "Accessibility Statement". In general, pages are very similar to posts in that they both have titles and content. WordPress Theme template files maintain a consistent look throughout your site. Pages, though, have several key distinctions that make them different from posts. What Pages Are Pages are for content that isn't specifically time-dependent, or which isn't "blog content". Pages can be organized into pages and subpages. Pages can use different page templates, including template files, Template Tags and other PHP code. More sophisticated themes may provide a wider range of adjustments or display options for individual pages. It's quite possible to make a website using WordPress which only contains pages. What Pages Are Not Pages are not posts, so they don't appear in the time-structured views within a blog section of a website. Pages cannot be associated with Categories, but they can be assigned Tags. However, Tags on Pages are not included in lists displayed via the "tag" permalink. The organizational structure for Pages comes from hierarchical interrelationship, not from a system of categorization. (e.g. Tags or Categories.) Pages are not files. They are stored in your database, just like posts. Although you can put Template Tags and PHP code into a Page Template file, you cannot put these into the Page or Post content without using a WordPress Plugin. But be careful: integrating PHP code directly into page or post content may introduce a security problem, or an unexpected error on your website. Pages are not included in your site's "feeds". (e.g. RSS or Atom.) Pages and Posts can be interpreted differently by site visitors and by search engines. Commonly, search engines place more relevance to time-dependent site content - posts - because a newer post on a topic may be more relevant than a static page. A specific page (or a specific post) can be set as a static front page. Websites which are set up in this way usually have a secondary page defined on which the latest blog posts are displayed. Creating Pages To create a new Page, log in to your WordPress installation with sufficient admin privileges to create new pages. Select the Pages > Add New option to begin writing a new Page. Organizing Your Pages Just as you can have subcategories within your Categories, you can also have subpages within your Pages, creating a hierarchy of pages. For example, a WordPress site for a travel agent may feature an individual Page for each continent and country to which the agency can make travel arrangements. Under the Page titled "Africa" would be subpages for Cameroon, Lesotho, Swaziland and Togo. Another parent Page "South America" would feature subpages of Argentina, Brazil and Chile. The structure of the pages on the site would then look like this. Africa Cameroon Lesotho Swaziland Togo South America Argentina Brazil Chile To create a subpage Go to Administration > Pages > Add New screen. In the right menu, click the "Page Parent" drop-down menu. The drop-down menu contains a list of all the Pages already created for your site. Select the appropriate parent Page from the drop-down menu to make the current Page a child Page. Add content to the subpage. Click Publish when ready. When your Pages are listed, the Child Page will be nested under the Parent Page. The Permalinks of your Pages will also reflect this Page hierarchy. In the above example, the Permalink for the Cameroon Page would be: http://example.com/africa/cameroon/ Changing the URL of Your Pages To change the URL part (also referred to as "slug") containing the name of your Page, use the "Edit" button under the Page title on the Edit screen of the particular Page, accessible from Pages tab of WordPress Administration Screen. Creating a List of Pages WordPress is able to automatically generate a list of Pages on your site within the sidebar or footer, for example, using a Template Tag called wp_list_pages(). See the wp_list_pages page for information on how to customize how WordPress displays the list of Pages on your site. There are also WordPress Plugins that will help you display a list of Pages within in Posts and in other areas of your WordPress Theme. Page Templates Individual Pages can be set to use a specific custom Page Template (a WordPress Theme PHP template file, e.g., my-custom-page.php) you create within your Theme. See Custom Page Templates for instructions on how to create a custom template file for a Page. This new Page Template will then override the default page.php Page Template included with your Theme. The Dynamic Nature of WordPress Pages A web page can be static or dynamic. Static pages, such as a regular HTML page that you might create with Dreamweaver, are those which have been created once and do not have to be regenerated every time a person visits the page. In contrast, dynamic pages, such as those you create with WordPress, do need to be regenerated every time they are viewed; code for what to generate on the page has been specified by the author, but not the actual page itself. These use extensive PHP code which is evaluated each time the page is visited, and the content is thus generated upon each new visit. Almost everything in WordPress is generated dynamically, including Pages. Everything published in WordPress (Posts, Pages, Comments, Blogrolls, Categories, etc...) is stored in the MySQL database. When the site is accessed, the database information is used by your WordPress Templates from your current Theme to generate the web page being requested. An example of a static page might be an HTML document (without any PHP code). The problem with purely static pages is that they are difficult to maintain. Changes you make to your WordPress settings, Themes and Templates will not be propagated to pages coded only in HTML. The Page feature of WordPress was developed to alleviate this problem. By using Pages, you no longer have to update your static pages every time you change the style of your site. If written properly, your dynamic Pages will update along with the rest of your blog. Despite the dynamic nature of Pages, many people refer to them as being static. They are actually called "pseudo-static" web pages. In other words, a Page contains static information but is generated dynamically. Thus, either "static," "dynamic," or "pseudo-static" may be validly used to describe the nature of the WordPress Page feature. First steps with WordPress greensteph — Tue, 15 Mar 2016 14:11:29 +0000 I have done the 5 minute installation, now what? You've just completed the 5 Minute Installation of WordPress or one-click install from your web host. So what is your next step? Let's take a step-by-step tour through your WordPress site and see how the different functions work and how to make your new site your own. During the first part of this tutorial, please don't change anything within the program unless it is part of the tutorial. After following these steps, you'll soon be changing everything. Log In Begin by logging into the “administration area” or the back end of your website. Visit your site's login page by placing “wp-admin” after your domain name (e.g. http://example.com/wp-admin). Some themes provide a “login” link or form on the front end as well. Now log into WordPress using the username and password you created in the 5 minute install. Start at the Top After logging in you are on the main Administration Screen called the Dashboard. This is where the organization of your site begins. At the top of the screen is the area called the “toolbar”. Click on your site name, it's a link and it will take you to a view of your new WordPress site. Like it? Don't like it? Doesn't matter, just look at it. This is where you are going to be spending a lot of time! Test Drive Your WordPress Site Take time to look at the site before you get into the changing of things and figuring out how all of this works; it's important to see how the WordPress Twenty Seventeen theme is laid out and how it works. Consider this the test drive before you start adding on all the special features. The layout you are looking at is defined by a WordPress Theme. It is the appearance of your website, styling the look of the site and the framing of the content. The WordPress Twenty Seventeen theme features a “header” at the top with the title and tagline for your site. Below this is your Menu, if you have one. Along the side you will see some titles and links. This is the Sidebar. The different items inside a Sidebar are called Widgets. The main middle section of the page is the content area. Scroll down the page and notice the bar at the end of the page. This is called the “footer.” It says “Proudly powered by WordPress.” Back to the sidebar, you will see different sections with information. Among these you may find a list of Recent Posts, Recent Comments, Archives, Categories, links to the Administration Screens, Log Out, and RSS feeds. This is part of the menu or navigation Screen that people will use to move around your site, visiting posts from different categories or time periods. Take a Quick Trip Around For now you only have one post. It is residing within a page that is laid out as your home page or the front page. If you click on the title of the post, it will take you to the specific page for that post. The first page or home page of your site features the most recent posts on your site. Each post title will link to the actual page of the post. Some Theme designers design their single post pages to look different from the home page. In the single post, pay attention to the layout and notice what is different about the design elements. Is the header different? Smaller, larger, or a different color? Is there a sidebar? All of these changes are created from a few files called template files. You can learn more about how they work in Stepping Into Templates. For now, however, let's get on with how the rest of WordPress works. Test Drive the WordPress Administration Screens Now that you have an idea of how your site looks and what the different layout sections are called, it's time to test drive the WordPress Administration. This is like familiarizing yourself with the backend of your new website. In fact, the first page you see after logging in is called the Dashboard, a collection of information and data about the activities and actions on your WordPress site. The Dashboard features a list of the most recent activity you've accomplished on your site and it helps to keep you up to date on new and interesting bits of information from the many WordPress resources. On the left side of the screen is the main navigation menu detailing each of the administrative functions you can perform. Move your mouse down the list and the sub-menus will “fly out” for you to move your mouse to and click. Once you choose a “parent” navigation section, it will open up to reveal the options within that section. The various menu items are as follows: Dashboard Posts Media Pages Comments Appearance Plugins Users Tools Settings Let's start with the User screen Click on the Users tab. The screen will change and you will see the Screen called All Users that shows a list of all your users; from here you can add or change existing users and authors accounts. In the navigation menu, click on the Your Profile menu choice. This is where you will enter information about you, the author and administrator of the site. Fill in the information and click Update Profile when done. Now, let's look at some other powerful features of the WordPress Admin. Changing the Look The Appearance, Themes Screen allows you to change the look of your site using different Themes. Themes are presentation styles that completely change the look of your site. Designed by developers and users, there are hundreds of themes available for you to choose from. In your Appearance Screen, you will see a list of currently installed themes, including the WordPress Twenty Seventeen theme. To quickly change the theme, simply click on the Activate button under one of the themes listed, then click on your site name in the top toolbar to see how it looks. Wow, you have another look. It's that easy. Go back to Appearance > Theme and click the Activate button under the WordPress Twenty Seventeen theme to bring the design back to what you had. To see it again, click your site name in the toolbar, and there it is. Creating a post Back in the Administration Screen, take a look at the Posts Screen. You can use the tabs under the Posts Menu to write and manage your posts. Let's start by making your first test post in the Add New tab. Simply fill in the blanks, one by one, in the post beginning with the title and then write a little test message in the post window. This is just for a test, so you can write anything you want. When you are done, click the Publish button that is to the right of the post entry window and it is done. There's more exciting work ahead! Now that you've gotten a feel for writing posts, you can view your posts by clicking your site name in the toolbar at top of the screen. Comments Part of the fun of WordPress is the ability to have viewers leave comments on your site. It creates a dynamic interchange between you and the viewer. Do you want comments on your posts? Comments on posts come in a variety of forms, from pats on the back (Good job! Like the post!) to extensive conversations and commentary about the posts. Or maybe you are seeking comments that add to the information you've posted. Responding to comments and moderating them can also take up a lot of time. If they are critical to your site, then include them and consider how you want them presented. You can make a few comments yourself on the post you created. Take a look at how they are laid out and consider how you might want them to look to fit into the design and layout of your site. When you have reached your decision about how you want to handle comments, take time to read through the article on comments and WordPress discussion options to help you set those features. Preventing Spam There is more to think about when it comes to having comments on your site. Unfortunately we live in a world where spam is a fact of life. It is recommended that you begin battling the comment spammers with the helpful article, Introduction to Dealing with Comment Spam. Create Categories Posts are usually stored in Categories and/or Tags so you can keep related topics together. Right now you only have one category, but that will soon want more. In the Posts > Categories tab, in the Add New Category area, fill in the information about your category. Continue to add your parent categories, going down the list. Hold off on entering subcategories until all the main categories are entered. NOTE: You can add any new category at any time, but make a note of the fact that categories can be sorted in WordPress in two ways: by name (alphabetically) or by ID number. As you enter the categories, they are assigned an ID number. It is difficult to change this, so if you don't want your categories sorted alphabetically, enter them in the order you want to see them presented on the screen. Setting Up Your Site Before you get to the graphic look of your site, let's do a little more administration to your site to set it up. You may want to install plugins to supercharge your website, and don't forget to activate the Akismet WordPress Plugin that is available with all WordPress sites to help protect it from comment spam. When you have the parent categories entered, enter your subcategories. In the pull down menu for Parent Category, you can select the parent to the subcategory you are adding. When you view your categories in the Manage > Categories Screen, you will see the categories listed like this: Computer Tips Windows Linux Mac Internet News Web Page Design Web Standards WordPress Plugins Themes Put Posts in Categories Let's put some of your test posts into categories so you can see how this works. From the Posts > Category Screen, click on the tab for All Posts. You should see the test posts you entered here. When you hover your mouse over each post title, under the title, you should see the Edit | Quick Edit | Trash | View links. Click on Edit to edit one of the posts. On the right side of the Edit Post screen you will now see your Categories. Choose one of them by clicking in the box next to it. Then in the Publish module above, click the Update button. Repeat this for your other test posts, putting each one in a different category. Now view your page by clicking on your site name in the toolbar at the top of your Administration Screen. Do you see the categories listed in the sidebar now? Great. If you are missing a category, that usually means that there are no posts in it. This is the default function of WordPress, so not to worry. When you add a post to the “missing” category, it will appear on your web pages. Click on one of the categories and you will be taken to a page for just that category. You should see the posts that went into that category. This is a generated Category page. Now, click on the Archives for the month showing. Now you are visiting a generated page of your posts listed in chronological order for this month - well, specifically for today only. Two methods of finding the same information. What Is Next You've now done all the basics for your new WordPress website. You know how to write a post, create a category, and how to view your site's information by category and archive. You can start the customization process, and when you are done, don't forget to delete your test posts! Then start writing some wonderful information to share with your new-found public! Using WordPress Themes There are hundreds of WordPress Themes to choose from. All do basically the same thing but graphically present the information in a myriad of ways. Choose a few that look interesting to you, and meet your audience's needs and your desires, and then test drive them following the test drive instructions above. Click through the whole site, the categories and archives as well as the individual posts to see how the Theme handles each one. The look may be nice on the front page, but if it handles things in a way you don't like on the single post, then you will have to dig into the code and make changes. Not ready for that, try another theme. WordPress Theme Directory Using Theme Creating your own Theme If you are familiar with CSS, HTML, and even PHP and MySQL, consider either customizing the Theme to your own needs, or creating your own Theme. WordPress Theme Developer Handbook Using WordPress Plugins Plugin Screen WordPress Plugins are also known as add-ons or extensions. They are software scripts that add functions and events to your website. They cover the gamut from up-to-date weather reports to simple organization of your posts and categories. Plugins are designed by volunteer contributors and enthusiasts who like challenges and problem solving. They are usually fairly simple to install through the WordPress Admin Plugin Screen, just follow the instructions provided by the plugin author. Remember, these are free and non-essential. If you have any problems with plugins, contact the plugin author's website or plugin source first, then search the Internet for help with that specific plugin, and if you haven't found a solution, then visit the WordPress forums for more help. WordPress Plugin Directory Managing Plugins Creating your own Plugin If you are familiar with PHP, HTML, and maybe even MySQL, you may be able to customize WordPress to work the way you want by creating your own Plugin. WordPress Plugin Developer Handbook Above and Beyond the Basics The exciting thing about WordPress is that there are few limits. Thousands of people are using WordPress for blogging and for running their websites. For example, look at some of the entries under the WordPress.org Theme Showcase. All have a different look and different functions on their sites. What you do from here is up to you, but here are a few places to take that first step beyond the basics: WordPress Features Working with WordPress WordPress Semantics Using Pages Troubleshooting Using Permalinks Getting More Help Using the Support Forums Designing Headers greensteph — Tue, 15 Mar 2016 15:03:53 +0000 [codex_languages en="Designing Headers" es_codex="Diseñando Headers" ja_codex="Designing Headers" ko_codex="Designing Headers" ru_codex="Дизайн Заголовка" zhcn_codex="头部标题设计"] They say you can not judge a book by its cover, and yet every day people do. They pick up a book, look at the cover, and then are moved to either put it down, turn it over, or open it up just because of how the cover looks. Websites are also judged by their covers and the first impression often comes from the header. The header of your site is typically the first thing people see. From this masthead or header art across the top of your page, people make sweeping judgements about what they are about to see and read. The same people who say you can not judge a book by its cover, also say that you only have 30 seconds to make a good impression. In the world of the Internet where the next web page is a click away, you have much less than that. We are going to take you inside the architecture of a WordPress header and offer tips on how to customize it to become your own book cover, enticing people into your site with a good first impression. Then we will offer some tips from some experts on what makes a good website header. The WordPress Header By default, the WordPress header is a simple piece of code. You do not have to get into the code to change the header that comes with whatever WordPress Theme you choose. You set the blog or website title and description in the Administration > Settings > General panel, and WordPress does the rest. In its simplest form, the WordPress Classic Theme features the header code like this in the wp-content/themes/classic/header.php template file: The header is set in an h1 HTML tag and features one template tag used with two different options or parameters. You can learn more about these parameters in the documentation for bloginfo(). Basically, the first one displays the URL of the website in a link, and the second one displays the name of the blog or website as set in the Administration > Settings > General panel. When the user moves the mouse over the header title, the header can be clicked to return back to the main or front page of the site as set in the Administration > Settings > General panel. The WordPress Default Theme features an image in the background and presents the header like this in wp-content/themes/default/header.php: Award Winning Themes The Theme Headers showcased in this article are some of the award winners of the 2005 WordPress Themes Contest by Alex King. The header of the Kubrick Theme Again, the template tag featuring the name of the blog or website is in a link, but this shows another usage similar to the URL request above. It gets the same information, just in a different way. It also adds the description of the site from the Administration > Settings > General panel. Basically, these two header examples do the same thing in different ways. They provide information in the header, with the potential for an image, and make the header title clickable to help navigation on the site. It is just a matter of how much information you want in your header, and how that information is displayed. Using the first example from the Classic Theme, an image can still be used in the background, set within the style sheet in the h1 selector, but the second one gives more control to the use of an image in the header by giving it its own division. How these look are totally controlled by the style sheet. Styling the Header As listed in the two above examples, the styles for the header are contained within the h1, header, headerimg, and description CSS selectors. These are all found within the style.css, though may be found in the styles in the header.php of the Theme you are using. You will have to check both places. In the Classic Theme, the CSS for the header are found in one selector, the #header. #header { background: #90a090; border-bottom: double 3px #aba; border-left: solid 1px #9a9; border-right: solid 1px #565; border-top: solid 1px #9a9; font: italic normal 230% 'Times New Roman', Times, serif; letter-spacing: 0.2em; margin: 0; padding: 15px 10px 15px 60px; } The background color is set to a green shade and there is a border all the way around the header which changes colors creating a recessed, shadow effect. The Times font is set with a size of 230% with a wider than normal letter spacing. The padding on the left side indents the text in from the left. All of these can be easily changed, giving the border a thicker width and making it all the same color, changing the background color, the font size and style, the letter spacing, and more by modifying the information in each style attribute. The same is true of the Default WordPress Theme header, except there are more styles to think about and they are found within the header.php's "head" tag and the style.css, though once you have your styles set, you can move the information into your style sheet. The styles that control the header's look is found within the h1, header, headerimg, and description CSS selectors. Just like the Classic Theme, find these references and make your modifications there to change the look. Changing the header image of the Default WordPress Theme has been simplified with the introduction of a utility called Kubrickr. It simply asks you to supply a new image file name for the header and then switches it for you, so you do not have to dig into the code. If all you want to change is the header image, this is an extremely useful and easy tool. If you do want to get your hands into the code, dig into your header styles and make the changes. Below is a simple tutorial on changing just the header image manually. Changing the Header Image There are many different header images and header art available for you to use to change the image in the header. The styles for the header image for the Default or Kubrick WordPress Theme, and any Theme based upon that Theme, are more complicated to change than those for the Classic Theme. The styles are found within the styles in the header.php "head" section, as well as in the styles.css. To change only the header image reference, open the header.php template file and look for the styles like this: #header { background: url("/images/wc_header.jpg") no-repeat bottom center; } #headerimg { margin: 7px 9px 0; height: 192px; width: 740px; } NOTE: The use of the bloginfo tag only works when the style is used within the head of the template file. WordPress template tags will not work in the style sheet (style.css). To move this style to the style sheet, change the template tag to the actual address (URL) of the header image graphic. To change the image file, replace the "kubrickheader.jpg" with the name of the new graphic image you have uploaded to your site to replace it. If it is in a different directory, change that by replacing the bloginfo() tag with the specific address of the graphic's location. If you are using an image that is the same size, then simply replace the image. If it is a different size, fill in the height and width of the image in the next section called #headerimg. If you do not know, and are using Windows, view the folder in which the image resides on your computer in Thumbnail view mode. Click View > Thumbnail from the Windows Explorer menu. In Thumbnail view mode, find your image and hold the mouse over it. A small balloon tip will pop up listing the dimensions. Use that information in the styles. Otherwise, just right click on the image file and choose Properties and it should give you the file size and dimensions. Save the template file and upload it and the image to your website and take a look. Some changes may need to be made to fine-tune the placement and look. With the header image in place, it is time to tackle the rest of the header. Open your style.css style sheet file and look for the following: h1 header headerimg description Your Theme may or may not have all of these, but the Default Theme has all of them in different places within the style sheet. All or some of these may need to have the attributes changed to change the look of your header. If you change the size of the header image or header art, be sure and change the other structural CSS selectors like content and sidebar to accommodate the change in the header size. Header Image Specifications A header image that fits within the Default WordPress Theme is about 192 x 740 pixels. If you are replacing the header within any WordPress Theme, check the size of the header image and then find a replacement that matches that size. If you choose a header image that is smaller or wider or taller than the replacement, you may have to modify the other structural elements of the web page to allow for the change in size of the header. If you are modifying the entire site's Theme, the width of the overall page or content area needs to be taken into consideration for the header image's size. The two most common screen sizes are 1024x768 and 800x600 pixels. Yet, wide screen monitors are gaining ground and web designers now need to prepare for screen widths of 1280x1024 and 1600x1200. If you set your website to "float," positioned in the middle of the browser window with space on either side, then you can set your header width to whatever you want. If you are designing a Theme with a flexible or "elastic" screen width, then the width of your header becomes important. If you are using a header image that can be repeated, and you are using elastic widths, you can set the styles within the header to repeat to fill the space: #header { background: url("/images/kubrickheader.jpg") repeat-x top left; } This sets the header image to repeat horizontally beginning from the top left corner and going across. You can adjust these to whatever background position your header design and layout needs. Header Art A new term growing in the web design field is header art. These are header images that are usually handmade using combinations of color, shapes, symbols, images, and text. They can take some time and labor to create. While there are some free header art sites, some sites sell their handmade header art. Although a photograph may be unique in its own way and convey the needed visual style, handmade header artwork is easier to match to other web page colors and is usually more aesthetically pleasing because of its distinctive nature. Choosing pre-made header art has some benefits. The artists have already done the work and all you have to do is choose the design that best matches your website. And the graphic is ready to use, already sized and saved as a small file size. Digital Westex's WordPress Header Art features a wide range of header art sized and ready for free download specifically for WordPress. Header Art Copyrights The best header art to use, if you do not want to generate your own, is any that bear the Creative Commons License that specifically allows its public use. Read the individual license for the image's use to make sure that you have permission to use the header art on your site. Usually you must attribute the author, share alike and not use it for commercial purposes. If in doubt, always ask permission from the author before use. As header art is made and licensed "as is" by the designer/artist, some header art cannot be modified without the artist's permission. Check the website copyrights and licenses and ask if you are in doubt and wish to modify the artwork. Designing Your Own Header Art You can also design your own header art. Any graphic design software program will work. Popular ones include Adobe Photoshop, Adobe Elements, JASC PaintShop Pro, The Gimp and Macromedia Fireworks. The graphic design software should have the ability to resize and control the resolution and type of the image when saved. The size of your header art should be the size of the header container you're going to put it in. You can use your own photographs, artwork, fonts, and any combination of images to create your header art. When done, save it "for the web" as a jpg, gif, or .png file. For an explanation on which to use read Sitepoint's GIF-JPG-PNG What's the Difference article. These file types will compress the image's resolution, reducing the file's size. In general, avoid file sizes larger than 50K as larger sizes tend to slow a site access times. Hiding the Header Text Many Themes and Theme designers want to feature their header with a picture only, no text. Some will put the text in the graphic image, therefore not requiring the actual use of the text. One option is to remove the template tags that generate the title and description. The other option is to leave it in, but hide it. To hide the header text while leaving it in the code, do not change anything in your template files. Only change the CSS. Add display:none to the CSS selectors you do not want to appear. For example, to hide the text within the h1 selector: h1 {display:none; font-size: 230%; color: blue;....... It is still there, but the browser has been commanded to not show it in any way. The container literally is "not there." It might be hidden, but some web page screen readers and search engines will still find the information. If you are serious about making your site be accessible, some newer text readers access the style sheet and do not read the elements marked display:none. There are two popular methods for working around this. One is to use the display:none as outlined above, but also include an aural style sheet that changes that selector to display:block, "turning the visibility" back on. The other method is to position the content literally "off the page" by a negative indent. Here is an example: h1 { font-size: 0; text-indent: -1000px; } This technique moves the entire h1 tag and its contents physically off the web page. The screen reader will still "read" the text because it is there, but it will not display on the page. Extensive testing has proven so far that this technique works across most browsers and with all screen readers. For more information on either technique and aural style sheets: What do Screen Readers really say? (Accessibility and display:none) Testing Screen Readers and display:none Facts and Opinion About Fahrner Image Replacement Hiding Text But Not From Screen Readers W3's Aural Style Sheets About Web Design's Aural Style Sheets ACSS: Aural Style Sheets Richinstyles Guide to Aural Style Sheets Making the Whole Header Clickable To make the entire header, graphic and all, clickable, you must put the header graphic inside of a link. There are two ways to do this. You can put the graphic directly into the WordPress Theme manually, or you can use the stylesheet to define the link size area to encompass the header art area. To make the header art clickable by embedding it into the header, in the wp-content/themes/classic/header.php template file of your WordPress Theme, change the following: to this code snippet: " /> " title=""> You can style the h1 heading to overlap or sit below, or not even be visible in the header. To make the overall area of the header clickable, the header must have a width area set for the h1 anchor HTML tag to make the clickable area cover the header image in the background. The styles are set in the stylesheet. The HTML and WordPress Template Tags look like this, the same as above: The CSS would then be styled something like this to enlarge the clickable link area and hide the header text (optional), customized to your own design needs. #header h1 a { width: 400px; height: 100px; display: block; background: url(images/headerimage.gif) no-repeat top left; } #header h1 a span { display: none; } Another option is to add a script to make the header section clickable, which may not work for all browsers. This is showcased in the Default WordPress Theme (Kubrick) with its clickable header: Open the wp-content/themes/default/header.php template file. Change from to: If you want both text areas of the header to be clickable and not the entire header image, use the following to make the header art and the blog title and description clickable. Rotating Header Images There are several scripts available that will allow you to rotate images within the header, sidebar, or on any template file. We will examine the use of one of these, the Random Image Rotator. Save the script to a separate folder in which you have the header images you wish to rotate in your header. For this example, call it rotate.php. To use this as a background image that changes or rotates with every load of the web page: #header { background: url("/images/headerimgs/rotate.php") no-repeat bottom center; } To actually put this in your header, or elsewhere on your site, add an image link like this within the header division: Image rotating scripts include: Photomatt's Random Image Rotator Adding Navigation to Your Header Headers are another area where you can add navigation elements to your website. Typically these are horizontal menus at the top or bottom of your header. To add these, create a new division within the header to style your header navigation elements. This can be as simple as displaying your categories across the top of the header using one of the List Categories template tags. Let us look at one example using the list_cats() tag. In this example, the list_cats() template tag is set to sort the list of categories by ID in an unordered list ( ) without dates or post counts, does not hide empty categories, uses category "description" for the title in the links, does not show the children of the parent categories, and excludes categories 1 and 33. It sits in its own "category" division. Notice that a link to the "home" page or front page has been included manually at the start of the list. list_cats() has been deprecated. check wp_list_categories() as replacement. HOME To style this list, the #categorylist in the style.css might be: #categorylist {font-size:12px; font-style:normal; text-transform:uppercase; } #categorylist ul {list-style-type: none; list-style-image:none; margin:0; padding-bottom: 20px; } #categorylist li { display: inline; padding: 0px 5px;} #categorylist a:link, #category a:visited {color:blue} #categorylist a:hover {color:red} It might look like this: WORDPRESS COMPUTERS INTERNET NEWS You can also add your Pages, archives, and other links within your header navigation. For more information on navigation menus: Good Navigation Links Dynamic Menu Highlighting Creating Horizontal Menus Styling Lists with CSS wp_list_cats() list_cats() Header Tips Here are some tips and information to help you choose and customize your WordPress site's header. Pay attention to text placement and color. The colors and placement of the text within a header can add or subtract to your presentation. Here are some tips. If you use white text, make sure there is a background color in the header and/or headerimg to showcase the white text again if for some reason the image does not appear on the screen or the user has "show images" turned off. This will allow your white text to still be visible. If the image has a main feature or element, position the text so it does not cover the main subject of the image. If the text is hard to read against a busy area of the graphic, position the text to a less busy area of the header image. Make sure the color of the text is easily seen by your visitors and does not clash with the header art colors. Fluorescent orange text on a lime green background is painful. Be aware that some color differences and patterns in your header art may make the text letters in your overlaid text "disappear." The same applies if you embed the text in your header art or header image. Have a purpose and point. A good header reflects the content of the site. The rest of the site has to meet expectations and live up to the header, so the header must reflect the content, purpose and intention of the site. It should invite visitors to remain. A good header is like the cover of a book or magazine. It should encourage people to stay and have a look around, read and look more, and find something of value. It is the teaser, the lead that grabs their attention and says "there is something worth exploring here." It should blend in with the overall look. Bold and dramatic headers lend themselves to boldly designed sites, whereas soft and pastel colored sites lend themselves to gentler graphic headers. A site dedicated to punk rock and grunge should have a header look punky and grungy. It is up to you, but think consistency. Headers do not need to have pictures. Not all headers must have pictures and graphics. Sometimes the words are more important, whether they are against a wash of color or a white background. Cluttered headers are still cluttered. Avoid cramming ads, navigation, text, scrolling news feeds, and the kitchen sink into your header. Simple is always better. Maintain accessibility standards in your header. We mentioned hiding the header text, and there is more you can do to make sure your header meets accessibility standards. Use the h1 tag so screen readers will recognize it as a header. Use titles and alt descriptions in links and images used in the template file (not in the style sheet as background images). Headers can be any height, but remember content sells. The average header is less than 200 pixels high, but headers range in height from very thin to a half page. Remember that the main reason people visit your site is its content, and the more they have to scroll down past your header to get to the content, the less interested they tend to be. Help lead them to the content with your header. Think "Site Identity." A header is part of the site's identity or "brand" and people like to know they are on the same site when they click a link to another page within that site. Consider your header or header art as your site's "brand identity". Header Resources and Information Header Images Many WordPress Themes come with header image graphics you can use because they are released for free use under the GPL - General Public License. Or you can use one of the many resources available for free on the Internet, or design your own. Here are a few resources for header images: Digital Westex Image Gallery (See "Header Art" category) Free Header Images by 100pixel Image * After - Free Stock Image Library Stock.xchng - Free Stock Image Library StockUp - Free Stock Image Search Engine About.com's Webclipart Welcome, Headers, and Logos Low-poly header and background images Header Information Designing Headings Kubrickr - Changes Default Theme Header Images Experiments with CSS headings, background images, and more Using Real Headers Image Format Cheat Sheet Yale Manual: Headers and Footers - The best measure of home page efficiency FAQ Troubleshooting atachibana — Sun, 27 Mar 2016 05:19:01 +0000 Back to FAQ Why can't I see my posts? All I see is Sorry, no posts match your criteria? Clearing your browser cache and cookies may resolve this problem. Also, check your search.php and index.php template files for errors. See also: I Make Changes and Nothing Happens How do I find more help? There are various resources that will help you find more help with WordPress, in addition to these FAQ. Troubleshooting Finding WordPress Help Using the Support Forums Resources and Technical Articles about WordPress Installation Problems Where can I find help with the CSS problems I'm having? The following are articles that will help you troubleshoot and solve many of your CSS problems: Blog Design and Layout Finding Your CSS Styles CSS Fixing Browser Bugs CSS Troubleshooting WordPress CSS Information and Resources Why do I get an error message about Sending Referrers? If you got this message when trying to save a post, consider checking Administration > Settings > General and make sure both your WordPress address (URI) and the Blog address (URI) do not use 'www'. For example, instead of http://www.sample.com use http://sample.com in those fields. This information originally reported via http://wordpress.org/support/topic/72235 See also: Enable Sending Referrers How do I empty a database table? See also: Emptying a Database Table How do I fix the following error SQL/DB Error errcode 13 Can't create/write to file? Problem: The MySQL variable tmpdir is set to a directory that cannot be written to when using PHP to access MySQL. To verify this, enter MySQL at the command line and type show variables; You'll get a long list and one of them will read: tmpdir = /somedir/ (whatever your setting is.) Solution: Alter the tmpdir variable to point to a writable directory. Steps: Find the my.cnf file. On *nix systems this is usually in /etc/. On Windows system, Find the my.ini. Once found, open this in a simple text editor and find the [mysqld] section. Under this section, find the tmpdir line. If this line is commented (has a # at the start), delete the # and edit the line so that it reads: tmpdir = /writable/dir where /writable/dir is a directory to which you can write. Some use /tmp, or you might also try /var/tmp or /usr/tmp. On Windows, use C:/Windows/tmp. Save the file. Shutdown MySQL by typing mysqlshutdown -u -p shutdown. Start MySQL by going to the MySQL directory and typing ./bin/safe_mysqld &. Usually the MySQL directory is in /usr/local or sometimes in /usr/ on Linux systems. If none of this make sense and you have someone to administrate your system for you, show the above to them and they should be able to figure it out. How do I solve the Headers already sent warning problem? Description: You get a warning message on your browser that says: Warning: Cannot modify header information - headers already sent by (output started at Reason and Solution: It is usually because there are spaces, new lines, or other stuff before an opening tag, typically in wp-config.php. This could be true about some other file too, so please check the error message, as it will list the specific file name where the error occurred (see "Interpreting the Error Message" below). Replacing the faulty file with one from your most recent backup or one from a fresh WordPress download is your best bet, but if neither of those are an option, please follow the steps below. Just because you cannot see anything does not mean that PHP sees the same. Download the file mentioned in the error message via FTP or the file manager provided in your host's control panel. Open that file in a plain text editor (NOT MS Word or similar. Notepad or BBEdit are fine). Check that the very first characters are with no blank lines or spaces after it. Before saving, or use the Save as dialog, ensure the file encoding is not UTF-8 BOM but plain UTF-8 or any without the BOM suffix. To be sure about the end of the file, do this: Place the cursor between the ? and > Now press the DELETE key on your computer Note to MAC users: The "DELETE" key on a PC deletes characters to the right of the cursor. That is the key noted here. Keep that key pressed For at least 15 seconds Now type > and save without pressing any other key at all. If you press another key, you will bring the problem back. DO NOT PUT CODE IN UNNECESSARY CODE BLOCKS, PUT THEM IN A SINGLE PHP BLOCK. Wrong: Correct: Upload the file back to your server after editing and saving the file. Note: Also check the encoding of the file. If the file is encoded as UTF-8 with BOM, the BOM is seen as a character which starts the output. Interpreting the Error Message: If the error message states: Warning: Cannot modify header information - headers already sent by (output started at /path/blog/wp-config.php:34) in /path/blog/wp-login.php on line 42, then the problem is at line #34 of wp-config.php, not line #42 of wp-login.php. In this scenario, line #42 of wp-login.php is the victim. It is being affected by the excess whitespace at line #34 of wp-config.php. If the error message states: Warning: Cannot modify header information - headers already sent by (output started at /path/wp-admin/admin-header.php:8) in /path/wp-admin/post.php on line 569, then the problem is at line #8 of admin-header.php, not line #569 of post.php. In this scenario, line #569 of post.php is the victim. It is being affected by the excess whitespace at line #8 of admin-header.php. Other issues that might cause that error: In case you've used the function: wp_redirect() or tried to use a header redirect after the header (or any content at all was sent) that error message will pop. Instead use javascript redirection if needed. Why doesn't my "Publish" or "Save Draft" button work? To resolve this and similar issues, disable your plugins one at a time until you find the source of the issue. Generally, this will be due to two or more plugins trying to use the same resources (for example, JQuery or other Java-based tools). In addition, it could be that there is a problem with your browser. A common resolution is to empty the browser's cache. Please consult the documentation for your preferred browser to learn how to do this. Why can't I see the visual rich editor or Quicktag buttons when using Apple's Safari browser? Update your Safari browser. Early versions of Safari are not supported. E-mailed passwords are not being received Description: When users try to register with your blog or change their passwords by entering their username and/or email, WordPress indicates that their password has been emailed to them, but it is never received. Reason and Solutions: WordPress uses the standard PHP mail() function, which uses sendmail. No account information is needed. This is not generally a problem if you are using a hosting service, but if you are using your own box and do not have an SMTP server, the mail will never send. If you are using a *NIX box, you should have either postfix or sendmail on your machine; you will just need to set them up (search the Internet for how-to's). If you do not want to go through setting up a complete mail server on your *NIX box you may find ssmtp useful -- it provides "A secure, effective and simple way of getting mail off a system to your mail hub". On a Windows machine, try a sendmail emulator like Glob SendMail. More help can be found on this thread of the WordPress Support Forums: http://wordpress.org/support/topic.php?id=24981 For a plugin based alternative, you could try Configure SMTP: "Configure SMTP mailing in WordPress, including support for sending e-mail via SSL/TLS (such as GMail)." Windows Host Server Specific: Check your "Relay" settings on the SMTP Virtual Server. Grant access to 127.0.0.1 . Then in your php.ini file, set the SMTP setting to the same IP address. Also set smtp_port to 25. Ensure Proper Return Address is Used: By default, the WordPress mailer fills in the From: field with wordpress@yourdomain.com and the From: name as WordPress. This is fine if this is a valid e-mail address. For example, if your real e-mail is wordpress@yourdomain.com, your host should pass the email on for delivery. It will probably send your mail as long as yourdomain.com is setup to send and receive mail, even if wordpress is not a valid mail box. But if you set you real email as the From: address and it's something like wpgod@gmail.com, the mail may not send because gmail.com is not a domain handled by the mail server. Treated as Spam: Your email message may have been routed to a spam folder or even worse, simply discarded as malicious. There are a couple measures you can use to convince recipient's mail servers that your message is legitimate and should be delivered as addressed. SPF: (Sender Policy Framework) This is the most common anti-spam measure used. If you are on a hosted system, there is a good chance your host has set this up for the mail server you are using. Have Wordpress email you and check the message headers for evidence that the message passed the SPF check. You can get a message sent by following the Forgot Password link on the login page. To keep your old password, do not follow the link in the message. If your system email failed the SPF check, you can set up the credentials if you have access to your DNS records and your mail server's domain belongs to you. Check the return path of the email your system sent. If the mail server listed there has your domain name, you can set up SPF credentials. There are several how-tos on the Internet. DKIM: (Domain Key Identified Mail) This system is also used. You can use both SPF and DKIM in the same message. Again, just as with SPF, you can check if your receiving mailserver verified your host's domain key by examining the mail header. There is a fair chance no signature key was provided, indicating your host chose to not use this protocol. Also as with SPF, if you can edit your DNS records and the mail server belongs to your domain, you can set up DKIM credentials yourself. Some how-tos exist if you search the Internet. To get WordPress to send the proper DKIM keys, hook the 'phpmailer_init' action. You are passed the $phpmailer object. Set the necessary properties and return the object. See the class source code for more information. It's on wp-includes/class-phpmailer.php . I used the Quicktag in a post so why doesn't it work? In some Themes, such as the WordPress Classic Theme, you may see the work properly on your main page, but other Themes, such as the WordPress default Theme, may only show the page break when viewing the posts individually. It may be necessary to change your Theme's template page.php or index.php file to make this feature work according to your wishes. You'll need to add the following: MySQL Error 28 It could be because: you are out of space on /tmp (wherever tmpdir is), or, you have too many files in /tmp (even if there is lots of free space) This is a MySQL error and has nothing to do with WordPress directly; you should contact your host about it. Some users have reported that running a "repair table" command in phpMyAdmin fixed the problem. Why are the Quote Marks escaped or not escaped? If you write plugins or make advanced custom templates, you may eventually find yourself dealing with data in the database. WordPress usually manages this data for you in such a way that it is immediately usable. There are circumstances though (especially if you are dealing directly with the database without using WordPress) where you will experience weirdness. For example, quote marks cannot be stored directly in the MySQL database. MySQL uses quote marks in its SQL language. When a quote mark is used, for example, in a post, when the post is saved to the database, every quote mark gets escaped. That means a backslash character is prepended, which signifies that the next character should be taken as part of the input, and not as part of the SQL command. For example, if you are adding the following in your post: ...an article about "Happiness" is at Happiness if you would like to read it... Is actually imported into the database looking like this: ...an article about \"Happiness\" is at Happiness if you would like to read it... When pulling data out of the database, the backslashes may not always be automatically removed. If this becomes an issue, you can use the stripslashes() PHP function on the text. Why do I get a blank page when I submit a comment? Description: When anyone tries to comment on a post, the window goes blank and the comment doesn't appear to have been recognised by WordPress. Reason and Solution: The Theme that you are using is missing a critical part of the comment form so WordPress doesn't know which post the comment refers to. You need to check the comment.php in your Theme and ensure that the following code appears within the form. Relevant discussion threads: http://wordpress.org/support/topic/38683 How to deactivate all plugins when not able to access the administrative menus? Sometimes it may be necessary to deactivate all plugins, but you can't access the administrative menus to do so. One of two methods are available to deactivate all plugins. Use phpMyAdmin to deactivate all plugins. In the table wp_options, under the option_name column (field) find the active_plugins row Change the option_value field to: a:0:{} Or reset your plugins folder via FTP or the file manager provided in your host's control panel. This method preserves plugin options but requires plugins be manually reactivated. Via FTP or your host's file manager, navigate to the wp-contents folder (directory) Via FTP or your host's file manager, rename the folder "plugins" to "plugins.hold" Login to your WordPress administration plugins page (/wp-admin/plugins.php) - this will disable any plugin that is "missing". Via FTP or your host's file manager, rename "plugins.hold" back to "plugins" How to clear the "Briefly unavailable for scheduled maintenance" message after doing automatic upgrade? As part of the automatic upgrade WordPress places a file named .maintenance in the blog base folder (folder that contains the wp-admin folder). If that file exists, then vistors will see the message Briefly unavailable for scheduled maintenance. Check back in a minute. To stop that message from being displayed to vistors, just delete the .maintenance file. The automatic upgrade should be executed again, just in case it failed. Note the core automatic upgrade feature was added with Version 2.7. How to fix 404 error when using Pretty Permalinks? If an error 404 occurs when using the Pretty Permalink choices such as Day and Name in Administration > Settings > Settings_Permalinks_Screen it could be a result of the mod_rewrite module not being activated/installed. The solution is to activate mod_rewrite for the Apache web-server. Check the apache\conf\httpd.conf file for the line # LoadModule rewrite_module modules/mod_rewrite.so and delete the # in front of the line. Then stop Apache and start it again. Note: you may have to ask your host to activate mod_rewrite. See also: Using Permalinks Relevant discussion thread: http://wordpress.org/support/topic/234726 Why isn't the admin user listed as an author when editing posts? Not sure why this problem happens, but here's a couple of things to try one of these two solutions. This usually fixes the problem: Create new admin user (e.g. newadmin) with Administrator Role Login as 'newadmin' Degrade the old 'admin' user to Role of Subscriber and Save Promote the old 'admin' back to Administrator Role and Save Login as the old 'admin' If that doesn't work, try: Create a new admin user (e.g. newadmin) with Administrator Role Login as 'newadmin' Delete the old 'admin' user and assign any posts to 'newadmin' Create 'admin' user with Administrator Role Login as 'admin' Delete 'newadmin' user and assign posts to 'admin' Why is the wrong author name displayed for a post on a blog? This problem is usually solved by the same solution as is presented in the question right before this one: Why isn't the admin user listed as an author when editing posts? An update was just released, so why does my blog not recognize the update is available? When an update is released, notification of that release is displayed at the top administration screens saying WordPress x.x.x is available! Please update now. Not every blog will see that message at the same time. Your blog is programmed to check for updates every 12 hours, but the timing of that check is purely random. So if your blog just checked for updates minutes before an update was released, you won't see the update message until your blog checks for updates 12 hours later. If you want your blog to check right now for updates, you can delete the update_core option name record in your wp_options table. Note that plugins and themes each have their own check and update cycle, controlled by the records update_plugins and update_themes, in wp_options. Relevant discussion thread: http://wordpress.org/support/topic/242485 Why did I lose custom changes to the WordPress Default Theme during the last automatic upgrade? A core upgrade copies all the new files from the distribution over the old ones, so if you changed existing files in the WordPress default theme (e.g. wp-content/themes/twentysixteen/style.css), those changes got overwritten with the new version of that file. Please note, a core upgrade goes through a list of "old files", as defined in wp-admin/includes/update-core.php, and deletes those files. Any files not on the list, and not in the distribution, are preserved. Remember, that before upgrades, whether automatic or manual, both the WordPress Files and database should be backed-up as explained in WordPress Backups. A better way to modify the default theme is by using a child theme. It's a little more work to set up, but worth the effort because your customizations will be safe when the main theme is updated. See also: WordPress Backups Child Themes How do you repair a MySQL database table? Every once in a while, it may be necessary to repair one or more MySQL database tables. According to the How to Repair MyISAM Tables at dev.mysql.com there are a number of reasons to repair a table including errors such as "tbl_name.frm is locked against change", "Can't find file tbl_name.MYI (Errcode: nnn)", "Unexpected end of file", "Record file is crashed", or "Got error nnn from table handler". Here are the steps to repair a table in a MySQL database using phpMyAdmin: Login to hosting account. Login to phpMyAdmin. Choose the affected database. If you only have one database, it should choose it by default so you don't need to do anything. In the main panel, you should see a list of your database tables. Check the boxes by the tables that need repair. At the bottom of the window just below the list of tables, there is a drop down menu. Choose "Repair Table" '''Remember, that it is advisable to have a current backup of your database at all times. See also: WordPress Backups Back to FAQ Administration Screens atachibana — Sun, 27 Mar 2016 10:05:48 +0000 The Administration Screen provides access to the control features of your WordPress installation. Common Layout Each Administration Screen is presented in sections, the toolbar (and header), the main navigation, the work area, and the footer. Toolbar has links to various administration functions, and is displayed at the top of each Administration Screen. Many Toolbar items expand (flyout) when hovered over to display more information. Main Navigation menu details each of the administrative functions you can perform. At the bottom of that section is a Collapse menu button that shrinks the menu into a set of icons, or to expands to list them by major function. Within each major function, such as Posts, the sub-menu expands (fly-out) when hovered over, and expands fully if an item clicked. In the work area, the specific information relating to a particular navigation choice, such as adding a new post, is presented and collected. Footer, at the bottom of each Administration Screen in light shading, are links to WordPress, thanking you for using it, and the version of WordPress you have installed is shown. Toolbar - Keeping It All Together The Toolbar contains links to information About WordPress, as well as quick-links to create new posts, pages and links, add new plugins and users, review comments, and alerts to available updates to plugins and themes on your site. Tips: To hide the Toolbar, go to Administration Screens > Users > Your Profile, and turn off "Show Toolbar when viewing site" of Toolbar option. About WordPress At the left-most side of the Toolbar is a WordPress logo. Place, or hover, the mouse cursor over the logo to see to About WordPress, WordPress.org, Documentation, Support Forums, and Feedback. The top link on that menu is for the 'About WordPress' page, which contains tabs for What's New, Credits, Freedoms and Privacy. What's New screen describes many of the new features WordPress current version. Credits screen provides some details about the various individuals who contribute to the WordPress code base. Freedoms screen describes your rights as a user of WordPress as open source software. Privacy screen describes handling of privacy information in WordPress. Visit Site link In the Toolbar, to the right of the WordPress logo, your site name is displayed as a link. Hover over the site name to see the View Site link to visit the main page of your site. Howdy, User On the far right of the Toolbar is "Howdy, User", with an image of your Gravatar. When hovered over, this expands to link you to your Profile Screen as well as a Log Out link. When you log in to your blog, WordPress stores a so called cookie in your web browser. This cookie allows WordPress to remember who you are; if you leave your blog's site for a while but come back to it later, WordPress will see the cookie and not require you to log in again. Tips: If you have a WordPress cookie set in your web browser, anyone using your computer can access the Administration Screens of your blog. If you don't want this to happen (perhaps you are using a public computer or a computer which other people use), you can click this Log Out link, and WordPress will delete the cookie from your web browser. Screen Options Screen Options, displayed as a hanging tab under the toolbar, allow the user to decide what fields or modules are presented in the work area for a given Administration Screen. Each Screen may have a different set of Screen Options. Click on the Screen Options tab to expand the options available for a particular Screen, check (or uncheck) the desired options, then click the Screen Options hanging tab to collapse the Screen Options. Help Contextual Help, displayed as a hanging tab under the toolbar, displays one or more Help items that are related to the Screen that is displayed in the work area. Click on the Help tab to expand the Help available for a particular Screen, then click the Help hanging tab to collapse the Help display. Dashboard - Information Central The Dashboard tells you about recent activity both at your site and in the WordPress community, and update information. Dashboard Welcome - Shows links for some of the most common tasks when setting up a new site. At A Glance - Displays a summary of the content on your site and identifies which theme and version of WordPress you are using. Activity - Shows the upcoming scheduled posts, recently published posts, and the most recent comments on your posts and allows you to moderate them. Quick Draft - Allows you to create a new post and save it as a draft. Also displays links to the 5 most recent draft posts you've started. WordPress Events and News — Latest local events and news from the official WordPress project. Updates You can update to the latest version of WordPress, as well as update your themes, plugins, and translations from the WordPress.org repositories. If an update is available, you᾿ll see a notification appear in the Toolbar and navigation menu. Keeping your site updated is important for security. It also makes the internet a safer place for you and your readers. Updating WordPress Click on the Update Now button when you are notified that a new version is available. Tips: In most cases, WordPress will automatically apply maintenance and security updates in the background for you. Updating Themes, Plugins and Translations To update individual themes, plugins or Translations, use the checkboxes to make your selection, then click on the appropriate Update button. To update all of your themes, plugins or Translations at once, you can check the box at the top of the section to select all before clicking the update button. Posts - Make some content Posts are the principal element (or content) of a blog. The Posts are the writings, compositions or discussions. All Posts Via the All Posts Screen you can select the Post or Posts you wish to edit, delete, or view. Multiple Posts can be selected for deletion and for editing. A powerful bulk edit feature allows you to change certain fields for a group of Posts. A handy in-line edit tool, called Quick Edit, allows you to update many fields for an individual Post. Various search and filtering options allow you to find the Posts you want to edit or delete. Add New Post Posts Add New Screen is where you write new Posts. While you are writing those Posts, you can also create new Categories and new Tags. In addition, any Media (pictures, video, recordings, files) can be uploaded and inserted into the Posts. Categories Every Post in WordPress is filed under one or more Categories. Categories allow the classification of your Posts into groups and subgroups, thereby aiding viewers in the navigation and use of your site. Each Category may be assigned to a Category Parent so that you may set up a hierarchy within the category structure. Using automobiles as an example, a hierarchy might be Car->Ford->Mustang. In creating categories, recognize that each category name must be unique, regardless of hierarchy. When using the WordPress default theme, all the Categories to which a given post belongs are displayed under that post. When someone viewing your blog clicks on one of those Category links, a archive page with all the Posts belonging to that Category will be displayed. The Posts Categories Screen allows you to add, edit, and delete Categories, as well as organize your categories hierarchically. Multiple Categories can be selected for deletion. A search option allows you to find the Categories you want to edit or delete. Also remember Categories can be added in the Posts Add New Screen. Tags Tags are the keywords you might assign to each post. Not to be confused with Categories, Tags have no hierarchy, meaning there's no relationship from one Tag to another. But like Categories, Tags provide another means to aid your readers in accessing information on your blog. When using the WordPress default theme, Tags are displayed under each Post those Tags are assigned. Someone viewing your blog can click on one of those Tag links, and an archive page with all the Posts belonging to that Tag will be displayed. The Posts Tags Screen allows you to add, change, or delete Tags. Multiple Tags can be selected for deletion. A search option allows you to find the Tags you want to edit or delete. Also remember Tags can be added in the Posts Add New Screen. Media - Add pictures and movies to your posts Media is the images, video, recordings, and files, you upload and use in your blog. Media is typically uploaded and inserted into the content when writing a Post or Page. Note that the Uploading Files section in the Settings Media Screen describes the location and structure of the upload directory. Library The Media Library Screen allows you add, edit, delete or view Media previously uploaded to your blog. Multiple Media objects can be selected for deletion. Search and filtering ability is also provided to allow you to find the desired Media. Add New Media The Media Add New Screen allows you to upload new media to later use with posts and pages. A Flash Uploader is provided and the ability to use a Browser Uploader is supplied if the Flash Uploader does not work. Edit Media The Edit Media page allows you to edit the information (title, caption, alt text, etc.) of media files uploaded to your site. This page does not appear as a link in the main Dashboard navigation, but is reached by clicking on the Edit link in the Media Library Screen that appears when you hover over each item, or when uploading media for the first time on th Media Add New Screen once your upload has completed. Pages - Your Static Content A Page is another tool to add content to a WordPress site and is often used to present "static" information about the site; Pages are typically "timeless" in nature. A good example of a Page is the information contained in "About" or "Contact" Pages. A Page should not be confused with the time-oriented objects called Posts, nor should a WordPress Page be confused with the word "page" referring to any web page or HTML document on the Web. Because Pages live outside of the normal blog chronology, and as such, are not displayed with the rest of your Posts, but are displayed individually. All Pages The All Pages Screen provides the necessary tools to edit, delete or view existing Pages. On this Screen you can select the Page to edit, delete or view. Multiple Pages can be selected for deletion and for editing. A powerful bulk edit tool allows certain fields to be edited for a whole group of Pages. A handy in-line edit tool, called Quick Edit, allows you to update many fields for an individual Page. Various search and filtering options allow you to find the Pages you want to edit or delete. Add New Page The Add New Page Screen allows you to create new Pages. Also see the Pages article for an in depth discussion. Comments - Reader Feedback Comments are a feature of blogs which allow readers to respond to Posts. In the Comments Screen you can edit and delete as well as mark comments as spam. Comments that are awaiting moderation can be marked as approved or previously approved comments can be unapproved. Multiple comments can be selected and approved, marked as spam, unapproved, or deleted. A section at the top of the Comments Screen displays the number of comments awaiting moderation and the number of approved comments. A search box allows you to find specific comments Appearance - Change the Look of your Blog WordPress allows you to easily style your site by either installing and activating new Themes or customizing existing Themes. Tips: From Theme Customizer launched by Appearance > Customize, you can customize all other options such as Theme, Widgets, Menus and Header. Also, modern theme has other settings or options. You should try Theme Customizer Themes A Theme is the overall design of a site and encompasses color, graphics, and text. WordPress site-owners have available a long list of Themes to choose from in deciding what to present to their sites' viewers. From the Appearance Themes Screen, you can choose which Theme will be presented to users visiting your site. You can also view screenshots of each Theme you have uploaded to your site. In addition, under the Install Themes tab you can find and install new Themes. Customize The Customize Screen displays the settings that can be customized for a specific theme. For instance, the WordPress default theme provides options that allows the user to set the colors and a background image. The Customize Screen page describes the details of this feature. Widgets Widgets are gadgets or gizmos that allow you to add various pieces of information to your Theme's sidebar content. Widgets, for example, can be used to add Categories, Archives, Blogroll, Recent Posts, and Recent Comments to your sidebar. From the Appearance Widgets Screen you can add, delete, and configure, the Widgets use in one or more of your Theme's sidebar. Menus The Menus feature allows you to create a navigation menu of pages, categories, custom links, tags, etc. that is presented to your visitors. A custom menu WordPress Widget allows display of a custom menu in the sidebar or other widgetized areas in the Theme. From the Appearance Menus Screen you can create and edit navigation menus for visitors use. Header The Header feature allows you to manage what image is displayed in a Theme's header. WordPress default theme allows you to preview, upload, remove, and set as default, the images you want randomly displayed in the header. The Appearance Header Screen describes the details of this feature. Theme Editor Tips: Instead of Theme Editor, consider to use Child Theme to modify Theme Template fand CSS files. Refer WordPress Theme Developer Handbook. Using the Theme Editor, you can edit the various files that comprise your Themes. The Appearance Editor Screen allows you to designate which theme you want to edit then displays the files in that theme. Each file (Template and CSS) in the theme can be edited in the large text box. Plugins - Add Functionality to your Blog Plugins allow you to add new features to your WordPress blog that don't come standard with the default installation. There are a rich variety of Available Plugins for WordPress, and with the following Screens, plugin installation and management is a snap. Installed Plugins The Plugins Installed Screen allows you to view the plugins you've downloaded and choose which plugins you want activated on your site. For information on downloading and installing plugins, see Managing Plugins. Add New Plugins The Plugins Add New Screen allows you to add new plugins. For information on downloading and installing plugins, see Managing Plugins. Plugin Editor Using the Plugins Editor Screen, you can modify the source code of all your plugins. Users - Your Blogging Family Every blog probably has at least two users: admin, the account initially set up by WordPress, and the user account you, as the author/owner of the blog, use to write posts. If you want a person to be able to post to your blog, that person must have access to a user account; typically, every person will have her or his own user account. Via the Users option in the main navigation menu you can set up all of the user accounts you need, as well as change user information, or delete users. Also you can specify your, and others', personal information, such as name, e-mail, etc. from these User Administration Screens. All Users You can manage the accounts of all your site's users at the All Users Screen. Add New User You can create new users with the Users Add New Screen. Your Profile The Users Your Profile Screen allows to change any information related to your user account. Tools - Managing your Blog WordPress Tools provide you the ability to speed up WordPress for your local machine, import content from other sources, export your content, or to upgrade your WordPress software to a new release. Available Tools There is a link to the Categories and Tag Converter. The Available Tools Screen describes the function. Import WordPress supports the importing data from a number external sources. In many cases, posts, comments, pages, categories, tags, and users, can be imported. The Importing Content for a more extensive list of import possibilites. Export WordPress Export will create an XML file for you to save to your computer. The format, which is called a WordPress eXtended RSS or WXR file, will contain your posts, comments, custom fields, categories, and tags. The Tools Export Screen guides you through the easy process of exporting your blog. Take note that the Exporting is a useful method to backup your WordPress data. Settings - Configuration Settings In the Settings Administration Screen are all of the settings that define your blog as a whole: settings which determine how your site behaves, how you interact with your site, and how the rest of the world interacts with your site. General The Settings Administration Screen and controls some of the most basic configuration settings for your site: your site's title and location, who may register an account at your blog, and how dates and times are calculated and displayed. Writing Using the Settings Writing Screen, you can control the interface with which you write new posts. These settings control the default Category, the default Post Format, and the optional feature. Reading The settings in the posts, or a "static" Page, displayed as your blog's front (main) page. You can also adjust how many posts are displayed on that main page. In addition, you can adjust syndication feed features to determine how the information from your site is sent to a reader's web browser or other applications. Discussion The Settings Discussion Screen allows you to control settings concerning incoming and outgoing comments, pingbacks and trackbacks. You can also control from this Screen the circumstances under which your blog sends you e-mail notifying you about the goings on at your site, and you can decide if your blog should show Avatars and their ratings. Media The Settings Media Screen allows you to determine how images, documents, and other media files will be organized when uploaded, and to specify the maximum dimensions in pixels to use when inserting an image into the body of a post. Permalinks For a nice introduction to Permalinks, check out the Pretty Permalinks section of Introduction to Blogging. By default, WordPress uses web URLs which have question marks and lots of numbers in them; however, WordPress offers you the ability to create a custom URL structure for your permalinks and archives. This can improve the aesthetics, usability, and forward-compatibility of your links. The Settings Permalinks Screen controls how that custom URL structure is defined. Status Post Clorith — Sun, 08 Dec 2013 22:31:59 +0000 Status Post Video Post Clorith — Sun, 08 Dec 2013 22:32:21 +0000 Video Post Appearance Menus Screen bellaratmelia — Tue, 05 Apr 2016 14:23:25 +0000 The Menu Screen enables user to create a custom menu (also known as navigation bar, navigation menu, or main menu). It is a section of the site which helps visitors to navigate in the site. Depending on the theme used, typically a site will have one navigation menu, while some themes may enable secondary or footer menus. It is essential to have a neat and simplified navigation menu, so as not to confuse your visitors. By default, WordPress adds all the published pages to the menu automatically. However, customization of menu is possible, such as adding a link to a category or to external site, changing the order of the menu link, or creating a sub-menu. The Appearance Menu Screen is accessible via Dashboard > Appearance > Menus. Screen Options The Screen Options allow you to choose which modules are displayed, or not displayed, in the underlying Screen. Clicking on the Screen Options tab shows a list of the possible modules and options with a check-box next to each. Check the box for each module or option you want displayed, or uncheck the box to not display that module. Click the Screen Options tab again to close the Screen Options. Certain modules, like Posts are hidden by default. Creating Menu Go to the WordPress Dashboard. From the 'Appearance' menu on the left-hand side of the Dashboard, select the 'Menus' option to bring up the Menu Editor. Select Create a new menu at the top of the page Enter a name for your new menu in the Menu Name box Click the Create Menu button. Adding Items to a Menu You can add different item types into your menu, such as Pages, Categories, or even Custom Links. These are split between panes left of the menu you're currently editing. An example on how to add link to a page: Locate the pane entitled Pages. Within this pane, select the View All link to bring up a list of all the currently published Pages on your site. Select the Pages that you want to add by clicking the checkbox next to each Page's title. Click the Add to Menu button located at the bottom of this pane to add your selection(s) to the menu that you created in the previous step. Click the Save Menu button once you've added all the menu items you want. Your custom menu has now been saved. Note: The Screen Options allow you to choose which items you can use to add to a menu. Certain items, like Tags are hidden by default. Deleting a Menu Item Locate the menu item that you want to remove in the menu editor window Click on the arrow icon in the top right-hand corner of the menu item to expand it. Click on the Remove item. The menu item will be immediately removed. Click the Save Menu button to save your changes. Creating Multi-level Menus When planning the structure of your menu, it helps to think of each menu item as a heading in a formal report document. In a formal report, main section headings (Level 1 headings) are the nearest to the left of the page; sub-section headings (Level 2 headings) are indented slightly further to the right; any other subordinate headings (Level 3, 4, etc) within the same section are indented even further to the right. The WordPress menu editor allows you to create multi-level menus using a simple 'drag and drop' interface. Drag menu items up or down to change their order of appearance in the menu. Drag menu items left or right in order to create sub-levels within your menu. To make one menu item a subordinate of another, you need to position the 'child' underneath its 'parent' and then drag it slightly to the right. Position the mouse over the 'child' menu item. Whilst holding the left mouse button, drag it to the right. Release the mouse button. Repeat these steps for each sub-menu item. Click the Save Menu button in the Menu Editor to save your changes. Adding Your Menu to Your Site If your current theme supports custom menus, you will be able to add your new menu to one of the Theme Locations. Scroll to the bottom of the menu editor window. In the section titled Theme locations, click the check box for the location where you want your menu to appear. Click Save menu once you've made your selection. If your current theme does not support custom menus, you will need to add your new menu via the Custom Menu widget in the Appearance Widgets Screen. Rearranging, Configuring Menu Items Once an item is added to a menu, those menu items can be rearranged. Placing the mouse cursor over the menu item title, when the mouse cursor changes to 4-arrows, hold the left-mouse button down, drag the module to where you want to place it, then release the mouse button (this is called drag-and-drop). Remember you can drag a menu item slightly to the right of the menu item above it to create a hierarchy (parent/child) relationship in the menu. Each Menu Item has a configuration arrow on the right side of the Menu Item title, that when clicked opens the configuration box. Click the arrow a second time closed the configuration box. If you don't see Link Target, CSS Classes, Link Relationship (XFN), and Description, then under Screen Options make sure those boxes are checked to expose them here. Then configuration choices are: Navigation Label The label for this particular menu item Title Attribute The attribute used when displaying the label Link Target Select "Same window or tab" or "New window or tab" from the pulldown. CSS Classes Optional CSS Classes for this menu item Link Relationship (XFN) Allows for the generation of XFN attributes automatically so you can show how you are related to the authors/owners of site to which you are linking. See Link Relationship for details. Description Description for this link. The description will be displayed in the menu if the current theme supports it. Original A link to the original source of the menu item (e.g. a link to view the post or page). Remove Remove this menu item from the menu. Cancel Cancel the configuration of the menu item and WordPress Widgets atachibana — Sun, 10 Apr 2016 14:48:32 +0000 WordPress Widgets add content and features to your Sidebars. Examples are the default widgets that come with WordPress; for Categories, Tag cloud, Search, etc. Plugins will often add their own widgets. Widgets were originally designed to provide a simple and easy-to-use way of giving design and structure control of the WordPress Theme to the user, which is now available on properly "widgetized" WordPress Themes to include the header, footer, and elsewhere in the WordPress design and structure. Widgets require no code experience or expertise. They can be added, removed, and rearranged on the Theme Customizer or Appearance > Widgets in the WordPress Administration Screens. Some WordPress Widgets offer customization and options such as forms to fill out, includes or excludes of data and information, optional images, and other customization features. The Appearance Widgets Screen explains how to use the various Widgets that come delivered with WordPress. Plugins that come bundled with widgets can be found in the WordPress Plugin Directory. Installing Widgets WordPress comes pre-packaged with a variety of Widgets. If those are insufficient for your needs you can install new ones by searching the WordPress Plugin Directory which is accessible from the WordPress Administration Plugins > Add New Screen. Displaying Widgets Existing Widgets in Existing Widget Areas Before you can add a Widget you must verify that the Theme you're using supports Widgets (more specifically: Widget Area). You can do so by simply navigating to the Appearance menu and looking for a sub menu titled "Widgets". If your Theme supports Theme Customizer then you can use the following Steps. In Theme Customizer, the live preview of changes is available. Go to Appearance > Customize in the WordPress Administration Screens. Click the Widget menu in the Theme Customizer to access to the Widget Customize Screen. Click the down arrow of Widget Area to list the already registered Widgets. Click Add a Widget button at the bottom of sidebar. It shows the list of available widgets. Click a widget you want to add. The widgets should be added in the sidebar. Preview your site and you should see the content from your new Widget. To arrange the Widgets within the Sidebar, drag and drop the widgets in the order you want or click Reorder link and click up arrow and down allow of each widget and click Done after the arrange operation. To customize the Widget features, click the down arrow in the right to expand the Widget's interface. To remove the widget, click Remove from Widget's interface in above step. If your Theme does not support Theme Customizer then you can use the following conventional steps: Go to Appearance > Widgets in the WordPress Administration Screens. Choose a Widget and either drag it to the sidebar where you wish it to appear, or click the widget, (select a destination sidebar if your theme has more than one) and click the Add Widget button. There might be more than one sidebar option, so begin with the first one. Once in place, WordPress automatically updates the Theme. Preview the site. You should find that the "default" sidebar elements are now gone and only the new addition is visible. Return to the Widgets Screen to continue adding Widgets. To arrange the Widgets within the sidebar or Widget area, click and drag it into place. To customize the Widget features, click the down arrow in the upper right corner to expand the Widget's interface. To save the Widget's customization, click Save. To remove the Widget, click Delete. If you want to remove the widget but save its setting for possible future use, just drag it into the Inactive Widgets area. You can add them back anytime from there. This is especially helpful when you switch to a theme with fewer or different widget areas. When changing themes, there is often some variation in the number and setup of widget areas/sidebars and sometimes these conflicts make the transition a bit less smooth. If you changed themes and seem to be missing widgets, scroll down on the screen to the Inactive Widgets area, where all of your widgets and their settings will have been saved. Enabling Accessibility Mode, via Screen Options, allows you to use Add and Edit buttons instead of using drag and drop. Widget Areas While widget areas typically occur in webpage sidebars, a theme can place widget areas anywhere on a page. For example, besides the usual sidebar locations, the Twenty Seventeen theme has a widget area in the footer of every page. If you would like to place a Widget somewhere on your Theme that does not have a pre-defined Widget Area, you will need some programming knowledge and should follow the instructions on the Widgets API section found here. Using Text Widgets The Text Widget is one of the most commonly used WordPress Widgets that comes with every WordPress installation. It allows users to add text, video, images, custom lists, and more to their WordPress sites. To use the WordPress Text Widget: Go to Appearance > Customize in the WordPress Administration Screens and click the Widget menu in the Theme Customizer. Or Go to Appearance > Widgets in the WordPress Administration Screens. Open the sidebar to which you wish to add the Text Widget. Find the Text Widget in the list of Widgets. Click and drag the Widget to the spot you wish it to appear. To open and edit the Text Widget: Click the down arrow to the right of the Text Widget title. Set the Text Widget Title (optional). Add the text or HTML code to the box or edit what is currently there. Choose the option to Automatically add paragraphs to wrap each block of text in an HTML paragraph tag (recommended for text). Click Save to save the Text Widget. Click Close to close the Text Widget. Switch tabs in your browser and preview the results and make changes if necessary. The Text Widget can hold a variety of HTML, XHTML, and multimedia links and players such as video and object embeds. Adding Code to the Text Widget Basic HTML, embeds, and JavaScript are added easily to the WordPress Text Widget. Most embed codes from social sharing sites for multimedia will work in a WordPress Text Widget. However, active code and programming languages such as PHP will not work as the Widget will strip out code it cannot display. To add active code to the Text Widget, use one of the many WordPress Plugins from the WordPress Plugin Directory that override WordPress restrictions on using PHP in posts. Check that they will work on Widgets as some will not. Using RSS Widgets The RSS Widget allows you to integrate an external feed source for content into a Widget area of your site, such as your Twitter account, Facebook posts, Google+ posts, or other blogs. The RSS Widget displays the most recently published content from any source with an active feed. This is an ideal way of integrating outside content into your site. By default, WordPress RSS Widget displays the post title or the first 100 or so characters of a Tweet or long untitled post. These are either in the form of a link or features a link to the original source depending upon the feed's design and structure. Enter the RSS feed URL in the first box, copied from the source page for the content you wish to include in your sidebar or other widgetized space. Give the feed a title: This is optional and gives you the chance to showcase the source of the content. How many items would you like to display?: By default, 10 are show, but you can choose from 1-20 posts. Display item content?: This allows you to show an excerpt of the content not just the title. Display item author if available?: If you wish to give credit to the original author of the content, check this to display the author. Display item date?: If available, the date of the original content will be shown. You may add multiple RSS Widgets for incoming feeds to your WordPress sidebar and other widgetized areas of your site. Resources Widgetizing Themes Widgets API WordPress Tips on Exploring the WordPress Text Widget WordPress Widgets Announcement (historical reference) Pages Add New Screen atachibana — Sun, 10 Apr 2016 15:01:08 +0000 Pages → Add New The Pages Add New Screen allows you to add new Pages. Back to Administration Screens. Screen Options The Screen Options allow you to choose which modules are displayed, or not displayed, in the underlying Screen. Clicking on the Screen Options tab shows a list of the columns with a check-box next to each column. Check the box for each module you want displayed, or uncheck the box to not display that module. Click the Screen Options tab again to close the Screen Options. These options are saved so that you can customize how your own editing screen looks. So if modules such as Custom Fields, Discussion, Slug and Post Author are hidden from view use the Screen Options to expose those modules. Expanding, Collapsing, and Rearranging, Modules The modules, Publish, Page Attribute, Features Image and others, can be expanded, or collapsed, by clicking on the module title bar. In addition, those modules can be moved by hovering the mouse cursor over the module title bar, when the mouse cursor changes to 4-arrows, hold the left-mouse button down, drag the module to where you want to place it, then release the mouse button (this is called drag-and-drop). Add New Page Title The title of your page. You can use any words or phrases. Avoid using the same title twice as that will cause problems. You can use commas, apostrophes, quotes, hypens/dashes, and other typical symbols in the page like "About My Site - Here's Lookin' at You, Kid." WordPress will clean it up for the link to the page, called the slug. Page Editing Area The blank box where you enter your writing, links, links to images, and any information you want to display on your site. You can use either the Visual or the Text view to compose your posts. For more on the Text view, see the Visual Versus Text View article. Preview button Allows you to view the page before officially publishing it. Publish box Contains buttons that control the state of your page. The main states are Published, Pending Review, and Draft. A Published status means the page has been published on your blog for all to see. Pending Review means the draft is waiting for review by an editor prior to publication. Draft means the page has not been published and remains a draft for you. If you select a specific publish status and click the update page or Publish button, that status is applied to the page. For example, to save a page in the Pending Review status, click Edit link of Status and select Pending Review from the drop-down box, click OK to close the drop-down box and click Save As Pending button. (You will see all pages organized by status by going to Pages > All Pages). To schedule a page for publication on a future time or date, click "Edit" in the Publish area next to the words "Publish immediately". You can also change the publish date to a date in the past to back-date pages. Change the settings to the desired time and date. You must also hit the "Publish" button when you have completed the page to publish at the desired time and date. Visibility - This determines how your page appears to the world. Public pages will be visible by all website visitors once published. Password Protected pages are published to all, but visitors must know the password to view the page content. Private pages are visible only to you (and to other editors or admins within your site) Permalink After you save your page, the Permalink below the title shows the potential URL for the page, as long as you have permalinks enabled. (To enable permalinks, go to Settings > Permalinks.) The URL is generated from your title. In previous versions of WordPress, this was referred to as the "page-slug." The commas, quotes, apostrophes, and other non-HTML favorable characters are changed and a dash is put between each word. If your title is "My Site - Here's Lookin' at You, Kid", it will be cleaned up to be "my-site-heres-lookin-at-you-kid" as the title. You can manually change this, maybe shortening it to "my-site-lookin-at-you-kid". Save Allows you to save your page as a draft / pending review rather than immediately publishing it. To return to your drafts later, visit Pages > All Pages from dashboard, then click your page title from the list. Publish Publishes your page on the site. You can edit the time when the page is published by clicking the Edit link above the Publish button and specifying the time you want the page to be published. By default, at the time the page is first auto-saved, that will be the date and time of the page within the database. Parent Parent page controls how deep your page hierarchy goes. Template Some Themes have custom templates you can use for certain pages that might have additional features or custom layouts. If so, you'll see them in this dropdown menu. Order Page order to sort the list of Pages. Back to Administration Screens. Sticky Posts ankitguptaindia — Thu, 14 Apr 2016 19:48:22 +0000 Sticky Posts is a feature introduced with Version 2.7. A check box is included on the Administration >Posts > Add New Screen (In the Publish panel under Visibility. Click edit to see the checkbox). If checked, the post will be placed at the top of the front page of posts, keeping it there until new posts are published. Please notice that this feature is only available for the built-in post type post and not for custom post types. Function Reference Template Tags is_sticky() sticky_class() Administration Menus atachibana — Sat, 16 Apr 2016 02:00:54 +0000 [codex_languages en="Adding Administration Menus" zhcn_codex="Adding Administration Menus" ja_codex="Adding Administration Menus" ru_codex="Добавление административных меню"] Introduction Usually, plugin and theme authors need to provide access to a settings (options) screen so users can customize how the plugin or theme is used. The best way to present the user with such a screen is to create an administration menu item that allows the user to access that settings screen from all the Administration Screens. This article explains how plugin authors can add administration menus and screens. Note: the following information assumes a knowledge of the basics of Writing a Plugin and using the Plugin API of Actions and Filters. Function Reference General Functions Menu Pages add_menu_page() add_object_page() add_utility_page() remove_menu_page() SubMenu Pages add_submenu_page() remove_submenu_page() WordPress Administration Menus add_dashboard_page() add_posts_page() add_media_page() add_pages_page() add_comments_page() add_theme_page() add_plugins_page() add_users_page() add_management_page() add_options_page() Every Plot Needs a Hook To add an administration menu, you must do three things: Create a function that contains the menu-building code Register the above function using the admin_menu action hook. (If you are adding an admin menu for the Network, use network_admin_menu instead). Create the HTML output for the page (screen) displayed when the menu item is clicked It is that second step that is often overlooked by new developers. You cannot simply call the menu code described; you must put it inside a function, and then register the function. Here is a very simple example of the three steps just described. This plugin will add a sub-level menu item under the Settings top-level menu in main plugin PHP file or a separate PHP include file. '; echo 'Here is where the form would go if I actually had options.'; echo ''; } ?> In this example, the function my_plugin_menu() adds a new item to the Settings administration menu via the add_options_page() function. Note: more complicated multiple menu items can be added, but that will be described later. Notice the add_action() call in Step 2 that registers the my_plugin_menu() function under the admin_menu hook. Without that add_action() call, a PHP error for undefined function will be thrown when attempting to activate the plugin. Finally, the add_options_page() call refers to the my_plugin_options() function which contains the actual page to be displayed (and PHP code to be processed) when someone clicks the menu item. These processes are described in more detail in the sections below. Remember to enclose the creation of the menu and the page in functions, and use the admin_menu hook to get the whole process started at the right time! Determining Location for New Menus Before creating a new menu, first decide if the menu should be a top-level menu, or a sub-level menu item. A top-level menu displays as new section in the administration menus and contains sub-level menu items. A sub-level menu means the menu item is a member of an existing menu. It is rare that a plugin would require the creation of a top-level menu. If the plugin introduces an entirely new concept or feature to WordPress, and needs many screens to do it, then that plugin may warrant a new top-level menu. Adding a top-level menu should only be considered if you really need multiple, related screens to make WordPress do something it was not originally designed to accomplish. Examples of new top-level menus might include job management or conference management. Please note with the native post type registration, WordPress automatically creates top-level menus to manage those features. If the creation of a top-level menu is not necessary, decide under what top-level menu to place your sub-level menu item. As a point of reference, most plugins add sub-level menu items underneath existing WordPress top-level menus. For example, the Backup plugin adds a sub-level menu option to the Tools top-level menu. Please note with the taxonomy registration, WordPress automatically creates sub-level menus under the applicable top-level menu to manage those features. Use this guide of the WordPress top-level menus to determine the correct location for your sub-level menu item: Dashboard Information central for your site and include the Updates option for updating WordPress core, plugins, and themes. Posts Displays tools for writing posts (time oriented content). Media Uploading and managing your pictures, videos, and audio. Pages Displays tools for writing your static content called pages. Comments Controlling and regulation reader to responses to posts. Appearance Displays controls for manipulation of theme/style files, sidebars, etc. Plugins Displays controls dealing with plugin management, not configuration options for a plugin itself. Users Displays controls for user management. Tools Manage the export, import, and even backup of blog data. Settings Displays plugin options that only administrators should view (also see Creating Settings Pages). Network Admin Displays plugin options that are set on the Network. Instead of "admin_menu", you should use "network_admin_menu" (see also Create A Network) Admin Menu Functions Now that you have decided where to add your top-level or sub-level menu, the next step is to tell WordPress about your new pages. All of this will take place in a function registered to the 'admin_menu' action. A working example is presented at the end of this section. Top-Level Menus If you have decided your plugin requires a brand-new top-level menu, the first thing you'll need to do is to create one with the add_menu_page function. Note: skip to Sub-Level Menus if you don't need a top-level menu. Parameter values: page_title The text to be displayed in the title tags of the page when the menu is selected. menu_title The on-screen name text for the menu. capability The capability required for this menu to be displayed to the user. When using the User levels are deprecated and should not be used here! menu_slug The slug name to refer to this menu by (should be unique for this menu). Prior to Version 3.0 this was called the file (or handle) parameter. If the function parameter is omitted, the menu_slug should be the PHP file that handles the display of the menu page content. function The function that displays the page content for the menu page. Technically, the function parameter is optional, but if it is not supplied, then WordPress will basically assume that including the PHP file will generate the administration screen, without calling a function. The page-generating code can be written in a function within the main plugin file. In the event that the function parameter is specified, it is possible to use any string for the menu_slug parameter. This allows usage of pages such as ?page=my_super_plugin_page instead of ?page=my-super-plugin/admin-options.php. The function must be referenced in one of two ways: if the function is a member of a class within the plugin it should be referenced as array( $this, 'function_name' ) in all other cases, using the function name itself is sufficient icon_url The url to the icon to be used for this menu. This parameter is optional. position The position in the menu order this menu should appear. By default, if this parameter is omitted, the menu will appear at the bottom of the menu structure. To see the current menu positions, use print_r($GLOBALS['menu']) after the menu has loaded. Sub-Level Menus Once your top-level menu is defined, or you have chosen to use an existing WordPress top-level menu, you are ready to define one or more sub-level menu items using the add_submenu_page function. Make sure to add the sub-level menu items in the order you want them displayed. Using add_submenu_page Parameter values: parent_slug The slug name for the parent menu, or the file name of a standard WordPress admin file that supplies the top-level menu in which you want to insert your submenu, or your plugin file if this submenu is going into a custom top-level menu. Examples: For Dashboard: add_submenu_page('index.php',...) For Posts: add_submenu_page('edit.php',...) For Media: add_submenu_page('upload.php',...) For Pages: add_submenu_page('edit.php?post_type=page',...) For Comments: add_submenu_page('edit-comments.php',...) For Custom Post Types: add_submenu_page('edit.php?post_type=your_post_type',...) For Appearance: add_submenu_page('themes.php',...) For Plugins: add_submenu_page('plugins.php',...) For Users: add_submenu_page('users.php',...) For Tools: add_submenu_page('tools.php',...) For Settings: add_submenu_page('options-general.php',...) page_title Text that will go into the HTML page title for the page when the submenu is active. menu_title The text to be displayed in the title tags of the page when the menu is selected. capability The capability required for this menu to be displayed to the user. User levels are deprecated and should not be used here! menu_slug For existing WordPress menus, the PHP file that handles the display of the menu page content. For submenus of a custom top-level menu, a unique identifier for this sub-menu page. ''In situations where a plugin is creating its own top-level menu, the first submenu will normally have the same link title as the top-level menu and hence the link will be duplicated. The duplicate link title can be avoided by calling the add_submenu_page function the first time with the parent_slug and menu_slug parameters being given the same value. '' function The function that displays the page content for the menu page. Technically, as in the add_menu_page function, the function parameter is optional, but if it is not supplied, then WordPress will basically assume that including the PHP file will generate the administration screen, without calling a function. Most plugin authors choose to put the page-generating code in a function within their main plugin file. In the event that the function parameter is specified, It's possible to use any string for the menu_slug parameter. This allows usage of pages such as ?page=my_super_plugin_page instead of ?page=my-super-plugin/admin-options.php. See the Top-Level Menus for notes about how to reference class members as function parameters. Example Here's a quick example illustrating how to insert a top-level menu page and a sub-menu page, where the title on the sub-menu page is different from the top-level page. In this example, 'my_magic_function' is the name of the function that displays the first sub-menu page: Here's an example of adding an option page under a custom post type menu block (see also here): Using Wrapper Functions Since most sub-level menus belong under the Settings, Tools, or Appearance menus, WordPress supplies wrapper functions that make adding a sub-level menu items to those top-level menus easier. Note that the function names may not match the names seen in the Administration Screens as they have changed over time: Dashboard Posts Media Pages Comments Appearance Plugins Users Tools Settings Also see Creating Options Pages for more on this. Inserting the Pages Here is an example of a WordPress plugin that inserts new menus into various places: " . __( 'Test Settings', 'menu-test' ) . ""; } // mt_tools_page() displays the page content for the Test Tools submenu function mt_tools_page() { echo "" . __( 'Test Tools', 'menu-test' ) . ""; } // mt_toplevel_page() displays the page content for the custom Test Toplevel menu function mt_toplevel_page() { echo "" . __( 'Test Toplevel', 'menu-test' ) . ""; } // mt_sublevel_page() displays the page content for the first submenu // of the custom Test Toplevel menu function mt_sublevel_page() { echo "" . __( 'Test Sublevel', 'menu-test' ) . ""; } // mt_sublevel_page2() displays the page content for the second submenu // of the custom Test Toplevel menu function mt_sublevel_page2() { echo "" . __( 'Test Sublevel2', 'menu-test' ) . ""; } ?> Sample Menu Page Note: See the Settings API for information on creating settings pages. The example above contains several dummy functions, such as mt_settings_page, as placeholders for actual page content. We need to turn them into real menu pages. So, let's assume that our plugin has an option called mt_favorite_color, and that we want to allow the site owner to type in his/her favorite color via a Settings page. The mt_options_page function will need to put a data entry form on the screen to enable this, and also process the entered data. Here is a function that does this: // mt_settings_page() displays the page content for the Test Settings submenu function mt_settings_page() { //must check that the user has the required capability if (!current_user_can('manage_options')) { wp_die( __('You do not have sufficient permissions to access this page.') ); } // variables for the field and option names $opt_name = 'mt_favorite_color'; $hidden_field_name = 'mt_submit_hidden'; $data_field_name = 'mt_favorite_color'; // Read in existing option value from database $opt_val = get_option( $opt_name ); // See if the user has posted us some information // If they did, this hidden field will be set to 'Y' if( isset($_POST[ $hidden_field_name ]) && $_POST[ $hidden_field_name ] == 'Y' ) { // Read their posted value $opt_val = $_POST[ $data_field_name ]; // Save the posted value in the database update_option( $opt_name, $opt_val ); // Put a "settings saved" message on the screen ?> '; // header echo "" . __( 'Menu Test Plugin Settings', 'menu-test' ) . ""; // settings form ?> A few notes: The WordPress functions such as add_menu_page and add_submenu_page take a capability which will be used to determine whether the top-level or sub-level menu is displayed. The function which is hooked in to handle the output of the page must check that the user has the required capability as well. The WordPress administration functions take care of validating the user login, so you don't have to worry about it in your function. The function example above has been internationalized -- see the Internationalization section of Writing a Plugin for more information. The function processes any entered data before putting the data entry form on the screen, so that the new values will be shown in the form (rather than the values from the database). You don't have to worry about this working the first time, because the WordPress update_option function will automatically add an option to the database if it doesn't already exist. These admin-menu-adding procedures are parsed every single time you navigate to a page in Admin. So if you are writing a plugin which has no options page, but add one later, you can just add it using the instructions above and re-upload, and tweak until you're happy with it. In other words, menus are not "permanently added" or put into a database upon activating a plugin. They're parsed on the fly, so you can add or subtract menu items at will, re-upload, and the change will be reflected right away. Page Hook Suffix Every function that adds a new administration menu (add_menu_page(), add_submenu_page() and its specialized versions such as add_options_page()) returns a special value called Page Hook Suffix. It can be used later as a hook to which an action called only on that particular page can be registered. One such action hook is load-{page_hook}, where {page_hook} is the value returned by one of these add_*_page() functions. This hook is called when the particular page is loaded. In the example below, it is used to display the "Plugin is not configured" notice on all admin pages except for plugin's options page: My Plugin is not configured yet. Please do it now.\n"; } function my_plugin_options() { if (!current_user_can('manage_options')) { wp_die( __('You do not have sufficient permissions to access this page.') ); } echo ''; echo 'Here is where the form would go if I actually had options.'; echo ''; } ?> Resources Admin Menu Editor Plugin - allows adding, deleting, hiding, and re-ordering of administration items Finding Your CSS Styles geoffreyshilling — Fri, 22 Apr 2016 16:48:58 +0000 The following article isn't so much about choosing a WordPress Theme, but about finding the CSS styles within your current theme. Sometimes a problem occurs in one part of the layout or template, and you'll want to be able to fix it. For example, let's say you have an unwanted border between the sidebar menu and the rest of the page. You hunt and hunt but you can't find any reference to the border. Now what? Playing CSS Detective Let's begin by playing CSS detective. You'll want to start by searching diligently for the border that you want to remove. There are a couple of ways that you can start searching for it. The first method involves using the built-in web inspector tools found in most modern web browsers. (Two popular examples are Web Inspector in Google Chrome and Page Inspector in Mozilla Firefox.) First, highlight the section that contains the border, and then right click and choose "Inspect" (in Chrome), or "Inspect Element" (in Firefox). This will pull up an inspection tool that will show you the code associated with the currently highlighted section of text. You can then use this inspection tool to help pinpoint the code that you need to change. If you're using Chrome, you can also try disabling styles and then seeing how the page changes. That way you'll know for sure that this is the CSS that you should change. Once you know which specific bit of CSS it is, you can head into your style.css file and remove it. Pat yourself on the back for a job well done! If you don't have a browser with built-in inspection tools handy, you can still seek out the rogue line of CSS code. You can do this by viewing the page source. Let's say you have a sidebar that includes a post titled "All About Harry." When you view the page's source code, you'll see that title listed in your sidebar div. To view a page's source code, navigate to the menu bar of your browser and choose View > Page Source or View > Source. A page will pop up displaying the source code for that page. Use your handy detective tool (Ctrl+F on Windows or CMD+F on a Mac) to activate your search. Type in "all about harry" and click Find. This will take you to the first occurrence of the phrase. Unless you have the words "all about harry" in your post, odds are that it will take you directly to the phrase in your sidebar. If not, click Find again until you've found the phrase in the right area. Once you've found the phrase, it's time to play CSS detective. Look above the code starting with the phrase "all about harry" for one of two things. It will look something like either of the following examples, using words like sidebar, menu, or sidecolumn: [code language="html"] [/code] or [code language="html"] [/code] This is the main section that contains your sidebar menu. You've found the first suspect. Now, open your style.css file and do another search for sidebar (or whatever the resulting name was that you uncovered). It can usually be identified in two ways: [code language="css"]#sidebar[/code] or [code language="css"].sidebar[/code] Look at the styles under these CSS selectors and see if there is a mention of "border," often looking something like this: [code language="css"]#sidebar { position: relative; float: right; width: 170px; color: blue; font-size: 90%; border-right: solid 1px blue; }[/code] If this is the guilty party, delete the reference to the border and you are good to go. If it isn't, then the hunt continues. Sometimes the real culprit is the one that you least suspect. Maybe the border isn't caused by the obvious suspect, the sidebar, but by the content section. Return to the page's source code and search for the first words of your post. Look above that for something like: [code language="html"] [/code] It could be called content, page, post, maincolumn, or widecolumn (or it could have another alias) but it should be the CSS container that holds your post information. Now, go back to the stylesheet and check to see if there is a border in that section. Frisk the Style Sheet Even if all of these methods fail, the CSS detective refuses to give up the hunt. Return to the hiding place of all styles, the style.css file, and frisk it by doing a search for "border," looking carefully at each suspected line of code. Note the selector ID name (such as sidebar, menu, content or page) and then go back to the page's source code to see if that particular selector might be your culprit. You can also select the border suspect that you've found on the stylesheet, cutting and pasting it into a text file which you can leave open on your computer like a scratchpad. Be sure to make a note of the selector name that you removed it from, using notation that is similar to this: Removed border: solid 2px green from #content Then save the edited style.css file and upload it to your site. Refresh the generated test post and see if the unwanted border is gone. If so, you've found the culprit! If not, copy the code from your scratchpad and paste it back into your style.css file in the content section, putting things back where you found them. Once you have found your culprit, do a little dance, squeal, cheer, and make others suspicious and nervous when they are around you. The CSS detective solves another CSS crime! More CSS Troubleshooting Help CSS Fixing Browser Bugs CSS Troubleshooting Nginx alt3red — Fri, 22 Apr 2016 19:50:36 +0000 While the LAMP stack (Linux + Apache + MySQL + PHP) is very popular for powering WordPress, it is also possible to use Nginx. WordPress supports Nginx, and some large WordPress sites, such as WordPress.com, are powered by Nginx. When talking about Nginx, it is important to know that there are multiple ways to implement Nginx. It can be setup as a reverse-proxy in front of Apache, which is a very powerful setup that allows you to use all of the features and power of Apache, while benefitting from the speed of Nginx. Most websites that report using Nginx as the server (based on stats gathered from HTTP response headers), are actually Apache running with Nginx as the reverse proxy. (The HTTP response headers showing "Nginx" are being reported by the reverse-proxy, not the server itself.) This guide is referring to a standalone Nginx setup, where it is used as the primary server instead of Apache. It should be noted that Nginx is not a completely interchangeable substitute for Apache. There are a few key differences affecting WordPress implementation that you need to be aware of before you proceed: With Nginx there is no directory-level configuration file like Apache's .htaccess or IIS's web.config files. All configuration has to be done at the server level by an administrator, and WordPress cannot modify the configuration, like it can with Apache or IIS. Pretty Permalinks functionality is slightly different when running Nginx. Since Nginx does not have .htaccess-type capability and WordPress cannot automatically modify the server configuration for you, it cannot generate the rewrite rules for you. Without modifications to your install, "index.php" will be to be added to your Permalinks. (There are ways to mitigate this with plugins (see below) and/or adding custom code to your child theme's functions.php.) However, if you do want to have some (limited) .htaccess capability, it is technically possible to do add by installing the htscanner PECL extension for PHP. (However, this is not a perfect solution so be sure to test and debug thoroughly before using on a live site.) This guide is not going to cover how to install and configure Nginx, so this assumes that you have already installed Nginx and have a basic understanding of how to work with and debug it. Generic and Multi-Site Support To make WordPress work with Nginx you have to configure the backend php-cgi. The options available are 'fastcgi' or 'php-fpm'. Here, php-fpm is being used because it is included with PHP 5.3+, so installing it is straight forward. The Nginx configuration has been broken up into five distinct files and is heavily commented to make each option easier to understand. The author also made a best-effort attempting to follow "best practices" for nginx configurations. Main (generic) startup file This is equivalent to /etc/nginx/nginx.conf (or /etc/nginx/conf/nginx.conf if you're using Arch Linux). [code language="bash"] # Generic startup file. user {user} {group}; #usually equal to number of CPUs you have. run command "grep processor /proc/cpuinfo | wc -l" to find it worker_processes 2; error_log /var/log/nginx/error.log; pid /var/run/nginx.pid; # Keeps the logs free of messages about not being able to bind(). #daemon off; events { worker_connections 1024; } http { # rewrite_log on; include mime.types; default_type application/octet-stream; access_log /var/log/nginx/access.log; sendfile on; # tcp_nopush on; keepalive_timeout 3; # tcp_nodelay on; # gzip on; #php max upload limit cannot be larger than this client_max_body_size 13m; index index.php index.html index.htm; # Upstream to abstract backend connection(s) for PHP. upstream php { #this should match value of "listen" directive in php-fpm pool server unix:/tmp/php-fpm.sock; # server 127.0.0.1:9000; } include sites-enabled/*; } [/code] This is a bit different from standard nginx.conf files. This configuration follows the Ubuntu/Debian method of declaring enabled sites for maximum flexibility - using 'sites-available' to store a config and then symlink to the config file from 'sites-enabled'. Per Site configuration # Redirect everything to the main site. We use a separate server statement and NOT an if statement - see http://wiki.nginx.org/IfIsEvil server { server_name _; return 302 $scheme://example.com$request_uri; } server { server_name example.com; root /var/www/example.com; index index.php; include global/restrictions.conf; # Additional rules go here. # Only include one of the files below. include global/wordpress.conf; # include global/wordpress-ms-subdir.conf; # include global/wordpress-ms-subdomain.conf; } Splitting sections of the configuration into multiple files allows the same logic to be reused over and over. A 'global' subdirectory is used to add extra rules for general purpose use (either /etc/nginx/conf/global/ or /etc/nginx/global/ depending on how your nginx install is set up). Global restrictions file # Global restrictions configuration file. # Designed to be included in any server {} block. location = /favicon.ico { log_not_found off; access_log off; } location = /robots.txt { allow all; log_not_found off; access_log off; } # Deny all attempts to access hidden files such as .htaccess, .htpasswd, .DS_Store (Mac). # Keep logging the requests to parse later (or to pass to firewall utilities such as fail2ban) location ~ /\. { deny all; } # Deny access to any files with a .php extension in the uploads directory # Works in sub-directory installs and also in multisite network # Keep logging the requests to parse later (or to pass to firewall utilities such as fail2ban) location ~* /(?:uploads|files)/.*\.php$ { deny all; } General WordPress rules For single site installations, here is the 'global/wordpress.conf' file: # WordPress single site rules. # Designed to be included in any server {} block. # Upstream to abstract backend connection(s) for php upstream php { server unix:/tmp/php-cgi.socket; server 127.0.0.1:9000; } server { ## Your website name goes here. server_name domain.tld; ## Your only path reference. root /var/www/wordpress; ## This should be in your http block and if it is, it's not needed here. index index.php; location = /favicon.ico { log_not_found off; access_log off; } location = /robots.txt { allow all; log_not_found off; access_log off; } location / { # This is cool because no php is touched for static content. # include the "?$args" part so non-default permalinks doesn't break when using query string try_files $uri $uri/ /index.php?$args; } location ~ \.php$ { #NOTE: You should have "cgi.fix_pathinfo = 0;" in php.ini include fastcgi.conf; fastcgi_intercept_errors on; fastcgi_pass php; } location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ { expires max; log_not_found off; } } This is more uptodate example for nginx v .10 and ↑. Ref: https://www.nginx.com/resources/wiki/start/topics/recipes/wordpress/ WordPress Multisite Subdirectory rules For multisite subdirectory installations, here is the 'global/wordpress.conf' file: # WordPress multisite subdirectory rules. # Designed to be included in any server {} block. map $uri $blogname{ ~^(?P/[^/]+/)files/(.*) $blogpath ; } map $blogname $blogid{ default -999; #Ref: http://wordpress.org/extend/plugins/nginx-helper/ #include /var/www/wordpress/wp-content/plugins/nginx-helper/map.conf ; } server { server_name example.com ; root /var/www/example.com/htdocs; index index.php; location ~ ^(/[^/]+/)?files/(.+) { try_files /wp-content/blogs.dir/$blogid/files/$2 /wp-includes/ms-files.php?file=$2 ; access_log off; log_not_found off; expires max; } #avoid php readfile() location ^~ /blogs.dir { internal; alias /var/www/example.com/htdocs/wp-content/blogs.dir ; access_log off; log_not_found off; expires max; } if (!-e $request_filename) { rewrite /wp-admin$ $scheme://$host$uri/ permanent; rewrite ^(/[^/]+)?(/wp-.*) $2 last; rewrite ^(/[^/]+)?(/.*\.php) $2 last; } location / { try_files $uri $uri/ /index.php?$args ; } location ~ \.php$ { try_files $uri =404; include fastcgi_params; fastcgi_pass php; } #add some rules for static content expiry-headers here } NGINX provides 2 special directive: X-Accel-Redirect and map. Using these 2 directives, one can eliminate performance hit for static-file serving on WordPress multisite network. WordPress Multisite subdomains rules map $http_host $blogid { default -999; #Ref: http://wordpress.org/extend/plugins/nginx-helper/ #include /var/www/wordpress/wp-content/plugins/nginx-helper/map.conf ; } server { server_name example.com *.example.com ; root /var/www/example.com/htdocs; index index.php; location / { try_files $uri $uri/ /index.php?$args ; } location ~ \.php$ { try_files $uri =404; include fastcgi_params; fastcgi_pass php; } #WPMU Files location ~ ^/files/(.*)$ { try_files /wp-content/blogs.dir/$blogid/$uri /wp-includes/ms-files.php?file=$1 ; access_log off; log_not_found off; expires max; } #WPMU x-sendfile to avoid php readfile() location ^~ /blogs.dir { internal; alias /var/www/example.com/htdocs/wp-content/blogs.dir; access_log off; log_not_found off; expires max; } #add some rules for static content expiry-headers here } Ref: https://www.nginx.com/resources/wiki/start/topics/recipes/wordpress/ HTTPS in Nginx Enabling HTTPS in Nginx is relatively simple. server { # listens both on IPv4 and IPv6 on 443 and enables HTTPS and HTTP/2 support. # HTTP/2 is available in nginx 1.9.5 and above. listen *:443 ssl http2; listen [::]:443 ssl http2; # indicate locations of SSL key files. ssl_certificate /srv/www/ssl/ssl.crt; ssl_certificate_key /srv/www/ssl/ssl.key; ssl_dhparam /srv/www/master/ssl/dhparam.pem; # indicate the server name server_name example.com *.example.com; # Enable HSTS. This forces SSL on clients that respect it, most modern browsers. The includeSubDomains flag is optional. add_header Strict-Transport-Security "max-age=31536000; includeSubDomains"; # Set caches, protocols, and accepted ciphers. This config will merit an A+ SSL Labs score as of Sept 2015. ssl_session_cache shared:SSL:20m; ssl_session_timeout 10m; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_prefer_server_ciphers on; ssl_ciphers 'ECDH+AESGCM:ECDH+AES256:ECDH+AES128:DH+3DES:!ADH:!AECDH:!MD5'; } Mozilla offers an excellent SSL config generation tool as well. WP Super Cache Rules # WP Super Cache rules. # Designed to be included from a 'wordpress-ms-...' configuration file. set $cache_uri $request_uri; # POST requests and urls with a query string should always go to PHP if ($request_method = POST) { set $cache_uri 'null cache'; } if ($query_string != "") { set $cache_uri 'null cache'; } # Don't cache uris containing the following segments if ($request_uri ~* "(/wp-admin/|/xmlrpc.php|/wp-(app|cron|login|register|mail).php|wp-.*.php|/feed/|index.php|wp-comments-popup.php|wp-links-opml.php|wp-locations.php|sitemap(_index)?.xml|[a-z0-9_-]+-sitemap([0-9]+)?.xml)") { set $cache_uri 'null cache'; } # Don't use the cache for logged in users or recent commenters if ($http_cookie ~* "comment_author|wordpress_[a-f0-9]+|wp-postpass|wordpress_logged_in") { set $cache_uri 'null cache'; } # START MOBILE # Mobile browsers section to server them non-cached version. COMMENTED by default as most modern wordpress themes including twenty-eleven are responsive. Uncomment config lines in this section if you want to use a plugin like WP-Touch # if ($http_x_wap_profile) { # set $cache_uri 'null cache'; #} #if ($http_profile) { # set $cache_uri 'null cache'; #} #if ($http_user_agent ~* (2.0\ MMP|240x320|400X240|AvantGo|BlackBerry|Blazer|Cellphone|Danger|DoCoMo|Elaine/3.0|EudoraWeb|Googlebot-Mobile|hiptop|IEMobile|KYOCERA/WX310K|LG/U990|MIDP-2.|MMEF20|MOT-V|NetFront|Newt|Nintendo\ Wii|Nitro|Nokia|Opera\ Mini|Palm|PlayStation\ Portable|portalmmm|Proxinet|ProxiNet|SHARP-TQ-GX10|SHG-i900|Small|SonyEricsson|Symbian\ OS|SymbianOS|TS21i-10|UP.Browser|UP.Link|webOS|Windows\ CE|WinWAP|YahooSeeker/M1A1-R2D2|iPhone|iPod|Android|BlackBerry9530|LG-TU915\ Obigo|LGE\ VX|webOS|Nokia5800)) { # set $cache_uri 'null cache'; #} #if ($http_user_agent ~* (w3c\ |w3c-|acs-|alav|alca|amoi|audi|avan|benq|bird|blac|blaz|brew|cell|cldc|cmd-|dang|doco|eric|hipt|htc_|inno|ipaq|ipod|jigs|kddi|keji|leno|lg-c|lg-d|lg-g|lge-|lg/u|maui|maxo|midp|mits|mmef|mobi|mot-|moto|mwbp|nec-|newt|noki|palm|pana|pant|phil|play|port|prox|qwap|sage|sams|sany|sch-|sec-|send|seri|sgh-|shar|sie-|siem|smal|smar|sony|sph-|symb|t-mo|teli|tim-|tosh|tsm-|upg1|upsi|vk-v|voda|wap-|wapa|wapi|wapp|wapr|webc|winw|winw|xda\ |xda-)) { # set $cache_uri 'null cache'; #} #END MOBILE # Use cached or actual file if they exists, otherwise pass request to WordPress location / { try_files /wp-content/cache/supercache/$http_host/$cache_uri/index.html $uri $uri/ /index.php?$args ; } Experimental modifications: If you are using HTTPS, the latest development version of WP Super Cache may use a different directory structure to differentiate between HTTP and HTTPS. try_files line may look like below: location / { try_files /wp-content/cache/supercache/$http_host/$cache_uri/index-https.html $uri $uri/ /index.php?$args ; } W3 Total Cache Rules W3 Total Cache uses different directory structure for disk-based cache storage depending on WordPress configuration. Cache validation checks will remain common as shown below: #W3 TOTAL CACHE CHECK set $cache_uri $request_uri; # POST requests and urls with a query string should always go to PHP if ($request_method = POST) { set $cache_uri 'null cache'; } if ($query_string != "") { set $cache_uri 'null cache'; } # Don't cache uris containing the following segments if ($request_uri ~* "(/wp-admin/|/xmlrpc.php|/wp-(app|cron|login|register|mail).php|wp-.*.php|/feed/|index.php|wp-comments-popup.php|wp-links-opml.php|wp-locations.php|sitemap(_index)?.xml|[a-z0-9_-]+-sitemap([0-9]+)?.xml)") { set $cache_uri 'null cache'; } # Don't use the cache for logged in users or recent commenters if ($http_cookie ~* "comment_author|wordpress_[a-f0-9]+|wp-postpass|wordpress_logged_in") { set $cache_uri 'null cache'; } #ADD mobile rules from WP SUPER CACHE section above #APPEND A CODE BLOCK FROM BELOW... FOR Normal WordPress (without Multisite) Use following: # Use cached or actual file if they exists, otherwise pass request to WordPress location / { try_files /wp-content/w3tc/pgcache/$cache_uri/_index.html $uri $uri/ /index.php?$args ; } FOR Multisite with subdirectories Use following: if ($request_uri ~* "^/([_0-9a-zA-Z-]+)/.*" ){ set $blog $1; } set $blog "${blog}."; if ( $blog = "blog." ){ set $blog ""; } # Use cached or actual file if they exists, otherwise pass request to WordPress location / { try_files /wp-content/w3tc-$blog$host/pgcache$cache_uri/_index.html $uri $uri/ /index.php?$args ; } FOR Multisite with Subdomains/Domain-mapping Use following: location / { try_files /wp-content/w3tc-$host/pgcache/$cache_uri/_index.html $uri $uri/ /index.php?$args; } Notes Nginx can handle gzip & browser cache automatically so better leave that part to nginx. W3 Total Cache Minify rules will work with above config without any issues. Nginx fastcgi_cache Nginx can perform caching on its own end to reduce load on your server. When you want to use Nginx's built-in fastcgi_cache, you better compile nginx with fastcgi_cache_purge module. It will help nginx purge cache for a page when it gets edited. On the WordPress side, you need to install a plugin like Nginx Helper to utilize fastcgi_cache_purge feature. For Ubuntu users, you can use launchpad repo by Brian Mercer to install/upgrade nginx with fastcgi_cache_purge support. Config will look like below: Define a Nginx cache zone in http{...} block, outside server{...} block #move next 3 lines to /etc/nginx/nginx.conf if you want to use fastcgi_cache across many sites fastcgi_cache_path /var/run/nginx-cache levels=1:2 keys_zone=WORDPRESS:500m inactive=60m; fastcgi_cache_key "$scheme$request_method$host$request_uri"; fastcgi_cache_use_stale error timeout invalid_header http_500; For wordpress site config, in server{..} block add a cache check block as follow #fastcgi_cache start set $no_cache 0; # POST requests and urls with a query string should always go to PHP if ($request_method = POST) { set $no_cache 1; } if ($query_string != "") { set $no_cache 1; } # Don't cache uris containing the following segments if ($request_uri ~* "(/wp-admin/|/xmlrpc.php|/wp-(app|cron|login|register|mail).php|wp-.*.php|/feed/|index.php|wp-comments-popup.php|wp-links-opml.php|wp-locations.php|sitemap(_index)?.xml|[a-z0-9_-]+-sitemap([0-9]+)?.xml)") { set $no_cache 1; } # Don't use the cache for logged in users or recent commenters if ($http_cookie ~* "comment_author|wordpress_[a-f0-9]+|wp-postpass|wordpress_no_cache|wordpress_logged_in") { set $no_cache 1; } Then make changes to PHP handling block Just add this to the following php block. Note the line fastcgi_cache_valid 200 60m; which tells nginx only to cache 200 responses(normal pages), which means that redirects are not cached. This is important for multilanguage sites where, if not implemented, nginx would cache the main url in one language instead of redirecting users to their respective content according to their language. fastcgi_cache_bypass $no_cache; fastcgi_no_cache $no_cache; fastcgi_cache WORDPRESS; fastcgi_cache_valid 200 60m; Such that it becomes something like this location ~ [^/]\.php(/|$) { fastcgi_split_path_info ^(.+?\.php)(/.*)$; if (!-f $document_root$fastcgi_script_name) { return 404; } # This is a robust solution for path info security issue and works with "cgi.fix_pathinfo = 1" in /etc/php.ini (default) include fastcgi.conf; fastcgi_index index.php; # fastcgi_intercept_errors on; fastcgi_pass php; fastcgi_cache_bypass $no_cache; fastcgi_no_cache $no_cache; fastcgi_cache WORDPRESS; fastcgi_cache_valid 200 60m; } Finally add a location for conditional purge location ~ /purge(/.*) { # Uncomment the following two lines to allow purge only from the webserver #allow 127.0.0.1; #deny all; fastcgi_cache_purge WORDPRESS "$scheme$request_method$host$1"; } If you get an 'unknown directive "fastcgi_cache_purge"' error check that your nginx installation has fastcgi_cache_purge module. Better Performance for Static Files in Multisite By default, on a Multisite setup, a static file request brings php into picture i.e. ms-files.php file. You can get much better performance using Nginx Map{..} directive. In nginx config for your site, above server{..} block, add a section as follows: map $http_host $blogid { default 0; example.com 1; site1.example.com 2; site1.com 2; } It is just a list of site-names and blog-ids. You can use Nginx helper to get such a list of site-name/blog-id pairs. This plugin will also generate a map.conf file which you can directly include in the map{} section like this: map $http_host $blogid { default 0; include /path/to/map.conf ; } After creating a map{..} section, you just need to make one more change in your Nginx config so requests for /files/ will be first processed using nginx map{..}: location ~ ^/files/(.*)$ { try_files /wp-content/blogs.dir/$blogid/$uri /wp-includes/ms-files.php?file=$1 ; access_log off; log_not_found off; expires max; } Notes Whenever a new site is created, deleted or an extra domain is mapped to an existing site, Nginx helper will update map.conf file automatically but you will still need to reload Nginx config manually. You can do that anytime later. Till then, only files for new sites will be served using php-fpm. This method does not generate any symbolic links. So, there will be no issues with accidental deletes or backup scripts that follow symbolic links. For large networks, this will scale-up nicely as there will be a single map.conf file. Notes A couple of final but important notes: This whole setup assumes that the root of the site is the blog and that all files that will be referenced reside on the host. If you put the blog in a subdirectory such as /blog, then the rules will have to be modified. Perhaps someone can take these rules and make it possible to, for instance, use a: set $wp_subdir "/blog"; directive in the main 'server' block and have it automagically apply to the generic WP rules. Warning A typo in Global restrictions file can create loopholes. To test if your "uploads" directory is really protected, create a PHP file with some content (example: ), upload it to "uploads" directory (or one of its sub-directories), then try to access (execute) it from your browser. Resources Reference nginx + php-fpm + PHP APC + WordPress multisite (subdirectory) + WP Super Cache (Thanks bigsite) Notes on removing 'index.php' from Permalinks (Can be done using Nginx Helper Plugin) External Links Nginx WordPress wiki page Nginx Full Example Nginx Full Example 2 LEMP guides on Linode's Library Various guides about Nginx on Linode's Library Lightning fast WordPress with Php-fpm and Nginx Virtual Hosts Examples List of 20+ WordPress-Nginx Tutorials for common situations An introduction to Nginx configuration A comprehensive blog series on hosting WordPress yourself using Nginx WordPress Installation CentminMod Nginx WordPress Installation Guide Scripts & Tools For WordPress Nginx scripted installation CentminMod can be used for CentOS. Linode users can use LEMP WordPress StackScript Script by Review Signal LEMP WordPress Script For wordpress-nginx based site management, EasyEngine can be used. EasyEngine is collection of shell scripts for Ubuntu. Securing Nginx Securing Nginx and PHP Setting up PHP-FastCGI and nginx? Don’t trust the tutorials: check your configuration! Backing Up Your Database atachibana — Sat, 23 Apr 2016 09:32:41 +0000 [codex_languages en="Backing Up Your Database" ja_codex="データベースのバックアップ" ptbr_codex="Backups do Banco de Dados" ru_codex="Создание резервной копии базы данных" th_codex="แบคอัพเวิร์ดเพรส" zh-hans_codex="备份数据库"] It is strongly recommended that you backup your database at regular intervals and before an upgrade. Restoring your database from backup is then possible if something goes wrong. NOTE: Below steps backup core WordPress database that include all your posts, pages and comments, but DO NOT backup the files and folders such as images, theme files on the server. For whole WordPress site backup, refer WordPress Backups. Backup using cPanel X cPanel is a popular control panel used by many web hosts. The backup feature can be used to backup your MySQL database. Do not generate a full backup, as these are strictly for archival purposes and cannot be restored via cPanel. Look for 'Download a MySQL Database Backup' and click the name of the database. A *.gz file will be downloaded to your local drive. There is no need to unzip this file to restore it. Using the same cPanel program, browse to the gz file and upload it. Once the upload is complete, the bottom of the browser will indicate dump complete. If you are uploading to a new host, you will need to recreate the database user along with the matching password. If you change the password, make the corresponding change in the wp-config.php file. Using phpMyAdmin phpMyAdmin is the name of the program used to manipulate your database. Information below has been tried and tested using phpMyAdmin version 4.4.13 connects to MySQL version 5.6.28 running on Linux. Quick backup process When you backup all tables in the WordPress database without compression, you can use simple method. To restore this backup, your new database should not have any tables. Log into phpMyAdmin on your server From left side window, select your WordPress database. In this example, the name of database is "wp". The right side window will show you all the tables inside your WordPress database. Click the 'Export' tab on the top set of tabs. Ensure that the Quick option is selected, and click 'Go' and you should be prompted for a file to download. Save the file to your computer. Depending on the database size, this may take a few moments. Custom backup process If you want to change default behavior, select Custom backup. In above Step 4, select Custom option. Detail options are displayed. The Table section All the tables in the database are selected. If you have other programs that use the database, then choose only those tables that correspond to your WordPress install. They will be the ones with that start with "wp_" or whatever 'table_prefix' you specified in your 'wp-config.php' file. If you only have your WordPress blog installed, leave it as is (or click 'Select All' if you changed the selection) The Output section Select 'zipped' or 'gzipped' from Compression box to compress the data. The Format section Ensure that the SQL is selected. Unlike CSV or other data formats, this option exports a sequence of SQL commands. The Format-specific options section Leave options as they are. The Object creation options section Select Add DROP TABLE / VIEW / PROCEDURE / FUNCTION / EVENT / TRIGGER statement. Before table creation on target database, it will call DROP statement to delete the old existing table if exist. The Data creation options section Leave options as they are. Now click 'Go' at the bottom of window and you should be prompted for a file to download. Save the file to your computer. Depending on the database size, this may take a few moments. Remember - you have NOT backed up the files and folders - such as images - but all your posts and comments are now safe. Using Straight MySQL/MariaDB Commands phpMyAdmin cannot handle large databases so using straight MySQL/MariaDB code will help. 1. Change your directory to the directory you want to export backup to: user@linux:~> cd files/blog user@linux:~/files/blog> 2. Use mysqldump command with your MySQL server name, user name and database name. It prompts you to input password. (For help, try: man mysqldump.) To backup all database tables mysqldump --add-drop-table -h mysql_hostserver -u mysql_username -p mysql_databasename To backup only certain tables from the database mysqldump --add-drop-table -h mysql_hostserver -u mysql_username -p mysql_databasename mysql_tablename1 mysql_tablename2 mysql_tablename3 Example: user@linux:~/files/blog> mysqldump --add-drop-table -h db01.example.net -u dbocodex -p wp > blog.bak.sql Enter password: (type password) 3. Use bzip2 to compress the backup file user@linux:~/files/blog> bzip2 blog.bak.sql You can do the same thing that above two commands do in one line: user@linux:~/files/blog> mysqldump --add-drop-table -h db01.example.net -u dbocodex -p wp | bzip2 -c > blog.bak.sql.bz2 Enter password: (type password) The bzip2 -c after the | (pipe) means the backup is compressed on the fly, and the > blog.bak.sql.bz2 sends the bzip output to a file named blog.bak.sql.bz2. Despite bzip2 being able to compress most files more effectively than the older compression algorithms (.Z, .zip, .gz), it is considerably slower (compression and decompression). If you have a large database to backup, gzip is a faster option to use. user@linux:~/files/blog> mysqldump --add-drop-table -h db01.example.net -u dbocodex -p wp | gzip > blog.bak.sql.gz Using MySQL Workbench MySQL Workbench (formerly known as My SQL Administrator) is a program for performing administrative operations, such as configuring your MySQL server, monitoring its status and performance, starting and stopping it, managing users and connections, performing backups, restoring backups and a number of other administrative tasks. You can perform most of those tasks using a command line interface such as that provided by mysqladmin or mysql, but MySQL Workbench is advantageous in the following respects: Its graphical user interface makes it more intuitive to use. It provides a better overview of the settings that are crucial for the performance, reliability, and security of your MySQL servers. It displays performance indicators graphically, thus making it easier to determine and tune server settings. It is available for Linux, Windows and MacOS X, and allows a remote client to backup the database across platforms. As long as you have access to the MySQL databases on the remote server, you can backup your data to wherever you have write access. There is no limit to the size of the database to be backed up as there is with phpMyAdmin. Information below has been tried and tested using MySQL Workbench version 6.3.6 connects to MySQL version 5.6.28 running on Linux. Backing Up the Database This assumes you have already installed MySQL Workbench and set it up so that you can login to the MySQL Database Server either locally or remotely. Refer to the documentation that comes with the installation package of MySQL Workbench for your platform for installation instructions or online document. Launch the MySQL Workbench Click your database instance if it is displayed on the top page. Or, Click Database -> Connect Database from top menu, enter required information and Click OK. Click Data Export in left side window. Select your WordPress databases that you want to backup. Specify target directory on Export Options. You need write permissions in the directory to which you are writing the backup Click Start Export on the lower right of the window. Restoring From a Backup Launch the MySQL Workbench Click your database instance if it is displayed on the top page. Or, Click Database -> Connect Database, and Click OK. Click Data Import/Restore in left side window. Specify folder where you have backup files. Click "..." at the right of Import from Dump Project Folder, select backup folder, and click Open Click Start Import on the lower right of the window. The database restore will commence. MySQL GUI Tools In addition to MySQL Workbench, there are many GUI tools that let you backup (export) your database. Name OS (Paid edition) OS (Free edition) Notes MySQL Workbench Windows/Mac/Linux Windows/Mac/Linux See above EMS SQL Management Studio for MySQL Windows - Aqua Data Studio Windows/Mac/Linux Windows/Mac/Linux (14 days trial) Available in 9 languages Navicat for MySQL Windows/Mac/Linux Windows/Mac/Linux (14 days trial) Available in 8 languages SQLyog Windows - Toad for MySQL - Windows HeidiSQL - Windows Sequel Pro Mac CocoaMySQL successor Querious - Mac Using WordPress Database Backup Plugin Austin Matzko maintains a WordPress plugin originally created by Skippy called WordPress Database Backup (WP-DB-Backup). It was bundled with WordPress 2.0 but is no longer included with WordPress. Installation Search "WP-DB-Backup" on Administration > Plugins > Add New. Click Install Now. Activate the plugin. Backing up Navigate to Administration > Tools > Backup Core WordPress tables will always be backed up. Select some options from Tables section. Select the Backup Options; the backup can be downloaded, or emailed. Finally, click on the Backup Now! button to actually perform the backup. You can also schedule regular backups. Restoring the Data The file created is a standard SQL file. If you want information about how to upload that file, look at Restoring Your Database From Backup. More Resources Backup Plugins on the official WordPress.org repository Restoring Your Database From Backup WordPress Backups External Resources How to Schedule Daily Backup of WordPress Database Using FileZilla atachibana — Sat, 23 Apr 2016 13:02:30 +0000 FileZilla is an open-source FTP-client and FTP-server developed by Tim Kosse (Germany) et.al. The FTP-client is available for multiple platforms such as Windows, Linux and Mac OS X, and the FTP-server is available for Windows only. FileZilla FTP-client may be used to manage your WordPress site by uploading and downloading files and images. This article will guide you through the process of installing and using FileZilla FTP-client to manage your WordPress site. For more information about FileZilla, view the list of features at the official site. Why would I want to download FileZilla? It's fast, stable, easy to use, and free. FTP is a standard way to upload or download files between your local system and your web server, and FileZilla is a solid client for everyday FTP needs. Setting Up the Options You will need the following details regarding the FTP account on your server: Your website ftp address (usually ftp://example.com if your URL is http://example.com) Your ftp username Your ftp password If you do not already have an FTP account on your server, use your cPanel or website administration tool to set one up -- it will have all the information needed. If in doubt, ask your host for directions or help regarding an FTP account for your use to access your webspace. Before connecting the FTP server, you should register it in the Site Manager. Once you register it, you just one click to connect the same server. To register the FTP server, follow below steps: Click File > Site Manager from FileZilla main window. Click New Site then name the new connection to what you want (example: My blog server). Enter the ftp address for your website in Host box. Usually, if your website is http://www.example.com, then the ftp address will be ftp://ftp.example.com or ftp://example.com. Note: Do not put a / at the end unless specifically told to do so on your cPanel or by your host. Leave the Port box blank. Default value 21 should be used. Only change these if your FTP account details explicitly indicate that you should. Select Normal from Logon Type box Enter the full username that you have been given in User box. It may be just a username, or it may look like an email address (but it isn't one). For instance, it would look similar to user or user@example.com. Enter password. Remember that the password might be case sensitive. Click OK. Connecting In the Toolbar of FileZilla main window, Select the down arrow of most left icon "Open the Site Manager", and select your FTP server from drop down list. Or, start Site Manager from File > Site Manager, select your FTP server and click 'Connect'. If all is well, then in the top window of FileZilla, you will have seen a series of messages, and in the large window, you will see a listing of the files will appear. Troubleshooting If you had a problem, then it is time to go troubleshooting! Look at the top area of FileZilla main window and check the messages. If there was no attempt to connect, then the ftp address is wrong. All it needs is one character to be incorrect and it will fail. Click the red X, break the connection and click the Site Manager to check what you entered. If it says that the user does not exist or Incorrect Login and so on, check the Site Manager setting and ensure that it reflects what your FTP account and password details provided by your host says, or use the webserver administration interface provided to you by your host to re-check the existence of the FTP account. Check your password carefully. It is case sensitive(capitals and small letters). You may want to ask your web host for some assistance, too. If it says Could not retrieve directory listing you may need to change the Transfer Setting. From Site Manager, select your FTP Server and click Transfer Settings' tab. Select Passive''' from Transfer mode and click OK. Resources Set Code Editor To Open Files in FileZilla >> NEXT: Next Page : Uploading WordPress to a remote host Installing Multiple WordPress atachibana — Sat, 23 Apr 2016 13:23:56 +0000 If you need multiple WordPress instances, there are three types of installations divided by System architecture or combination of WordPress and database. Using WordPress' Multisite feature, Single WordPress instance with Single database installation. Multiple WordPress instances with Single database installation. Multiple WordPress instances with Multiple databases installation. At first, let's see the 3rd one "Multiple WordPress instances with Multiple databases" because it is the same installing process with the single WordPress site except the number of sites. Multiple WordPress instances with Multiple databases You'll need a separate MySQL database for each blog you plan to install. If you have not yet created these, basic instructions are found here. The wp-config.php file will vary for each installation. The lines to change are: define('DB_NAME', 'wordpress'); // The name of the database define('DB_USER', 'username'); // Your MySQL username define('DB_PASSWORD', 'password'); // ...and password DB_NAME will be the name of the individual database created for that blog. If you are using different user logins for each database, edit DB_USER and DB_PASSWORD to reflect this, as well. Upload each wp-config.php file to its specific root/installation directory, and run the installation. See Installing WordPress for more information. Multisite feature If you want multiple sites using WordPress, you can use multisite feature to create what was referred to as a 'Network' of sites. Multisite feature install single WordPress and database. Multisite feature seems to be simpler than other multiple WordPress installation, but there are some considerations and restrictions. Refer following documents for more detail information: Before You Create A Network Create A Network Multisite Network Administration Multiple WordPress instances with Single database As with the multiple databases solution described above, the wp-config.php file will vary for each installation. In this case, however, only a single line will be unique to each blog: $table_prefix = 'wp_'; // example: 'wp_' or 'b2' or 'mylogin_' By default, WordPress assigns the table prefix wp_ to its MySQL database tables, but this prefix can be anything you choose. By using more than one, you create unique identifiers for each blog in your database. For example, let's say you have three blogs to set up, with the names Main, Projects and Test. You want to substitute the prefix wp_ for each blog's wp-config.php: Main blog: $table_prefix = 'main_'; Projects blog: $table_prefix = 'projects_'; Test blog: $table_prefix = 'test_'; As noted, you may use a prefix of your own making. Those provided here are for example purposes only. Upload each wp-config.php file to its specific root/installation directory, and run the installation. See Installing WordPress for more information. Multiple Databases, Same Users You can use the same userbase with all your blogs on the same domain, by defining the CUSTOM_USER_TABLE and optionally the CUSTOM_USER_META_TABLE constants to point to the same wp_your_blog_users and wp_your_blog_usermeta tables. See Editing wp-config.php/Custom User and Usermeta Tables. Updating WordPress alt3red — Mon, 25 Apr 2016 17:08:58 +0000 WARNING: The upgrade process will affect all files and folders included in the main WordPress installation. This includes all the core files used to run WordPress. If you have made any modifications to those files, your changes will be lost. You should always update WordPress to the latest version. When a new version of WordPress is available you will receive an update message in your WordPress Admin Screens. To update WordPress, click the link in this message. There are two methods for updating - the easiest is the one-click update, which will work for most people. If it doesn't work, or you just prefer to be more hands-on, you can follow the manual update process. If you are updating across multiple versions, follow the procedure at Upgrading WordPress - Extended Instructions Contents 1 Back up WordPress 2 Automatic Background Updates 3 One-click Update 3.1 File Ownership 3.2 Failed Updates 4 Manual Update 4.1 Step 1: Replace WordPress files 4.2 Step 1.5: Remove .maintenance file 4.3 Step 2: Update your installation 4.4 Step 3: Do something nice for yourself 5 Final Steps 6 Troubleshooting 6.1 Other options Back up WordPress Before you get started, it's a good idea to back up your website. This means if there are any issues you can restore your website. Complete instructions to make a backup can be found in the WordPress Backups section of the Codex. Automatic Background Updates For WordPress 3.7+, you don’t have to lift a finger to apply minor and security updates. Most sites are now able to automatically apply these updates in the background. If your site is capable of one-click updates without entering FTP credentials, then your site should be able to update from 3.7 to 3.7.1, 3.7.2, etc. (You’ll still need to click “Update Now” for major feature releases.) See Also: Configuring Automatic Background Updates One-click Update Modern versions of WordPress let you update with the click of a button. (This feature was added in 2.7, so if you are using an older version, you will need to follow the steps to update manually.) You can launch the update by clicking the link in the new version banner (if it's there) or by going to the Dashboard > Updates screen. Once you are on the "Update WordPress" page, click the button "Update Now" to start the process off. You shouldn't need to do anything else and, once it's finished, you will be up-to-date. One-click updates work on most servers. If you have any problems, it is probably related to permissions issues on the filesystem. File Ownership WordPress determines what method it will use to connect to the filesystem of your server based on the file ownership of your WordPress files. If the files are owned by the owner of the current process (i.e., the user under which the web server is running), and new files created by WordPress will also be owned by that user, WordPress will directly modify the files all by itself, without asking you for credentials. WordPress won't attempt to create the new files directly if they won't have the correct ownership. Instead, you will be shown a dialog box asking for connection credentials. It is typical for the files to be owned by the FTP account that originally uploaded them. To perform the update, you just need to fill in the connection credentials for that FTP account. Whether your files are owned by the web server user, or not, will depend on how you installed WordPress and how your server is configured. On some shared hosting platforms, it is a security risk for the files to be owned by the web server user and not a FTP user. See the tutorial on Changing File Permissions for more information, including how to configure file permissions so that multiple FTP users are able to edit the files. Failed Updates If you see a "failed update" nag message, delete the file .maintenance from your WordPress directory using FTP. This will remove the "failed update" nag message. If the one-click upgrade doesn't work for you, don't panic! Just try a manual update. Manual Update These are the short instructions, if you want more check out the extended upgrade instructions. If you experience problems with the Three Step Update, you may want to review the more detailed upgrade instructions For these instructions, it is assumed that your blog's URL is http://example.com/wordpress/. Step 1: Replace WordPress files Get the latest WordPress zip (or tar.gz) file. Unpack the zip file that you downloaded. Deactivate plugins. Delete the old wp-includes and wp-admin directories on your web host (through your FTP or shell access). Using FTP or your shell access, upload the new wp-includes and wp-admin directories to your web host, in place of the previously deleted directories. Upload the individual files from the new wp-content folder to your existing wp-content folder, overwriting existing files. Do NOT delete your existing wp-content folder. Do NOT delete any files or folders in your existing wp-content directory (except for the one being overwritten by new files). Upload all new loose files from the root directory of the new version to your existing wordpress root directory. NOTE - you should replace all the old WordPress files with the new ones in the wp-includes and wp-admin directories and sub-directories, and in the root directory (such as index.php, wp-login.php and so on). Don't worry - your wp-config.php will be safe. Be careful when you come to copying the wp-content directory. You should make sure that you only copy the files from inside this directory, rather than replacing your entire wp-content directory. This is where your themes and plugins live, so you will want to keep them. If you have customized the default or classic themes without renaming them, make sure not to overwrite those files, otherwise you will lose your changes. (Though you might want to compare them for new features or fixes..) Lastly you should take a look at the wp-config-sample.php file, to see if any new settings have been introduced that you might want to add to your own wp-config.php. Step 1.5: Remove .maintenance file If you're upgrading manually after a failed auto-upgrade, delete the file .maintenance from your WordPress directory using FTP. This will remove the "failed update" nag message. Step 2: Update your installation Visit your main WordPress admin page at /wp-admin. You may be asked to login again. If a database upgrade is necessary at this point, WordPress will detect it and give you a link to a URL like http://example.com/wordpress/wp-admin/upgrade.php. Follow that link and follow the instructions. This will update your database to be compatible with the latest code. You should do this as soon as possible after step 1. Don't forget to reactivate plugins! Step 3: Do something nice for yourself If you have caching enabled, clear the cache at this point so the changes will go live immediately. Otherwise, visitors to your site (including you) will continue to see the old version (until the cache updates). Your WordPress installation is successfully updated. That's as simple as we can make it without Updating WordPress Using Subversion. Consider rewarding yourself with a blog post about the update, reading that book or article you've been putting off, or simply sitting back for a few moments and letting the world pass you by. Final Steps Your update is now complete, so you can go in and enable your Plugins again. If you have issues with logging in, try clearing cookies in your browser. Troubleshooting If anything has gone wrong, then the first thing to do is go through all the steps in our extended upgrade instructions. That page also has information about some of the most common problems we see. If you run into a request for FTP credentials with trying to update WP on a IIS server automatically, it may well be a matter of rights. Go into the IIS Management Console, and there to the application pool of your blog. In its advanced settings, change the Process Model Id into LocalSystem. Then on Sites, choose your blog, right click, click on Edit permissions and on security tab add authenticated users. That should do it. If you experience problems after the upgrade, you can always restore your backup and replace the files with ones from your previous version from the release archive. Other options If you have some knowledge of unix shells you should check out wp-cli. Upgrading WordPress - Extended Instructions alt3red — Mon, 25 Apr 2016 17:18:02 +0000 This page contains a more detailed version of the upgrade instructions. Detailed Instructions Overview of the Upgrade Process Backup your database. Read Backing Up Your Database for a detailed explanation. Backup ALL your WordPress files in your WordPress directory. Don't forget your .htaccess file. Verify the backups you created are there and usable. This is essential. Deactivate ALL your Plugins. Ensure first four steps are completed. Do not attempt the upgrade unless you have completed the first four steps. Download and extract the WordPress package from http://wordpress.org/download/. Delete the old WordPress files on your site, but DO NOT DELETE *wp-config.php file; *wp-content folder; Special Exception: the wp-content/cache and the wp-content/plugins/widgets folders should be deleted. *wp-images folder; *wp-includes/languages/ folder--if you are using a language file do not delete that folder; *.htaccess file--if you have added custom rules to your .htaccess, do not delete it; *robots.txt file--if your blog lives in the root of your site (ie. the blog is the site) and you have created such a file, do not delete it. Upload the new files from your computer's hard drive to the appropriate WordPress folder on your site. Run the WordPress upgrade program and follow the instructions on the screen. Update Permalinks and .htaccess. Update your Permalink Structure and merge the custom rules, if necessary, into your .htaccess file. Install updated Plugins and Themes. Please review the list of Plugins that work in Version {{CurrentVersion}}. Check for Theme Compatibility with {{CurrentVersion}} and ask your Theme author for any new version. Reactivate Plugins Add security key definitions to the wp-config.php file Review what has changed in WordPress. That's the overview of the upgrade process. Please continue reading the Detailed Upgrade Instructions. Remember, if you do encounter problems, re-read the Instructions below to insure you've followed the proper procedures and consult Troubleshooting: Common Installation Problems. Upgrading Across Multiple Versions While the methodology given below is the "safe" approach, as long as you have proper backups, then it is indeed possible to upgrade directly from the very first version of WordPress to the very latest version in one-easy-step. WordPress does support this process, and WordPress is extremely backwards compatible in this respect. That said, if you have a large site, the upgrade process may take longer than expected, in which case an incremental approach may help. Just remember to retain a backup of a working site so that you always have a fallback position. If you plan on upgrading across more than two major releases, you should consider upgrading incrementally to avoid potential conflicts and minimize the risks of database damage. For example, if you plan on upgrading from 2.5 to {{CurrentVersion}}, upgrade to 2.7 first, followed by 2.9, then 3.1, and so on. Essentially, it's okay to skip one release, but never skip TWO when upgrading. Older versions of WordPress can be downloaded from the release archive. Please note that WordPress 3.7 introduced an easy to use one-button updater which will take you directly to {{CurrentVersion}}. This update step is safe, and it is possible to one-click update from 3.7 to any later version. Step 1: Back up your database Perform a backup of your database. All of your WordPress data, such as Users, Posts, Pages, Links, and Categories, are stored in your MySQL database. Please read Backing Up Your Database for a detailed explanation of this process. It is extremely important to back up your database before beginning the upgrade. If, for some reason, you find it necessary to revert back to the 'old' version of WordPress, you may have to restore your database from these backups. Step 2: Back up ALL your WordPress files Back up ALL of your files in your WordPress directory and your .htaccess file. Typically, this process involves using an FTP program to download ALL your WordPress files from your host to your local computer. Please read Backing Up Your WordPress Site for further explanation. If you have made changes to any core WordPress files, or if you've got customized Plugins or Themes, you will want to have a good backup of those files. It is extremely important to back up your files before beginning the upgrade. If for some reason you find it necessary to revert back to the 'old' version of WordPress you will need to upload these files. Step 3: Verify the backups Verify that the backups you created are there and usable. This is the most important step in the upgrade process! The verification process involves making sure you can see the backup files on your local computer (or wherever you've stored them) and that you can navigate into any sub-folders. If the files are in a zip file, make sure you can open the zip file. Also consider opening a .sql file in an editor to see if the tables and data are represented. Step 4: Deactivate ALL your Plugins In your Administration Screen, under the Plugins choice, deactivate any Plugins. Because of the changes to WordPress, some Plugins may conflict with the upgrade process. If you're not able to access the administrative menus you can deactivate all plugins by resetting the plugins folder. Step 5: Ensure first four steps are completed If you have not completed the first four procedures, STOP, and do them! Do not attempt the upgrade unless you have completed the first four steps. The best resource for problems with your upgrade is the WordPress Support Forums, and if you have problems, the volunteers at the WordPress Support Forums will likely ask if you have completed the first four steps. Step 6: Download and extract the WordPress package Download and unzip the WordPress package from https://wordpress.org/download/. If you will be uploading WordPress to a remote web server, download the WordPress package to your computer with your favorite web browser and unzip the package. If you have shell access to your web server, and are comfortable using console-based tools, you may wish to download WordPress directly to your web server. You can do so using wget , lynx or another console-based web browser, which are valuable if you want to avoid FTPing. Place the package in a directory parallel to your current wordpress directory (like "uploads," for example). Then, unzip it using: gunzip -c wordpress-{{CurrentVersion}}.tar.gz | tar -xf - or by using: tar -xzvf latest.tar.gz The WordPress package will be extracted into a folder called wordpress. Step 7: Delete the old WordPress files Why Delete? Generally, it is a good idea to delete whatever is possible because the uploading (or upgrading through cPanel) process may not correctly overwrite an existing file and that may cause problems later. DO NOT DELETE these folders and files: wp-config.php file; wp-content folder; wp-includes/languages/ folder--if you are using a language file, and it is here rather than in wp-content/languages/, do not delete this folder (you might want to move your language files to wp-content/languages/ for easier upgrading in the future);. .htaccess file--if you have added custom rules to your .htaccess, do not delete it; Custom Content and/or Plugins--if you have any images or other custom content or Plugins inside the wp-content folder, do NOT delete them. Delete these Files and Folders: wp-* (except for those above), readme.html, wp.php, xmlrpc.php, and license.txt; files; Typically files in your root or wordpress folder. Again, don't delete the wp-config.php file. Note: some files such as wp.php may not exist in later versions such as 2.7. wp-admin folder; wp-includes folder; If you have a language file here, remember not to delete the wp-includes/languages/ folder wp-content/cache folder; You only see this folder if you are upgrading FROM WordPress 2.0. wp-content/plugins/widgets folder; You only see this folder if you previously installed the Sidebar Widgets plugin. The Sidebar Widgets code conflicts with the built-in widget ability. How to Delete? There are several ways to delete the files from your WordPress site. You can use your FTP Client, or if you have access to Telenet or SSH you can use that. Some host providers also provide the ability to delete files and folders. Using FTP to delete files and folders The same FTP client you use for uploading can be used to delete files and folders. If your FTP client does not appear to permit you to delete non-empty folders, check the available options for your FTP client. You'll usually find an option that permits deleting non-empty folders. Deleting non-empty folders is a quick and thorough method cleaning out an old installation of WordPress. It is recommended that once the deleting is done, you switch back to the original setting for safety reasons. Using Telnet or SSH to delete file If you have a command-line login (telnet or ssh), you can enter the following commands to make backup copies of the files you need to keep and to delete ONLY the wordpress files in your directory (plus .htaccess). If you've customized other files (like index.php) not included by the cp commands below, copy them as well: * mkdir backup * cp wp-config.php .htaccess backup * cp -R wp-content backup * rm wp*.php .htaccess license.txt readme.html xmlrpc.php * rm -rf wp-admin wp-includes * cp backup/wp-config.php . * After you have finished with the upgrade, you can restore any customizations to your templates or plugins from your backup directory. For example, use cp backup/index.php . to restore index.php. Alternatively, using SSH, you could copy wp-config.php, .htaccess, and any content files you've added or altered into the new wordpress directory. Then, rename the old one (to archive it), and move the new one into its place. Step 8: Upload the new files With the new upgrade on your local computer, and using FTP, upload the new files to your site server just as you did when you first installed WordPress. See Using FileZilla and Uploading WordPress to a remote host for detailed guidelines in using an FTP Client to upload. NOTE: If you did not delete the wp-content folder, you will need to overwrite some files during the upload. The wp-content folder holds your WordPress Themes and Plugins. These should remain. Upload everything else first, then upload only those WordPress files that are new or changed to your new wp-content folder. Overwrite any old versions of default plugins with the new ones. The WordPress default theme has changed so you will want to upload the wp-content/themes/default folder. If you have custom changes to the default theme, those changes will need to be reviewed and installed after the upgrade. Step 9: Run the WordPress upgrade program Using a web browser, go to the WordPress admin pages at the normal /wp-admin location. WordPress will check to see if a database upgrade is necessary, and if it is, it will give you a new link to follow. This link will lead you to run the WordPress upgrade script by accessing wp-admin/upgrade.php. Follow the instructions presented on your screen. Note: Make sure the database user name registered to WordPress has permission to create, modify, and delete database tables before you do this step. If you installed WordPress in the standard way, and nothing has changed since then, you are fine. If you want to run the upgrade script manually: If WordPress is installed in the root directory, point your browser to: http://example.com/wp-admin/upgrade.php If WordPress is installed in its own subdirectory called blog, for example, point your browser to: http://example.com/blog/wp-admin/upgrade.php If you experience difficulties with login after your upgrade, it is worth clearing your browser's cookies. Step 10: Update Permalinks and .htaccess In your Administration Screen > Settings > Permalinks screen update your Permalink Structure and, if necessary, place the rules in your .htaccess file. Also see Using Permalinks for details regarding Permalinks and the .htaccess file. Step 11: Install updated Plugins and Themes Please review the Plugin Compatibility List and Theme Compatibility List, or plugin/theme authors, to find plugins and themes compatible with your new WordPress version. Upload and install new versions of your Plugins and Themes, if necessary. Step 12: Reactivate Plugins Use your Administration Screen, Plugins, to activate your Plugins. If your plugins do not appear on the Plugin Compatibility List and you are not sure if they will work correctly with the new version, activate each plugin, one at a time, and test that there are no problems before continuing. Step 13: Add security key definitions to the ''wp-config.php'' file Beginning with WordPress Version 2.6, three (3) security keys, AUTH_KEY, SECURE_AUTH_KEY, and LOGGED_IN_KEY, are used to insure better encryption of information stored in the user's cookies. Beginning with Version 2.7 a fourth key, NONCE_KEY, was added to this group. If you don't find the keys in your wp-config.php file, add the keys definitions with reference to Editing wp-config.php - Security Keys, and upload to your server. Step 14: Review what has changed in WordPress Please review these resources to see what's new in WordPress: Version {{CurrentVersion}} Details Complete version history including Development News Special note for Fantastico Upgrades When using the Fantastico upgrade process to upgrade from a pre-Version 2.2, Fantastico will use the wp-config-sample.php file to regenerate a new wp-config.php file. By doing this, two new values, DB_CHARSET and DB_COLLATE, are placed into the wp-config.php file. Those lines should be deleted from your wp-config.php if you are upgrading from a pre-Version 2.2 (like 2.0.10 or 2.1.3) to Version {{CurrentVersion}}. A detailed explanation about DB_CHARSET and DB_COLLATE can be found in Editing wp-config.php. Troubleshooting Scrambled Layout or Errors If your blog looks scrambled now or features line errors, an old plugin that doesn't work with the new code may be the culprit. In your WordPress Administration Screen, deactivate all plugins that do not come with WordPress by default. Re-activate them one by one. Made Custom Changes/Hacks? If you have made changes to other WordPress files ("hacked" WordPress), you are supposed to keep track of your changes. You will have to transfer your edits into the new code. WordPress Versions lists the files that have changed in each release. Resist Using Old Code Upgrading gives you the newest and best code. Using your old code, no matter how much you have customised it, almost certainly will cause problems. The temptation just to use your old modified code will be great, but the chances of errors are much greater. Can I Go Back to Old Versions You can, but it is usually not recommended to rollback (revert) your current version to an older version. That is because newer versions often include security updates and a rollback may put your site at risk. Second, the change between the database structure between versions may cause complications in maintaining your site content, posts, comments, and plugins that are dependent upon the information stored in the database. If you are still intent on this, proceed at your own risk. Please note, that without a backup of your entire site and your database, made prior to your upgrade attempt, a successful rollback is near impossible. Delete all WordPress files except for wp-config. Upload the files from your backup to your server and restore your database backup. Remember, you must have good backups for the rollback to work. For older WordPress versions, a rollback might not work. Get More Help If you get any errors following an upgrade, check Troubleshooting: Common Installation Problems, Troubleshooting, and the Codex Installation Category of Articles. If you can't find an answer, post a clear question on the WordPress Suppport Forums. You will be asked if you have used any old code. You'll be told to change it then, so you may as well change it now :) Custom Backgrounds hardeepasrani — Tue, 26 Apr 2016 16:51:59 +0000 [codex_languages en="Custom Backgrounds" ja_codex="Custom Backgrounds"] Custom Backgrounds is a theme feature that provides for customization of the background color and image. Adding Theme Support Since Version 3.4, themes need to use add_theme_support() in the functions.php file to support custom backgrounds, like so: add_theme_support( 'custom-background' ); Note that you can add default arguments using: $defaults = array( 'default-color' => '', 'default-image' => '', 'default-repeat' => '', 'default-position-x' => '', 'default-attachment' => '', 'wp-head-callback' => '_custom_background_cb', 'admin-head-callback' => '', 'admin-preview-callback' => '' ); add_theme_support( 'custom-background', $defaults ); Example An example using default '#000000' background color with 'background.jpg' background image: $args = array( 'default-color' => '000000', 'default-image' => '%1$s/images/background.jpg', ); add_theme_support( 'custom-background', $args ); Outcome The purpose of this call to add_theme_support() is to enable the Custom Background screen in the administrator's Appearance menu. It also serves as a declaration that the theme has properly implemented the body_class() and wp_head() template tags to provide feature compatibility. When the administrator sets custom values for the theme, WordPress generates an extra style sheet in-line with the HTML headers, usually right before the end of the document's HEAD element. The extra style sheet overrides the background values from the theme's style sheet. Example output: Note that setting the default-image parameter will instantly cause that value to become the effective Custom Background, whereas setting the default-color has no effect until the administrator visits the Custom Background page. To override this default behavior, you would have to provide a replacement for the _custom_background_cb() function. Backwards Compatibility To add backwards compatibility for older versions, use the following code: global $wp_version; if ( version_compare( $wp_version, '3.4', '>=' ) ) : add_theme_support( 'custom-background' ); else : add_custom_background( $args ); endif; Note: As we're now beyond the release WordPress 3.6, providing backwards compatibility for any version prior to 3.4 will be a violation of the Theme Review guidelines. Resources WordPress Theme Support Generator Related Theme Development Administration Over SSL atachibana — Fri, 29 Apr 2016 03:01:48 +0000 To easily enable (and enforce) WordPress administration over SSL, there are two constants that you can define in your site's wp-config.php file. It is not sufficient to define these constants in a plugin file; they must be defined in your wp-config.php file. You must also already have SSL configured on the server and a (virtual) host configured for the secure server before your site will work properly with these constants set to true. Note: FORCE_SSL_LOGIN was deprecated in Version 4.0. Please use FORCE_SSL_ADMIN. To Force SSL Logins and SSL Admin Access The constant FORCE_SSL_ADMIN can be set to true in the wp-config.php file to force all logins and all admin sessions to happen over SSL. Example define('FORCE_SSL_ADMIN', true); Using a Reverse Proxy If WordPress is hosted behind a reverse proxy that provides SSL, but is hosted itself without SSL, these options will initially send any requests into an infinite redirect loop. To avoid this, you may configure WordPress to recognize the HTTP_X_FORWARDED_PROTO header (assuming you have properly configured the reverse proxy to set that header). Example define('FORCE_SSL_ADMIN', true); // in some setups HTTP_X_FORWARDED_PROTO might contain // a comma-separated list e.g. http,https // so check for https existence if (strpos($_SERVER['HTTP_X_FORWARDED_PROTO'], 'https') !== false) $_SERVER['HTTPS']='on'; Further Information The rest of this article serves as information in case you're using an older version of WordPress (which ideally you shouldn't!) or your SSL setup is somewhat different (ie. your SSL certificate is for a different domain). Sometimes, you want your whole wp-admin to run over a secure connection using the https protocol. Conceptually, the procedure works like this: Set up two virtual hosts with the same url (the blog url), one secure, the other not. On the secure virtual host, set up a rewrite rule that shuttles all non-wp-admin traffic to the insecure site. On the insecure virtual host, set up a rewrite rule that shuttles all traffic to wp-admin to the secure host. Put in a filter (via a plugin) that filters the links in wp-admin so that once activated, administrative links are rewritten to use https and that edits cookies to work only over encrypted connections. The following guide is for WordPress 1.5 and Apache running mod_rewrite, using rewrite rules in httpd.conf (as opposed to .htaccess files) but could easily be modified to fit other hosting scenarios. Virtual Hosts You need a (virtual) host configured for the secure server in addition to the non-secure site. In this example, the secure virtual host uses the same DocumentRoot as the insecure host. Hypothetically, you could use a host with a different name, such as wpadmin.mysite.com and link the document root to the wpadmin directory. Please ask your ISP to set up a secure virtual host for you, or if you have administrative access set up your own. Note that you cannot use name based virtual hosting to identify different SSL servers. Rewrite Rules For The Insecure Host In the .htaccess or virtual host stanza in httpd.conf for your insecure host, add this rewrite rule to automatically go to the secure host when you browse to http://mysite.com/wp-admin/ or http://mysite.com/wp-login.php This should go above the main wordpress rewrite block. RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /(.*)\ HTTP/ [NC] RewriteCond %{HTTPS} !=on [NC] RewriteRule ^/?(wp-admin/|wp-login\.php) https://mysite.com%{REQUEST_URI}%{QUERY_STRING} [R=301,QSA,L] If you are using permalink rewrite rules, this line must come before RewriteRule ^.*$ - [S=40]. An important idea in this block is using THE_REQUEST, which ensures only actual http requests are rewritten and not local direct file requests, like an include or fopen. Rewrite Rules For Secure Host (Optional) These rewrite rules are optional. They disable access to the public site over a secure connection. If you wish to remain logged in to the public portion of your site using the plugin below, you must not add these rules, as the plugin disables the cookie over unencrypted connections. The secure virtual host should have two rewrite rules in an .htaccess file or in the virtual host declaration (see Using Permalinks for more on rewriting): RewriteRule !^/wp-admin/(.*) - [C] RewriteRule ^/(.*) http://www.mysite.com/$1 [QSA,L] The first rule excludes the wp-admin directory from the next rule, which shuffles traffic to the secure site over to the insecure site, to keep things nice and seamless for your audience. Setting WordPress URI For some plugins to work, and for other reasons, you may wish to set your WordPress URI in options to reflect the https protocol by making this setting https://mysite.com. Your blog address should not change. Example Config Stanzas NOTE: The below config is not 100% compatible with WordPress 2.8+, WordPress 2.8 uses some files from the wp-includes folder. The redirection that the first set of Rewrite rules introduces may cause security warnings for some users. See http://core.trac.wordpress.org/ticket/10079 for more information. ServerName www.mysite.com SSLEngine On SSLCertificateFile /etc/apache2/ssl/thissite.crt SSLCertificateKeyFile /etc/apache2/ssl/thissite.pem SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown DocumentRoot /var/www/mysite RewriteEngine On RewriteRule !^/wp-(admin|includes)/(.*) - [C] RewriteRule ^/(.*) http://www.mysite.com/$1 [QSA,L] ... # Insecure site ServerName www.mysite.com DocumentRoot /var/www/ii/mysite RewriteEngine On RewriteBase / RewriteCond %{REQUEST_FILENAME} -f [OR] RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^wp-admin/(.*) https://www.mysite.com/wp-admin/$1 [C] RewriteRule ^.*$ - [S=40] RewriteRule ^feed/(feed|rdf|rss|rss2|atom)/?$ /index.php?&feed=$1 [QSA,L] ... ... Rewrite for Login and Registration It is probably a good idea to utilize SSL for user logins and registrations. Consider the following substitute RewriteRules. Insecure RewriteRule ^/wp-(admin|login|register)(.*) https://www.mysite.com/wp-$1$2 [C] Secure RewriteRule !^/wp-(admin|login|register)(.*) - [C] Rewrite for sites running on port 443 or port 80 # BEGIN WordPress RewriteEngine On RewriteBase / # For a site running on port 443 or else (http over ssl) RewriteCond %{SERVER_PORT} !^80$ RewriteRule !^wp-(admin|login|register)(.*) - [C] RewriteRule ^(.*)$ http://%{SERVER_NAME}/$1 [L] # For a site running on port 80 (http) RewriteCond %{SERVER_PORT} ^80$ RewriteCond %{REQUEST_FILENAME} -f [OR] RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^wp-(admin|login|register)(.*) https://%{SERVER_NAME}:10001/wp-$1$2 [L] RewriteCond %{SERVER_PORT} ^80$ RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] Summary This method does not fix some inherent security risks in WordPress, nor does it protect you against man-in-the-middle attacks or other risks that can cripple secure connections. However, this should make it much harder for a malicious person to steal your cookies and/or authentication headers and use them to impersonate you and gain access to wp-admin. It also obfuscates the ability to sniff your content, which could be important for legal blogs which may have drafts of documents that need strict protection. Verification On the author's server, logs indicate that both GET and POST requests are over SSL and that all traffic to wp-admin on the insecure host is being shuttled over to the secure host. Sample POST log line: [Thu Apr 28 09:34:33 2005] [info] Subsequent (No.5) HTTPS request received for child 6 (server foo.com:443) xx.xxx.xxx.xxx - - [28/Apr/2005:09:34:33 -0500] "POST /wp-admin/post.php HTTP/1.1" 302 - "https://foo.com/wp-admin/post.php?acti on=edit&post=71" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3" More testing, preferably with a packet sniffer and some hardcore network analysis tools, would help to confirm. Limitations The author assumes (but hasn't checked) that if the user has stored cookies/told their browser to remember passwords (not based on form fields but if using certain external auth mechanism) and hits http://www.mysite.com/wp-admin/, those packets are sent in the clear and the cookie/auth headers could be intercepted. Therefore, to ensure maximum security, the user should explicitly use the https host or always log in at the beginning of new sessions. Related force_ssl_admin() force_ssl_content() is_ssl() Media Library Screen atachibana — Fri, 29 Apr 2016 04:22:55 +0000 Media → Library Media consists of the images, video, recordings, and files that you upload and use in your blog. Media is typically uploaded and inserted into the content when writing a Post or writing a Page. Note that the Uploading Setting in the Settings Media Screen describes the location and structure of the upload directory (where your media files are stored). If you do need to upload Media, even if that Media is not related to a Post or Page, then you need to use the Media Add New Screen. Visit the Media Add New Screen to install new media by clicking Add New link at the top of this screen or Select Media > Add New from left side menu. Media Library The Media Library Screen allows you to edit, view, and delete Media previously uploaded to your blog. Multiple Media objects can be selected for deletion. Search and filtering ability is also provided to allow you to find the desired Media. Media Library provides two type of views. One is simple visual Grid View and another is conventional List View. Switch between these views using the icons to the left above the screen. Media Library Grid View In Media Library Grid View, thumbnails of image, Audio icons and Movie icons are arranged in the grid. Filtering Options At the top of Grid View, you can filter the media by media type and date: All media items This dropdown allows you to select, by media type such as Images, Audio and Video or Unattached to any Posts nor Pages, which Media are displayed in the Table of Media. By default, "All media items" is selected and all of your Media are displayed. All Dates This dropdown allows you to select, by date, which Media are displayed in the Grid View. By default, "Show all dates" is selected and all of your Media are displayed. To the right, is a Search box where you can enter a word, or series of words to search and display all the Media meeting your search words. The search results will be updated as you type. Delete Media To delete media items, click the Bulk Select button at the top of the screen. Select any items you wish to delete, then click the Delete Selected button. Clicking the Cancel Selection button takes you back to viewing your media. Attachment Details In Media Library Grid View, clicking an Image thumbnail, Audio icon or Video icon will display an Attachment Details dialog, which allows you to preview media and make quick edits. Any changes you make to the attachment details will be automatically saved. You can also delete individual items and access the extended edit screen from the details dialog. Use the arrow buttons at the top of the dialog, or the left and right arrow keys on your keyboard, to navigate between media items quickly. Attachment Details changes its appearance and information by media type. The left side of this dialog shows the Image, Audio player or Video player. The right side lists the following media file attributes and optional data. Some of them are editable from this dialog. File name – The name of media file File type – The MIME Type of media file Uploaded on – The date when media file was uploaded File size – The file size of media file Dimensions – (Image files only) The dimensions of image media URL – Read only display of a direct link to the media file. Title – The name of the media. A title is often shown on attachment pages and galleries if themes or plugins are designed to display it. Caption – A brief explanation of the media. Description – An explanation of this particular media. Alt Text – (Image files only) The alt text for the image, e.g. “The Mona Lisa” to describe the media. Used for accessibility. Artist – (Voice files only) Singer, composer or producer of this media. Album – (Voice files only) Album title that includes this media. Uploaded By – author who uploaded the Media. Uploaded To – Title of the Post or Page that contains this Media. Click on the title to view that Post or Page in an edit Screen. If the Media was unattached to any Post or Page, this line does not appear. At the bottom there are three link menus: View attachment page shows the media in a simulated view of how the image would look when displayed in your Theme. Edit more details displays the Edit Media Screen. See the Edit Media for details on editing Media information. Delete Permanently deletes the media. Also, image files has Edit Image button at the lower left Edit Image (Image files only) allows you to make edits such as rotate, scale, and crop. See the Edit Image Screen. Media Library List View In Media Library List View, a table lists all of your Media, by row. The Media are listed with the newest uploaded Media first. Table of Media The table of Media contains the following columns: [ ] – This checkbox, when clicked (checked), 'selects' that particular Media to be processed by a Bulk Action. "thumbnail" - There is no column heading for "thumbnail", but a small image of the actual media is displayed in this column File - Displayed in the form of a link, this is Title, the name of the media. Clicking the title link opens Edit Media Screen. See the Edit Media for details on editing Media information. Below the Title the actual name of the file that holds this particular Media is displayed. Author - Displayed in the form of a link, this is the author who uploaded the Media. Clicking the author link causes all the Media authored by that user to be displayed in the Table of Media (thus allowing a Bulk Action to be applied to all Media for a given author). Uploaded to - Uploaded to describes the title of the Post or Page that contains this Media and the date of that Post or Page. Click on the title to view that Post or Page in an edit Screen. If the Media was unattached to any Post or Page, an "Attach" link will appear and when clicked this Media can be attached to selected Posts or Pages. For more detail about selecting, see Find Posts or Pages. If the Media has been attached to more than one Post or Page, only the details of the first Post or Page will be displayed. comment bubble - Each Media row has comment bubble with the number of comments for that Media. If a Media has any comments, then the number of comments is displayed in a bubble. Clicking on a blue comment bubble causes the Comments Screen to be displayed to allow moderation of those comments. Date - The date the Media was uploaded. Sortable Columns Some column headings, such as the File, Author, Uploaded to, and Date headings, can be clicked to sort the Table of Media in ascending or descending order. Hover over the column title, e.g. File, to see the up arrow or down arrow. Click the heading to change the sort order. Page Navigation Under the Screen Options, the number of Media displayed per page is determined. If more than one page of Media is available, two double-arrow boxes to move to the first and last page are provided. Also two single-arrow boxes are displayed to move one page backward or forward. Finally, a box showing the current page number can be used to enter a page to directly display. Screen Options The Screen Options allow you to choose which columns are displayed, or not displayed, in the underlying Table. Clicking on the Screen Options tab shows a list of the columns with a check-box next to each column. Check the box for each column you want displayed in the Table, or uncheck the box to not display that column. In addition, the number of Media items to display in the Table of Media can be set. Click the Screen Options tab again to close the Screen Options. Search Above the Table, to the right, is a Search box where you can enter a word, or series of words, and hit the Enter key to search and display all the Media meeting your search words. Filtering Options At the top of List view, you can filter the media by media type and date: All This dropdown allows you to select, by media type such as Images, Audio and Video or Unattached to any Posts nor Pages, which Media are displayed in the Table of Media. By default, "All" is selected and all of your Media are displayed. All Dates This dropdown allows you to select, by date, which Media are displayed in the Table of Media. By default, "All dates" is selected and all of your Media are displayed. Filter Clicking this button applies the settings you select in the dropdown. Using Selection, Actions, and Apply Selection This Screen allows Bulk Actions to be performed on one or more Media selected in the Table. For Bulk Actions to be performed on multiple Media at once, those Media must be first selected via one of these methods: Select one Media at a time - To select a Media, the checkbox to the left of the Media entry must be checked (clicked). It is possible to keep selecting more Media by checking their respective checkbox. Select all Media in given Table - All Media in a given table can be selected by checking the checkbox in the Table's title, or footer bar. Of course, unchecking the header or footer title bar checkbox will cause all entries in that Table to be unchecked (NOT selected). Reverse Selection - A Reverse Selection means checked items become unchecked, and unchecked items become checked. A Reverse Selection is accomplished by holding the Shift key on the keyboard and clicking the header or footer title bar checkbox. Actions Actions describe the process to be performed on particular Media. There are two styles of Actions that will be referred to as Bulk Actions and Immediate Actions. The follow describes these Actions: Bulk Actions - These Actions can be performed on one, or more Media, at one time, if those Media have been previously selected. Bulk Actions are available, when appropriate, as choices in the Bulk Actions pulldown box, above the Table. The only Bulk Action allowed is Delete Permanently. Immediate Actions - Immediate Actions are performed immediately, on an individual Media. Hovering the mouse cursor over the Media row reveals the Edit, Delete Permanently, and View options under the File column, in that Media row. Clicking on a Media Title will also initiate the Edit Action. The available Actions are described below: Edit - This Immediate Action displays the Edit Media Screen. This Action can be initiated by click on the Media Title. See the Edit Media for details on editing Media information. Delete Permanently - This Action deletes the Media. Delete Permanently is available both as a Bulk Action, and an Immediate Action. View - This Action presents the Media in a simulated view of how the image would look when displayed in your Theme. View is available only as an Immediate Action. Attach - In Unattached filtered view, "Attach" action is displayed. By clicking this link, the media can be attached to selected Posts or Pages. For more detail about selecting, see Find Posts or Pages. Find Posts or Pages Clicking Attach link in the "Attached to" column or "Media" column when Unattached filtered view appears Find Posts or Pages dialogue box. From this dialogue box, you can select a Posts or Pages that the media should be attached to. Follow the steps: Search posts or Pages by keyword. Select the post/Page one wants to attach the media. Click the Select button. Apply After one or more Media are selected, and after a Bulk Action is specified, the Apply button performs the given Action on the selected Media. Apply - Click the Apply button to execute the Bulk Action, specified in the Actions pulldown, on the selected Media. Remember, prior to executing Actions, one or more Media must be selected, as described before. Posts Screen atachibana — Fri, 29 Apr 2016 04:36:17 +0000 Posts → Posts The Posts Screen provides the facility to manage all the Posts in a blog. Via this Screen, Posts can be edited, deleted, and viewed. Filtering, and searching, also makes it easy to quickly find Posts matching certain criteria. A powerful bulk edit feature allows Posts to be edited in bulk (en masse) allowing fields such as Author, Comments Allowed, Status, Pings Allowed, and Sticky to be changed for a whole batch of Posts. It is important to note, at least with Version 2.7, that Categories and Tags can be ADDED in bulk to a set of Posts, but it is not possible to CHANGE, or DELETE, a Category, or Tag, for those Posts. In addition, a Quick Edit feature provides an easy method to change a mulititude of values, such as Title, Slug, Date, and Category, for a given Post. Back to Administration Screens. Edit Posts Table of Posts A table lists all of your Posts, by row. The Posts are listed with the newest Post first. The table of Posts contains the following columns: [ ] – This checkbox, when clicked (checked), 'selects' that particular Post to be processed by a Bulk Action. Title - This is the Post's Title displayed as a link. Click the Title link to allow this Post to be edited. Next to the Title, if a Post is of a Draft, Private, Pending, Sticky, or Password Protected nature, bold text will display showing that. "ID" - This is not a column in the Table, but by hovering the mouse over the Post Title, the Post ID is revealed as part of the URL displayed in the browser status bar (in Firefox the status bar is displayed at the bottom of the screen). A Post's ID number is the unique number WordPress' database uses to identify individual Posts. Author - Displayed in the form of a link, this is the author who wrote the Post. Clicking the author link causes all the Posts authored by that user to be displayed in the Table of Posts (thus allowing a Bulk Action to be applied to all Posts for a given author). Categories - Displays all the Categories, in the form of links, to which this Post belongs. Each Category link, when clicked will cause the list of Posts assigned that Category to be displayed in the Table of Posts (note the Category Filter box at the top of the Table will depict the Category being displayed). Tags - Displays all the Tags, in the form of links, associated with a Post. Each Tag link, when clicked will cause the list of Posts assigned that Tag to be displayed in the Table of Posts. comment bubble - A comment bubble is the column heading, and each Post row has comment bubble with the number of comments for that Post. If a Posts has any comments, then the number comments is displayed in a blue bubble. Clicking on a blue comment bubble causes the Comments Screen to be displayed to allow moderation of those comments. Date - The Date column for each Post shows the Date 'Published' for Published Posts or the Date 'Last Modified' for other Posts. If the Post is a "future Post," the scheduled date for publishing is displayed. Sortable Columns Some column headings, such as the Title, Author, and Date, can be clicked to sort the Table of Posts in ascending or descending order. Hover over the column title, for example Title, to see the up-arrow or down-arrow. Click the heading to change the sort order. View Just to the right above the Table of Posts, two icons, List View, and Excerpt View, can be clicked to determine the amount of information listed with each Post. The default view is the List View and only the Post Title is listed for each Post. Click the Excerpt View to cause an excerpt for the Post to be displayed just below the Post Title. Page Navigation Under the Screen Options, the number of Posts displayed per page is determined. If more then one page of Posts is available, two double-arrow boxes to move to the first and last page are provided. Also two single-arrow boxes are displayed to move one page backward or forward. Finally, a box showing the current page number can be used to enter a page to directly display. Screen Options The Screen Options allow you to choose which columns are displayed, or not displayed, in the underlying Table. Clicking on the Screen Options tab shows a list of the columns with a check-box next to each column. Check the box for each column you want displayed in the Table, or uncheck the box to not display that column. Click the Screen Options tab again to close the Screen Options. In addition, the number of Posts per page can be set. Search Above the Table, to the right, is a search box where you can enter a word, or series of words, and click the "Search Posts" button to search and display all the Posts meeting your search words. Filtering Options At the top of this Screen are links such as All, Published, Schedules, Pending Review, Draft, Private, that when clicked, will cause just the Posts of that type to be displayed in the underlying Table. Below that, and to the right of the Bulk Actions Apply button, are two other filter options: Show all dates This dropdown allows you to select, by date, which Posts are displayed in the Table of Posts. By default, "Show all dates" is selected and all of your Posts are displayed. View all categories This dropdown allows you to select, by Category, which Posts are displayed in the Table of Posts. By default, "Show all categories" is selected and all of your Posts are displayed. Filter Clicking this button applies the settings you select in the dropdowns. Using Selection, Actions, and Apply Selection This Screen allows Bulk Actions to be performed on one or more Posts selected in the Table. For Bulk Actions to be performed on multiple Posts at once, those Posts must be first selected via one of these methods: Select one Post at a time - To select a Post, the checkbox to the left of the Post entry must be checked (clicked). It is possible to keep selecting more Posts by checking their respective checkbox. Select all Posts in given Table - All Posts in a given table can be selected by checking the checkbox in the Table's title, or footer bar. Of course, unchecking the header or footer title bar checkbox will cause all entries in that Table to be unchecked (NOT selected). Reverse Selection - A Reverse Selection means checked items become unchecked, and unchecked items become checked. A Reverse Selection is accomplished by holding the Shift key on the keyboard and clicking the header or footer title bar checkbox. Actions Actions describe the process to be performed on particular Posts. There are two styles of Actions that will be referred to as Bulk Actions and Immediate Actions. The following describes these Actions: Bulk Actions - These Actions can be performed on one, or more Posts, at one time, if those Posts have been previously selected. Bulk Actions are available, when appropriate, as choices in the Bulk Actions pulldown box, above the Table. The only Bulk Actions allowed are Edit and Delete. Immediate Actions - Immediate Actions are performed Immediately, on an individual Post. Hovering the mouse cursor over the Post row reveals the Edit, Delete, and View options under the Title column, in that Post's row. Clicking on a Post's Title will also initiate the Edit Action. The available Actions are described below: Edit - This Action can be either an "Immediate Action" or a "Bulk Action". The Immediate Action, initiated by click on the Post Title or clicking on the Edit option just below the Post Title, causes the Edit Posts screen to display. Edit is also available as a Bulk Action for the selected Posts, so see the Bulk Edit section for details on the Bulk Editing process. Quick Edit - Quick Edit is an "Immediate Action" that allows a quick in-line edit of certain fields related to a Post. See the Quick Edit section for details on this Action. Delete - This Action deletes the Posts. Delete is available both as a Bulk Action, and an Immediate Action. Note: You cannot delete locked posts. View - This Action presents the Post as it appears in a single Post view on your blog. View is available only as an Immediate Action. Bulk Edit The Bulk Edit Posts 'screen' is displayed below the Table Of Posts header once, one, or more Posts, have been selected, and the Bulk Action of Edit is Applied. Bulk Edit allows the fields, Author, Comments Allowed, Status, Pings Allowed, and Sticky, to be changed for all the selected Posts. It is important to note, Categories and Tags can be ADDED in bulk to a set of Posts, but it is not possible to CHANGE, or DELETE, a Category, or Tag, for those Posts. Cancel - Click Cancel to cancel and abort the Bulk Edit of these Posts. Update - Click Update to save the Bulk Edits made to these Posts. Quick Edit Quick Edit is an Immediate Action performed on one Post by clicking the Quick Edit link, under the Post Title in the Table of Posts. Quick Edit is just an in-line edit that allows you to change the following items--Title, Slug, Date, Author, Password or Private post box, Categories, Tags, Allow Comments, Allow Pings, Status, and Make this a post-sticky. Cancel - Click Cancel to cancel and abort the Edit of this Post. Update - Click Update to save the Edits made to this Post. Editing Individual Posts This mode is essentially the same as the Posts Add New Screen so see the Posts_Add_New_Screen for the specific details of writing a Post. The only difference is that the button to save your work is called "Update" instead of "Publish". Apply After one or more Posts are selected, and after a Bulk Action is specified, the Apply button performs the given Action on the selected Posts. Apply - Click the Apply button to execute the Bulk Action, specified in the Actions pulldown, on the selected Posts. Remember, prior to executing Actions, one or more Posts must be selected, as described before. Backing Up Your WordPress Files atachibana — Fri, 29 Apr 2016 04:57:47 +0000 There are two parts to backing up your WordPress site: Database and Files. This page talks about Files only; if you need to back up your WordPress database, see the Backing Up Your Database. Your WordPress site consists of the following files: WordPress Core Installation WordPress Plugins WordPress Themes Images and Files Javascripts, PHP scripts, and other code files Additional Files and Static Web Pages Everything that has anything to do with the look and feel of your site is in a file somewhere and needs to be backed up. Additionally, you must back up all of your files in your WordPress directory (including subdirectories) and your .htaccess file. While most hosts back up the entire server, including your site, it is better that you back up your own files. The easiest method is to use an FTP program to download all of your WordPress files from your host to your local computer. By default, the files in the directory called wp-content are your own user-generated content, such as edited themes, new plugins, and uploaded files. Pay particular attention to backing up this area, along with your wp-config.php, which contains your connection details. The remaining files are mostly the WordPress Core files, which are supplied by the WordPress download zip file. Please read Backing Up Your WordPress Site for further information. Other ways to backup your files include: Website Host Provided Backup Software Most website hosts provide software to back up your site. Check with your host to find out what services and programs they provide. Create Synchs With Your Site WinSCP and other programs allow you to synchronize with your website to keep a mirror copy of the content on your server and hard drive updated. It saves time and makes sure you have the latest files in both places. Synchronize your files in WinScp Log in to your ftp server normally using WinScp. Press the "Synchronize" button. Remote directory will automatically be set to the current ftp directory (often your root directory). Local directory would be set to the local directory as it was when you pressed Synchronize. You may want to change this to some other directory on your computer. Direction should be set to "local" to copy files FROM your web host TO your machine. Synchronization Mode would be set to Synchronize files. Click "OK" to show a summary of actions. Click "OK" again to complete the synchronization. Copy Your Files to Your Desktop Using FTP Clients or UNIX Shell Skills you can copy the files to a folder on your computer. Once there, you can zip or compress them into a zip file to save space, allowing you to keep several versions. Normally, there would be no need to copy the WordPress core files, as you can replace them from a fresh download of the WordPress zip file. The important files to back up would be your wp-config.php file, which contains your settings and your wp-content directory (plus its contents) which contains all your theme and plugin files Read Further WordPress Backups Upgrading WordPress Extended Appearance Widgets Screen atachibana — Fri, 29 Apr 2016 05:14:04 +0000 [codex_languages en="Appearance Widgets Screen" fr_codex="Apparence Écran des Widgets" ja_codex="Appearance Widgets SubPanel" ptbr_codex="Sub-Painel Widgets" zhcn_codex="外观小工具页面"] Appearance → Widgets Themes usually have at least 1 or 2 sidebars. Sidebars are the narrow columns to the left or right of your blog posts. Each section in the sidebar is known as a "Widget" that you can add or remove, and move up or down. You configure Widgets in your sidebar by via the Appearance Widgets Screen. Some themes also are configured to accept widgets in certain parts of the footer. 640px||Appearance Widgets Screen Back to Administration Screens Widgets Management in Customizer WordPress Theme Customizer. You can add, rearrange and remove Widgets just like in Appearance Widgets Screen, but you also get a live preview of your changes. From the Appearance Widgets Screen, click the "Manage in Customizer" link at the top to access the Widgets section of Theme Customizer. Configuring Your Widgets Click on Appearance > Widgets from the main navigation menu in your Dashboard. Add new widgets from the Available Widgets section by dragging them to the Sidebar you want to customize. (There might be more than one sidebar option, depending on your theme.) Preview your site and you should see the content from your new Widget. Return to the Widgets Screen to continue adding Widgets to the Sidebar as needed. To arrange the Widgets within the Sidebar, click, drag and drop the widgets in the order you want. To customize the Widget features, click the down arrow (or edit link) in the upper right corner to expand the Widget's interface. To save the Widget's customization, click Save. (If simply moving a widget to the sidebar without making customizations, you do not need to click the Save button.) Preview your site again, and all of your changes should be visible. Remove a Widget Click on Appearance > Widgets from the main navigation menu in your Dashboard. Decide which Sidebar from which you want to remove your widget if there is more than one option. For the Widget that is to be removed, click the down arrow (or edit link) in the upper right corner to expand the Widget's interface Click the Delete link in the dialog box. The Widget will now be removed permanently. Preview your site to see your changes. Note: If you would like to remove a widget temporarily and keep your settings, drag the widget from the Sidebar into the Inactive Widgets section. When you are ready to return the widget, drag it from your Inactive Widgets section back to the Sidebar. Moving a Widget To move a Widget: The Widget must be located in a Sidebar or other active content area before it can be moved. Click on the Widget Title and hold the mouse button down, then drag the Widget bar up or down to the location desired. At that point release the mouse button. That process is called drag-and-drop. Descriptions of Each Widget Here's a description of the various types of widget along with their configuration options: Archives - displays archive links for each month that has posts. Title — description that appears over the list of archive links. Display as a drop down — if checked, this box causes the archives to be displayed in a drop-down box. Show post counts — if checked, this box causes a count of the number of posts for each archive period. Calendar - displays a calendar of the current month. Dates appear links if there are posts for that day. Title — description that appears over the calendar Categories - displays a list of post categories as links to those posts. Title — description that appears over the list of categories. Display as dropdown — if checked, this box causes the categories to be displayed in a dropdown box. Show post counts — if checked, this box causes the count of the number of posts to display with each category. Show hierarchy — if checked, shows parent/child relationships in an indented manner. Custom Menu - displays a custom menu. Title — description that appears over the menu Select Menu — select the desired created menu Meta - displays links to meta functions such as Register, Site Admin, Login/out, Entries RSS, Comments RSS, and WordPress.org. Title — description that appears over the list of meta links. Pages - displays a link to each Page. Title — description that appears over the list of pages. Sort by — select the order to sort the list of pages. Choose Page Title, Page Order, or Page ID from pulldown box Exclude (Page IDs, separated by commas) — enter the Page ID(s) to exclude, separating each Page ID with a comma Recent Comments - displays a list of the blog's most recent approved comments. Title — description that appears over the list of recent comments. Number of comments to show: (at most 15); enter the number of comments to be displayed. Recent Posts - displays list of the blog's most recent posts. Title — description that appears over the list of recent posts. Number of posts to show: (at most 15) — enter the number of posts to display. Display post date? — check this to display the date the post was published. RSS - displays an RSS Feed. Multiple instances of this widget can be added to the Current Widgets list. Using RSS Widgets lists several feeds to use with this widget. Enter the RSS feed URL here — enter a complete feed URL, e.g. http://wordpress.org/development/feed/ Give the feed a title (optional) — enter a description that appears over the list of feed items How many items would you like to display? — enter the number of items from the feed you want displayed. Display item content? — check this to display the content of the feed Display item author if available? — check this to display the author of this particular item content Display item date? — check this to display the date the item was published Search - displays a Search box to enter text to search your blog. A submit button is also provided. Title — description that appears over the Search box. Tag Cloud - displays list of the blog's top 45 used tags in a tag cloud. Title — description that appears over the tag cloud. Taxonomy — select the desired registered taxonomy (e.g. Tags, Category). Text - used to enter HTML, JavaScript, or just plain text. Multiple instances of this widget can be added to the Current Widgets list. Using Text Widgets details a number of possible uses for text widgets. Title area — a description of the text widget Text area — use this area to enter text, valid HTML, or even valid JavaScript. Automatically add paragraphs — check this to automatically add paragraphs to wrap each block of text in an HTML paragraph tag (recommended for text). Adding Multiple Widgets of the Same Kind To add multiple text widgets, RSS widgets, or any other widgets, just drag and drop the widget from Available Widgets to your Sidebar as many times as you need. No Sidebars Defined If the current active Theme is not widget compatible, meaning the theme is not coded for widgets, you will see the message, "You are seeing this message because the theme you are currently using isn't widget-aware, meaning that it has no sidebars that you are able to change. For information on making your theme widget-aware, please follow these instructions". Settings Permalinks Screen atachibana — Fri, 29 Apr 2016 05:47:47 +0000 Settings → Permalinks Permalinks are the permanent URLs to your individual pages and blog posts, as well as your category and tag archives. A permalink is the web address used to link to your content. The URL to each post should be permanent, and never change — hence the name permalink. The Settings Permalinks Screen allows you to choose your default permalink structure. You can choose from common settings or create custom URL structures. You must click the Save Changes button at the bottom of the screen for new settings to take effect. By default, WordPress uses web URLs which have day and name in them; however, WordPress offers you the ability to create a custom URL structure for your permalinks and archives. This can improve the aesthetics, usability, and forward-compatibility of your links. For a more in depth description of the way this structure is specified, see the Using Permalinks article. For an introduction to Permalinks, read the Pretty Permalinks section of Introduction to Blogging. Customize Permalink Structure A number of tags are available, and here are some examples to get you started. Common settings Check one of the radio buttons corresponding to the correct Permalink Structure for your blog. Plain - An example of the default structure is http://www.sample.com/?p=123 Day and name - An example of the day and name based structure is http://www.sample.com/2008/03/31/sample-post/ Month and name - An example of the month and name based structure is http://www.sample.com/2008/03/sample-post/ Numeric - An example of the numeric structure is http://www.sample.com/archives/123 Post name - An example of the post name structure is http://www.sample.com/sample-post Custom structure - In the box specify the custom structure you desire to use. One example is /archives/%year%/%monthnum%/%day%/%postname%/. Look at the Permalink Structure Tags. Optional You may enter custom bases for your category and tag URLs here. For example, using /topics/ as your category base would make your category links like http://example.org/topics/uncategorized/. If you leave these blank the defaults will be used. Again, see the Permalink Structure Tags. Category base - Enter a custom prefix for your category URLs here. Tag base - Enter a custom prefix for your tag URLs here. Save Changes Click the Save Changes button to ensure any changes you have made to your Settings are saved to your database. Once you click the button, a confirmation text box will appear at the top of the page telling you your settings have been saved. After you've clicked this button, you should receive one of two messages depending on whether your .htaccess file is writeable. For information on how to make .htaccess writeable, see Changing File Permissions. If .htaccess is writeable, you will get a message that says "Permalink structure updated." You're all set; WordPress has been able to do everything for you automatically. If .htaccess is not writeable, you will see a message at the top of the screen that says "You should update your .htaccess now.". Near the bottom of the screen you will see "If your .htaccess file were writable, we could do this automatically, but it isn't so these are the mod_rewrite rules you should have in your .htaccess file. Click in the field and press CTRL + a to select all." This means you'll have to do one extra step yourself. In the text box at the bottom of the Screen, WordPress displays several lines of rewrite rules associated with the Permalink Structure you designated above. You need to manually copy everything in this text box into your .htaccess file to make your new Permalinks work. Note: Visiting the Permalinks screen triggers a flush of rewrite rules. There is no need to save just to flush the rewrite rules. Note: If you're writing your .htaccess file on your own local computer, remember, some operating systems do not allow the creation of a file named ".htaccess" because of the initial dot ("."). You can always name the file without the initial dot or with a standard extension (e.g. "htaccess.txt"). Once the file is uploaded to your weblog's directory, rename it with your FTP software. Most FTP Clients should provide you a way to rename files this. Also Note: Files that begin with a dot (".") like ".htaccess" are hidden on most servers by default. Consult the user guide or FAQ of the FTP software you use to find out how to have the software display these hidden files, and also how to use the software to change file permissions, rename files, etc. For more information on all of this see Changing File Permissions. Using cPanel atachibana — Fri, 29 Apr 2016 05:57:50 +0000 This tutorial provides step-by-step examples of creating a database and database user using the cPanel MySQL Database Wizard tool. Login to your site Login to your hosting control panel (cPanel) with information provided by your host company. MySQL Database Wizard Under the Database section, click on the MySQL Database Wizard icon. Step 1. Create a Database Step 1 in the wizard is creating the database. Simply give your database a name. The actual database name will be prepended by your hosting account name. In this example, after clicking Next Step, the database michaelh_demowp will be created. Step 2. Create Database Users The next step in the wizard requires creating a database user and assigning that user a password. When entering the password, make sure the password strength meter registers Very Strong for your selected password. Also remember the password you enter as you will need that information later. In this example, dbuser is entered in the Username field, but when the Create User button is clicked, the database user ultimately will be named michaelh_dbuser. Step 3. Add User to Database In Step 3, you assign the user to the database and you assign the necessary database privileges. In this case, click the All Privileges checkbox and click the Next Step button to assign all privileges to the database user. Step 4. Complete the task In this step, you are notified that the user was addeed to the database. You have successfully created the database, created the user, and assigned privileges to that user. Editing the WordPress Config File Open the file wp-config-sample.php using a text editor. There are the four pieces of information you need to complete in the file. The following is an example; yours may look slightly different: // ** MySQL settings - You can get this info from your web host ** // /** The name of the database for WordPress */ define('DB_NAME', 'michaelh_demowp'); /** MySQL database username */ define('DB_USER', 'michaelh_dbuser'); /** MySQL database password */ define('DB_PASSWORD', 'abc.123.!@#'); /** MySQL hostname */ define('DB_HOST', 'localhost'); Note that the prefix michaelh_ assigned by that cPanel is part of the database and database user. Also note, the DB_HOST value for almost all cPanel hosts is localhost. Important!!!! Save the completed file as wp-config.php. Continuing the Installation The database is created, and user is created and assigned to the database with the proper privileges. And the wp-config.php is updated with the database information. At this point it is okay to move to Step 4 of the Installation process. Writing Posts normalize — Mon, 06 Jun 2016 23:25:20 +0000 Posts are entries that display in reverse order on your home page and/or blog page. Posts usually have comment fields beneath them and are included in your site's RSS feed. To write a post: Log in to your WordPress Administration Screen (Dashboard). Click the 'Posts' tab. Click the 'Add New' sub-tab. Start filling in the blanks: enter your post title in the upper field, and enter your post body content in the main post editing box below it. As needed, select a category, add tags, and make other selections from the sections below the post. (Each of these sections is explained below.) When you are ready, click Publish. Screen Options There are more editing fields available to you than you see on first login. The Screen Options area allows you to choose which Post Fields are displayed or hidden from your editing area, which allows you to minimize clutter and customize according to your needs. You'll find the Screen Options tab at the very top of your screen, and if you click on it, you'll see a list of available editing boxes that you can use. Check the box for each Post Field you want displayed, or uncheck the box to hide that module. Click the Screen Options tab again to close the tab. Once you've customized how editing screen, your options are saved so you don't have to select or hide them again next time you log in. Post Field Descriptions WordPress Admin Writing Post Advanced Panel - Top of Page Title/Headline Box This box should contain the title of your post. You can use any phrase, words, or characters. (Avoid using the same title on more than one page.) You can use commas, apostrophes, quotes, hyphens/dashes, and other typical symbols in the post like “My Site – Here’s Lookin’ at You, Kid.” WordPress will then clean it up to generate a user-friendly and URL-valid name of the post (also called the “post slug”) to create the permalink for the post. Permalink Permalink stands for "permanent link." That means a post URL that does not expose the post ID which could be subject to a change (e.g. when moving to different blogging system), but it rather contains a user-friendly post name derived from the post title which could also change, although not recommended, but in a more controllable way. This post name (also referred to as "post slug" or just "slug") can be edited, depending on your Permalinks settings, using the "Edit" button. (To change your settings, go to Administration Panels > Settings > Permalinks). The permalink is automatically generated based on the title you set to the post and is shown below the title field. Punctuation such as commas, quotes, apostrophes, and invalid URL characters are removed and spaces are substituted with dashes to separate each word. If your title is "My Site - Here's Lookin' at You, Kid", it will be cleaned up to create the slug "my-site-heres-lookin-at-you-kid". You can manually change this, maybe shortening it to "my-site-lookin-at-you-kid". Body Copy Box The blank box where you enter your writing, links, images, links to images, and any information you want to display on your site. You can use either the visual (WYSIWYG) editor or the text view to compose your posts. For more on the text view, see the section below, Visual Versus Text Editor. Publish Box Contains buttons that control the state of your post. The main states are Draft and Published. Draft means the post has not been published and remains in draft status for the post creator. A Published status means the post has been published and is live on your site. Preview Button Allows you to view the post before publishing. Save Draft Allows you to save your post as a draft rather than immediately publishing it. To return to your drafts later, visit Posts - Edit in the menu bar, then select your post from the list. Status If you select a specific publish status (click Edit next to Status:Draft) and click the update post or "Publish" button, that status is applied to the post. For example, to save a post in the Pending Review status, select Pending Review from the Publish Status drop-down box, and click Save As Pending. (You will see all posts organized by status by going to Administration Panels > Posts > Edit). Visibility This determines how your post appears to the world. (click Edit next to Visibility) Public posts will be visible by all website visitors once published. Password Protected posts are published to all, but visitors must know the password to view the post content. Private posts are visible only to you (and to other editors or admins within your site). Revisions Click Browse to see all of the changes you've made to your post. Scheduling To schedule a post for publication on a future time or date, click Edit next to the words "Publish immediately." You can also change the publish date to a date in the past to back-date posts. Change the settings to the desired time and date. You must also click the Publish button when you have completed the post to publish at the desired time and date. Format Box Allows you to choose a format for a post. Styling and appearance are handled by the individual themes. Categories Box The general topic of the post. It is typical for a blog to have 7-10 categories for content. Readers can browse specific categories to see all posts in the category. You can manage your categories by going to Administration Panel > Posts > Categories. Tags Box These are micro-categories for the post, similar to including index entries for a page. Posts with similar tags are linked together when a user clicks one of the tags. Tags have to be enabled with the right code in your theme for them to appear in your post. Add new tags to the post by typing the tag into the box and clicking "Add." You can also click on the "Choose from the most-used tags" link to see all of the tags used by the site. Excerpt A summary or brief teaser of your post that may appear on the front page of your site as well as on the category, archives, and search non-single post pages. Note: the Excerpt does not usually appear by default. It only appears in your post if you have modified the template file listing the post to use the_excerpt() instead of the_content() to display the Excerpt instead of the full content of a post. If so, WordPress will automatically use as the Excerpt the first 55 words of your post content or the content before the quicktag. If you use the "Excerpt" field when editing the post, this will be used no matter what. For more information, see Excerpt. Send Trackbacks A way to notify legacy blog systems that you've linked to them. If you link other WordPress blogs, they'll be notified automatically using pingbacks. No other action is necessary. For those blogs that don't recognize pingbacks, you can send a trackback to the blog by entering the website address(es) in this box, separating each one by a space. See Trackbacks and Pingbacks for more information. Custom Fields Custom Fields offer a way to add information to your site. In conjunction with extra code in your template files or plugins, Custom Fields can modify the way a post is displayed. These are primarily used by plugins, but you can manually edit that information in this section. Discussion Options to enable interactivity and notification of your posts. This section hosts two check boxes: Allow Comments on this post and Allow trackbacks and pingbacks on this post. If Allowing Comments is unchecked, no one can post comments to this particular post. If Allowing Pings is unchecked, no one can post pingbacks or trackbacks to this particular post. Post Author A list of all blog authors you can select from to attribute as the post author. This section only shows if you have multiple users with authoring rights in your blog. To view your list of users, see Administration Panel > Users. For more information, see Users and Authors. WordPress Admin Writing Post Advanced Panel - Bottom of Page Note: You can set basic options for writing, such as the size of the post box, how smiley tags are converted, and other details by going to Administration Panel > Settings > Writing. Best Practices For Posting You can say or show the world anything you like on your WordPress site. Here are some tips you need to know to help you write your posts in WordPress. Practice Accessibility To be compliant with web standards for accessibility, be sure to include ALT and TITLE descriptions on links and images to help your users, such as http://wordpress.org/">WordPress.ORG. Use Paragraphs No one likes to read writing that never pauses for a line break. To break your writing up into paragraphs, use double spaces between your paragraphs. WordPress will automatically detect these and insert HTML paragraph tags into your writing. Use Headings If you are writing long posts, break up the sections by using headings, small titles to highlight a change of subject. In HTML, headings are set by the use of h1, h2, h3, h4, and so on. Use HTML You don't have to use HTML when writing your posts. WordPress will automatically add it to your site, but if you do want control over different elements like boxes, headings, and other additional containers or elements, use HTML. Spell Check and Proofread There are spell check Plugins available, but even those can't check for everything. Some serious writers will write their posts in a text editor with spell check, check all the spelling and proof it thoroughly before copying and pasting into WordPress. Visual Versus Text Editor When writing your post, you have the option of using the Visual or Text mode of the editor. The visual mode lets you see your post as is, while the Text mode shows you the code and replaces the WYSIWYG editor buttons with quicktags. These quicktags are explained as follows. b - HTML tag for strong emphasis of text (i.e. bold). i - HTML tag for emphasis of text (i.e. italicize). b-quote - HTML tag to distinguish quoted or cited text. del - HTML tag to label text considered deleted from a post. Most browsers display as striked through text. link - HTML tag to create a hyperlink. ins - HTML tag to label text considered inserted into a post. Most browsers display as underlined text. ul - HTML tag will insert an unordered list, or wrap the selected text in same. An unordered list will typically be a bulleted list of items. ol - HTML tag will insert a numbered list, or wrap the selected text in same. Each item in an ordered list is typically numbered. li - HTML tag will insert or make the selected text a list item. Used in conjunction with the ul or ol tag. code - HTML tag for preformatted styling of text. Generally sets text in a monospaced font, such as Courier. more - WordPress tag that breaks a post into "teaser" and content sections. Type a few paragraphs, insert this tag, then compose the rest of your post. On your blog's home page you'll see only those first paragraphs with a hyperlink ((more...)), which when followed displays the rest of the post's content. page - WordPress tag similar to the more tag, except it can be used any number of times in a post, and each insert will "break" and paginate the post at that location. Hyperlinks to the paginated sections of the post are then generated in combination with the wp_link_pages() or link_pages() template tag. lookup - Opens a JavaScript dialogue box that prompts for a word to search for through the online dictionary at answers.com. You can use this to check spelling on individual words. Close Tags - Closes any open HTML tags left open--but pay attention to the closing tags. WordPress is not a mind reader (!), so make sure the tags enclose what you want, and in the proper way. Workflow Note - With Quicktag buttons that insert HTML tags, you can for example click i to insert the opening tag, type the text to be enclosed, and click /i or Close Tags to insert the closing tag. However, you can eliminate the need for this 'close' step by changing your workflow a bit: type your text, select the portion to be emphasized (that is, italicized), then click i and your highlighted text will be wrapped in the opening and closing tags. More Information and Resources About Weblogs - What is Blogging all about? First Steps With WordPress See also Administration Screens. FAQ Working with WordPress atachibana — Fri, 29 Apr 2016 06:41:21 +0000 Administration Can my posts have URL instead of /index.php?p=76? See: Using Permalinks How can I find out if I have mod_rewrite? To get information about your server, you can use the phpinfo() function: 1. Paste this into text editor 2. Save as info.php Upload to server. Visit in your browser (www.example.com/info.php) The info.php file returns a page outlining the details of your PHP installation. You can see if mod_rewrite is loaded. Under the apache header, look in the Loaded Modules section and see if mod_rewiite is listed. How do I change file and folder permissions? See: Changing File Permissions How long is the release cycle of WordPress? A major release of WordPress happens every 6 months or so. Suggest and vote on ideas for future releases at the WordPress Extend Ideas site. Also refer WordPress Versions for the chronologically listed versions of WordPress along with the Change Log information on new features and improvements in each version. There are the future releases and links to their respective milestones in the bug tracker. How do I turn on Permalinks, and what do I do about the errors? See: Using Permalinks What are Roles for and what permissions do different Roles have? See: Roles and Capabilities Does the 644 permissions on wp-config.php compromise the username and password to all other users on my shared server? This is a limitation of the way PHP is set up on your server. If you previously used Movable Type, Perl was probably set up with suexec so Movable Type executed as your user. In this case, PHP is running as the web server user, which is why it has to be at least 444. There is phpsuexec but it seems many hosts don't use it. However this is often not an issue on modern shared hosts because even though the file is "World" readable each account is set up with a "jailshell" which keeps people locked in their home directory, and PHP can be easily modified with an open_basedir restriction to keep people from writing PHP scripts to read your files. If you are really concerned, you should contact your host to see what measures they are taking. How do I redirect users back to my blog's main page after they login? By default, WordPress reroutes a registered user to the Administration Screens after they log into the blog. To change the page, there are WordPress Plugins that can handle the redirect, or you can set the Theme function to handle it. See Function_Reference/wp_login_url. How do I change permissions for my files so I can edit them using the Theme Editor? See: Changing File Permissions How do I prevent my images from being hot-linked by another website? You can use your .htaccess file to protect images from being hot linked, or, in other words, being linked-to from other websites. This can be a drain on your bandwidth, because if someone links directly to the image on your site, then you lose the bandwidth. How do I backup and restore my WordPress database using phpMyadmin? See: Backing Up Your Database and Restoring Your Database From Backup How do I prevent comment flooding? Comment flooding is when a lot of comments (probably spam) are posted to your website in a very short duration of time. This is only one aspect of the broader problem of comment spam in general, but it can quickly overwhelm a moderator's ability to manually delete the offending comments. WordPress manages the worst floods automatically by default. Any commenters from the same IP or e-mail address (other than registered users with manage_options capabilities) that post within 15 seconds of their last comment gets their comment discarded. The time setting can be changed by a number of plugins that extend this functionality. You might also consider one of the many broader spam blocking plugins, such as Akismet, or even turning your comment system over to Disqus. You could also just change the time setting by inserting the following filter into functions.php of your current theme. Or you may create and install a very basic plugin and insert the following code: function dam_the_flood( $dam_it, $time_last, $time_new ) { if ( ($time_new - $time_last) < 300 ) // time interval is 300 return true; // seconds return false; } add_filter('comment_flood_filter', 'dam_the_flood', 10, 3); Creating plugins can be very easy, the above code actually has most of the work done for you. Why can't I delete the uncategorized Category? Deleting a category does not delete the posts in that category. Instead, posts that were only assigned to the deleted category are set to the uncategorized category. Also, all Pages are assigned the uncategorized Category. The uncategorized category cannot be deleted, however you can specify your default categories for posts on the Settings - Writing screen of the Administration Screens. Why is there no Page Template option when writing or editing a Page? If there is no Page Template option when writing or editing a Page it may because there is no template file with the proper structure. For the Page Template box to be available to assign to a Page there must be a least one template file in your theme that has a structure at the beginning of the template file that looks like this: Create a new PHP file with any name under the theme directory and put above codes into the file. You will see the Page Template box appears that includes "My Custom Page" option in the Page Edit Screen. For more detail about Custom Page Template, refer Page Templates. How can I have a static front page and posts display on a page as Web site top page? See: Creating a Static Front Page This is the example Page Template if you want to display one latest post, instead of the Page content, on your static front page. 1, 'cat' => 1); $the_query = new WP_Query( $args ); // The Loop while ( $the_query->have_posts() ) : $the_query->the_post(); get_template_part( 'content', get_post_format() ); // End the loop. endwhile; ?> See also: Stepping Into Templates Forum thread showing this in action How do I determine a Post, Page, Category, Tag, or User ID? Sometimes it is necessary to know the ID of a particular Post, Page, Category, Tag, or User. To determine that ID, use one of these method: Look in your browser status bar for the ID: Visit the related list table screen in your Administration Screen. For instance in the case of Posts visit Posts->All Posts, for Pages visit Pages->All Pages, and for Categories visit Posts->Categories. Now hover your mouse over the 'item' you need the ID. In the case of Pages, hover over that particular Page's title in the Title column and for Categories hover over the Categories Name in the Name column. Look at the status bar (at the bottom of your browser) and the you will find at the end of the line something like "post=123" or "tag_ID=67". In these cases, 123 is the Page ID, and 67 is the Category ID. Install a plugin: Install and activate Reveal IDs for WP Admin or others. Find the ID displayed with each item. Configuration How can I change how the date and / or time is displayed? See: Formatting Date and Time How can I control comments people make? See: Comment Moderation What do the Discussion Options mean? See: Discussion Screen How do I install plugins? See: Managing Plugins How can I change what appears between Categories when I post in more than one Category? In Twenty Fifteen theme, the post's multiple categories are displayed with commas between them. To configure the way the categories display, 1. Create a Child Themes of Twenty Fifteen theme. 2. Copy twentyfifteen_entry_meta() function from parent's inc/template-tags.php to child theme's functions.php. function twentyfifteen_entry_meta() { if ( is_sticky() && is_home() && ! is_paged() ) { : } } 3. Replace ', ' in the argument of get_the_category_list call in twentyfifteen_entry_meta() function. $categories_list = get_the_category_list( _x( ', ', 'Used between list items, there is a space after the comma.', 'twentyfifteen' ) ); If you change it by ' > ', ' • ' or ' | ' then you will see an arrow, a bullet or "pipe" (|) between the categories. 4. Activate the child theme. Why are all the comments being moderated? Go to the Settings > Discussion screen and make sure that Comment must be manually approved is unchecked. With that option selected, all comments are sent to the moderation queue to await approval. Make sure that Hold a comment in the queue if it contains x or more links. is not blank and contains a number higher than zero. If this value is blank or zero, all comments containing links will be moderated. If the option mentioned above is unchecked, the link moderation value is higher than zero, and you still have this problem, then upgrade the comment spam plugins you have installed. If this continues to be a problem, deactivate the comment spam plugins one by one to determine the culprit and contact the plugin author for help. How do I disable comments? First, uncheck Allow people to post comments on new articles on the Settings > Discussion screen. This will only disable comments on future posts. Next, to completely disable comments, you will have to edit each past post and uncheck Allow Comments from the Edit Post screen. Use Bulk Edit to disable multiple posts at once. In the Posts_Screen, check the checkbox in the Table's title to select all Posts in a given table. From Bulk Actions box, select Edit and click Apply. In the Bulk Edit Screen, select Do not allow option from Comments box Click Update. Alternatively, you could run below MySQL query from the command line on a shell account or using phpMyAdmin, or through a wp-cli `wp db query`: UPDATE wp_posts SET comment_status = 'closed'; If your goal is to permanently remove comments, then follow the next steps. This is the example of Twenty Fifteen theme customization. 1. Create a Child Themes of Twenty Fifteen theme. 2. Copy twentyfifteen_entry_meta() function from parent's inc/template-tags.php to child theme's functions.php. 3. Comment out the if block that contains comments-link. function twentyfifteen_entry_meta() { if ( is_sticky() && is_home() && ! is_paged() ) { : } // if ( ! is_single() && ! post_password_required() && ( comments_open() || get_comments_number() ) ) { // echo ''; // /* translators: %s: post title */ // comments_popup_link( sprintf( __( 'Leave a comment on %s', 'twentyfifteen' ), get_the_title() ) ); // echo ''; // } } It removes the number of comments or "Leave a comment" message from bottom of each post. 4. Newly create comments.php under the Child Theme's directory without any contents. It removes the comment area of exsiting posts. 5. Activate the Child Teheme. How do I disable trackbacks and pingbacks? First, uncheck Allow link notifications from other blogs (pingbacks and trackbacks) on new articles on the Settings > Discussion screen. This will only disable trackbacks and pingbacks on future posts. Next, to completely disable trackbacks and pingbacks, you will have to edit each past post and uncheck Allow trackbacks and pingbacks on this page from the Edit Post screen. Use Bulk Edit to disable multiple posts at once. See also above image. In the Posts_Screen, check the checkbox in the Table's title to select all Posts in a given table. From Bulk Actions box, select Edit and click Apply. In the Bulk Edit Screen, select Do not allow option from Pings box. Click Update. Alternatively, you could run this MySQL query from the command line on a shell account or using phpMyAdmin, or through a wp-cli `wp db query`: UPDATE wp_posts SET ping_status = 'closed'; How do I change the site admin name? To change your Admin Name, in the Administration Screens, choose the Users->Your Profile menu. Make your changes there. However, you are not able to change the username from within the Administration screen. In order to do this you must directly edit the MySQL database, however this is not recommended as your username is not often seen by other users. See: Users Your Profile Screen How do I find the absolute path I need for uploading images? 1. Open the below page from your Browser http://(site URL)/wp-admin/options.php 2. Refer upload_url_path option value. If the value is blank, then the directory wp-content/upload is the default destination to save. Which files do I change to alter the way my blog looks? See: Theme Development Handbook How do I upload images? See: Inserting Media into Posts and Pages Can I change the "Error establishing database connection" message to something more descriptive? Just simply create a file to reside at wp-content/db-error.php, and in that file put the message you want displayed to users when WordPress determines the database connection is not available. That file will be used in place of "Error establishing database connection" message. You could even use the db-error.php to redirect users elsewhere. Here's an example for db-error.php: echo ' This site is currently experiencing a problem with the database server. Press your browser Reload button to try again!'; ?> Modifying Can I change the Smilies? See: Using Smilies How do I edit files? See: Editing Files What is The Loop? See: The Loop and The Loop in Action How can I change the URL-structure for my posts? See: Using Permalinks How can I change URL-structure for my posts on a Windows server? See: Using Permalinks Without mod rewrite How do I use WordPress Template Tags to change what is displayed on the blog? See: Template Tags How do I get All links to open in a new window? Put this inside the section of your Theme's template header.php file: See: Using Themes W3 Schools base tag explanation How can I add an image to my RSS feed? See: Add an image to your RSS 2.0 feed at wordlog.com If I turn off comments, it says "Comments Off" on the weblog. so how do I remove that? Depending on your theme, some other message of similar intent may be displayed. The specifics of how to remove this message is theme dependent. You should be able to find the offending text in your theme's comments.php file. If it's displayed by a PHP function, comment out the function with slash-asterisks '/*' and '*/' (without quotes) on either end of the function: If it's simply HTML, comment out the enclosing HTML tags by adding '' (not including the quotes, note the space after the first and before the last comment symbols): If you decide later to restore the message, you can simply remove the comment symbols. How do I change what is shown when I password protect a post? Hook the filters 'the_title' and 'the_password_form'. Your filter function is passed exactly what the filter names imply. Use the str_replace() function to search out the offending text and replace it with your preference (or nothing). Note the 'the_title' filter fires for every single title, not just password protected posts, so you need to use the existence of the post_password property to know whether to apply the string replace function or not. Some themes may also have additional locations where content needs to be canged. Next example works with Twenty Fifteen Theme. add_filter('the_title', 'replace_protected', 10, 2); function replace_protected( $title, $id ) { $post = get_post( $id ); if ( ! empty( $post->post_password ) ) { $title = str_replace('Protected:', 'Hidden:', $title); } return $title; } add_filter('the_password_form', 'replace_message'); function replace_message( $form ) { return str_replace('This post is password protected. To view it please enter your password below:', 'Enter you password below to see the surprise:', $form); } How can I allow certain HTML tags in my comments? Use a custom filter in your themes functions.php or plugin: add_filter('preprocess_comment','fa_allow_tags_in_comments'); function fa_allow_tags_in_comments($data) { global $allowedtags; $allowedtags['span'] = array('style'=>array()); $allowedtags['p'] = array(); return $data; } How can I add advanced search ability to WordPress? See: Advanced Contextual Search for Wordpress at Weblog Tools Collection Posts How do I upload an image and display it in a post? See: Inserting Media into Posts and Pages What is pingback? See: Introduction to Blogging, Pingbacks What is trackback? See: Introduction to Blogging, Trackbacks Where is the permalink to my post? See: Linking Posts, Pages, and Categories Can I use desktop blogging software? See: Weblog Client Can I blog by email? See: Post to your blog using email Spam, Spammers, Comments What can I do to stop comment spam? See: Combating Comment Spam More Information on Comment Spam See: Comment Spam Importing and Exporting How do I Import a WordPress WXR file when it says it is too large to import? If a WordPress WXR file, an XML file exported from WordPress, is too large to import, there are several things you might try to overcome that limit. Edit php.ini'. Some hosts may not allow this settings. memory_limit = 300M post_max_size = 200M upload_max_filesize = 100M max_execution_time = 600 memory_limit: Maximum amount of memory in bytes that a PHP script is allowed to allocate. post_max_size: Maximum size of post data allowed. upload_max_filesize: Maximum size of an uploaded file. max_execution_time: Maximum time in seconds a PHP script is allowed to run before it is terminated by the parser. Note: memory_limit should be larger than post_max_size, and post_max_size must be larger than upload_max_filesize. Edit .htaccess. Some hosts may not allow this settings. php_value memory_limit 300M php_value post_max_size 200M php_value upload_max_filesize 100M Edit wp-config.php define('WP_MEMORY_LIMIT', '64MB'); See also Increasing memory allocated to PHP. In multisite environment, configure following settings From Network Admin dashboard, select Settings > Network Settings and increase the values of 'Site upload space' and 'Max upload file size'. From Network Admin dashboard, select Sites > All Sites and click Edit menu under your site. Click Settings tab and incease the value of 'Site Upload Space Quota' or leave it blank for network default GZip the file. On some hosting services, a gzipped file can be automatically expanded in the background, without WordPress ever knowing the difference. This can allow you to make the file small enough to be fit into the maximum upload size constraints. On Windows, use 7Zip to create a gz archive out of the WXR file. On Linux, use the gzip command line. Make sure that the resulting file has the file extension of ".gz" before uploading it, as this is often necessary. This is not guaranteed to work, as it highly depends on the hosting configuration. If this fails, then try another method instead. Break the WordPress WXR file into smaller pieces by separating the data between posts and pasting the header/footer into each file. 1. Always have the header including all info like category, tags, etc to just before the first 2. Always have the footer 3. In between, add the posts start with end with and check to see whether the XML file you're creating is less than or equal to 2MB. You'll get the hang of it. 4. As always, before importing the new XML's, backup the database of the blog you are importing the XML files to and might as well export XML file of that blog as well for good measure. See: Importing Content Editing wp-config.php Forum discussion on program that helps with splitting the file into pieces WXR Splitter Utilities: WordPress WXR File Splitter utility for Windows WordPress WXR File Splitter utility for Mac OS X How do I import links (blogroll) from another WordPress blog? See: Importing Content Back to FAQ WordPress Backups atachibana — Sun, 08 May 2016 13:46:52 +0000 Note: Want to skip the hard stuff? Skip to Automated Solutions such as WordPress Plugins for backups. Your WordPress database contains every post, every comment and every link you have on your blog. If your database gets erased or corrupted, you stand to lose everything you have written. There are many reasons why this could happen, and not all are things you can control. With a proper backup of your WordPress database and files, you can quickly restore things back to normal. Instructions to back up your WordPress site include: WordPress Site and your WordPress Database Automatic WordPress backup options In addition, support is provided online at the WordPress Support Forum to help you through the process. Site backups are essential because problems inevitably occur and you need to be in a position to take action when disaster strikes. Spending a few minutes to make an easy, convenient backup of your database will allow you to spend even more time being creative and productive with your website. Backup Questions Back up your database regularly, and always before an upgrade. How often should you back up? That depends on how often you blog, how often you want to do this, and how you would feel if your database were lost along with a few posts. It is your decision. Can you use this method to back up other data? Yes. Backups are good all around. How many backups should I keep? The general rule of thumb is to keep at least three backups and keep them in three different places or forms, like CD/DVDs, different hard drives, a thumbdrive, web disk, your e-mail account, etc. This prevents problems if a single backup becomes corrupted or damaged. Can backups be automated? Yes. There are several methods of automating the backup process available, and we've listed some in the Automatic WordPress backup section. However, it is highly recommended that you back up those auto backups with a manual backup once in a while to guarantee that the process is working. Is there more information on backing up WordPress available? Yes. See Backup Resources for more information. Backup Documentation The following are general documents for helping you to back up and restore your WordPress data. Backing Up Your Database Restoring Your Database From Backup Backing Up Your WordPress Site There are two parts to backing up your WordPress site: Database and Files. You need to back up the entire site, and you need to back up your WordPress database. Below are instructions for backing up your WordPress database for various server programs. We will start with backing up the rest of your WordPress site. Your WordPress site consists of the following: WordPress Core installation WordPress plugins WordPress themes Images and files JavaScript, PHP, and other code files Additional files and static web pages All of these are used in various combinations to generate your website. The database contains your posts and a lot of data generated on your site, but it does not include the above elements that all come together to create the look and information on your site. These need to be saved. Most hosts back up the entire server, including your site, but it takes time to request a copy of your site from their backups, and a speedy recovery is critical. You need to learn how to back up your own site files and restore them. Here are some methods to backup your site files: Website Host Provided Backup Software Most website hosts provide software to back up your site. Check with your host to find out what services and programs they provide. Create Sync With Your Site WinSCP and other programs allow you to sync with your website to keep a mirror copy of the content on your server and hard drive updated. It saves time and makes sure you have the latest files in both places. Copy Your Files to Your Desktop Using FTP Clients or UNIX Shell Skills you can copy the files to a folder on your computer. Once there, you can compress them into a zip file to save space, allowing you to keep several versions. Remember, keep at least three backups on file, just in case one is corrupted or lost, and store them in different places and on different mediums (such as CD's, DVDs or hard drives). Database Backup Instructions Back up your WordPress database regularly, and always before an upgrade or a move to a new location. The following information will help you back up your WordPress database using various popular server software packages. For detailed information, contact your website host for more information. Accessing phpMyAdmin See phpMyAdmin for more information on phpMyAdmin. While familiarity with phpMyAdmin is not necessary to back up your WordPress database, these instructions should take you step-by-step through the process of finding phpMyAdmin on your server. Then you can follow the instructions below as a simple and easy backup. For more detailed instructions, see Backing Up Your Database. Plesk cPanel Direct Admin Ensim vDeck Ferozo Plesk On your Websites & Domains screen, click Open button corresponding to the database you have set up during the WordPress installation. This will open phpMyAdmin interface: If you cannot see the Open button, make sure to close the Start creating your website prompt: Click Select Existing Database to find select your WordPress database: cPanel On your main control panel for cPanel, look for the MySQL logo and click the link to MySQL Databases. On the next page, look for phpMyAdmin link and click it to access your phpMyAdmin. Direct Admin From Your Account page, look for MySQL Management and click it to access phpMyAdmin. Ensim Look for the MySQL Admin logo and click the link. Under Configuration choose MySQL Administration Tool. vDeck From the main control panel, click Host Manager, then click Databases. In the next window, click Admin. Another window will popup taking you to the phpMyAdmin login screen. Ferozo Login to your Ferozo Control Panel by using your credentials. Once inside, go to the “Base de Datos” (“Data Base”) menu and then click on “Acceso phpMyAdmin” (“Access phpMyAdmin”). A new window will open displaying the phpMyAdmin login screen. Simple Backup with phpMyAdmin The following is a very simple version of Backing Up Your Database. Once you have discovered how to access your site's phpMyAdmin, follow these simple instructions. 1. Click on Databases in your phpMyAdmin panel. (It may not be necessary to do this, depending on your version of phpMyAdmin) 2. You may have several databases. Click the one that holds your WordPress data, the database you created when you installed WordPress. (In older versions this may be done through a pull-down menu.) 3. Below is a picture of the default tables in the Structure view tab. You may have more tables -- this would happen if you have any statistics plugins or anti-spam plugins. 4. Click Export. There are two methods to export, Quick and Custom; if you choose Custom, follow these steps: Select all the tables. In the Output section check Save output to a file and select None for Compression. (If your database is very large use a compression method) Select SQL from the Format drop-down menu. Check "Add DROP TABLE": this can be useful for over-writing an existing database. Check "IF NOT EXISTS": this prevents errors during restores if the tables are already there. Click Go. The data will now be saved into your computer. 5. Keep these files safe, copied and stored in separate places on separate media. Automatic Backups Various plugins exist to take automatic scheduled backups of your WordPress database. This helps to manage your backup collection easily. You can find automatic backup plugins in the Plugin Browser on the WordPress Administration Screens or through the WordPress Plugin Directory. List of Backup Plugins Backup Resources FTP Backups - How to automate backing up to a FTP server Incremental Backups - How to make encrypted incremental backups using duplicity Backing Up Your Database Backing Up Your WordPress Files Restoring Your Database From Backup Using phpMyAdmin with WordPress Backup Tools Using phpMyAdmin FTP Clients Using FileZilla Creating a Favicon atachibana — Sat, 21 May 2016 16:47:32 +0000 A favicon (short for "favorite icon") is an icon associated with a particular website or web page. It is generally intended to be used when you bookmark a web page. Web browsers use them in the URL bar, on tabs, and elsewhere to help identify a website visually. Favicons are also used as application icons on mobile devices. A favicon is typically a graphic 16 x 16 pixels square, and is saved as favicon.ico in the root directory of your server. You can use a favicon with any WordPress site on a web server that allows access to the root directories. WordPress Version 4.3 or later WordPress Version 4.3 implemented a Site Icon feature that enables favicons on your web site. When you use the Site Icon feature, you don't need to prepare the favicon.ico file by yourself, or modify your template file. All you have to do is navigate to the Customize screen and specify a square image that has a height and width of at least 512 px. Later paragraphs in this article contain instructions for manually setting up your own favicon. However, it is highly recommended that you use the Site Icon feature (a feature that is built-in to WordPress) instead. Follow the steps below to use Site Icon to set up a favicon for your site. Prepare the image file. (It must be square, having a height and width of at least 512 px.) Navigate to Administration Screen > Appearance > Customize Click Site Identity Click Select Image (located under the Site Icon subheading). Click on the Upload Files tab, then click Select Files to upload the image file that you prepared in the previous step. Creating a Favicon A favicon can be created by using any graphics/image editing software that allows the saving of .ico files. There are also online services that will allow you to create a favicon for free. The image should be clear and visually appealing. Ideally it should be designed to match your site's brand image and/or content. To prepare the image to be saved as favicon.ico: Make the image square by cropping or adding space around it. Resize the image to 16 x 16 pixels. Save the file as favicon.ico. If you're using an online service to create your favicon (such as Faviconer.com or Dynamic Drive) follow the instructions provided by the site, and then download the favicon.ico image to your computer. Installing a Favicon in WordPress If there is already an old favicon.ico file in your current theme's main folder, delete it using an FTP Client. Use an FTP Client to upload the new favicon.ico file into your current theme's main folder. Upload another copy of your favicon.ico file to the main directory of your site (ex. http://example.com/favicon.ico). This will display the favicon in your subscribers' feed readers. In order for your favicon to show up in some older browsers, you will need to edit your page header. (Remember, the best way to edit your theme's files is via a Child Theme. As you follow along with the following instructions, it is highly recommended that you create and modify the copy of header.php that is located in your child theme.) Go to your WordPress Administration Screen. Click on Appearance. Click on Theme Editor. Select the file called Header or header.php to edit the file. Search for the line of code that begins with and ends with /favicon.ico" />. Overwrite it, if it exists, or add the following code below the HTML tag. Save the changes. How to create a favicon with a transparent background Before implementing this method, please make sure that your source image already has a transparent background, which means it should be a GIF or a PNG. The rest of the steps are as mentioned above. The one difference in the code is that, instead of using a favicon.ico file, use favicon.png or favicon.gif instead. Search for the line of code that begins with and ends with /favicon.ico" />. Overwrite it, if it exists, or add the following code below the HTML tag. To see your new favicon, clear your browser's cache. You may need to restart your browser in order to see the new favicon. Advantages of using .ico over .png or .gif Compatibility - As of this writing, most modern browsers--except for iOS Safari and Opera Mini--support the .ico format. Avoid 404 server errors - Virtually all modern browsers will request a favicon.ico, so it's best to always have a favicon.ico file, to avoid a "404 not found" error. An .ico file can hold more than one icon, so there is no need to include multiple files for 16x16 and 48x48 icons. Customizing the Read More atachibana — Sun, 29 May 2016 14:31:20 +0000 [codex_languages en="Customizing the Read More" ja_codex="「続きを読む」のカスタマイズ" ptbr_codex="Personalizando "Leia Mais""] If you have set your WordPress site to display post excerpts on the front or home page, you will want visitors to click on the title or a link to encourage them to continue reading your post or article, right? WordPress makes this technique easy, and customizable. The Excerpt Basics Excerpts (teasers) can be shown on WordPress through two methods: The first, keeping the the_content() template tag and inserting a quicktag called more at your desired "cut-off" point when editing the post. The second, by replacing the the_content() template tag with the_excerpt(). In both cases, if you have set anything in the Excerpt meta box on the post editor screen, that text will be used. Otherwise, the excerpt will be automatically trimmed. The most commonly used method is the first one, because the user editing the post can choose between showing the whole content or just the excerpt, individually for each post. However, using the_excerpt() in your template file can also get a teaser from the first 55 words of the post content, without the need to place a more quicktag in the post. To add a more quicktag in your post, put your cursor where you want to end the excerpted content of your post and click the more quicktag button. quicktags are the little buttons found above the editing window in your Administration > Post > Add New Post. They include bold, italic, links, and others, and the famous more. It will insert a code at that point that looks like this: [code language="html"] and I told him that he should get moving or I'd be on him like a limpet. He looked at me with shock on his face and said [/code] The rest of the post continues in the editing window, but when viewed on the non-single/non-permalink web page such as archives, categories, front page, and searches, the post is shown as an excerpt to the more point. Users can then continue reading more as you have enticed them with your summary introduction, by clicking on a link to the full article. Themes usually include this link in the title and the above methods will generate it by default trailing your teaser, as the example below. and I told him that he should get moving or I'd be on him like a limpet. He looked at me with shock on his face and said more... Read More Techniques The parameters within the template tag the_content() are as follows: [code language="php"] [/code] The $more_link_text sets the link text like "Read More". The second one, $strip_teaser, sets whether or not the teaser part or excerpt part before the more text should be stripped (TRUE) or included (FALSE). The default is FALSE, which shows the teaser part. To remove the teaser part: Change the_content(); in your index.php to (i.e., the second parameter controls this): [code language="php"] the_content( '', TRUE ); [/code] Include in the post text, immediately after the . Prevent Page Scroll When Clicking the More Link By default, clicking the .more-link anchor opens the web document and scrolls the page to section of the document containing the named anchor (#more-000). This section is where writers choose to place the tag within a post type. Users can prevent the scroll by filtering the_content_more_link with a simple regular expression. [code language="php"] function remove_more_link_scroll( $link ) { $link = preg_replace( '|#more-[0-9]+|', '', $link ); return $link; } add_filter( 'the_content_more_link', 'remove_more_link_scroll' ); [/code] Simply add the above code to the theme's functions.php file and the named anchors are no more. Modify The Read More Link Text Adding this code to your functions.php file enables you to customize the read more link text. [code language="php"] function modify_read_more_link() { return 'Your Read More Link Text'; } add_filter( 'the_content_more_link', 'modify_read_more_link' ); [/code] Code reference: https://developer.wordpress.org/reference/hooks/the_content_more_link/ Modify the Read More text when using the the_excerpt() Sometimes you can't afford adding a more quicktag to all your posts, so the only way to show an excerpt is modifying the template, changing the_content() to the_excerpt(). It will show the text "Read More" (Version 4.1 and later) or "[...]" (older versions). To customize this text, add the following code to your functions.php file. [code language="php"] // Replaces the excerpt "Read More" text by a link function new_excerpt_more($more) { global $post; return ' Read the full article...'; } add_filter('excerpt_more', 'new_excerpt_more'); [/code] If you are using a Child Theme, the above code will not work without modification if the parent theme has its own filters setting its own "more" link. You will need to use the remove_filter() function to remove the parent's filters for yours to work. The problem is your functions.php file is loaded before the parent's functions.php, so at the time of your file's execution, there is no filter to remove yet, and your remove_filter() code will fail without warning. The key is to put your remove_filter() code in a function that executes from an action hook that triggers after the parent theme is loaded. The following code is an example of the additional code needed to get the above code to work from a child theme of the parent theme Twenty Eleven. You will need to examine your actual parent theme's code for the correct parameters in the remove_filter() code, they must exactly match the add_filter() parameters used by the parent. [code language="php"] function child_theme_setup() { // override parent theme's 'more' text for excerpts remove_filter( 'excerpt_more', 'twentyeleven_auto_excerpt_more' ); remove_filter( 'get_the_excerpt', 'twentyeleven_custom_excerpt_more' ); } add_action( 'after_setup_theme', 'child_theme_setup' ); [/code] Customizing the "more…" text Seeing that you know how it works, now look at how we can make this little invitation to continue reading your post be more inviting. By design, the the_content() template tag includes a parameter for setting the text to be displayed in the the "more…" link which allows you to continue reading. By default, it looks like this: and I told him that he should get moving or I'd be on him like a limpet. He looked at me with shock on his face and said more... If you want to change the words from more.... to something else, just type in the new words into the template tag: [code language="php"] [/code] Or get more sophisticated and make it fun: [code language="php"] [/code] You can style the text in the template tag, too. [code language="php"] ...on the edge of your seat? Click here to solve the mystery.'); ?> [/code] Then set the moretext class in your style.css style sheet to whatever you want. Here is an example of the style which features bold, italic text that is slightly smaller than the default text: and I told him that he should get moving or I'd be on him like a limpet. He looked at me with shock on his face and said ...On the Edge of Your Seat? Click Here to Solve the Mystery. Some people do not want the text and prefer to use an extended character or HTML character entity to move the reader on to the full post. [code language="php"] [/code] Would look like this: and I told him that he should get moving or I'd be on him like a limpet. He looked at me with shock on his face and said » » » » If you want to include the title of the post in the more text, use the_title() template tag:: [code language="php"] [/code] and I told him that he should get moving or I'd be on him like a limpet. He looked at me with shock on his face and said ...continue reading the story called A Tale That Must Be Told Having a custom text for each post Although the_content() is usually called from the template with a standard text as described above, it is possible to have an individual text for certain posts. In the text editor, simply write . So, you may have something like this: Adding An Image The design possibilities with CSS are practically unlimited, and WordPress allows you to use images in many of their Template Tags, including the more tag. To add an image, there are two ways to do it. Begin with the most simple -- listing it in the_content() template tag. This examples features the image of a leaf after the "Read More" text and assumes that the image file is within your theme's images folder. [code language="php"] [/code] Notice that the code uses an ALT and TITLE in the image tag. This is in compliance with accessibility and web standards, since the image is both an image and a link. Here is what it might look like. and I told him that he should get moving or I'd be on him like a limpet. He looked at me with shock on his face and said Read More... You could even add a style to the image and more tag, as mentioned above, to style it even more. To use the image without the "Read More" text, just delete the text. The second example uses the CSS background image. We have described how to use style classes in the above examples. This is a little tricker. The container's style must be set to allow the background image to show out from behind the text. If you were to use the above example as a background image, the style.css style sheet for this might look like this: [code language="css"] .moretext { width: 100px; height: 45px; background:url(/images/leaf.gif) no-repeat right middle; padding: 10px 50px 15px 5px} [/code] The 50px padding against the right margin should make sure the text is pushed over away from the image as to not overlap it. The height ensures that the container will expand wide enough so the image is visible within the container, since a background image isn't "really there" and can not push against the container's borders. You may have to experiment with this to fit the size and shape of your own image. You have gotten the basics. From here, it is up to your imagination. How to use Read More in Pages Please remember that the "Read More" tag is used only on the Home page which shows the latest posts. It does not work in "Pages". If you want to turn it on in Pages too for showing a set of partial posts, use the following code inside the loop for the dynamic content: [code language="php"] //The code must be inserted ahead of the call the_content(), but AFTER the_post() [/code] When to set $more It's important that if you're going to over-ride the default $more global variable you do it inside The Loop, but after your setup the post. If you're working with the standard Loop and using the_post(), make sure you set $more after the_post (but before the_content(). See More tag ignored on static front page forum topic. More about $more If you set the $more variable to -1, the More tag will not be displayed. This can be useful in a "mullet loop", which displays the full content for only the first post, and then displays only excerpts for all remaining posts. Like this: [code language="php"] [/code] Writing Code in Your Posts normalize — Tue, 31 May 2016 14:14:01 +0000 Whether you write plugins or hacks for WordPress, or you want to add bits and pieces of code about your own WordPress site or other programming code like HTML, CSS, PHP, or JavaScript, putting code in your post that looks like code, but doesn't behave like code, is a frequent challenge for bloggers. By default, the way a piece of code written or pasted to WordPress post editor is interpreted depends on whether you use visual or HTML post editor. Visual editor will consider the code to be an ordinary text, converting (encoding) the < and > characters into their < and > character entity equivalents, so that the code is not interpreted by a web browser. Quotes are converted too, but remember that by default, WordPress also applies auto-correction so that the text is quoted properly according to your language specifics. HTML editor does not convert any of these characters, so be aware that HTML and CSS markup you use in your code examples will be recognized by a web browser and you may end up with a funky looking text and a messed up layout. Note that this behavior may differ with respect to the WordPress version, post editor and other plugins used. In some older versions of WordPress, unrecognized uses of the < and > characters were converted into the < and > character entities, and when an HTML tag was found within the post, the tag was left as it was, allowing for its interpretation in a web browser. In general, there are two uses of code within a web page. There is code found within a paragraph to make a point about the code that is being discussed, and then there is code that is highlighted... [code]in such a way as to look like a block of code.[/code] Code Within Paragraphs The HTML tag which will turn text into a monospaced font is . The tag distinguishes text that is computer code from natural language. This is an example which mentions code within a paragraph, namely the functions wp_title(), wp_content(), and wp_footer(), which are very useful in WordPress. This is great for making a piece of non-HTML text look like code, but what about HTML tags that you want to showcase? In the header.php template file, look for the section to change the heading. Using the tag doesn't tell WordPress to encode HTML markup within the tag or strip it from the post. WordPress thinks that you are using this markup for formatting, leaving it untouched. A web browser then sees a tag followed by a tag and so it responds by creating a new container in your web page. Similarly afterwards, it sees the start of an tag which will screw up your entire web page layout and design, like this: In the header.php template file, look for the section to change the heading. To avoid this behavior, use character entities or extended characters to represent the left and right arrow characters in a way that is not recognized as the beginning and end of an HTML tag by a web browser, like this: In the header.php template file, look for the section to change the heading. URLs Within Paragraphs By default, WordPress will turn any phrase that begins with http: into a link. If you are giving an example of how to link to a specific post within a WordPress site, instead of using the link with http://example.com/index.php?p=453 and having it turn into a link, you can use extended characters for the slashes, so WordPress won't "see" the link: http://example.com/index.php?p=453 List of Related Character Entities Here is a list of some HTML character entities related to the topic of this article: < = < or < > = > or > / = / ] = ] [ = [ " = " or " ' = &39; “ = “ or “ ” = ” or ” ‘ = ‘ or ‘ ’ = ’ or ’ & = & or & There is a list of resources below which will help you turn HTML tags into character entities automatically, so you don't have to memorize these character codes. Troubleshooting Codes Writing code within a WordPress post can be a challenge, maybe forcing you to override the WordPress default styles and to use filters which "fix" what we write. If you are having trouble with writing code within your WordPress post, this section might help. Quotes Auto-correction A frequent problem when using codes within your post is the quotes auto-correction feature of WordPress, mostly known from word processing software. By default, when serving a web page, WordPress converts the "straight" quotes into the opening and closing “curly” quotation marks according to your WordPress installation language set in the wp-config.php file. Note that the auto-correction (also called smart quotes) feature is applied regardless of whether you have written the quotes in visual or HTML post editor. In HTML post editor, you can avoid this problem by wrapping the quotes with the tags. Other solution is replacing quotes with their respective character entities, e.g. using: [code]<p class="red">[/code] instead of: [code][/code] Note that in some older versions of WordPress, if you edited a page again after publishing it, the HTML editor replaced all these entities with their literal equivalents. For example, if you carefully used " for your quotes, they would have come back as ", and if saved, the auto-correction feature would have an effect on them. Resources Fun Character Entities WordPress Resource Tools Encode Frequent Code User If you consistently use a lot of formulas, functions, and programming code in your posts, consider using a plugin or PHP tool to make the entire process easier. If you tend to post a LOT of code blocks, consider pasting the code in a Paste Bin and linking to it on your site. FigureRender - LaTeX rendering plugin 9 Syntax Highlighter Plugins and Services for Embedding Code Snippets in WordPress - Following are list of best WordPress plugins or 3rd-party services to highlight code snippets within your blog that I have personally tried in 2013. Coffee2code's Preserve Code Formatting WordPress Plugin QuickCode WordPress Plugin - Hides/unhides formatted blocks of code. Using ASCIIMath LaTex - A document preparation system Using LaTeX in WordPress Display mathematical equations within your posts using the phpmathpublisher library How to Build Dean Lee's Plugin - A plugin for GeSHi - Generic Syntax Highlighter Visual Code Editor Plugin - Modifies WordPress's behavior so that code format is preserved when using the visual editor. It will work with any syntax highlighter that accepts encoded/escaped syntax. SyntaxHighlighter Evolved - allows you to easily post syntax-highlighted code to your site without having to escape the code. Uses the SyntaxHighlighter JavaScript package by Alex Gorbatchev to do the highlighting and supports all of the package’s parameters via shortcode. Paste Tools Pastebin.com GitHub:Gist Pastie Using Image and File Attachments juhisaxena — Wed, 08 Jun 2016 05:18:46 +0000 In WordPress you can upload, store, and display a variety of file types or media. The most common file types are image, video and audio files, but other file types such as document files, spreadsheet files, and code samples (among others) can also be managed within WordPress. Media can be uploaded by accessing either Media > Add New or Media > Library (both of which are found in the admin panel sidebar). Media can also be uploaded by using quick links on the edit screen. In order to upload media, you may need to ensure that the correct file permissions are set for the wp-content directory in your WordPress installation. Contents 1 Edit Screen Links 2 Attachment to a Post 3 Inserting in a Post 4 Usage in Themes 5 See Also Edit Screen Links By default, above the post editing area is a link to add media into the post. Attachment to a Post If a media file is uploaded within the edit screen, it will automatically be attached to the current post being edited. If it is uploaded using Media > Add New or Media > Library, it will be unattached. However, it can still be attached to a post when it is inserted into that post. (When using Media > Library, there is also an option to attach previously unattached media items.) Note that media items are considered posts in their own right and can be displayed as such via the WordPress Template Hierarchy. Themes can make use of this feature to loop over media items, or to create galleries. If the parent post of an attached media item is deleted, the media item will remain attached to the deleted post's parent (if it exists). If there is no parent for the deleted post, then the media item becomes unattached, and is open for reattachment to another post. Inserting in a Post Once a media file has been uploaded, it may be inserted into a post. When the media file is inserted you can choose to: Link directly to the media file. Link to the attachment post, in which case the file will be served via the WordPress Template Hierarchy. Not link to the media file. (For example, in the case of images, the image file will still be embedded in the page, but not linked to allow the browser to display the image file by itself.) Usage in Themes Themes may use various template tags to display post attachments. They may also use the attachment.php file to customize the display of attachments. In addition, a shortcode tag is available to display a gallery of images attached to a post. See Also Using Images Media > Add New SubPanel Media > Library SubPanel Template Hierarchy Post Thumbnails Gallery Shortcode Embeds Common WordPress Errors atachibana — Sun, 19 Jun 2016 14:15:31 +0000 If you are encountering a WordPress error message or white screen, don't panic. Someone has likely encountered the same message before and it can easily be solved. This page lists the most common WordPress errors experienced by WordPress users, and provides a starting point for fixing them. You will also find links to more detailed pages on the HelpHub and DevelopersHub. If you can't find your answers here, try the WordPress Support Forums where a volunteer will be there to help. The White Screen of Death Both PHP errors and database errors can manifest as a white screen, a blank screen with no information, commonly known in the WordPress community as the WordPress White Screen of Death (WSOD). Before resorting to desperate measures, there are a number of reasons for the WordPress white screen of death: A Plugin is causing compatibility issues. If you can access the Administration Screens try deactivating all of your Plugins and then reactivating them one by one. If you are unable to access your Screens, log in to your website via FTP. Locate the folder wp-content/plugins and rename the Plugin folder plugins_old. This will deactivate all of your Plugins. You can read more about manually deactivating your plugins in the Troubleshooting FAQ. Your Theme may be causing the problem. This is especially likely if you are experiencing the white screen of death after you have just activated a new Theme, or created a New Site in a WordPress Network. Log in to the WordPress Administration Screens and activate the default WordPress Twenty Fifteen Theme. If you can't access your Administration Screens, access your website via FTP and navigate to the /wp-content/themes/ folder. Rename the folder for the active Theme. The WP_DEBUG feature often provides additional information. If you are still experiencing problems and are looking in your error logs you can check out the PHP errors below for more information. Internal Server Error There can be a number of reasons for an Internal Server Error. Here are some thing you can do to solve it: The most likely issue is a corrupted .htaccess file. Log in to your site root using FTP and rename your .htaccess file to .htaccess_old. Try loading your site to see if this has solved your problem. If it works, make sure to visit Settings > Permalinks and reset your permalinks. This will generate a new .htaccess file for you. Try deactivating all of your Plugins to see if it is a Plugin issue. If you are unable to access your WordPress Administration Screens, deactivate your Plugins via FTP by following these instructions. Switch the Theme to the WordPress Twenty Fifteen Theme to eliminate any Theme-related problems. Increase the PHP Memory limit Try re-uploading the wp-admin and wp-includes folders from a fresh install of WordPress. Error Establishing Database Connection If you get a page featuring the message "Error Establishing Database Connection," this means that there is a problem with the connection to your database and there could be a number of reasons for this. The following are possible reasons and solutions. Incorrect wp-config.php Information "Error establishing a database connection" is usually caused by an error in your wp-config.php file. Access your site in your FTP client. Open up wp-config.php and ensure that the following are correct: Database name Database username Database password Database host Learn more about editing wp-config.php. If you are sure your configuration is correct you could try resetting your MySQL password manually. Problems with Your Web Host The next step is to contact your web host. The following hosting issues may be causing the problem: Your database has met its quota and has been shut down. The server is down. Contact your hosting provider to see if either of these issues is causing your problem. Compromised Website If you have checked wp-config.php for errors, and confirmed with your host for hosting issues, it is possible that your site has been hacked. Scan your site with Sucuri SiteCheck to ensure that it hasn't been compromised. If it has you should check out My Site was Hacked. Failed Auto-Upgrade There will be situations when the WordPress auto-update feature fails. Symptoms include: A blank white screen and no information. A warning that the update failed. A PHP error message. The WordPress automatic upgrade feature may fail due to a glitch in the connection with the main WordPress files, a problem with your Internet connection during upgrade, or incorrect File Permissions To update your WordPress site manually, see the Manual Update article. Connection Timed Out The connection timed out error appears when your website is trying to do more than your server can manage. It is particularly common on shared hosting where your memory limit is restricted. Here are some things you can try: Deactivate all Plugins. If deactivating all the WordPress Plugins on your site resolves the issue, reactivate them one-by-one to see which plugin is causing the problem. If you are unable to access your Administration Screens, read about how to manually deactivate your plugins. Switch to the default WordPress Twenty Fifteen Theme. This should rule out any Theme-related problems. Increase your memory limit in wp-config.php. If you are on shared hosting you may have to ask your hosting provider to increase your memory limit for you. Increase the maximum execution time in your php.ini file. This is not a WordPress core file so if you are not sure how to edit it, contact your hosting provider to ask them to increase your maximum execution time. See instructions for increasing maximum execution time. Maintenance Mode Following Upgrade When WordPress updates, it automatically installs a .maintenance file. Following upgrade, you may receive a message that says "Briefly unavailable for scheduled maintenance. Please check back in a minute." The maintenance file may not have been removed properly. To remove this message do the following: Log in to your website using your FTP program Delete the .maintenance file, which will be found in your site root. Read more about the maintenance mode issue. You Make Changes and Nothing Happens If you are making changes to your website and you do not see the changes in your browser, you may need to clear your browser cache. Your browser stores information about the websites that you visit. This makes it faster to load websites when you visit them because the browser just has to reload information already stored on your computer, rather than downloading it again. If you make a change to a website and the browser does not think it is significant, it will simply load the data from your cache, and you won't see your changes. To fix the problem, simply empty your browser cache or close the tab and reopen the link. Pretty Permalinks 404 and Images not Working If you are experiencing 404 errors with pretty permalinks and a white screen when you upload images, mod_rewrite may not be enabled in Apache by default. Mod_rewrite is an extension module of the Apache web server software which allows for "rewriting" of URLs on-the-fly. It's what you need to make pretty permalinks work. WordPress Multisite networks usually experience this but it can also occur on shared hosting providers or after a site migration or server move. Reset your permalinks through Settings > Permalinks. If this does not work, you may have to edit the .htaccess file manually. [code language="php"]# BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> # END WordPress [/code] If you are not familiar with editing your .htaccess file, contact your hosting provider to ask them to turn on mod_rewrite rules. There is more information on pretty permalinks in the WordPress Codex. Custom Post Type 404 Errors You may experience problems with 404 errors and custom post types. Try the following steps: Make sure that none of your Custom Post Types and single pages have the same name. If they do, rename the single page, including the slug. Log in to your WordPress Administration Screens, navigate to Settings > Permalinks. Select the default permalinks. Save. Then reselect your preferred permalinks. This will flush the rewrite rules and should solve your problem. Specific Error Messages There are a number of different errors that will appear in your error logs. To access your error logs you will need to turn on debugging and then locate your error log via FTP. The following information will help you to decipher some of the common error messages. PHP Errors Below are some common PHP error messages. Fatal Errors and Warnings Cannot modify header information - headers already sent If you receive a warning that WordPress cannot modify header information and headers are already sent, it usually means that you have spaces or characters before the opening tags or after the closing tags. Read how to fix the headers already sent error. If you are experiencing this problem when you have just installed WordPress you may have introduced a syntax error into wp-config.php. These instructions will help you to fix the error. Call to undefined function An error reading call to undefined function could mean that a WordPress Plugin is trying to find a file or data which isn't present or accessible in the code. Reasons for this include: An error when trying to auto-install or auto-upgrade a Plugin. Try installing or upgrading the Plugin manually. An error when trying to auto-install or auto-upgrade a Theme. Try installing or upgrading the Theme manually. You may be using an incompatible WordPress Plugin or incompatible Theme. This could happen with older versions of WordPress and a new WordPress Plugin, or if you are trying to use a WordPress Multisite Plugin on a single site installation. Upgrade WordPress to resolve this issue. You may be trying to call a function that doesn't exist. Check functions.php for misspellings. Try deactivating the WordPress Plugin or changing the WordPress Theme that caused the error to appear. If you are unable to do this from within the Administration Screens, you may have to do this manually via FTP. Allowed memory size exhausted An Allowed Memory Size Exhausted error means that your WordPress installation doesn't have enough memory to achieve what you want. You can try out the following steps: Increase your memory limit in wp-config.php Increase your memory limit by editing php.ini. This is not a file that comes with WordPress so if you are unfamiliar with it you should contact your web host about increasing your memory limit. Maximum execution time exceeded You may receive a message such as "Maximum execution time of 30 seconds exceeded" or "Maximum execution time of 60 seconds exceeded". This means that it is taking to longer for a process to complete and it is timing out. There are a number of ways to fix this error. Editing .htaccess Make sure you back up .htaccess before you edit it. Add the following line to .htaccess: [code language="php"] php_value max_execution_time 60 [/code] Editing php.ini Add the following to php.ini [code language="php"] max_execution_time = 60 [/code] If you are unsure of how to make these changes, or if you are on shared hosting that prevents you from making them yourself, you should contact your hosting provider and ask them to increase your maximum execution time. Parse errors Syntax Error A syntax error means that you have made a mistake while creating your PHP structure. You could, for example, be; Missing a ; at the end of an individual line. Using curly quotation marks. Missing a curly bracket. When this error appears it will tell you which file the error appears in (functions.php for example) and approximately which line (it may not always be the exact line so be sure to check just before and just after) in the code. Unexpected If you are receiving an error which says 'parse error: unexpected' this usually means that you have forgotten to include a character. The most common are: Unexpected '=' : you have forgotten to include the $ when referencing a variable Unexpected ')' : you have forgotten to include the opening bracket ( Unexpected '(' : you have forgotten to include the closing bracket ) Unepxpected T_STRING: you have forgotten a quotation mark or a semi-colon at the end of the previous line Unexpected T_ELSE: you have an else statement with no opening if statement Use of an undefined constant As with parse errors, "use of an undefined constant" means that you are missing a character. It could be one of the following: Missing a $ when referencing a viariable Missing quotation marks around array keys Database Errors The following errors may appear in relation to your WordPress database. Cannot Create/Write to File There are a number of reasons why you may be experiencing this error: MySQL cannot create a temporary file The file permissions are incorrect To fix the problem you will need to either: Alter alter the tmpdlr variable to point to a writable directory. Correct the File Permissions. CREATE Command Denied to User This error occurs when the user assigned to the database does not have adequate permissions to perform the action to create columns and tables in the database. You will need to log in to CPanel or Plesk to give your database user adequate permissions. Alternatively you can create a new user to assign to your database. If you do create a new user you will need to ensure that it is updated in wp-config.php. Error 28 This MySQL error has nothing directly to do with WordPress. You should contact your host about it. It may be caused by one of a number of reasons: Your cache on your server is full. You should contact your web host to resolve this. You have too many files in your /tmp. Again, contact your web host. You can read more about Error 28 in the Troubleshooting FAQ. Error 145 This indicates that a table in your database is damaged or corrupted. If you are comfortable using phpMyAdmin you can use these instructions on repairing your MySQL database tables. Always backup your database before performing any actions on it. If you have not used phpMyAdmin before, or are uncomfortable doing so, contact your web host and ask them to run CHECK/REPAIR on your database. Unknown Column An unknown column error can be caused by a missing column in the database. If you have just upgraded WordPress then try manually upgrading again. To update your WordPress site manually, see the Update article. If you are running a database query when you encounter the error then you may by using incorrect quotation marks for the identifier quote character. This question on Stack Overflow provides more details. Also see the MySQL documentation. Resources Troubleshooting Advanced Topics PHP Glossary MySQL Error Codes and Messages WP Error Fix Plugin Hosting WordPress geoffreyshilling — Thu, 30 Jun 2016 16:47:11 +0000 Most hosting providers and personal installations on Unix/Linux systems should be able to host WordPress under very common configurations. Server Requirements WordPress server requirements: PHP version 5.6 or greater MySQL version 5.6 or greater or MariaDB version 10.0 or greater (Optional) (Required for Multisite) Apache mod_rewrite module (for clean URIs known as Permalinks) Note: If you are in a legacy environment where you only have older PHP or MySQL versions, WordPress also works with PHP 5.2.4+ and MySQL 5.0+, but these versions have reached official End Of Life and as such may expose your site to security vulnerabilities. For this reason, it's best you follow the recommended setup above and use the latest versions of PHP and MySQL/MariaDB that your host supports. Recommended Setup It is recommended you use a platform comprised of the Linux operating system, and either the Apache or NGINX webserver, but any server that supports PHP and MySQL will do. For permalinks your server needs to support mod_rewrite, or an alternative. Also your hosting is more secure when PHP applications, like WordPress, run using a separate user account instead of the servers default shared username. It is also essential that your host allows remote connections for many of the WordPress features to work. If your host blocks outgoing HTTP connections, many parts of WordPress might not function. Hosting Providers Hosting is a commodity these days and with a little digging, it's easy to find a host that supports the above. If you're looking for hosting suggestions, please try: WordPress Recommended Hosts - these hosts support WordPress, in more ways than one. Searching the WordPress support forums for recommendations See WordPress Speedtest if you are planning to rent a VPS for hosting your WordPress site WordPress Feeds atachibana — Sun, 03 Jul 2016 14:38:38 +0000 [codex_languages en="WordPress Feeds" ja_codex="WordPress Feeds" ko_codex="WordPress Feeds" ptbr_codex="Feeds no WordPress"] Introduction to Feeds A feed is a function of special software that allows feedreaders to access a site, automatically looking for new content and then posting the information about new content and updates to another site. This provides a way for users to keep up with the latest and hottest information posted on different blogging sites. There are several different kinds of feeds, read by different feedreaders. Some feeds include RSS (alternately defined as "Rich Site Summary" or "Really Simple Syndication"), Atom or RDF files. WordPress Built-in Feeds By default, WordPress comes with various feeds. They are generated by template tag for bloginfo() for each type of feed and are typically listed in the sidebar and/or footer of most WordPress Themes. They look like this: URL for RDF/RSS 1.0 feed URL for RSS 0.92 feed URL for RSS 2.0 feed URL for Atom feed URL for comments RSS 2.0 feed The first four feeds display recent updates and changes to your site's content for the different feedreaders. Of these, the RSS feeds are the most well known. The last feed example is used by RSS 2.0 feedreaders and does not show your site's content. It only shows the comments made on your site. To track the comments on a specific post, the post_comments_feed_link() template tag is used on single post pages like this: [code language="php"][/code] There are ways to modify these feeds, and these are covered in the article on Customizing Feeds. Finding Your Feed URL There are times when you want to tell someone your site's feed address or URL, or you need it to submit it to search engines and directories, many of which now accept feed URL submissions. There are four possible URLs for each of your feeds. Any of these will work. [code language="php"]http://example.com/?feed=rss http://example.com/?feed=rss2 http://example.com/?feed=rdf http://example.com/?feed=atom[/code] If you are using custom permalinks, you should be able to reach them through this usage: [code language="php"]http://example.com/feed/ http://example.com/feed/rss/ http://example.com/feed/rss2/ http://example.com/feed/rdf/ http://example.com/feed/atom/[/code] Comments Your site has feeds for all comments on the site, and each post has its own comment feed. Site comment feed Permalink format: [code language="php"]http://example.com/comments/feed/[/code] Default format: [code language="php"]http://example.com/?feed=comments-rss2[/code] Post-specific comment feed Permalink format: [code language="php"]http://example.com/post-name/feed/[/code] Default format: [code language="php"]http://example.com/?feed=rss2[/code] Categories and Tags You can also provide feeds to only specific categories or tags on your site by adding the following to the end of the link: [code language="php"]http://www.example.com/?cat=42&feed=rss2[/code] or [code language="php"]http://www.example.com/?tag=tagname&feed=rss2[/code] or [code language="php"]http://www.example.com/category/categoryname/feed[/code] or [code language="php"]http://www.example.com/tag/tagname/feed[/code] You can include posts from one of multiple categories or tags in a feed by comma-separating their values. For example: [code language="php"]http://www.example.com/?cat=42,43&feed=rss2[/code] or [code language="php"]http://www.example.com/?tag=tag1,tag2&feed=rss2[/code] or [code language="php"]http://www.example.com/category/cat1,cat2/feed[/code] You can include posts from all of multiple categories or tags in a feed by adding to the end of the link. For example: [code language="php"]http://www.example.com/category/cat1/category/cat2/feed[/code] or [code language="php"]http://www.example.com/tag/tag1/tag/tag2/feed[/code] You can exclude categories from the feed by using something like this: [code language="php"] http://www.example.com/?cat=-123&feed=rss2 [/code] Older versions of WordPress used a format such as but this has been deprecated in newer versions. [code language="php"]http://example.com/wp-rss2.php?cat=42[/code] Authors Every author has an RSS feed for their posts. Here is the format: [code language="php"]http://example.com/author/authorname/feed/[/code] Search Search results can also have their own feed. Here is the format: [code language="php"]http://example.com/?s=searchterm&feed=rss2[/code] Adding Feeds Not all WordPress Themes feature all of the RSS Feed types that are available through WordPress. To add a feed to your site, find the location of where the other feeds are, typically in your sidebar.php or footer.php template files of your Theme. Then add one of the tags listed above to the list, like this example: [code language="php"] RSS'); ?> RSS'); ?> [/code] Adding Graphics to Feed Links Many people like to have a graphic representing the feed instead of words. There are now standards for these graphics or "buttons", but you can make your own to match the look and colors on your site. To add a graphic to your feed link, simply wrap the link around the graphic such as: [code language="php"] http://www.mozilla.org/images/feed-icon-14x14.png" alt="RSS Feed" title="RSS Feed" /> [/code] Changing Addresses If you are currently using other webblog software and are changing to WordPress, or are moving your weblog to a new location, you can "forward" RSS readers to your new RSS feeds using file rewrites and redirects in your .htaccess file. Edit the .htaccess file in your root folder; if no file exists, create one. Here is an example for a b2 feed: [code language="php"]RewriteRule ^b2rss2.php(.*)? /wordpress/?feed=rss2 [QSA][/code] Here is an example for MovableType Users: [code language="php"]RewriteRule ^index.xml(.*)? /wordpress/?feed=rss2 [QSA][/code] Feed Director provides rewrite rules for common feed filenames used by other blogging platforms, such as index.xml, index.rdf, rss.xml, rss2.xml, atom.xml, *.xml, via an easy-to-use "install it and forget it" plugin. RSS feed time and date format WordPress adheres to the RSS specifications. This means that the time and date format will NOT use your blog time/date format as set in your settings, instead it uses the time and date format from the RFC822 specification. This looks for example like this: Sun, 06 Sep 2009 16:10:34 +0000 Note: The time/date format of feed should NOT be localized since the the current RSS specifications are referring to RFC822 specification which specifies English as a default. This implies that every RSS consumer should take care of translating time/date according to its locale. Feed Errors in Browsers A feed is a stream of data meant to be interpreted by a feed reader, like NewsBlur or RSSOwl. Not all browsers have the capability to interpret feeds, and one of the most popular browsers lacking this feature is Google Chrome. Users of Chrome and other similar browsers will notice a "This XML file does not appear to have any style information associated with it. The document tree is shown below." error followed by the raw feed. This is normal, as Chrome was not built to interpret feeds. Instead, subscribe to the feed in a real feed reader, or install Google's RSS Subscription Extension. More Information and Resources Feed error - How to - hints and tips to solve common feed errors (ex. white spaces before xml declaration) Customizing Feeds Styling your RSS feeds How to setup and create category RSS feeds Complete reference for determining your various WordPress feed URLs How to add an image to your RSS feed in WordPress 2.0 and above Work with RSS in WordPress site (Pre 2.0) How to add an image to your RSS 2.0 feed How to add images to RSS and Atom feeds Add RSS feed link icons to WordPress categories Mezzoblue's What is RSS/XML/Atom/Syndication? NewsForge: Save time with syndication Using FeedBurner with WordPress Changing feed url with .htaccess Redirect WordPress Feeds to Feedburner without a plugin Subscribe Me allows you to easily add various subscription buttons to your sidebar Add to any Subscribe Button plugin lets your visitors add your feed to any feed reader Feed Icons provides official RSS icons in many formats (AI, EPS, SVG, PSD, PDF, PNG, JPG, GIF). WP RSS Aggregator an RSS aggregrator/import plugin for WordPress Wikipedia - RSS an overview on RSS Playing With Fonts normalize — Mon, 27 Jun 2016 01:13:58 +0000 Fonts Represent Your Content There's no doubt that your words, your posts, are the meat and potatoes of your blog or website. Those words, along with your lovely colors and pictures, tell your website's story. But, don't forget to pay attention to your font selections. The fonts you choose in designing your theme can influence whether or not people hang around to see more than a page or two of your pretty work. Fonts come in a wide variety of types and styles. Fonts can either be loaded from the site visitor's computer or downloaded to the visitor's computer when the website loads. Fonts loaded from a visitor's computer are known as "web safe" fonts as these will always load; fonts downloaded to a visitor's computer may not always load. A website can set a desired font and also list fallback fonts which will load in the event the desired font is not available. Themes Control Fonts In your theme's style sheet (style.css usually) you can control the font-family (the list of fonts to display), the color, the size, and other aspects of your font. The following example sets the fonts for your sidebar menu, sets the size to 1em high, and sets the color to blue: [code]#menu { font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 1em; color: blue; }[/code] As you can see, you've set more than one font in the font-family. If the user doesn't have Verdana, Arial will take over. If Verdana and Arial are missing, they have a chance to use Helvetica. If all else fails, the user's system fonts takes over and uses the default font for sans-serif. This list of choices helps the designer control the fonts and insures a more consistent look and feel. Font families tend to be single words, but on occasion you will find a phrase to represent a font such as Lucida Console. This is set in the style selector surrounded with quote marks such as: [code]#menu { font-family: Verdana, Arial, Helvetica, "Lucida Console", sans-serif; } [/code] Fonts in WordPress WordPress Themes use fonts in many different ways, and not always consistently. It depends upon the Theme author's decisions and needs in designing a Theme. Different fonts can be found in different areas of the website, one type in the header, another in the sidebar (or maybe two or three), and another font style or type in the post content area. Finding those fonts in order to change them, can give a user grief. Since fonts can be anywhere, finding the font you want to change can be a challenge. Generally, an overall font is set in the body of a website. [code]body { font-family: Verdana, Arial, Helvetica, Futura, sans-serif; font-size: 1em; padding: 0; margin: 0; } [/code] This covers the definition of the fonts found within the site that are not defined by a specific tag, class, or div. It's the "fall back font." Fonts found within the header of a site are normally found within the header div and same for the sidebar or menu and footer style divisions. The content, though, may be more challenging to track down. Fonts within the post content area are often, but not always, found within the following CSS classes: content post entry post-entry They may have the font information in the specific class or in a paragraph tag: [code].content p { margin: 5px; padding: 5px; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: 110%; color: black; } [/code] Fonts within the sidebar or menu nested lists can be very difficult to narrow down. For a step-by-step guide of all the nested lists found within many WordPress sites, see Styling Lists with CSS. If you are still having trouble tracking down a specific font code, consider using some of the tips and techniques in Finding Your CSS Styles. Which Font Determining which font will work best on your site is a personal choice, but there are articles that will help you decide. We recommend that you begin with fonts that are most commonly found on most computers and that are easy to read. Font Surveys To find out what fonts are most popular, check out the following: Web Style Guide: Typefaces Font Face Fonts can be downloaded to a user's computer using a CSS rule called @font-face. This allows the use of fonts the user doesn't have installed on their system. To use the @font-face rule you must do two things: Add the @font-face rule to your style.css file. Upload the custom font to your website. You should add the @font-face rule to the top of the styles.css like this: [code]@font-face { font-family: Museo300; src: local('Museo300-Regular'), url("fonts/Museo300-Regular.ttf") format('truetype'); font-weight: normal; } [/code] You'll now need to upload the custom font to your website. You can do this either by using FTP or cPanel. You should upload the font to your theme's folder, found under /wp-content/themes/theme-name/. Finally, you can now use the font you've added anywhere in your style.css file: [code].post-item { font-family: Museo300; } [/code] You can get more information about @font-face rule in following links: Official document about font-face rule The Essential Guide to @font-face Google Fonts An alternative for using @font-face is to use Google's free font embedding service, Google Fonts. Using a plugin such as Easy Google Fonts, one can easily add any font from Google's library. Install and activate the plugin, the head to Appearance > Customize. Open the Typography tab and you'll be able to choose from Google Font's library, with the Customizer's live preview. Make your changes, and Save & Publish when done. Font Sizes You can also change the font size your viewers see. In the days of the typewriter and even with today's word processors and desktop publishing software, the "point" system is still in use. You should be familiar with things like "12pt Times Roman" and "8pt Arial." Point sizes don't work well on web pages because most browsers can't interpret what a "point" is. They understand pixels and percentages of a base size, but typewriter point sizes are interpreted differently on different browsers. You can use point size, but there are better alternatives. You can set your fonts to be absolute, which means they are fixed in size, but that has disadvantages as well. The problem with absolute font size is that if a user has their browser set to "see" larger fonts (View > Text Size) or are using special software for the visually or physically disabled, you may have taken away their rights to "see" larger fonts. If you have to set the font to a specific size in order for your layout to work, make sure you don't use that font for your site's more important information. This example shows how to set an absolute font size: [code]#menu ul li { font-size: 12px; color: green; } [/code] The more popular method is to set your font-size for the whole document, then, base everything on a relative size from there. A percentage of the base font is used, allowing the font to resize itself based upon the user's preferences, too: [code]body { font-size: 1em; } #menu ul li { font-size: 110%; color: green; } [/code] Font and Text Characteristics There are a lot of fun things you can do with fonts! You can make your fonts italic, you can make them bold, and you can make the first letter of a paragraph larger than the rest of the text. The list of variations goes on and on. This lesson is just a peek into how to style and size fonts on your WordPress site. There is a lot more that goes into deciding which font to use, how to use it, how many to use, what sizes, and...well, which fonts will look best on your site. Different browsers interpret fonts in different ways, too. You can find more information to help you make your font decisions below. Font Resources The Noodle Incident's CSS and Text W3 Schools: CSS Fonts About.com's Web Design (CSS): What is a Font HTML Source: Text Formating University of Minnesota Creative Standards Guide: Text and Fonts About.com's Web Design: How Many Fonts are Too Many Font-Finder Thinking with Type Adding Fonts In WordPress – Includes Video Meta Tags in WordPress atachibana — Mon, 04 Jul 2016 11:17:22 +0000 [codex_languages en="Meta Tags in WordPress" ja_codex="Meta Tags in WordPress" ko_codex="Meta Tags in WordPress" ru_codex="Тег Meta в WordPress"] As a search engine prowls your site, it gathers information from the title, headings, content, and Meta Tags such as description or keywords. It compares the words within each of these sections and "ranks" the site dependent upon how well the information matches. We have more information on how to maximize your meta tag references below. It is important for website developers to understand that a default installation of WordPress does not contain the description and keywords meta tag data. Meta tags can be added manually, through changes to the Theme template files or through WordPress Plugins. What Are Meta Tags? The word meta means information about. Meta Tags were created early on to provide concise information about a website. Meta tags list information about the web page, such as the author, keywords, description, type of document, copyright, and other core information. This is an example of a meta tag for description: [code language="php"] [/code] The most common meta tags examples include: [code language="php"] [/code] Why Are Meta Tags Missing? In the default installation, WordPress does not include meta tags such as description and keywords. Why? Well, let's look at the above tags. The second tag sets the character set for the page and the third tag sets the language. Specifically, this example sets the character set to be in the English language style as found in the United States, using the ASCII character set. This means that the page will probably feature spellings like "center" instead of "centre" and "humor", not "humour". It also gives information to the browser to recognize the characters as not being Chinese. The author and contact information lists a specific person. The description tag lists a description of the post that is unique to that post. The keywords also list words found within that post. Are you seeing the pattern? All of this is unique information. WordPress may do some magical things, but it can't read your mind. If you want to supply search engines better information that is more specific to your web pages, you have to add the meta tag data yourself. Are Meta Tags Necessary? A good question to ask is if meta tags are still necessary. They used to be more helpful, providing important information to the Internet browser. As browsers became more sophisticated, they stopped needing a lot of hand holding in order to figure out if your site is in English or Chinese. Google no longer uses the meta keyword in search result ranking and they confirm this in their Webmaster Central Blog. Some search engines don't use the meta tag information any more because many people abused it. In fact, meta tags may not represent the content of your site, but, it still doesn't hurt your status with search engines if you make use of these little bits of information, and do so truthfully. Furthermore, Google does still use the meta description tag in some situations as part of the snippet of your site displayed in search results. Without a doubt, content is the biggest contributor to search engine page ranking, so if you want to raise your rankings, make sure you have quality content. Covering all the reasons meta tags are and aren't important to search engines is beyond the scope of this article. In the Resource section below are some links to more information on meta tags and their impact on search engines. Putting Meta Tags Back In To add meta tags to your site, simply add them to the header.php template file in your WordPress Theme, specifically in the head section near the link for the style sheet. At the top you will see the DOCTYPE tag and below that you will see a couple more tags and then the </code> tag, looking something like this:</p> <p></p> [code language="php"]<title><?php bloginfo('name'); ?><?php wp_title(); ?>[/code] Below this line you can add your meta tags. You can add meta tag information such as the content, language, author, contact, and copyright, since these are basically the same on every page of your site. But what about the 'dynamic' types of information such as description and keywords? This information is unique to every web page on your site. Putting them in the header.php means the information won't change throughout your site. What you need is something to dynamically add keywords and descriptions on a per-post basis. To add a description, keywords, and other meta tags that are unique to each post or Page generated, you have two choices: you can add them as generic references or you can use plugins. Generic Meta Tags If you have a clear purpose for your website, then you can use that information to create generic meta tags and place these in your header. Let's say Harriet Smith is a veterinarian, and enjoys sharing her animal stories on her WordPress blog. A description meta tag that would describe all of her posts might be: [code language="php"] [/code] If Harriet writes a story about a dog giving birth in the middle of a hurricane, and accompanying the dog were two humans who risked their lives to stay with the dog during the delivery, the descriptive words of bravery and courage, life and death, pets and human, would surely apply. Another story about an animal that returns home to its owner after missing for 5 years might also be described with the words of bravery, courage, life, death, and companionship. From these two stories, Harriet could create a good generic set of keywords: [code language="php"] [/code] With these generic description and keywords meta tags, Harriet's website would be accurately described and that should please just about any search engine. This is the manual style of adding a description, but WordPress can make this easier for you. Add your description, similar to above, in your Admin > Options > General panel. The description is entered in the line designated as Tagline. Then paste in the following in your head area. [code language="php"][/code] WordPress will automatically generate the description. Note: Some Themes use this tag in the header just below the title of the blog or site. If you don't want it there, remove or comment out the tag in the header area. To get more sophisticated, you can add a conditional tag query that asks "If this is a single post view, show the post title; if this is a multi-post view, show the blog name and description." The conditional tag query looks like this: [code language="php"]" />[/code] Using Meta Tag Plugins There are several Plugins that allow the blog administrator to set the keywords, description, and other meta tags to be unique on each post. These plugins make use of the Custom Fields in the Write Post Screen. You can find meta tag Plugins in the Official WordPress Plugin Directory. Using Meta Tag Plugins allows you to customize each of your meta tags, and to choose the ones you want to add, or not, on a per-post basis. This allows your meta information to better describe each page. Meta Tag Resources Here are some sites that will help you learn more about meta tags, how they work, and why you should or shouldn't use them. Google does not use the keywords meta tag in web ranking Search Engine Watch's How to Use HTML Meta Tags WebDeveloper's Back to Basics: Meta Tags W3 Organization's Global Structure of an HTML Document and Meta Tags header.php code and tutorial outputs the correct robots, googlebot, and msnbot meta depending on page, single, home, archive. Meta Tags for SEO- A Complete Guide Importing Content atachibana — Mon, 04 Jul 2016 16:30:31 +0000 Using the WordPress Import tool, you can import content into your site from another WordPress site, or from another publishing system. You can find many of the importers described here under Tools > Import in the left nav of the WordPress Administration Screen. You can import content from publishing systems beyond those listed on the Administration Screen. Procedures differ for each system, so use the procedures and plugins listed below as necessary. If you're new to WordPress, review the WordPress Features and Working with WordPress pages to get started. If you run into problems, search the WordPress Support Forum for a solution, or try the FAQ. Before Importing If the file you're importing is too large, your server may run out of memory when you import it. If this happens, you'll see an error like "Fatal error: Allowed memory size of 8388608 bytes exhausted." If you have sufficient permissions on the server, you can edit the php.ini file to increase the available memory. Alternatively, you could ask your hosting provider to do this. Otherwise, you can edit your import file and save it as several smaller files, then import each one. If your import process fails, it still may create some content. When you resolve the error and try again, you may create duplicate data. Review your site after a failed import and remove records as necessary to avoid this. Atlassian Confluence To import from Atlassian Confluence, export your page(s) as HTML. Then, use the HTML Import 2 plugin. See the HTML Import 2 User Guide for more information about this plugin. Install and activate the HTML Import 2 plugin on your WordPress site. Select Settings->HTML Import on the left nav of the admin screen. Fill in the fields as necessary to configure your desired import. Click "Save settings." To execute the import, select Tools > Import on the left nav of the admin screen. Under HTML, click "Run Importer." b2 If you're using WordPress version 1.5.2 or earlier, you can use a script included in the source code. See wordpress/wp-admin/import-b2.php. b2evolution There are two methods of importing b2evolution content into WordPress. Movable Type Export Format You can re-skin a b2evolution blog so that when its source is viewed it appears to be in the Movable Type export format. You can save the export and import it as Movable Type data. See Movable Type and TypePad. BIMP Importer script You can use the BIMP Importer script to import b2evolution blogs, categories, posts, comments, files and users into your WordPress installation (v3 and higher). Note that this requires payment. Blogger You can import posts, comments, categories and authors from Blogger. WordPress includes an import tool designed specifically for importing content from Blogger. Export your Blogger contents as XML. In your WordPress site, select Tools > Import on the left nav of the admin screen. Under "Blogger," if you haven't already installed the Blogger importer, click "Install Now." Click the "Run Importer" link. Click "Choose File" and navigate to your Blogger XML file. Click “Upload file and import.” Blogroll WordPress includes an import tool designed specifically for importing content from Blogroll. In your WordPress site, select Tools > Import on the left nav of the admin screen. Under "Blogroll," if you haven't already installed the importer, click "Install Now." Click the "Run Importer" link. Click "Choose File" and navigate to your Blogroll OPML file. Click "Upload file and import." Drupal Many resources are available to help you migrate content from Drupal to WordPress. A few are highlighted here, and you're likely to find many others by searching the web. FG Drupal to WordPress. This is compatible with Drupal 6, 7 and 8. Drupal2WordPress Plugin. Use this plugin to import terms, content, media, comments and users. Any external images included in your Drupal site can be fetched and added to the media library, and added to your pages and posts. Drupal to WordPress migration utilities. This plugin is open source. This tutorial includes workarounds for some migration issues such as duplicate terms, terms exceeding maximum character length and duplicate URL aliases. How to Convert Drupal to WordPress. XML and CSV Here are some resources that can help guide you in importing XML or CSV content into WordPress. The WP All Import plugin can import any XML or CSV file. It integrates with the WP All Export plugin. With the WP CSV to DB plugin you can insert CSV file content into a WordPress database. CSV Importer plugin Really Simple CSV Importer plugin HTML WordPress includes an import tool designed specifically for importing content from static HTML pages. In your WordPress site, select Tools > Import on the left nav of the admin screen. Under "HTML," click the "Run Importer" link. Click "Choose File" and navigate to your HTML file. Click "Upload file and import." Alternatively, you can use the HTML Import 2 plugin. See the HTML Import 2 User Guide for more information about this plugin. Install and activate the HTML Import 2 plugin on your WordPress site. Select Settings > HTML Import on the left nav of the admin screen. Fill in the fields as necessary to configure your desired import. Click "Save settings." To execute the import, select Tools > Import on the left nav of the admin screen. Under HTML, click "Run Importer." Joomla For Joomla you can use FG Joomla to WordPress. This plugin has been tested with Joomla versions 1.5 through 3.8 and WordPress 4.9 on huge databases (72 000+ posts). It is compatible with multisite installations. LiveJournal WordPress includes an import tool designed specifically for importing content from LiveJournal. In your WordPress site, select Tools > Import on the left nav of the admin screen. Under "LiveJournal," if you haven't already installed the LiveJournal importer, click "Install Now." Click the "Run Importer" link. Enter your LiveJournal username and password, and click "Connect to LiveJournal and Import." Live Space See Live Space Mover for an article explaining how to use a python script for importing blog entries from live space to WordPress. Magento The FG Magento to WooCommerce plugin migrates your Magento products and CMS pages to WooCommerce. Mambo You can use the plugin FG Joomla to WordPress. This WordPress plugin works with Mambo 4.5 and 4.6. Movable Type and TypePad WordPress includes an import tool designed specifically for importing content from Movable Type and TypePad. In your WordPress site, select Tools > Import on the left nav of the admin screen. Under "Movable Type and TypePad," if you haven't already installed the importer, click "Install Now." Click the "Run Importer" link. Click "Choose File" and navigate to your export file. Click "Upload file and import." These articles provide more information on this process: Importing from Movable Type to WordPress Importing and Exporting Content Notes on a Massive WordPress Migration Nucleus CMS Here are some resources that can help guide you in migrating content from Nucleus CMS to WordPress. A Guide to Importing From Nucleus CMS Script for Importing From Nucleus CMS Nucleus to WordPress. Use this commercial service to migrate Nucleus posts, members, comments and categories to WordPress 3.0 and higher. Plone See this article on how to migrate Plone content into Wordpress via Movable Type format. Posterous Use WordPress.com's Posterous importer, then export as WXR (WordPress eXtended RSS). PrestaShop FG PrestaShop to WooCommerce. This WordPress plugin is compatible with Prestashop versions 1.1 to 1.6 Roller See Importing From Roller. See also Migrating a Roller Blog to Wordpress. RSS WordPress includes an import tool designed specifically for importing content from RSS. In your WordPress site, select Tools > Import on the left nav of the admin screen. Under "RSS," if you haven't already installed the importer, click "Install Now." Click the "Run Importer" link. Click "Choose File" and navigate to your XML file. Click "Upload file and import." Serendipity Moving from Serendipity to WordPress. Blog Migration from Serendipity to WordPress. Converting from Serendipity to WordPress. A commercial service for migrating from Serendipity to WordPress. Serendipity to WordPress - Post Import A script for importing Serendipity posts into WordPress. SPIP The plugin FG SPIP to WordPress migrates categories, articles, news and images from SPIP to WordPress. It has been tested with SPIP versions 1.8, 1.9, 2.0, 3.0 and 3.1 and WordPress 4.9. It is compatible with multisite installations. Sunlog Open phpMyAdmin to see the database of your Sunlog install. You only need two tables, "blogname_entries" and "blogname_comments". Use phpMyAdmin to export both tables as XML files. Install the WP All Import plugin to your WordPress site. Create the following field mappings: headline=title content=entry+more date=timestamp in Unix format categories="cat," with each value separated by a semicolon. Textpattern Topic on the WordPress Support Forum: Fix Textpattern import Textpattern to WordPress exporter script on Github:Textpattern to WordPress exporter Tumblr WordPress includes an import tool designed specifically for importing content from Tumblr. In your WordPress site, select Tools > Import on the left nav of the admin screen. Under "Tumblr," if you haven't already installed the importer, click "Install Now." Click the "Run Importer" link. Click "Choose File" and navigate to your export file. Click "Upload file and import." Create an app on Tumblr that provides a connection point between your blog and Tumblr's servers. Copy and paste the "OAuth Consumer Key" and "Secret Key." Click "Connect to Tumblr." See also Tumblr Importer. Twitter There are several plugins to import your tweets into WordPress, such as Ozh' Tweet Archiver Embedding Tweets into WordPress with Twitter Blockquotes Get Your Twitter Timeline into WordPress TypePad See Movable Type and TypePad. Vox Export your Vox blog content as a WXR file, then use WordPress.com’s Vox importer to import. WooCommerce products (CSV) If you've installed the WooCommerce plugin, this importer will already be installed. Click "Run Importer" to upload a CSV file. WooCommerce tax rates (CSV) If you've installed the WooCommerce plugin, this importer will already be installed. Click "Run Importer" to upload a CSV file. WordPress WordPress includes an import tool designed specifically for importing content from another WordPress blog. In your WordPress site, select Tools > Import on the left nav of the admin screen. Under "WordPress," if you haven't already installed the importer, click "Install Now." Click the “Run Importer” link. Click “Choose File” and navigate to the WXR file exported from your source. Click “Upload file and import.” You will first be asked to map the authors in this export file to users on the blog. For each author, you may choose to map to an existing user on the blog or to create a new user. WordPress will then import each of the posts, comments and categories contained in the uploaded file into your blog. In addition, you can import attachments by checking the "Download and import file attachments" option. Xanga xanga.r is a program that parses xanga pages to get the post and comments. Then it can output them in the WordPress rss 2.0 xml format for WordPress to import. Yahoo! 360 Use WordPress.com's Yahoo! 360 importer, then export/import as a WXR (WordPress eXtended RSS). Zenphoto zenphoto-to-wordpress.py is a python script to export galleries and comments to a standard WXR (WordPress eXtended RSS) file. See this article for details Zoomblog You can add a PHP file to your web server that will import your Zoomblog posts and comments. To migrate your posts from Zoomblog: Export your Zoomblog data as an XML file. Download the Zoomblog importer (http://noeda.com/ficheros/zoomblog.zip), unzip it, and upload the file zoomblog.php to your wp-admin/import directory. Log in to WordPress and go to Manage:Import:Zoomblog. Navigate to the XML file you created above. Editing Files atachibana — Wed, 06 Jul 2016 11:43:05 +0000 [codex_languages en="Editing Files" fr_codex="Modifier les Fichiers" ja_codex="Editing Files" ptbr_codex="Editando Arquivos" zhcn_codex="编辑文件"] There may be times when you’ll need to edit the files that make up your WordPress site--core, theme or plugins--to modify your site’s appearance or behavior. The most convenient way to do this is using the built-in Theme Editor or Plugin Editor. Alternatively, you can edit files on your local machine using a text editor or IDE, and then transfer those files to the server using an FTP client. Editing Files in Place on the Server Backups Save a backup of a file before you edit it. It’s easy to make a mistake that can cause site errors and even cut you off from your WordPress Dashboard. You need to have a safe copy of the original file in order to undo your changes in case of emergency. File Permissions To edit a file using the built-in WordPress Plugin or Theme Editors, the permissions for that file must be set to writable (at least 604). You can change a file’s permissions by using an FTP client program, web-based file manager provided by your host, or from the command line using SSH. Your options depend on the type of access your host offers. If you see a note at the bottom of the WordPress Built-in Editor panel that says “If this file was writable you could edit it,” this means that you need to change the file permissions before you can make any changes. Instant changes When you edit files directly on the server, your changes take effect on your site as soon as you save the file. Because of the immediate nature of the changes, it’s usually safer to edit copies of your files offline, then test and upload your changes when they are verified. Always make sure you have a current backup before editing files. Editor features The built-in WordPress Plugin and Theme editors are very basic, allowing easy access to view and edit plugin and theme files on your site only. There are no built-in editor features for search and replace, line numbers, syntax highlighting, code completion, or other advanced editing features. Use your browser’s internal search to help find code within file you’re editing. Theme editor Access the Theme Editor from the Administration > Appearance > Editor menu. The Theme Editor can only edit PHP and CSS files. Plugin editor The Plugin Editor is located at Administration > Plugins > Editor. You can edit the following file types using the Plugin Editor: HTML PHP CSS TXT (and text-like files such as RTF) Disable the Editors To prevent accidents, errors, and even hacking, you may wish to disable the Theme Editor and Plugin Editor by adding DISALLOW_FILE_EDIT to your wp-config.php file. Editing Files Offline Local edits + file transfer You can edit theme, plugin and WordPress core files locally on your own computer. This allows you to save backups, use the editor of your choice, and test your changes more carefully than making edits directly on the WordPress server. Caution: Editing WordPress core files is risky. Introducing errors into WordPress core files can break your site. Rely on your backups as necessary, or restore core by downloading from wordpress.org if necessary. Text Editors When editing WordPress files offline, you’ll need to choose an editor or IDE. This section will help you avoid choosing one that could corrupt your files. Editors to Avoid Don’t use a word processor or WYSIWYG HTML generator to edit your files. These programs can convert characters unexpectedly, and can introduce code that may corrupt your file. Avoid these: Microsoft Office (Word, Publisher, Excel, etc.) WordPerfect OpenOffice/LibreOffice Apple iWork Adobe Dreamweaver If you must use this editor, first delete Dreamweaver content from the document, then copy your content from the WordPress editor and paste it into the Dreamweaver file. Microsoft FrontPage If you must use this editor, do not use built-in templates. Avoid Internet Explorer-specific code. Any do-it-yourself instant web page software. Recommended Text Editors The following Text Editors are safe for editing your WordPress files: Atom (Mac OS X, Windows, Linux, Open Source, Free) BBEdit (Mac OS X, $) Boxer Text Editor (Windows) Brackets(Open Source, Mac OS X, Windows, Linux) Coda (Mac OS X, Shareware) Crimson Editor (Windows, Free) EditPad (Windows) EditPlus (Windows) Editra (Mac OS X, Windows, Linux, Open Source, Free) emacs (Unices, Windows, Mac OS X, Open Source, Free) gedit (Unices) JEdit (Mac OS X, Windows, Linux) Kate (Unices) Komodo Edit (Mac OS X, Windows, Linux, Open Source, Free) Kwrite (Unices) Notepad++ (Windows, Open Source, Free) Notepad2 (Windows, Free) phpDesigner (Windows) pico (Unices) PSPad (Windows, Free) Smultron (Mac OS X, $) SubEthaEdit (Mac OS X, $) Sublime Text 3 (Windows, Linux, Mac OS X, $) TextEdit (included with Mac OS X) TextMate (Mac OS X, $) TextPad (Windows) TextWrangler (Mac OS X, Free) UltraEdit-32 vim (Unices, Windows, Mac OS X, Open Source, Free) Recommended IDEs The following IDEs are safe for editing your WordPress files: Aptana Studio (Mac OS X, Windows, Linux, Free) Codelobster (Windows, Free) Eclipse (Mac OS X, Windows, Linux, Free) NetBeans (Mac OS X, Windows, Linux, Free) Update Services atachibana — Wed, 06 Jul 2016 16:05:14 +0000 Update Services are tools you can use to let other people know you've updated your blog. WordPress automatically notifies popular Update Services that you've updated your blog by sending a XML-RPC ping each time you create or update a post. In turn, Update Services process the ping and updates their proprietary indices with your update. Now people browsing sites like Technorati or Sphere can find your most recent posts! Common Usage Most people use Ping-o-Matic which, with just one "ping" from you, will let many other services know that you've updated. As for why, Ping-O-Matic puts it best: So why would you want to be on these sites? One word: traffic. Blogrolling scripts like WordPress check update services to see if you've updated and then shows it on everyone's site -- usually by moving you to the top of people's blogrolling list or putting a recently updated indicator by your link. Services like Technorati spider your links to track who links to you and who you link to; almost in real time. If you show up on someone's Technorati link list (often called an "egorati search") they're likely to visit your site to see what you said, increasing your exposure. Other sites like weblogs.com and blo.gs list recently updated blogs. Lots of people browse these when they're bored. Many of the services offer their own forms for pinging their own service, but keeping track of all those services is a hassle. WordPress makes this easy for you by listing Ping-O-Matic's server (rpc.pingomatic.com) by default. All you need to do is sit back and let it work for you! If you do not want the update services to be pinged, remove all the update service URIs listed under "Update Services" on the Settings->Writing administration screen of your WordPress installation. Certain web hosts - particularly free ones - disable the PHP functions used to alert update services. If your web host prevents pings, you should stop WordPress from attempting to ping. XML-RPC Ping Services [code] http://rpc.pingomatic.com http://rpc.twingly.com http://api.feedster.com/ping http://api.moreover.com/RPC2 http://api.moreover.com/ping http://www.blogdigger.com/RPC2 http://www.blogshares.com/rpc.php http://www.blogsnow.com/ping http://www.blogstreet.com/xrbin/xmlrpc.cgi http://bulkfeeds.net/rpc http://www.newsisfree.com/xmlrpctest.php http://ping.blo.gs/ http://ping.feedburner.com http://ping.syndic8.com/xmlrpc.php http://ping.weblogalot.com/rpc.php http://rpc.blogrolling.com/pinger/ http://rpc.technorati.com/rpc/ping http://rpc.weblogs.com/RPC2 http://www.feedsubmitter.com http://blo.gs/ping.php http://www.pingerati.net http://www.pingmyblog.com http://geourl.org/ping http://ipings.com http://www.weblogalot.com/ping [/code] Alternatives An alternative is Feed Shark, which pings over 60 services for free. Check Vladimir's WordPress Ping List, manually checked and updated WordPress Multisite Network By default, editing the Ping Services for a WordPress Multisite network site is disabled. This can be re-enabled with a plugin such as the Activate Update Services plugin. Multilingual WordPress atachibana — Sat, 09 Jul 2016 23:54:03 +0000 WordPress does not support a bilingual or multilingual blog out-of-the-box. There are however Plugins developed by the WordPress community which will allow you to create a multilingual blog easily. Creating a mulitlingual blog is basically installing WordPress in more than one language and letting the Plugin switch between them. This includes installing .mo languages files which most Plugins will require you to do manually. See Installing WordPress in Your Language for details. The free WPGlobus, Polylang, qTranslate-X, xili-language or Sublanguage plugins are installable on standalone WordPress sites. For multisite WordPress (one website per language), you can try Multisite Language Switcher, Zanto or Multilingual Press or purchase WPML. Different types of multilingual plugins There are a few basic types of multilingual Plugins: Manage multilingual posts in one post per language (e.g. WPML - paid, xili-language, Polylang, Bogo or Sublanguage). Translations are then linked together, indicating that one page is the translation of another. Store all languages alternatives for each post in the same post (e.g. qTranslate-X, WPGlobus). Manage translations on the generated page instead of using a post context (e.g. Transposh and Global Translator). Plugins like Multisite Language Switcher, Multilingual Press, and Zanto, link together separate WordPress network (multisite) installations for each language by pinging back and forth. One language per post Multilingual plugins that assign a single language per post will let the user select the post's language and add translations as new posts (same for pages, tag and categories). Then, different versions of the same content are linked together to form translation groups. This grouping allows users to switch the display language. Pros: The database contents for posts remain unmodified (easy install and uninstall). Everything gets translated by default. If a post includes custom fields, they're attached to that post, so they are already associated with the language. Some plugins use - for theme's displayed terms - the language files (.mo) delivered with localizable themes. In WordPress, localization is based in GNU gettext technology. So when a single post is in french, plugin switch all the terms of the theme in the same language (here french). The files can be completed with the specific terms of the site (categories titles, widget, links...). No need to re-translate all, just add specific terms and translations in target languages. Other plugins that analyze contents (like related posts) keep working correctly. Cons: More complex architecture. The plugin needs to hook to many WordPress functions and filter them so that only contents that matches the language is returned. Additional tables are required by some plugins - normally, to hold the translation grouping. Newer plugins likely use a custom taxonomy or post meta fields instead. May cause excessive database grow and slow performance as a result. A WooCommerce-based site having a 100,000 products will have 500,000 records after translating to 5 languages. All product metas (could be tens of those per product, and also transients will be duplicated, too, so the database might become huge). All languages in a single post Multilingual plugins that hold all the language contents in the same post use language meta tags to distinguish between contents in different languages. When the post is displayed, it's first processed and only the active language content remains. Pros: Side by side editing is easily implemented. Less things to break. There are no additional tables and much fewer things to modify in WordPress. The search will find the same post, regardless on which language you used for the keyword. Number of records in the database stays the same. Cons: Uninstall can be complicated, as the database needs to be cleaned from multilingual contents. Post permalinks may not be translatable. Manage translations on the generated page Multilingual plugins that use the content pages generated by WordPress and perform translation on those pages. When any page is displayed on WordPress the plugin (either offline or online) attempts to create a translated version of the page using machine translation. Later on that translation can be manually changed or modified. Pros: Installation is simple and translation for any content on the page is provided. Editing the translation can be done with ease. Cons: Automatic translation is not good enough and pages on the site might be badly translated. There's a strong coupling between content and translation, and changes in the original content might break the translation. Plugins that direct you to external translation services Those Multilingual plugins are normally used to create a widget that creates a shortcut for using online translation services (such as Google Translate). The content is auto translated on demand by the third party engine. Pros: Installation is simple and translation for any content on the page is provided. It is quite clear that the translation process is automated, so the users expectations are lowered. Cons: Automatic translation is not good enough and pages on the site might be badly translated. Without the ability to change the translation those plugins limit the ability of the content publisher to provide quality translated content. Each language in its own WordPress installation A separate site is created for each language you want to translate into (e.g. in a WordPress Multisite installation). All the sites need to run the same theme and plugin. When a translation is saved source posts get pinged by translation posts and the system keeps a separate table with the translation relationships. Pros: Each language site is a regular WordPress install with regular posts (postmeta and external db is used for translation data) If you turn off the plugin the content continues to work fine, albeit without knowledge of its sources/translations. Cons: Separate sites create more management needs which might be undesirable. Language negotiation Language negotiation means how to determine the language in which users see the site. Regardless of the solution for storing multilingual contents, multilingual plugins also need to be able to choose which language to display in. Normally, the URL indicates the display language. Different URL strategies for encoding language information are: Add the language name as a parameter: example.com/?lang=en or example.com/?lang=es Add virtual 'directories' as language names: example.com/en/ or example.com/es/ Use different domains for different languages: www.example.com or es.example.com How to choose the right multilingual solution Choosing the most suitable multilingual Plugin for your needs will take some time. See the WordPress Plugin Directory for a list of multilingual Plugins. There is not only one way but a way adapted to the content strategy, the data-model, the number of posts and pages, and the behavior/experience expected by visitors. And for WordPress Network (multisite), a good knowledge of server administration is required. In any case, installing a multilingual plugin is a big change for any site. It would be a good idea to first create a test site and verify that everything works correctly between all the required plugins and the theme and only then install. Since many multilingual plugins change the database significantly, doing a database backup is required before experimenting. Related WordPress in Your Language Multilingual Codex Creating a Search Page Sun, 10 Jul 2016 00:12:37 +0000 [codex_languages en="Creating_a_Search_Page" ja_codex="検索ページの作成"] A Search Page is a WordPress Page with a custom Page template to give users more information for searching your site. Things You Need to Know Different WordPress Themes feature different template files. Some include a search.php template file. This is not a Search Page, it is merely a template that displays the search results. There is also a template file called searchform.php. This is a template file that is often included in the sidebar of many themes and generates the search box form. If there isn't one in your theme, you can easily copy it from the Default theme. To create your own custom Search Page, you will need to create a Page template to include your search form and the information you want your users to see before they search your site. Check your WordPress Theme to see if it includes a page.php template file. The Default WordPress Theme does include this template, but many do not. If it does, then follow these instructions. If it does not, we have the information you need to create your own. Creating a Search Page Template 1. Using a text editor, open the page.php and save as searchpage.php. If you do not have a page.php, you can create one based upon your Theme's index.php template file. Note: The filename search.php is reserved as a special template name, so avoid its usage; the suggested searchpage.php just makes it easy to recognize in the list of files. 2. After saving it, edit the file: Delete The Loop (i.e. basically everything within your content div), leaving the div tags intact. Add a heading such as "Search Posts" or something similar. You can use an existing class from your CSS style sheet, or create a new one. Copy the following into the content div or any other div that contains the content of your Page: [code language="php"]&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;?php get_search_form(); ?&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;[/code] At the top of your searchpage.php, before anything else, add this to give your Search Page a heading WordPress will recognize in the Administration Screens: [code language="php"]&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;?php /* Template Name: Search Page */ ?&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;[/code] 3. Save the file. 4. Upload the file to your theme directory (if you made changes to your style.css style sheet file, upload that, too). If you create searchpage.php from page.php in Twenty Seventeen, it would be as like as followings: [code language="php"] &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;?php /* Template Name: Search Page */ ?&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt; &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;?php get_header(); ?&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt; &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;div class=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;wrap&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt; &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;div id=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;primary&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot; class=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;content-area&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt; &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;main id=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;main&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot; class=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;site-main&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot; role=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;main&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt; &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;?php get_search_form(); ?&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt; &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;/main&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;!-- #main --&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt; &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;/div&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;!-- #primary --&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt; &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;/div&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;!-- .wrap --&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt; &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;?php get_footer(); [/code] Creating a Search Page Based on the Search Page Template, we will create the seach page. In the Administration Screen go to Pages > Add New. In the title field enter Search. Do not write anything in the content area. While still on the same page, look for Page Attributes on right side menu. Select the drop-down menu in Template, and select Search Page. Click the Publish button. It will show simple search form such as Linking to Your Search Page You can now make a link to your custom Search Page in several ways. Using the Page ID Whether or not you use permalinks, you can link to your new Search Page by using Page ID number of the Page. Insert the next line into your any posts, pages or templates [code language="php"]&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;a href=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;index.php?page_id=17&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot; title=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;Search Page&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;Search Page&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;/a&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;[/code] OR you may insert the next line into templates [code language="php"]&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;a href=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;?php echo home_url(); ?&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;/?page_id=17&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;Search Page&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;/a&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;[/code] Using the Page Slug The Page slug is set in the Edit Page screen. It is the name of the page if you are using Permalinks. You can manually change this. An example of a Page slug link would be: [code language="php"]&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;a href=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;/wordpress/search-page/&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot; title=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;Search Page&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;Search Page&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;/a&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;[/code] for any posts, pages or templates when slug is 'search-page'. OR you may insert the next line into templates [code language="php"]&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;a href=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;?php echo home_url(); ?&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;/wordpress/search-page/&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot; title=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;Search Page&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;Search Page&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;/a&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;[/code] Using wp_list_pages() If you are using the wp_list_pages() template tag, the page name would be automatically generated in your Pages list. Customizing Your Search Page Now that you have created your custom Search Page, you can customize the display. Open your searchpage.php in a text editor and edit it there. Above the get_search_form() function for your searchform.php within the content div, you can add text to help visitors search your site. [code language="php"] &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;p&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt; My Site features articles about &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;a title=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;WordPress Articles&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot; href=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;/category/wordpress/&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;WordPress&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;/a&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;, &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;a title=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;Web Design Articles&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot; href=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;/category/web-design/&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;web page design&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;/a&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;, &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;a title=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;Development Articles&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot; href=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;/category/website-development/&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;website development&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;/a&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;, and &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;a title=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;CSS Articles&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot; href=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;/category/css/&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;CSS&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;/a&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;. &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;/p&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt; &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;p&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;To search my website, please use the form below.&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;/p&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt; &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;?php get_search_form(); ?&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt; [/code] You might want to include a list of keywords or other information, images, or details to customize your custom Search Page. Preserving Search Page Results and Pagination Search results and Pagination may stop working when applying customization to the search template. To avoid these issues the first thing any developer needs to do is add the following code to the start of their Search template to ensure that the original WordPress query is preserved. To customize the query append additional arguments to (array) $search_query. Execute the $search_query through a new $wp_query object, more information on the WP_Query object can be found at WP_Query. [code language="php"] &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;?php global $query_string; $query_args = explode(&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;, $query_string); $search_query = array(); if( strlen($query_string) &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt; 0 ) { foreach($query_args as $key =&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt; $string) { $query_split = explode(&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;=&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;, $string); $search_query[$query_split[0]] = urldecode($query_split[1]); } // foreach } //if $search = new WP_Query($search_query); ?&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt; [/code] Additional customization arguments can be found at WP_Query. Display Total Results To access the total number of search results from search.php, a search result page, you should retrieve the total number of posts found using the wp_query object. [code language="php"]&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;?php global $wp_query; $total_results = $wp_query-&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;found_posts; ?&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt; [/code] More information on WP_Query can be found at WP_Query. Login Trouble atachibana — Sun, 10 Jul 2016 01:00:32 +0000 If you are having trouble logging in to your WordPress Administration Screen, here are some possible solutions. Enable Cookies In order to make sure that cookies are enabled for your browser, you need to: Clear your browser cookies. Clear your browser cache. To see how to clear cookies and caches on various browsers, visit Clearing Cache and Cookies. WordPress MultiSite Network Check your wp-config.php file. Verify the DOMAIN_CURRENT_SITE value. Disable Plugins Some WordPress Plugins may interfere with the login process. Disable all of your WordPress Plugins, either through the Administration Screen or by removing them from the /wp-content/plugins/ folder, so they will not be recognized by the program. Alternatively, you can rename the plugins folder to something else temporarily to something like /wp-content/pluginsXX/ and they will not be recognized. Rename the folder back to /wp-content/plugins/ once the base WordPress installation has been recovered. Deactivate Theme Rename the active theme folder (in wp-content/themes) by using FTP. Once renamed, WordPress will revert to using the {{DefaultTheme}}. When finally logged in, change to a different theme. To find out what caused problem in the theme, upload and run this code when the theme is active: [code language="php"] [/code] New Login File Sometimes the wp-login.php file may have been corrupted or uploaded incorrectly. Delete wp-login.php off of your server and upload a new copy from a fresh WordPress download. Remember, overwriting file via FTP can lead to incomplete transfers. Edit wp-login.php as follows: Go to the case retrievepassword section, found under this comment: [code language="php"] // redefining user_login ensures we return the right case in the email [/code] Replace: [code language="php"] $user_login = $user_data["user_login"]; [/code] With: [code language="php"] $user_login = $user_data->user_login; [/code] Edit Users Table Access your site's phpMyAdmin and edit the database carefully. Open the WordPress database. Click on the users table in the left menu (default is wp_users, or yourprefix_users if you defined a different table prefix.) Click BROWSE. Click on the EDIT button next to the admin user. Delete whatever is in the password field. Enter your desired password. From the Function drop-down list, choose MD5. Save the info in the database. Log in to WordPress using "admin" and the password you used. In the case of newer versions of WordPress, the password is double hashed, but as long as you md5 the password, it will complete the hash (it upgrades your password for you). Password Problems For information on problems logging in due to a wrong or lost password, see Resetting Your Password. Remember: the Username and Password fields are case sensitive. Site URL Redirecting In certain cases your WordPress address URI may have been reset. Check the siteurl value in the wp-options table of your WordPress database. A guide to doing this is available here. Is it set as http:/? If it is, change siteurl to the correct value. Open wp-login.php in a text-editor and comment or delete the following lines: [code language="php"]// If someone has moved WordPress let's try to detect it // if ( dirname( 'http://' . $_SERVER['HTTP_HOST'] . $_SERVER['PHP_SELF']) != get_settings('siteurl') ) // update_option( 'siteurl', dirname('http://' . $_SERVER['HTTP_HOST'] . $_SERVER['PHP_SELF']) );[/code] Changed your WordPress address URI and cannot login nor access the database (but still can access the login page) ? wp-login.php can be used to reset the address: [code language="php"] //FIXME: do comment/remove these hack lines. (once the database is updated) update_option('siteurl', 'http://your.domain.name/the/path' ); update_option('home', 'http://your.domain.name/the/path' ); [/code] Subdomains or Subdirectories In your wp-config.php try changing from: [code language="php"]define( 'SUBDOMAIN_INSTALL', true);[/code] To: [code language="php"]define( 'SUBDOMAIN_INSTALL', false);[/code] Secure HTTPS If you are having a problem with secure HTTPS, change the following line in wp-includes/vars.php from: [code language="php"]define('COOKIEPATH', preg_replace('|http://[^/]+|i', '', get_settings('home') . '/' ) );[/code] To: [code language="php"]define('COOKIEPATH', preg_replace('|https?://[^/]+|i', '', get_settings('home') . '/' ) );[/code] Be sure also to change the URL in OPTIONS to https://. Headers Already Sent If you get an error about headers already sent, see Solving the Headers Already Being Sent Problem in the FAQ. Check Your URL Options In some situations, your blog can be seen from inside your domain, but not outside. Following the instruction above about changing the wp-options MySQL table might still result in login failure. In this event, double-check your wp-options table siteurl (WordPress address URL) and home (Blog Address URL) values to make sure they reference the same base externally available address; i.e., http://blog.yourdomain.com. The standard install may set them to your local (internal) host name, such as http://servername Another issue may be if you are redirecting using .htaccess from a non-www url prefix to a www while you have the wp-options table siteurl (WordPress address URL) and home (Blog Address URL) set with non-www prefix. Consequently this would create an endless loop which you need to avoid. One way is to disable the .htaccess redirection temporarily by placing # before the line or eliminating the entries entirely and trying to Login again. Advanced users may want to adjust the wp-options table siteurl (WordPress address URL) and home (Blog Address URL) through the database. Notice that this issue can also occur if you are redirecting from www to non-www but have your wp-options table siteurl (WordPress address URL) and home (Blog Address URL) set with a www url prefix. Check your Firewall Some firewalls (e.g., eTrust Personal Firewall) block you from logging in to WordPress. Disable your firewall and try to log in again. If All Else Fails If these steps fail, please indicate that you have tried all these possible solutions when posting at the WordPress Support Forum. Be sure to give details of your server setup, if you know it, including mySQL and PHP versions, as well as your operating system (OS), browser, and the WordPress version that is causing these problems. Keyboard Shortcuts atachibana — Sun, 10 Jul 2016 12:12:56 +0000 Editor Shortcuts In the WordPress visual editor you can use a combination of keys to do things that normally need a mouse, trackpad or other input device. Rather than reaching for your mouse to click on the toolbar, you can use the following keyboard shortcuts: Windows and Linux use "Ctrl + letter", Mac uses "Command (⌘) + letter". Ctrl + key Letter Action c .... Copy v .... Paste a .... Select all x .... Cut z .... Undo y .... Redo b .... Bold i .... Italic u .... Underline k .... Insert/edit link Alt + Shift + key The following shortcuts use a different key combination: Windows/Linux: "Alt + Shift (⇧) + letter". Mac: "Ctrl + Option (alt ⌥) + letter". (Macs running any WordPress version below 4.2 use "Alt + Shift (⇧) + letter"). Letter Action n .... Check Spelling (This requires a plugin.) l .... Align Left j .... Justify Text c .... Align Center d .... Strikethrough r .... Align Right u .... • List a .... Insert link o .... 1. List s .... Remove link q .... Quote m .... Insert Image w .... Distraction Free Writing mode t .... Insert More Tag p .... Insert Page Break tag h .... Help x .... Add/remove code tag 1 .... Heading 1 2 .... Heading 2 3 .... Heading 3 4 .... Heading 4 5 .... Heading 5 6 .... Heading 6 9 .... Address Formatting Shortcuts Formatting Shortcuts while using visual editor (Since Version 4.3) Letter . Action * ...... Start an unordered list - ...... Start an unordered list 1. ..... Start an ordered list 1) ..... Start an ordered list ## ..... H2 ### .... H3 #### ... H4 ##### .. H5 ###### . H6 > ...... transform text into blockquote --- .... horizontal line `..` ... transform text into code block Keyboard Shortcuts for Comments Beginning with WordPress Version 2.7, the ability to use keyboard shortcuts to browse and moderate comments was introduced. These keyboard shortcuts are designed to save time by allowing you to rapidly navigate and perform actions on comments. If your blog gets a large number of comments, you will find these shortcuts especially useful. Activating Keyboard Shortcuts Keyboard shortcuts are enabled on a per-user setting, and can be turned on by visiting the Profile panel in Administration > Users > Your Profile. Check the Keyboard Shortcuts checkbox to enable keyboard shortcuts for comment moderation. Please note, the keyboard shortcuts are designed to use both hands, simultaneously, on a QWERTY style keyboard layout. The Meaning of Selected The keyboard shortcuts are used for navigation and for actions. For any action to affect a comment, that comment must be first selected. The comment that is considered selected is indicated with a light-blue background. By default, no comment is selected, so, you will need to press either the letter j key, or letter k key, to start navigating. Using Keyboard Shortcuts to Navigate Comments Navigating comments is accomplished with the j and k keys. When you first visit the Comments page, no comments is selected, so, first press the letter j, or the letter k, to select the first comment. After that, just press the letter j to move the select to the next comment. Pressing j moves the current selection (light-blue background) down. Pressing k moves the current selection (light-blue background) up. Note that if you come to the bottom of a page of comments and press j again, you will be taken to the next page and the first comment of that next page will be selected. Likewise, pressing k at the top of a comment page will zoom you to the previous page, selecting the comment at the bottom of that previous page. This makes it very easy to navigate through a long list of comments to perform the necessary actions. Using Keyboard Shortcuts to Perform Actions on Comments For one of these actions to affect a comment, make sure the comment is first selected (see above). Pressing a approves the currently selected comment. Pressing s marks the current comment as spam. Pressing d moves the comment to the trash (WordPress 2.9) or deletes the current comment. Pressing z restores the current comment from the trash or activates the Undo when that row is selected. Pressing u unapproves the currently selected comment, placing it back into moderation. Pressing r initiates an inline reply to the current comment (you can press Esc to cancel the reply). Pressing q activates "Quick Edit" which allows for rapid inline editing of the current comment. Pressing e navigates to the edit screen for the current comment. Bulk Actions You can also perform an action on multiple comments at once. First, you'll need to select the comments for the bulk action, using the x key to check the checkbox for the currently selected comment. Shift-x can be used to toggle the checkboxes, inverting their state. Once you have some comments checked: Pressing Shift-a approves the checked comments. Pressing Shift-s marks the checked comments as spam. Pressing Shift-d deletes the checked comments. Pressing Shift-u unapproves the checked comments. Pressing Shift-t moves the checked comments to the Trash. Pressing Shift-z restores the checked comments from the Trash. Forum Welcome atachibana — Sun, 10 Jul 2016 12:23:56 +0000 [codex_languages en="Forum Welcome" es_codex="Bienvenida al Foro" it_codex="Benvenuto nel Forum" ja_codex="フォーラムへようこそ" ptbr_codex="Bem-vindos ao Fórum de Suporte" ro_codex="Bine ai venit pe Forum" uk_codex="Вітання Форуму" ru_codex="Добро пожаловать на форумы"] Welcome to the WordPress Support Forum This page is a welcome message for the Support Forums. We hope that you will find this a useful resource, as it is intended to be a "Quick-Start Manual" rather than full documentation. This introduction is designed to help you find your way around the forums and get started as quickly as possible. There is more information available at an expanded Codex article, Using the Support Forums. Before you post, make sure you're posting about a self hosted WordPress.org site and NOT a WordPress.com site. If you're not sure, read WordPress.com vs WordPress.org. These forums are meant for the core application, themes, and plugins that are distributed on wordpress.org. We do not support commercial themes or products. Search First Many of the questions that are posted in the forums have been posted many times before, and get the same answers each time. Before starting a new thread, please try searching the forums for an answer. Both the forums and the HelpHub have been indexed by Google. So if you can't find your answer with a forum search, it is worth typing it into Google as well (e.g. Google for site:wordpress.org/support widget). If you do find a topic that describes a problem similar to yours, read it but do not post in that topic to ask for help. Where To Post The forum is split into sections, with each forum having its own one-line description on the front page. Please try to choose the most suitable section for your new topic, and please post your topic in only one section. Multi posting is frowned upon. Duplicate postings will be closed or deleted. Posting your own topic is smiled upon. Unless you are using the same version of WordPress on the same physical server hosted by the same hosts with the same plugins, theme, and configurations as the original poster, do not post in someone else's thread. Start your own thread. Choose your section from the forum front page. After following the appropriate link, start a new thread by clicking the "Add New »" button to the right of the section's title. If you have a question about a specific theme or plugin, then we suggest visiting the homepage of the theme/plugin first and creating your topic on its support page. This has the effect of tagging the post with that item's name, making it more visible to the author and making it more clear what your post is about. You're more likely to get a response this way. What to post Choose A Good Topic Title When you start a new topic, try to use an appropriate title. "Database error creating a new post" is a good title. "URGENT HELP PLS!!!" is not a good title. A good title can be the difference between getting help and not. Include as Much Information as Possible Put down all the detail you can about your hosting environment, your WordPress install (plugins, themes, etc.), and the problem you are having. If you are seeing errors, copy them word for word into your post. It's better to include the full error than to summarise - sometimes wording is important. If you did something before you came across a problem, write down exactly what you did. You can post links to screenshots to illustrate your issues, but don't use screenshots in place of a website link. Forum volunteers need a link to the webpage with the issue, to see a working (or broken) example of it. Forum etiquette Linking to Your Site If you are asking for help and your question relates to a specific site or page, please provide a link to it. It may help others when they are trying to help you. But remember that the forum is not designed to be a link portal. Excessive linkage will be moderated, as might signatures or links with no associated question. Also be aware that links will not get removed after they've been posted, unless in extreme circumstances. Signatures Signatures in threads will be removed as they cause clutter and distract from the information provided. Warn About Adult Content Some sites contain content that is not suitable for a general audience or for viewing while at work. To avoid creating problems for anyone who is trying to help you, please add NSFW to the topic title of your post, as well as tag your post NSFW, if you think your site falls into this category. (If you don't, your post / links may be removed.) No Bumping Do not bump posts. Bumping a post to "the top" does not help your topic get noticed. The volunteers who try to answer questions look for those without replies first. If you bump a post, then it disappears from the 'No Replies' list. If you want help, do not bump. Moderators will delete bumps they find. This is in order to help you get back into the No Replies listing, where you are more likely to get an answer. About threads without replies We have a way of tracking down threads that have no answers. That list shows every thread that hasn't received a reply / comment. When your thread runs off the first page of the forum its likelihood of being found is reduced, but the 'no-replies' list gives your thread more chances to be found. Especially when some helpers use that list to prioritise over other answered threads. Your unanswered thread will still have the lifeline of the 'No Replies' list if it is no longer on the first page of the forum. When your thread has been answered it does not appear on the 'No Replies' list. It doesn't matter most of the time because the people replying are there to help you, but it matters when it's just you bumping your post. You may think you're helping your case by bumping your topic to the top of the list, but you are actually hurting yourself in the long-run. It's the long-run that you want to account for, as these volunteer-driven forums may struggle to provide you with quick support. Posting Code When you need help with code, it helps us if you post it in the forums. That said, we really need you to remember to keep your code enclosed in backticks (`) to stop it being parsed by the forum's software (which may also make it unreadable). Highlight your code in the editor and click on the "code" button to enclose your code in backticks. You don't have to mark each line, just the section (like you would for blockquotes). If you don't do this, the odds are high that your post will be caught as spam by the automated tool, and we'll have to fix your post for you. Posting Large Excerpt of Code When you post a large excerpt of code, it often makes the thread difficult to read. Instead, we ask you please paste your code in a Pastebin or create a Gist and link to it in your post. As for what constitutes a large excerpt, it's difficult to say. Certainly, if you're quoting an entire php/css/js file, put it on pastebin. For anything under 100 lines, we ask you use your best judgement. Do consider that you're asking people for free support, and it's much easier to read a pastebin/gist than a styled block of 150 lines of multi-indented code. Scrolling back and forth, as well as up and down, trying to unpick code via a cramped code box is a time-consuming activity that distracts from answering the actual questions. Note: Anything you put in a forum topic or a pastebin is public. Anybody can see it. Don't post any passwords or private info there. Paying for support Offering to Pay WordPress is free software and this is a free forum, so requesting paid help is discouraged. We also don't need bidding wars in the forums. If you post asking for paid help and you have posted some contact information, your thread will not be deleted but it will be closed. If you have not posted contact information, we may ask you to add it. The thread will then be closed. Any thread that offers any service for money can be closed at any time. We are not against paid services but these forums are not the right place for them. Forum volunteers may advise you to seek professional support from WP Jobs. Please don't take this as a rude gesture. The main reason for this is that you may require more support than this forum can provide. Offering to Work For Hire Please don't offer to work for hire in your replies on these forums. If you're going to help in the forums, help in the forums. If you're looking for work, please do so on WP Jobs instead. We're all for people making their living on WordPress, but we're trying to keep the free support forums ... free. Commercial Products If you use a commercial theme or plugin and need support, please go to their official support channel. In order to be good stewards of the WordPress community, and encourage innovation and progress, we feel it's important to direct people to those official locations. Doing this will provide the developer with the income they need to make WordPress awesome. Forum volunteers are also not given access to commercial products, so they would not know why your commercial theme or plugin is not working properly. This is one other reason why volunteers forward you to the commercial product's vendors. The vendors are responsible for supporting their commercial product. Where Did My Post Go? If you leave the forums and can't find your thread when you get back, you can see a list of all the threads you've been involved in on your profile page. To view your profile click on the "View your profile" link in the upper right of the header at the top of every forum page. Note: The "View your profile" link is only available after you log in. You might want to login now, if you haven't already. If you know you posted but you can't find it, it may have gotten caught by our over-ambitious spam filter. If that happens, don't panic. One of the volunteers will get around to finding it and clearing it, usually within an hour. You can get caught as spam if you post too many times in succession, or if your posts are all the same (yep, it can check that), and a score of other potential causes. It happens to pretty much everyone at least once. Helping Out If you are here to help others, you can view a quick list of unanswered topics by using the "No Replies" link at the bottom of the front page. The "No Replies" filter is often used by folks to find questions to answer next. This is also a good reason why nobody should bump their topics. Bumping is discouraged and bumps may be deleted by the moderators. If you're helping out, do your best to fully assist the person having the issues, and don't use your support as an excuse to promote your own site/themes/plugins. That behavior is frowned upon. Similarly, we ask that you not demand payment, solicit work, or take the conversation to a private location. The point of helping out on the WordPress.org forums is to help out on the forums. XKCD illustrates exactly what we don't want to happen. Leave something for the next person who has the same problem. Forum moderation Reporting Threads To report a bad (spam etc.) post, add a tag called 'modlook' to the thread. That feed is checked very regularly by the moderating team. The modlook tag is only for reporting issues with the forum itself - abusing this tag in the hopes of attracting the attention of a moderator to your support question will not be viewed kindly. Don't put the modlook tag on your support question - put it on things like spam, or people using signatures in their posts, or duplicate threads. Things that a forum moderator should see and correct. Note that it is not necessary to point out the actual problem, either with a post or with additional tags. Our moderators are smart. They'll scan the thread and find the problems themselves, and deal with it accordingly. Adding your own comments just gives them more to clean up, so please don't do it unless you feel the nature of the problem is very unclear like a double (or quadruple) post. Closing Posts Posts are automatically closed after 12 months, if there are no new replies. We also reserve the right to close posts that are deemed non-productive to the community. While many times non-productive posts are deleted, sometimes they have some relevance and instead are closed so the information remains, but discussion can no longer be furthered. This includes, but is not restricted to, posts on the following topics: hosting recommendations (for or against) off topic conversations (i.e. non-WordPress) old/outdated topics clearly resolved topics excessive rudeness or antagonism requests for paid support Sometimes you might notice that your posts are closed as soon as you post them. This means that they have been caught in the spam queue, which is an automated process and sometimes catches posts by mistake. If this happens, a moderator then has to manually unspam your posts, so it may take a little while to be rectified. Your patience is appreciated! Being 'Mod Watched' or Banned Sometimes, when someone's having a bad day, their posts will be flagged so all posts must be approved by a moderator. This is considered a cool-down tactic, and isn't intended to be a bad thing. It just means your behavior caught our attention in a slightly negative way, and we want to keep an eye on you. If this happens, just be patient. We will review and approve your posts pretty quickly, or edit them and reply, pointing out what's wrong. If, however, your actions escalate, you'll get banned. There's no one behavior to point at for this, but basically if you start lashing out, calling people names, making accusations, emailing people nasty messages, or challenging the authority of the moderators, you may end up banned. The basic rule of thumb is don't act like a bad person. You're an adult, you know how to behave. If you don't, or can't, you will be banned. Harassing anyone is not permitted, and you will be banned if you do this. tl;dr: If your posts are being moderated or caught as spam, don't panic, just relax and maybe take a break. We'll still be here. Deleting / Editing Posts We reserve the right to delete topics or posts that are off-topic or detrimental to the community, however it is not the general policy to edit or delete forum posts unless they are spam, harassing, illegal, or outright abuse. We will not delete your post or remove your link just because an Internet search for a term brings up the forums before your actual URLs. Users can edit a post for up to 35 minutes from the time of submission. After that, the post can only be edited by a moderator. When a post is made and people contribute answers to an issue, that then becomes part of the community resource for others to benefit from and deleting posts removes this added value. Forum topics will only be edited or deleted at the discretion of the moderators if they represent a valid legal, security, or safety concern. Don’t post things you aren’t 100% okay with being public. We’ll delete them if we agree it’s a big enough deal, but ‘My SEO!’ is never an acceptable reason. (Remember too that other sites take archive copies of the forums, and we can do nothing to control that.) Attention Plugin/Theme Authors: If users complain about your plugins, even if they are incorrect, we will not delete their posts. It's your responsibility to represent yourself well and educate them. Even if you are not running a business via your plugins, your reputation is impacted more by how you handle people's complaints versus how they treat you. Deleting Accounts Accounts are not deleted, not even for obvious spammers, due to technical limitations of the system. If you don't want to use the forums anymore, log off and don't return. We'll miss you! Usernames cannot be changed either. If you want to use a different username, then create the new username and stop using the old one. There are many systems that your forum account hooks into: support forums, make blogs, core SVN, plugins SVN, theme SVN, meta SVN, and so on and so forth. It's a technical mess and we know it's annoying when you want to walk away, or regret the username cocopuff as not professional, but it's just what we've got right now. Contacting the Moderators As most of the moderators are volunteers, we ask that if you need moderator help for any reason, you post your request in the forum and tag it with the term "modlook" - someone will come take a look. Do not abuse that tag, or your account will be disabled. If you use the modlook tag to bring attention to your topic you risk your account being disabled. Following moderators 'home' and sending them email can be harassment, so please, before you hit send or fill in their contact form, remember that these are real human beings, and calling them names because they won't delete your post (or did delete one), is not cool. What not to do We need to keep the forums friendly, so, occasionally, topic content will be moderated. In severe cases, users may be blocked. This might mean anything from the light editing of some posts to complete removal of topics and deactivation of accounts. It should really go without saying, but the following are likely candidates for moderation or intervention: Forum members should not post their email addresses, ask others to post their email or solicit contacting people off of the forums. Forum members should not post login information, even test IDs and test passwords. Plugin and theme authors may post their contact URL or even their email address in their own support sub-forum, but that should be a last resort thing. Forum members, including plugin and theme authors, should never ask for admin or FTP access to a server, MySQL, or WordPress installation. Harassment. This should be simple, but please don't harass or abuse people. Don't send them emails calling them names. Don't twitter stalk them. Do not follow any user or moderator home. This means, do not go to their websites, do not pick out their home addresses, phone numbers, Twitter ID, Skype ID, Facebook, any social media accounts or ways to contact them and use it to ask for support. You may not think this is harassment but it is. Only use contact methods explicitly given. Spam and affiliate links, duplicate posts, offensive posts, posts without content, flames, and references to adult content that have not been highlighted as NSFW. Ask for help regarding premium themes/plugins. We do NOT support premium themes as you paid for their support when you bought it and it is not our place to keep vendors in business. If someone wants to help, that is fine. Posting in all caps. This is considered shouting and is rude. Please note that this list is not exhaustive. Every post is judged on its own merits. Talking about the forum itself If you would like to discuss an aspect of the forum, or report a problem with the forum itself, use the #forums channel on slack. Note that the channel is for discussing issues with the support forum itself, rather than for posting your problems with WordPress. It's primarily used by forum moderators and other regular volunteers for discussion of code of conduct and behavioral issues on the forums. While the list is public for anyone to join or read, it's intended use is for better communication among volunteers. Finally And that's all. Enjoy your stay at the forums! Oh.. And, when you're done, please mark your topic as "Resolved". Thanks. Click here to return to the Forums Gallery Shortcode juhisaxena — Sun, 10 Jul 2016 16:13:37 +0000 The Gallery feature allows you to add one or more image galleries to your posts and pages using a simple shortcode. Since WordPress 2.5 and up until 3.5, the gallery shortcode was commonly used in its most basic form: [[gallery]] Following 3.5, gallery shortcodes started including the image IDs by default. Like this: [[gallery ids="729,732,731,720"]] It's important to note that this style of gallery shortcode is not new to 3.5. Previously, we could use the include attribute. However, it is much easier to generate and manage with the new Media Workflow introduced in 3.5. Specifying IDs in your shortcode allows you to include images in your gallery that aren't necessarily "attached" to your post — that is to say, not uploaded from within your post or page. This flexibility allows you to create and embed any number of galleries containing any number of images. Note: If you choose to use just the "barebones" version of the gallery shortcode in your post or page, only images that are "attached" to that post or page will be displayed. Usage There are several options that may be specified using this syntax: [code language="php"] [[gallery option1="value1" option2="value2"]] [/code] You can also print a gallery directly in a template like so: [code language="php"] [/code] This works too: [code language="php"] post_parent ) . '"]]'; print apply_filters( 'the_content', $gallery_shortcode ); ?> [/code] Options The following basic options are supported: orderby Specifies how to sort the displayed thumbnails. The default is "menu_order." Options: menu_order - You can reorder the images in the Gallery tab of the Add Media pop-up. title - Order images in the Media Library, based on the image title. post_date - Sort images by date/time. rand - Order images randomly. ID order Specifies the sort order used to display thumbnails. ASC or DESC. For example, to sort by ID, use DESC: [code language="php"] [[gallery order="DESC" orderby="ID"]] [/code] columns Specifies the number of columns. The gallery will include a break tag at the end of each row, and calculate the column width as appropriate. The default value is 3. If columns is set to 0, no row breaks will be included. For example, to display a 4 column gallery: [code language="php"] [[gallery columns="4"]] [/code] id Specifies the post ID. The gallery will display images which are attached to that post. The default behavior, if no ID is specified, is to display images attached to the current post. For example, to display images attached to post 123: [code language="php"] [[gallery id="123"]] [/code] size Specifies the image size to use for the thumbnail display. Valid values include "thumbnail," "medium," "large," "full" or any other additional image size that was registered with add_image_size(). The default value is "thumbnail." The size of the images for "thumbnail," "medium," and "large" can be configured in the WordPress admin panel under Settings > Media. For example, to display a gallery of medium sized images: [code language="php"] [[gallery size="medium"]] [/code] Some advanced options include: itemtag The name of the XHTML tag used to enclose each item in the gallery. The default is "dl." icontag The name of the XHTML tag used to enclose each thumbnail icon in the gallery. The default is "dt." captiontag The name of the XHTML tag used to enclose each caption. The default is "dd." For example, to change the gallery markup to use div, span and p tags: [code language="php"] [[gallery itemtag="div" icontag="span" captiontag="p"]] [/code] link Specify where you want the image to link. The default value links to the attachment's permalink. Options: file - Link directly to the image file. none - No link. [code language="php"] [[gallery link="file"]] [/code] include Comma-separated attachment IDs that include only the images from these attachments. [code language="php"] [[gallery include="23,39,45"]] [/code] exclude Comma-separated attachment IDs that exclude specific images from these attachments. Please note that include and exclude cannot be used together. [code language="php"] [[gallery exclude="21,32,43"]] [/code] Source File The gallery shortcode is located in wp-includes/media.php. Related WordPress Shortcodes: [[audio]], [[caption]], [[embed]], [[gallery]], [[playlist]], [[video]] WordPress Features atachibana — Sun, 10 Jul 2016 12:37:54 +0000 WordPress is a powerful semantic publishing platform, and it comes with a great set of features designed to make your experience as a publisher on the Internet as easy, pleasant, and appealing as possible. We are proud to offer you a freely distributed, standards-compliant, fast, light, and free content management system, with sensible default settings and features, and an extremely customizable core. The following is a list of some of the features that come standard with WordPress, however there are literally tens of thousands of plugins that extend what WordPress does, so the actual functionality is nearly limitless. You are also free to do whatever you like with the WordPress code, extend it or modify in any way or use it for commercial projects without any licensing fees. That is the beauty of free software, free meaning not only price but also the freedom to have complete control over it. At a Glance Proven WordPress powers more than a quarter of new sites today, is the content management system (CMS) of choice for nearly a half of the top million sites making it the most popular on the web, and is trusted by content publishers both large and small including CNN and the NY Times. With more than 50 million sites globally and 13 years of proven history, you know you’re getting the best software for the job. Easy to use At the core of WordPress is a simple interface similar to the desktop publishing software you use today. With no coding experience or expert knowledge necessary, the learning curve is often about as short as typing in your site’s URL and logging in. In fact, most users are able to pick up the basics without any training at all. Interfaces are polished and easy to use, and are the result of years of refinement. It’s the power of Microsoft Word with the intuitiveness of an iPhone. Built for Publishing WordPress makes sharing content and attracting readers to your site a breeze. Whether pushing content to social networks, ensuring that your website is provided in the optimal format to appear at the top of search results the moment you hit publish, or providing visitors the ability to subscribe to specific content sub-feeds in their favorite feed reader (or even via e-mail), WordPress is not simply a website, but rather a content-publishing platform. With a single click, you have a powerful megaphone to broadcast your message to the world. Backed by Community Support WordPress is supported by a vibrant community of users who have already solved many of the toughest challenges to sharing information today. WordPress Version 4.6 has been downloaded more than 20 million times since it was released a few months ago. With a library of more than 50,000 free, open-source Plugins and Themes growing each day, and hundreds of core contributors each release cycle, the WordPress community is an ecosystem built around the platform’s viability and proven success. Multisite WordPress can be extended to MultiSite feature on demand base. You are able to develop and maintain multiple sites using single WordPress installation. Multisite is a feature of WordPress 3.0 and later versions that allows multiple virtual sites to share a single WordPress installation. When the multisite feature is activated, the original WordPress site can be converted to support a network of sites. Content is King Your Entire Workflow WordPress can take the place of your entire workflow from the initial draft to the time you hit publish – spelling, grammar, collaboration, and review – there’s no need for e-mails back and forth or expensive desktop software. Beyond Black and White Everything that makes webpages feel rich – pictures, videos, music, documents – can feel right at home in WordPress. With a drag-and-drop file uploader that uses the latest technology to ensure your file effortlessly makes it to the web page every time, and a media browser to help you store, organize and find the files you’re looking for, WordPress hosts the files that make your pages pop. Distraction Free Writing Between E-Mail, IMs, Texts, Tweets, and Status Updates, we have enough distractions in today's world. Your publishing platform should not be one of them. While writing, WordPress literally fades away, letting you concentrate on your ideas themselves, not how you’re getting them out there. Never Lose a Word WordPress automatically saves your work as you type so you don’t have to worry if your computer crashes or you make a mistake. Want to go back to a previous version? Not a problem. Every time you hit save, WordPress creates a snapshot that you can restore with a single click. Time Travel Okay, not really, but it’s pretty close. WordPress lets you schedule posts for some time in the future or lets you backdate a post for some time in the past so that you can write when it's convenient for you. Publish Anywhere The internet’s everywhere, so why shouldn’t your workflow be? WordPress has mobile applications for Android, iOS, Blackberry, Nokia, Windows Phone 7, even WebOS. Wherever you are, control of your site is literally at your fingertips. Phone not listed? No fret. You can even post to your site by e-mail. Password protection You can give passwords to individual posts to hide them from the public. You can also have private posts which are viewable only by their author. Multi-paged posts If your post is too long, cut it up into pages, so your readers don't have to scroll to the end of the world. Save Drafts Save your unfinished articles, improve them later, publish when you're done. Previewing Posts Before you press the "Publish" button, you can look at the preview for the article you just wrote to check if everything is the way you want it. In fact, you can do that at any time, since the preview is "live". A Supercharged V8 Under the Hood The Right Tuxedo for Any Content Your content deserves the best. The site should conform to your content, not the other way around. WordPress comes with a full theme system which makes designing everything from the simplest site to the most complicated portal a piece of cake. Have a new design every day. Your ideas should look as good as what they say. Obsessively Organized It doesn’t matter how much content you have, if your visitors can’t find it. WordPress organizes your content by day, by month, by year, by author, by category — any way you can describe it — and dynamically creates browsable archives so things always stay up to date. Killer Search Inside and Out WordPress has killer search baked in. Every word you write is fully searchable through a single box at the top of each page and if your users choose to use an external search engine like Google, rest assured, WordPress will present your content in a way that all but ensures it makes it to the top of the results every time. Even the URLs are Beautiful Ever go to a site and look up to the URL bar only to see a string of letter and number gobbledygook? WordPress realizes that websites are built for people, not computers. Every URL is intuitively written for humans and describes what your content says, not where it sits in a database. Typography Nerds Rejoice To do it right, publishing on the web can be a pain without the right tools. Every time you hit publish WordPress silently typesets each and every letter for seamless web production. Where many other CMSs let the details fall by the wayside, WordPress uses the Texturize engine to intelligently convert web-unfriendly characters like quotes, apostrophes, ellipses, em and en dashes, multiplication symbols, and ampersands into typographically correct HTML entities. For information about the proper use of such entities see Peter Sheerin's article The Trouble With Em ’n En. ¡Bienvenidos a WordPress! WordPress has been fully translated to more than 70 different languages, so however you say “publish”, you’ll be saying it in no time flat. You can create a site that is localized to your choice, and delivered in a language of your choice. The gettext method is used to translate and localize WordPress to the fullest extent. Drag and Drop Administration Didn't major in computer science? No degree required. Most of what users see from menus to the dynamic functionality on each page can be fully customized with simple drag-and-drop controls on the back end. Multiple Personalities Got a bunch of users? Not a problem. WordPress lets you define different roles for different users – just like in real life – and lets you assign privileges accordingly. Users can register themselves (if you want), and can submit content for your review. User Tested, Geek Approved Out-of-the-box Power WordPress provides extensive functionality right out-of-the-box and often little customization is needed to adapt the software for your unique use. Many other CMSs rely on you to hunt down, install, and configure a long-list of add-ons just to get many of the features WordPress considers core (comments, RSS feeds, revisions, etc.) and relies on developers to undertake significant coding efforts to provide the functionality you need. WordPress does the heavy lifting so you don’t have to. Why reinvent the wheel when you already have the best wheel in the world? Open and Transparent WordPress is built by a dedicated community of professional developers, academics, and enthusiasts with the source code released to the world to take apart, build upon, and improve. Its hallmark is a rapid development cycle, meaning frequent updates and always up-to-date software, all with no licensing fees or direct costs. And with an extensive international community professional support is always wherever you are. It’s Your Data Some publishing platforms lock you in with proprietary data formats. Not here. WordPress relies on open standards to allow you to take your data with you, and even comes with tools to seamlessly import from many popular sources. It’s your data, and you should be able to do what you want with it. We currently have importers for Movable Type, Textpattern, Greymatter, Blogger, and b2. Work on importers for Nucleus and pMachine is under way. It’s Your Software WordPress is designed to be installed on your own web server, in the cloud, or in a shared hosting account. You have complete control. Unlike commercial software or third-party hosted services, you can be sure of being able to access and modify everything related to your site. You can even install WordPress on your personal computer, or on a corporate intranet. Power One Site or Millions WordPress offers multi-site technology. It is the same technology that powers over 20 million sites on WordPress.com and global sites like CNN and the New York Times. Multi-site technology allows users to have full administrative control over their own site, without any security concerns. Each site can have its own look-and-feel (themes), its own functionality (plug-ins), and manage its own users, while at the same time, network-wide policies and security updates can be deployed at the click of a button. Dynamic page generation No rebuilding of all your pages each time you update your site, or any aspect of it. All pages are generated using the database and the templates each time a page from your site is requested by a viewer. This means that updating your site, or its design is as fast as possible, and required server storage space usage is minimal. Template Driven Design WordPress uses templates to generate the pages dynamically. You can control the presentation of content by editing the templates using your favorite text-editor or IDE, or even the built-in Template Editor tool. Template tags make it easier to design the content and information displayed on your site. You don't need to be a PHP whiz to make your site's look-and-feel match your vision. A Serious Platform for Serious Content Your Site is Your Castle WordPress has more than eight years of history powering stable, secure websites. Vulnerabilities are discovered quickly because of the wide user-base and dedicated open-source community, patches are rapidly developed by the dedicated security team, and often released in the span of hours from the time they are reported. WordPress comes with an integrated core-update system, so patches are deployed at the click of a mouse. WordPress sanitizes all user input, restricts URL access, has an extensive user permissioning system, and never stores passwords in an unencryptable format. WordPress uses WordPress.com’s 20 million users to beta test releases before they come out, so that by the time new versions are released, stakeholders can be confident in their stability. Extensive APIs WordPress’s core relies on its own extensive API interface (commonly known as dogfooding) which consequently allows developers to quickly and effectively customize the application to their unique needs. Many aspects of the essential WordPress experience can be overridden or modified by user-generated hooks and filters. These APIs help WordPress integrate seamlessly with existing systems, a necessity in a stove-pipe rich environments. Enterprise Ready Any challenge the organization faces, chances are, someone else has already tackled it and provided the code free of charge. WordPress has been adapted to countless enterprise environments, and provides support for Active Directory authentication, user management, work-flow integration, and scheduled backups, among other enterprise-centric features. Interoperability Want to connect WordPress to another system? WordPress uses XML-RPC, an open XML standard that allows different systems in different environments to talk to one another. XML-RPC is designed to be as simple as possible, while at the same time allowing for complex tasks to be performed. WordPress also supports an extended version of the Blogger API, MetaWeblog API, and finally the MovableType API. You can even use clients designed for other platforms like Zempt. Maintenance so simple you’ll wonder why you did it the other way Installing and upgrading WordPress is a piece of cake. WordPress’s famous five minute installation is the envy of the industry, and with one click updates, you’ll know you are always using the best. Try it and you’ll wonder why all software isn’t this easy. Trust, but Verify Not everyone is evil, but keep those who are in check by limiting which html tags are kosher on your weblog. The default html tags allowed by WordPress are a sane choice to let people use html in their comments and posts, without compromising the safety of your data or server. Standards Compliant… and then some The WordPress team has gone to great lengths to ensure every bit of WordPress generated code is in full compliance with the standards of the W3C. This is important not only for interoperability with today’s browser but also for forward compatibility with the tools of the next generation. Your website is a beautiful thing, and you should demand nothing less. More than a Blog… Much, Much More Anyone who says WordPress is a mere blogging platform is covering for the fact that they haven’t been following the CMS’s explosive growth over the past couple years. Saying WordPress is only a blogging platform is like saying BMW is only a propeller manufacturer. In fact, the majority of the time, WordPress isn’t even used as a blog. With built in support for custom post types and custom taxonomies, if you can dream it, WordPress can make it a reality. Broadcast Your Ideas Feeds The RSS 1.0 (aka RDF), RSS 2.0 and ATOM specifications are fully supported by WordPress, and what's more, just about any page on your site has an associated feed that your readers can subscribe to - there's a feed for the latest posts, for categories, comments, well, like we said earlier, for anything you want. The more options your readers have to keep track of different sections of your site, the easier it is for you to spread the word around the world. WordPress also fully supports RSS 2.0 with enclosures, so adding mp3 files (such as podcasts) to your RSS feeds is a snap. Inter-site Communication In an increasingly connected world, WordPress comes ready for PingBack and TrackBack, two very useful ways of connecting to other sites, and to enable them to do the same. Plus, WordPress supports pinging Ping-O-Matic, which means maximum exposure for your site to search engines. Grow Your Community Community Building WordPress is not the YMCA, but it does help build communities around sites, through the use of comments, trackbacks and pingbacks, helping you keep in touch with the audience and fostering friendship Comments Visitors to your site can leave comments on individual entries, and through Trackback or Pingback can comment on their own site. You can enable or disable comments on a per-post basis. Spam protection Out of the box WordPress comes with very robust tools such as an integrated blacklist and open proxy checker to manage and eliminate comment spam on your blog, and there is also a rich array of plugins that can take this functionality a step further. Full user registration WordPress has a built-in user registration system that (if you choose) can allow people to register and maintain profiles and leave authenticated comments on your blog. You can optionally close comments for non-registered users. There are also plugins that hide posts from lower level users. Allowed html tags Not everyone is evil, but keep those who are in check by limiting which html tags are kosher on your site. The default html tags allowed by WordPress are a sane choice to let people use html in their comments, without compromising the safety of your data or server. Moderation For the control freak in all of us, WordPress provides an array of moderation options. You can moderate *all comments before they appear on the blog *comments with specific words in them *comments posted from specific IP addresses *comments containing more than some specified number of links. All these moderation options keep spammers and vandals in check. Notification WordPress can keep you in the loop by sending you an email each time there is a new comment or a comment awaiting moderation. License, Platform, and Philosophy License WordPress is licensed under the GPLv2 or later which guarantees users several freedoms: * The freedom to run the program, for any purpose. * The freedom to study how the program works, and change it to make it do what you wish. * The freedom to redistribute. * The freedom to distribute copies of your modified versions to others. Platform PHP 5.6 or greater and MySQL 5.6 or greater and mod_rewrite Apache module. More information Philosophy WordPress's development is guided by a set of unwavering principles. They are: * Work Out of the Box * Design for the Majority * Decision not Options * Clean, Lean, and Mean * Strive for Simplicity * Deadlines are not Arbitrary * Be Mindful of the Vocal Minority * The WordPress Bill of Rights phpMyAdmin atachibana — Sun, 10 Jul 2016 12:42:25 +0000 What is phpMyAdmin? An administrator's tool of sorts, phpMyAdmin is a PHP script meant for giving users the ability to interact with their MySQL databases. WordPress stores all of its information in the MySQL database and interacts with the database to generate information within your WordPress site. A "raw" view of the data, tables and fields stored in the MySQL database is accessible through phpMyAdmin. What is it good for? The phpMyAdmin program is handy for performing maintenance operations on tables, backing up information, and editing things directly in the event that WordPress is not working. Occasionally, in the Support Forums, someone will post a SQL query of some benefit or other that can be run using phpMyAdmin. Although many of the same tasks can be performed on the MySQL command line, doing so is not an option for many people. Where can I get it? Often host control panels, such as cPanel and Plesk, have phpMyAdmin pre-installed, so there is nothing special you have to do to use it. It is usually linked from the database page. Ask your host if this is available. You can download phpMyAdmin yourself and install it from the main phpMyAdmin project page. Warning With great power comes great responsibility. phpMyAdmin allows you to interact with the database directly: it also lets you mess up the database directly. There is no "undo" or "undelete" in your database. Always exercise caution when working with the database. Configuring Automatic Background Updates atachibana — Sun, 10 Jul 2016 12:58:04 +0000 Update Types Automatic background updates were introduced in WordPress 3.7 in an effort to promote better security, and to streamline the update experience overall. By default, only minor releases – such as for maintenance and security purposes – and translation file updates are enabled on most sites. In special cases, plugins and themes may be updated. In WordPress, there are four types of automatic background updates: Core updates Plugin updates Theme updates Translation file updates Core Updates Core updates are subdivided into three types: Core development updates, known as the "bleeding edge" Minor core updates, such as maintenance and security releases Major core release updates By default, every site has automatic updates enabled for minor core releases and translation files. Sites already running a development version also have automatic updates to further development versions enabled by default. Update Configuration Automatic updates can be configured using one of two methods: defining constants in wp-config.php, or adding filters using a Plugin. Configuration via wp-config.php Using wp-config.php, automatic updates can be disabled completely, and core updates can be disabled or configured based on update type. Constant to Disable All Updates The core developers made a conscious decision to enable automatic updates for minor releases and translation files out of the box. Going forward, this will be one of the best ways to guarantee your site stays up to date and secure and, as such, disabling these updates is strongly discouraged. To completely disable all types of automatic updates, core or otherwise, add the following to your wp-config.php file: [code language="php"]define( 'AUTOMATIC_UPDATER_DISABLED', true );[/code] Constant to Configure Core Updates To enable automatic updates for major releases or development purposes, the place to start is with the WP_AUTO_UPDATE_CORE constant. Defining this constant one of three ways allows you to blanket-enable, or blanket-disable several types of core updates at once. [code language="php"]define( 'WP_AUTO_UPDATE_CORE', true );[/code] WP_AUTO_UPDATE_CORE can be defined with one of three values, each producing a different behavior: Value of true – Development, minor, and major updates are all enabled Value of false – Development, minor, and major updates are all disabled Value of 'minor' – Minor updates are enabled, development, and major updates are disabled Note that only sites already running a development version will receive development updates. For development sites, the default value of WP_AUTO_UPDATE_CORE is true. For other sites sites, the default value of WP_AUTO_UPDATE_CORE is minor. Configuration via Filters Using filters allows for fine-tuned control of automatic updates. The best place to put these filters is in a must-use plugin. Do not add add_filter() calls directly in wp-config.php. WordPress isn't fully loaded and can cause conflicts with other applications such as WP-CLI. Disabling All Updates Via Filter You can also disable all automatic updates using the following filter: [code language="php"]add_filter( 'automatic_updater_disabled', '__return_true' );[/code] Core Updates via Filter To enable all core-type updates only, use the following filter: [code language="php"]add_filter( 'auto_update_core', '__return_true' );[/code] But let's say rather than enabling or disabling all three types of core updates, you want to selectively enable or disable them. That's where the allow_dev_auto_core_updates, allow_minor_auto_core_updates, and allow_major_auto_core_updates filters come in. There are two shorthand functions built into WordPress that will allow you to enable or disable specific types of core updates with single lines of code. They are __return_true and __return_false. Here are some example filters: To specifically enable them individually (for disabling, use false instead of true): [code language="php"] add_filter( 'allow_dev_auto_core_updates', '__return_true' ); // Enable development updates add_filter( 'allow_minor_auto_core_updates', '__return_true' ); // Enable minor updates add_filter( 'allow_major_auto_core_updates', '__return_true' ); // Enable major updates [/code] For Developers: To enable automatic updates even if a VCS folder (.git, .hg, .svn etc) was found in the WordPress directory or any of its parent directories: [code language="php"]add_filter( 'automatic_updates_is_vcs_checkout', '__return_false', 1 ); [/code] Plugin & Theme Updates via Filter By default, automatic background updates only happen for plugins and themes in special cases, as determined by the WordPress.org API response, which is controlled by the WordPress security team for patching critical vulnerabilities. To enable or disable updates in all cases, you can leverage the auto_update_$type filter, where $type would be replaced with "plugin" or "theme". Automatic updates for All plugins: [code language="php"] add_filter( 'auto_update_plugin', '__return_true' ); [/code] Automatic updates for All themes: [code language="php"] add_filter( 'auto_update_theme', '__return_true' ); [/code] You can use __return_false instead of __return_true to specifically disable all plugin & theme updates, even forced security pushes from the WordPress security team. The auto_update_$type filters also allow for more fine-grained control, as the specific item to updated is also passed into the filter. If you wanted to enable auto-updates for specific plugins only, then you could use code like this: [code language="php"] function auto_update_specific_plugins ( $update, $item ) { // Array of plugin slugs to always auto-update $plugins = array ( 'akismet', 'buddypress', ); if ( in_array( $item->slug, $plugins ) ) { return true; // Always update plugins in this array } else { return $update; // Else, use the normal API response to decide whether to update or not } } add_filter( 'auto_update_plugin', 'auto_update_specific_plugins', 10, 2 ); [/code] Translation Updates via Filter Automatic translation file updates are already enabled by default, the same as minor core updates. To disable translation file updates, use the following: [code language="php"]add_filter( 'auto_update_translation', '__return_false' );[/code] Disable Emails via Filter [code language="php"] // Disable update emails add_filter( 'auto_core_update_send_email', '__return_false' ); [/code] This filter can also be used to manipulate update emails according to email $type (success, fail, critical), update type object $core_update, or $result: [code language="php"] /* @param bool $send Whether to send the email. Default true. * @param string $type The type of email to send. * Can be one of 'success', 'fail', 'critical'. * @param object $core_update The update offer that was attempted. * @param mixed $result The result for the core update. Can be WP_Error. */ apply_filters( 'auto_core_update_send_email', true, $type, $core_update, $result ); [/code] Resources More examples at http://make.wordpress.org/core/2013/10/25/the-definitive-guide-to-disabling-auto-updates-in-wordpress-3-7/ More information here: http://wordpress.stackexchange.com/questions/120081/how-do-i-configure-automatic-updates-in-wordpress-3-7 Info about wp-cli conflict: https://github.com/wp-cli/wp-cli/issues/1310 Installing WordPress in Your Language atachibana — Sun, 10 Jul 2016 13:04:15 +0000 Note: this article is about displaying the WordPress Administrative "back-end" in your language. If you are looking for information on how to localize your "front-end" website, or customize your theme to be localizable, refer to i18n for WordPress Developers (and optionally Internationalization and Localization for theme developers. If you are interested in how to build a multilingual (e.g.: French / English) WordPress site, you can start your journey here. Although WordPress displays in U.S. English by default, it has the built-in capability to be used in any language. The WordPress community has already translated WordPress into many languages, and there are Themes, translation files, and support available in many other languages (see WordPress in Your Language). Installing Language Files from the Admin Dashboard As of version 4.0, you can have WordPress automatically install the language of your choice during the installation process. For WordPress 4.1 or later, you can install language packs directly from the Admin back-end at any time. WordPress will download them and switch the admin back-end to that language. Navigate to Settings > General > Site Language and select from the list of available languages. For Multisite Super Admins, you can set the default language using the Network Administration Settings pane. Manually Installing Language Files Here are the steps you will need to follow to install an international version of WordPress. Note: If you make an error in the steps or you do not specify the correct language, WordPress will default back to English. For more help Installing WordPress, see Installing WordPress and FAQ Installation. Download the .mo language file for your language. The naming convention of the .mo files is based on the ISO-639 language code (e.g. pt for Portuguese) followed by the ISO-3166 country code (e.g. _PT for Portugal or _BR for Brazil). So, the Brazilian Portuguese file would be called pt_BR.mo, and a non-specific Portuges file would be called pt.mo. Complete lists of codes can be found at (country codes) and (language codes). On your site server, create a new folder in your /wp-content directory called /languages. Upload the .mo file to the languages folder you just created. Use a plugin to install Language Files You can use the plugin wp-native-dashboard to automatically download language files stored in the wordpress svn repository. However, as of the time of this writing, the plugin is 2 years out of date and only supports a very small selection of languages. Setting the language for your site Single-Site Installations WordPress v4.0 and above Change the language in the admin settings screen. Settings > General > Site Language. WordPress v3.9.2 and below Open your wp-config.php file in a text editor and search for: [code language="php"]define ('WPLANG', '');[/code] Edit this line according to the .mo file you've just downloaded, e.g. for the Portuguese spoken in Brazil you must add: [code language="php"]define ('WPLANG', 'pt_BR');[/code] Note that if the .mo and .po files don't exist for a language code called for in wp-config.php then there is no error message, but the code is still used in language_attributes(). This is useful for those of us whose language is similar enough to en_US not to require translation, but who don't want en-US as the language tag in the blog, instead wanting some other variant of English. For example: [code language="php"]define ('WPLANG', 'en_GB');[/code] Once you've added your language code, save the file. Upload the modified wp-config.php file into the WordPress root directory. Open your browser and go to your WordPress site. It should now display in the newly-installed language. Multi-Site Installations If you have a site network (WordPress multisite), the language is set on a per-blog basis through the "Site language" option in the Settings > General subpanel. You can set the default language for the entire network under the Network Admin > Settings screen ("Default Language"). Adding Translation If you want to add translations for terms that are still displaying in English after installation, visit translate.wordpress.org and select your language. To get started, refer this page in the Translator's Handbook. Using Smilies atachibana — Sun, 10 Jul 2016 14:31:40 +0000 What Are Smileys? Smileys, also known as "emoticons", are glyphs used to convey emotions in your writing. They are a great way to brighten up posts. :smile: Text smileys are created by typing two or more punctuation marks. Some examples are: ;-) is equivalent to :wink: :-) is equivalent to :smile: :-( is equivalent to :sad: :-? is equivalent to :???: To learn more about emoticons and their history, see the Wikipedia entry on Emoticons. Smileys are not Emoji Although smileys and emoji can both display smiley faces and such, emoji are a newer development and have a much wider range of images that can be displayed. (They are also created differently.) For more information on emoji and how to use them, see the Emoji page. How Does WordPress Handle Smileys? By default, WordPress automatically converts text smileys to graphic images. When you type ;-) in your post you see :wink: when you preview or publish your post. To Turn off Graphic Smileys As of WordPress 4.3, the option to disable graphic smileys was removed from new installs. There is a plugin if you want to retain the option. What Text Do I Type to Make Smileys? Smiley images and the text used to produce them*: icon text text full text icon full text :smile: :) :-) :smile: :lol: :lol: :grin: :D :-D :grin: :oops: :oops: :sad: :( :-( :sad: :cry: :cry: :eek: :o :-o :eek: :evil: :evil: :shock: 8O 8-O :shock: :twisted: :twisted: :???: :? :-? :???: :roll: :roll: :cool: 8) 8-) :cool: :!: :!: :mad: :x :-x :mad: :?: :?: :razz: :P :-P :razz: :idea: :idea: :neutral: :| :-| :neutral: :arrow: :arrow: :wink: ;) ;-) :wink: :mrgreen: :mrgreen: * In some instances, multiple text options are available to display the same smiley. Category:Getting Started Troubleshooting Smileys Why Doesn't it Work? Smileys may have been disabled by your Wordpress admin. Another possibility is the smiley image files have been deleted from /wp-includes/images/smilies. Why Doesn't it Work for Me? If smileys work for others at your site but not for you: Type a space before and after your smiley text. That prevents the smiley being accidentally included in the text around it. :oops: Make sure not to use quotes or other punctuation marks before and after the smiley text. :roll: Where Are My Smiley Images Kept? The smiley or emoticon image graphics are found in the /wp-includes/images/smilies directory. Note that smileys is spelled 'eys' in this documentation and the directory name for the smiley images is 'smilies, spelled 'ies'. :shock: How Can I Have Different Smiley Images Appear? The easiest way is to filter the smilies. Upload the images you want with the same name to your server (say in wp-content/images/smilies) and put this in your theme's function.php: [code language="php"] add_filter( 'smilies_src', 'my_custom_smilies_src', 10, 3 ); function my_custom_smilies_src( $img_src, $img, $siteurl ) { return $siteurl.'/wp-content/images/smilies/'.$img; } [/code] That will replace http://example.com/wp-includes/images/smilies/icon_question.gif with http://example.com/wp-content/images/smilies/icon_question.gif Why are my Smiley Images Blank? If you recently uploaded the images, it could be that the images have been uploaded in ASCII format by your FTP program. Re-upload the smileys ensuring that they are transferred in BINARY format. Some FTP programs have an auto-detect setting which will upload files in the correct format without user intervention. If you have such a setting, turn it on. Smiley CSS The smiley images in WordPress are automatically given a CSS class of wp-smiley when they are displayed in a post. You can use this class to style your smileys differently from other post images. For example, it's not uncommon to set up images in a post to appear on the left-hand side of the content with text flowing around the image. The CSS for that might look like this: [code language="php"] .post img { float: left; } [/code] This would typically affect all images in a post, including your smiley images. To override this so that smileys stay inline, you could add this to your CSS: [code language="php"] img.wp-smiley { float: none; } [/code] For more on CSS in WordPress, you might want to start here. More Information on Smileys Wikipedia - Emoticon Customizing Your Sidebar juhisaxena — Mon, 11 Jul 2016 06:49:20 +0000 The sidebar is a narrow side column that contains an assortment of information not presented elsewhere on the website. On most WordPress sites, the sidebar is placed on the right or left-hand side of the web page. (Normally it is a vertical column, but sometimes it is also horizontal.) In some cases, a site will feature two sidebars--one on each side of the main content where your posts are found. This tutorial examines some of the informational items and features generally found in the sidebar. After reading this article, you’ll feel more comfortable adding or changing the content of a sidebar. Nested Lists The default WordPress theme uses nested lists to present sidebar information. (Nested lists are a series of unordered lists of information, set inside of each other.) Here's a simple example: [code language="html"] Title of Section One Apple Orange Banana Title of Section Two Beef Chicken Fish Title of Section Three Carrot Celery [/code] Each of these nested list sections can feature a CSS ID or class to make them all look different or all the same, depending on how they are styled within the style sheet. You don't have to use nested lists for your sidebar. That is up to you. If you do decide to use nested lists (an example of which can be found in the WordPress core themes) you need to know how they work. To learn more about how to style your WordPress nested lists, check out the article on Styling Lists with CSS. Navigation The main purpose of the sidebar is to provide various navigation aids for the user. These navigation aids are designed to help users find specific information as they move around a given website. Common navigation items include categories, pages, archives, and even the most recent posts. Another tool you'll often see in the sidebar is a search form. In the standard WordPress installation, the sidebar primarily displays a list of pages or categories. This list of pages helps users easily navigate to other sections of the website. Common names for these website sections are: About, Contact, Register, and Site Map. The information displayed in the sidebar is controlled by the sidebar.php file in your theme's template folder. Here is some sample code using the wp_list_pages() template tag, which can be found in your sidebar.php file: [code language="php"] Pages '); ?> [/code] This sample code puts the title Pages in an H2 heading, and then puts the actual page titles in a list below the main title. This is just one example of its usage--there are many other options available for controlling the end result of the wp_list_pages() template tag. The wp_list_cats template tag can be used to list categories, which help users find the information they want by topic. Here is a sample usage of this template tag: [code language="php"] [/code] This lists the title categories within the menu list, and then creates a nested list underneath to list the WordPress categories you've added to your site. (If you have no posts in a category, it will not show up in the list by default. However, once you have added a post to a given category, that category will then start showing up in the list.) The original default WordPress theme included a set of navigation tags in its index.php template file. However, you can also use this same set in your sidebar, to emphasize the navigation from one post to another in chronological order: [code language="php"] [/code] This example puts the text for the links to the right and left parts of the screen. You can change this to something more suitable for your sidebar's look by changing the style sheet references, or by further customizing the next and previous post links. Post Lists Part of helping your visitors navigate your site is to point them towards specific posts and archives. Your most recent posts and archives can be displayed in a variety of ways in your sidebar. The default WordPress theme showcases the archives by month: [code language="php"] [/code] Using the wp_get_archives() template tag, you can customize this list in a variety of ways. Let's say you want to list the last fifteen posts you've written, by their title. Replace the type=monthly as follows: [code language="php"][/code] There are also plugins that can help you customize different ways of showcasing your post lists. They can be customized according to category, highest number of comments, most recent, most recently updated, and so forth. Meta Data Did you know you could put anything you want in your sidebar? Some people like to add the post meta data to the sidebar, because it has information about the post, and it also adds links to different categories, dates, and possibly even next and previous posts. All of these links help to increase the visitor's navigation choices. WordPress Lessons features an article on designing your Post Meta Data Section which will help you to customize this information in your sidebar. Part of that meta data might be a little paragraph about who you are and what the site is about. You can add that using standard HTML and CSS, and place it where you would like it to appear in the sidebar, such as: [code language="php"] Have a passion for racing cars? Join the club. This site is dedicated to the hobby and passion of car racing. [/code] Remember, it's your sidebar, and you can add or remove anything you want! Different Sidebars Anyone? Old way of adding sidebars By default, the call for the sidebar is: [code language="php"] [/code] In a previous version of the default WordPress theme, the single.php template file did not request a sidebar. If you viewed a single post, you would see that the post stretches across the space where the sidebar would have been. Click back to an archive, category, or the front page and the sidebar returns. This theme has removed the call for the sidebar. To have a sidebar be different on a different template page, instead of using the default template tag, you can use the PHP command INCLUDE. [code language="php"] [/code] Placed in the single.php or the category.php template file instead of the default tag, this different sidebar would appear on those web pages. You could then customize sidebar2.php to feature whatever information you would like, so that it is different than the default sidebar. If you would like to have a different sidebar on the single.php template file, and another different sidebar visible when viewing an archive or category, edit the archive.php or category.php template files and change the sidebar call to: [code language="php"] [/code] Actually, you can use whatever name you want. You can also set up The Loop to call different sidebars depending on what you are viewing. New way of adding sidebars You can register more than one sidebar. In wp-includes/widgets.php you can find the function-definition for register-sidebars(), which you may use in your custom function within your theme folder (functions.php). If you don't already have a widgets.php file, you can create an empty php file using that name: [code language="php"] [/code] In the example above, 'custom' refers to a sidebar file called sidebar-custom.php. Sidebars get indexed in the WordPress database. Your default sidebar (sidebar.php) gets indexed as 1. Every succeeding sidebar will have an index higher than 1. You will now see your sidebars listed in 'Appearance' -> 'Widgets'. You can drag and drop widgets onto sidebars. In your sidebar templates, you may now call the dynamically generated content (widgets) according to the the index of your sidebars: [code language="php"] ... regular html ... ... regular html ... [/code] Or, even easier, call your sidebar by name. If your sidebar is named 'foo', you can use: [code language="php"] [/code] You can integrate your sidebars in your template files (e.g. index.php, single.php, archives.php): [code language="php"] [/code] The above code generates the default sidebar. [code language="php"] [/code] This code should display your custom sidebar. Sidebar Accessories You can put anything you want in your sidebar. Want to have a random image or a bit of text that changes with every view of a page on your site? Want to add buttons or icons to indicate favorite sites or social media links? How about weather reports or the latest news? You can honestly add anything you want to your sidebar. Here are some examples of what's possible. Random Images and Text There are a variety of scripts and techniques for creating random images on your site--images that change with every page or with each refreshing of the browser screen. The key to having these things in your sidebar is making sure they fit within your sidebar. Vertical photographs and graphics tend to fit well with the long vertical column of the sidebar. (You can also feature horizontal images, as long as they don't exceed the width of the sidebar. If they do exceed the sidebar width, they can cause problems by overlapping, or pushing the rest of your content around, which can mess up the overall layout.) There are a lot of random things you can add to your sidebar, and you can find many of these at the WordPress Plugin Repository. Buttons and Icons People enjoy listing their links and accomplishments in their sidebar highlighted by buttons and icons. Instead of listing a text link that proves your site has valid XHTML or CSS, you can create a link using the icon "awarded" to sites which pass the test. You can even use graphics to create links to your RSS feeds. The default WordPress theme provides a text link to validate your site. It looks like this: [code language="html"] Valid XHTML [/code] To replace the link with a graphic link, like the "Valid XHTML" icon, copy the icon to your site and try the following example, changing the file name and folders to match your site: [code language="html"] [/code] Linking to graphics for Feeds is a little different from putting graphics in links. WordPress uses template tags to display and coordinate feeds within a WordPress site. Without a graphic, a link to a RSS 2.0 Feed looks like this: [code language="html"] RSS'); ?> [/code] The template tag bloginfo() has parameters for the different feeds, so you don't have to come up with the URL yourself--it's automatic. Now, let's replace the text with a graphic. It used to be standard that RSS feeds were identified by an orange box, but now RSS feeds can look like anything. However, they tend to have a common look, so that they are easily identifiable across different websites. They typically feature a horizontal box with two columns of color (one bright and one light) saying RSS|FEED or RSS|Valid. You can make it say whatever you want, as long as it points your visitors towards this feature. Feedforall's DYI Feed Graphic Designer allows you to easily design your own feed icon. The Feed Icons site provides graphical icons using the icon created by the Mozilla Foundation and later adopted by Microsoft. A graphical icon helps avoid some of the issues currently associated with the wide variety of text-based icons. To use a different icon, here is how it might look: [code language="html"] [/code] We've given you some examples of how to create graphic links, buttons, or icons in your sidebar. The rest is up to you. If you can't find a plugin that does what you want it to do in your sidebar, you can also write your own plugin and share that with the world to use in their sidebars. Customizing Sidebars By Page As users are requiring more and more control over their websites, developers are relying on WordPress sidebars to offer this additional control. Until recently, the hurdle of displaying different widgets on every page, while using a single sidebar, was a daunting task that few accomplished. Visit the WordPress Plugin Repository to browse plugins that allow users to customize the display of widgets on pages. Plugin Resources As mentioned previously, the best place to find up-to-date information about WordPress plugins is the WordPress Plugins Repository. Custom Headers juhisaxena — Mon, 11 Jul 2016 11:01:06 +0000 Custom Header is a theme feature introduced with Version 2.1. Custom header is an image that is chosen as the representative image in the theme top header section. See also Appearance Header Screen. Adding Theme Support Since Version 3.4, themes need to use add_theme_support() in the functions.php file to support custom headers, like so: [code language="php"]add_theme_support( 'custom-header' );[/code] Note that you can add default arguments using: [code language="php"] $defaults = array( 'default-image' => '', 'width' => 0, 'height' => 0, 'flex-height' => false, 'flex-width' => false, 'uploads' => true, 'random-default' => false, 'header-text' => true, 'default-text-color' => '', 'wp-head-callback' => '', 'admin-head-callback' => '', 'admin-preview-callback' => '', ); add_theme_support( 'custom-header', $defaults ); [/code] You must also register the header image before it can be used as a default in your theme. Example Set a custom header image Set a default header image 980px width and 60px height: [code language="php"] $args = array( 'width' => 980, 'height' => 60, 'default-image' => get_template_directory_uri() . '/images/header.jpg', ); add_theme_support( 'custom-header', $args ); [/code] Upload other custom header images Set a default header image and allow the site owner to upload other images: [code language="php"] $args = array( 'width' => 980, 'height' => 60, 'default-image' => get_template_directory_uri() . '/images/header.jpg', 'uploads' => true, ); add_theme_support( 'custom-header', $args ); [/code] Use flexible headers Set flexible headers: [code language="php"] $args = array( 'flex-width' => true, 'width' => 980, 'flex-height' => true, 'height' => 200, 'default-image' => get_template_directory_uri() . '/images/header.jpg', ); add_theme_support( 'custom-header', $args ); [/code] update your header.php file to: [code language="php"] " height="height; ?>" width="width; ?>" alt="" /> [/code] Backwards Compatibility To add backwards compatibility for older versions, use the following code: [code language="php"] global $wp_version; if ( version_compare( $wp_version, '3.4', '>=' ) ) : add_theme_support( 'custom-header' ); else : add_custom_image_header( $wp_head_callback, $admin_head_callback ); endif; [/code] Resources WordPress Theme Support Generator Related Theme Support: add_theme_support(), remove_theme_support(), current_theme_supports() Theme Features: sidebar, menus, post-formats, title-tag, custom-background, custom-header, custom-logo, post-thumbnails, automatic-feed-links, html5, editor-style, content_width Function: header_image Function: get_header_image Function: get_custom_header The WordPress Gallery atachibana — Mon, 11 Jul 2016 16:27:30 +0000 Overview Image galleries are a great way to share groups of pictures on your WordPress site. The Create Gallery feature of the WordPress media uploader allows you to add a simple image gallery to pages or posts on your site. This article introduces how to add an image gallery using the media library, and explains gallery shortcode which will be generated and embedded into the post or page. Adding image gallery using media library Here’s how to add an image gallery step-by-step, using the media uploader: Note: Before adding a gallery, you should be comfortable using the Add media feature and the media uploader to add images to your media library and place them into posts. Step 1 – Place your cursor A gallery can go anywhere on a page or post - by itself on a blank page, or above, below, or in the midst of text. Start by placing your cursor where you want the gallery to appear - if it's in between blocks of text, like in the photo example below, consider adding a return and placing your cursor on a new line so there's space above and below. Step 2 – Click the Add Media button Once you've placed your cursor where you want your image gallery to appear, click on the Add Media button (located left above the editing window) to launch the media uploader interface. In the resulting popup window, select the 'Create a Gallery' option from the list of actions on the left. Step 3 – Add and/or Select the Images You Want to Include You can add or select the images you want to include in your image gallery by choosing from either of the following options in the center of the media uploader window: Upload Files: Upload the images you want to use from your computer by dragging them into the upload area. You can add more than one image, and they will be automatically grouped together as an image gallery. Media Library: Select from previously uploaded images in the media library by clicking on the ones you wish to add to the gallery. You will see a checkbox next to your selections. Note: You can create an image gallery using any combination of new images and previously uploaded images simply by switching back and forth between the Upload Files and Media Library tabs. As you upload and/or select images, you will see your selection confirmed on the Insert Media screen by check boxes at the top corner of each thumbnail. Also, a row of thumbnails appears at the bottom of the window to help you keep track of all the images you’ve selected. When you are happy with your selection, click the Create a new gallery button. Step 4 – Edit Your Gallery On the Edit Gallery page, you can do the following things before inserting the gallery you have created into your page or post: Rearrange your images: Drag and Drop image thumbnails to rearrange the order of images in your gallery. Reverse Order: Reverses the order of the images in your gallery. Add image descriptions: Add descriptions to your images (optional) which appear as image captions below each thumbnail in the gallery. Remove images: Hover over a thumbnail and click on the "X" to remove any of the images you previously selected. Add more images: Click on the "Add to Gallery" link in the left hand sidebar and add or select the images you want to include in your image gallery by choosing from either "Upload Files" or "Media Library" tabs. Cancel Gallery: Click on the "Cancel Gallery" link from the actions on the left to exit the Edit Gallery page and cancel your image gallery. Before inserting your gallery, you also have several Gallery Settings available in a pane on the right to control the following: Links To: Controls whether the gallery thumbnails (on the published page/post) link to the image attachment page or directly to the source image file itself. Columns: Set the number of columns you would like to have in your gallery. 3 Columns is the default settings, which is ideal for most sites. Random Order: Enables your gallery to display your image thumbnails in a random order each time they are viewed on the site. Size: Changes each image size in gallery. Available options are Thumbnail, Media, Large and Full Size. Editing Existing Galleries Within the visual editor, the image gallery is displayed as a series of thumbnail images. When you click any area of the image gallery, icon buttons appear top of the area. At any time, you can edit the images or settings of your gallery by clicking on the Edit button. You can remove the image gallery at any time by clicking on the Remove button. Gallery shortcode Above steps generates Gallery shortcode with image ids and other options, and embedded into the Post or Page, like this: [[gallery ids="729,732,731,720"]] You can specify options direct to this shortcode. Usage There are several options that may be specified using this syntax: [[gallery option1="value1" option2="value2"]] Options The following basic options are supported: orderby Specifies how to sort the displayed thumbnails. The default is "menu_order." Options: menu_order - You can reorder the images in the Gallery tab of the Add Media pop-up. title - Order images in the Media Library, based on the image title. post_date - Sort images by date/time. rand - Order images randomly. ID order Specifies the sort order used to display thumbnails. ASC or DESC. For example, to sort by ID, use DESC: [[gallery order="DESC" orderby="ID"]] columns Specifies the number of columns. The gallery will include a break tag at the end of each row, and calculate the column width as appropriate. The default value is 3. If columns is set to 0, no row breaks will be included. For example, to display a 4 column gallery: [[gallery columns="4"]] id Specifies the post ID. The gallery will display images which are attached to that post. The default behavior, if no ID is specified, is to display images attached to the current post. For example, to display images attached to post 123: [[gallery id="123"]] size Specifies the image size to use for the thumbnail display. Valid values include "thumbnail," "medium," "large," "full" or any other additional image size that was registered with add_image_size(). The default value is "thumbnail." The size of the images for "thumbnail," "medium," and "large" can be configured in the WordPress admin panel under Settings > Media. For example, to display a gallery of medium sized images: [[gallery size="medium"]] Some advanced options include: itemtag The name of the XHTML tag used to enclose each item in the gallery. The default is "dl." icontag The name of the XHTML tag used to enclose each thumbnail icon in the gallery. The default is "dt." captiontag The name of the XHTML tag used to enclose each caption. The default is "dd." For example, to change the gallery markup to use div, span and p tags: [[gallery itemtag="div" icontag="span" captiontag="p"]] link Specify where you want the image to link. The default value links to the attachment's permalink. Options: file - Link directly to the image file. none - No link. [[gallery link="file"]] include Comma-separated attachment IDs that include only the images from these attachments. [[gallery include="23,39,45"]] exclude Comma-separated attachment IDs that exclude specific images from these attachments. Please note that include and exclude cannot be used together. [[gallery exclude="21,32,43"]] Resources & Gallery Plugins Gallery Plugins Before You Install juhisaxena — Mon, 11 Jul 2016 12:37:00 +0000 Before installing WordPress, you need to check that your web hosting provider fulfills the necessary software and conditions. Also, you must have access method to the server and some tools. Requirements on the server side PHP 7.2 or greater MySQL 5.6 or MariaDB 10 or greater For a list of detail requirements on your web host, refer the official requirement page. Requirements on local Login Account (user id and password) to the server via FTP or shell Text Editor FTP Your web browser of choice You will need to know how to use a text editor to edit the main configuration file. If you are a Windows user, Notepad will do. If you're an OS X user you can use TextEdit. Later, you will likely want to edit your Template Files (see Templates for some references). You can do this through the WordPress Administration Screens, but using a good text editor is highly recommended. For more information on this, see Editing Files. You will need to be able to use an FTP program to upload files and set file permissions (optional). You could choose FileZilla for this task. Now you are all set to go on to Installation. Comments in WordPress normalize — Mon, 11 Jul 2016 15:37:48 +0000 Comments allow your website's visitors to have a discussion with you and each other. When you activate comments on a Page or post, WordPress inserts several text boxes after your content where users can submit their comments. Once you approve a comment, it appears underneath your content. Whether you want to customize how your receive comments or tweak how your site displays comments, WordPress provides a thorough set of options to build a community from the visitors to your site. Anatomy of a Comment Depending on your site's settings, comments display slightly differently from site to site. The basic comment form includes: Comment Name Email Website Once a visitor submits his or her comment, WordPress follows your preferences and either holds the comment for your approval or posts it immediately. Discussion Settings Before you enable comments on posts or Pages, reviewing the options under Settings > Discussion can help make your life as a moderator easier. Settings > Discussion contains a list of options that change how WordPress processes comments. Experimenting with these settings can help you find a balance between restricting comments to reduce the amount of spam or less-relevant comments you receive and encouraging your users to actively participate on your site. Notification Attempt to notify any blogs linked to from the article: This option will enable your site to automatically notify the sites you linked to that you have linked to them. They can then choose to tell their users that another site linked to them through a trackback or pingback. Allow link notifications from other blogs (pingbacks and trackbacks.): This is similar to the previous option, only your position is reversed. Instead of allowing your site to notify other sites, you are allowing other sites to notify your site. If you enable this option, pingbacks and trackbacks are managed in a similar way to comments. Commenter Rules Allow people to post comments on new articles: This will turn comments on for all future articles. The easiest way to prevent comment spam is to not allow any comments. If you don’t need comments, you can disable them by default by unchecking this option. Comment author must fill out name and e-mail: This prevents people from leaving anonymous comments (however, people could still use a fake name and e-mail address). Users must be registered and logged in to comment: This option will only allow registered users of your site to post comments. Automatically close comments on articles older than _____ days: Closing comments on posts that are no longer active is a good way to limit spam comments. This option will allow your site to do this automatically. Comment Display Enable threaded (nested) comments _____ levels deep: Enabling threaded comments allows your users to reply to one another. A reply to a comment is shown "nested" underneath the original comments. You can limit how many levels (a reply to a reply) of replies your site will allow by changing the number of levels here as well. Break comments into Pages with _____top level comments per Page and the _____ Page displayed by default: This option changes how your comments are displayed. You can set how many comments you see per Page and if oldest or newest comments are displayed first. Comments should be displayed with the _____ comments at the top of each Page: Set if you want newer or older comments at the top of each Page. Comment Administration Email me whenever … Anyone posts a comment and/or A comment is held for moderation: If you don't check your site often, this feature can help you stay up to date on your comments. Comment must be manually approved: If you don’t check this option, comments can appear on your site without your permission. This will not only allow an influx of spam comments, but they will appear on your posts and pages immediately after being submitted. Check this box to maintain the maximum amount of control over your site's comments. Comment author must have a previously approved comment: This option will allow you to cut down on the number of comments you have to approve. Once you approve one comment by an author, their future comments will be automatically approved. Comment Spam Hold a comment in the queue if it contains _____ links: Spam comments are designed to get users to click on links in order to drive traffic to other sites. As a result, many spam comments contain multiple links. Setting this option to hold all comments that contain 2 or more links will help catch more spam. Comment Moderation and Comment Blacklist: You can experiment with these text boxes to catch spam that contains certain words or is posted from a particular IP address. Comments caught through blacklisting are not deleted, but instead moved to your spam folder. Avatars The settings under "Avatars" control the images your site displays next to comments. For an introduction to Gravatars, read the WordPress Lesson about How to Use Gravatars in WordPress. Comment Spam Because spam is pervasive on the Web, some of the comments you receive will most likely be spam. However, WordPress developers and administrators have already developed a number of successful strategies to help you prevent spam comments from appearing on your site. In addition to experimenting with different options in Settings > Discussion, you can install a WordPress Plugin like Akismet or make other changes to help you keep spam comments under control. Enabling Comments on Your Site Once you have decided on your discussion options, you are ready to enable comments. If you chose not to enable comments on all articles automatically, you can turn on comments for a specific post or Page in several ways. Turning on Comments for a Single Post or Page After navigating to the editing screen for the post or Page you wish to add comments to, find the “Discussion” box and check “Allow Comments.” (If you do not see the “Discussion” box on the edit Page, click “Screen Options” in the upper right corner of the browser window. Make sure the box next to “Discussion” is checked.) Save your changes by clicking “Publish”, “Save Draft” or “Update." Turning on Comments from the Posts or Pages Screen Navigate to the Posts or Pages screen. In the list of Pages or posts, find the one you want and hover your cursor over the title of the post. You will see several links appear underneath the title. Click "Quick Edit" and check “Allow Comments.” Click “Update” to turn comments on for that post. Turning on Comments for Multiple Posts or Pages From the Posts/Pages screen, check the boxes next to the posts or Pages on which you want to enable comments. Select "Edit" from the "Bulk Edit" Dropdown box and click Apply. Then, select "Allow" next in the Comments dropdown box and finish by clicking "update." Managing Incoming Comments Once you start receiving comments on your site, you can check the status of comments quickly by looking at the dashboard, the admin bar, or the left navigation menu. When you log in, the dashboard's "Activity" box will show you the status of your comments. Hover over a comment to see your moderation options. From "Activity - Comments" you can approve, reply, edit, mark as spam, or trash comments. Alternatively, you can look to see if there is a number next to the comment bubble in the admin bar or "Comments" in the left navigation. This number represents how many pending comments require your attention. Moderating Comments with the Comment Screen WordPress makes moderating your users' comments a simple process. The Comments Screen lays out the basic information about each comment and lets you decide what to do with it. The Comments screen is divided into three columns: Author, Comment and In Response To. Each of these columns provide you with a different category of information about a particular comment. Number Key Commenter Gravatar Commenter Name Commenter Website URL Commenter Email Address Commenter IP Address Time and Date Comment was submitted Comment Text Comment Moderation Options. You can approve, spam or trash a comment with one click. Reply, Quick Edit or Edit will open up a new screen for you to write a reply to the comment or edit the comment. Post Name Number of Comments on the Post, Link to View Post Bulk Edit Comments Like the posts and Pages screens, the Comments screen supplies a Bulk Action dropdown box. Select the comments you want to edit, and then select Unapprove, Approve, Mark as Spam, or Move to Trash from the dropdown and click "Apply." Supporting Resources Moderating Your Recent Comments from the Dashboard Comments are King (WordPress.tv talk by Matt Browne about fostering a community of commenters) Comment Moderation Comment Spam Spam FAQ Content Visibility normalize — Mon, 11 Jul 2016 15:43:00 +0000 Content visibility is about controlling who can see your blog content. WordPress allows you to control the visibility of your posts and Pages on an individual basis. By default, all posts and Pages are visible. There are several ways to set the visibility for your blog content. You can set it on a per post/Page basis for public, private, or Password Protected, or make the entire blog private and Password Protected through the use of WordPress Plugins. Setting Page and Post Visibility Visibility for posts and Pages is set from the Edit screen. The option is available under the "Publish" option normally found at the top-right of the Edit screen. The screenshot below shows the interface, with the relevant section highlighted in the red rectangle. The default state for post and Page visibility is Public. Public visibility means that the content will be visible to the outside world as soon as it is published. By clicking on the edit link next to Visibility: Public in the Publish options, you can choose from an expanded selection of visibility options. The options are: Public: The default, viewable to all. Password Protected: Clicking this radio button followed by "OK" causes a further text box to appear, into which you can enter a password. Private: This option hides the content from the public completely. Password Protected Content Password Protected content is not immediately visible to the outside world. Instead, visitors will see a prompt similar to this: The title for your protected entry is shown, along with a password prompt. A visitor to your site must enter the password in the box in order to see the content of the post or Page. Private Content Private content is published only for your eyes, or the eyes of only those with authorization permission levels to see private content. Normal users and visitors will not be aware of private content. It will not appear in the article lists. If a visitor were to guess the URL for your private post, they would still not be able to see your content. You will only see the private content when you are logged into your WordPress blog. Once you change the visibility to private, the post or page status changes to "Privately Published" as shown. Private posts are automatically published but not visible to anyone but those with the appropriate permission levels (Editor or Administrator). WARNING: If your site has multiple editors or administrators, they will be able to see your protected and private posts in the Edit screen. They do not need the password to be able to see your protected posts. They can see the private posts in the Edit Posts/Pages list, and are able to modify them, or even make them public. Consider these consequences before making such posts in such a multiple-user environment. Hiding The Entire WordPress Blog Currently the functionality to hide your entire blog from public view, or to restrict it to certain users, is not part of the core WordPress product. There are possible plans to introduce this functionality into a later version. There are various WordPress Plugins to restrict the visibility such as: Page Restrict Force Login jonradio Private Site Alternatively, you could use the .htaccess to restrict who can visit your web site, but this is beyond the scope of this document. Links Manager normalize — Mon, 11 Jul 2016 16:06:38 +0000 As of Version 3.5, the Links Manager and blogroll are hidden for new installs and any existing WordPress installs that do not have any links. If you are upgrading from a previous version of WordPress with any active links, the Links Manager will continue to function as normal. If you would like to restore the Links panel to your install you may download and install the Links Manager plugin. This page is still relevant for any user with an existing Links Manager or with the plugin installed. WordPress allows you to store a set of external links, also known as your blogroll. These links can be put into categories, imported, exported, added, deleted, and edited. The link categories can also be added, deleted, and edited. This article describes how to do all of the above, using the Links section of the WordPress Administration Panels. Managing Links When you click on "Links" in the navigation menu on the left of your dashboard screen, you will come first to the Manage Links SubPanel, where you will see a list of all of your links. Listing Links In the Manage Links SubPanel, your links are displayed in a tabular format. Each link is a row in the table, and the table has the following columns: Name The name of the link (in bold) and its description. URL The URL (location) of the link. Categories The categories that the link is in. Relationship The XFN relationship for this link. Visible Whether or not the link is visible to visitors on your site. Rating A ranking of the Link, which can be used to sort links within Categories. You can change the display in the following ways: Restrict to just one category Choose a category from the "View All Categories" drop-down and click Filter, and the list will be restricted to the category you chose. Change the sorting order You sort the link entries by Name or URL by clicking on the small black arrow in the header of the table. By default, the links are sorted by name. Adding Links When you click Links in the navigation menu, and then click Add Link, you will come to the Add Link SubPanel, where you can add a new link to your list. The screen looks similar to the image above, and has the following sections - Sample input is shown in parentheses.: Name The text that will be shown on your blog screen for the link (John Doe's Blog). Web Address The URI of the web page you're linking to, with the http:// (http://example.com/). Description If your theme includes it, this descriptive text will be put on the screen after the actual link. It will also be shown to the user as a tool-tip when they hover their mouse over the link. Categories Select the category for the link. Links can be put into multiple categories. Target : Specifies the target attribute that will be put onto the link's a tag when displayed on the screen, which tells where the page will appear if the user clicks on the link. There are three options: *none: open the link in the same window or frame (default). *_top: if you're using frames, open the link at the top level of the frame system. *_blank: open the link in a new window. Link Relationship (XFN) XFN (Xml Friends Network) is a way to define your relationship with the linked person. For example, if you work with Harriet Smith, and you link to her blog, you can check co-worker or colleague, symbolizing that she is one of those. Same with crushes, dates, and you can also say whether this is another one of your sites. XFN relationships are optional for WordPress links. You can leave everything in this section blank and all your links will still work. Defining Relationships with XFN makes the links defined on your weblog more understandable to machines that will process your pages. rel - Specifies the rel attribute that will be put onto the link's a tag when displayed on the screen. Some possible values are nofollow (if you don't want search engines to follow the link), author, and smart. Multiple rel keywords should be separated with spaces. Advanced The Advanced fields can add extra information to the link. Image Address - An image to be displayed with the link. This can either be an absolute URI (http://some.site/images/image.png) or a relative path (/images/some.png). You may want this to be rather small, around 16x16, similar to a favicon. RSS Address - URI of the RSS feed associated with the Link, which will be displayed next to the Link itself (if your Template allows it). Example: http://example.com/feed/ Notes - Any notes you want to store, for your own internal use, about the Link. Example: Nice design, from #wordpress. Rating - A ranking of the Link, which can be used to sort links within Categories. When you have set all the options you are interested in, click Add Link to add the new Link to your blogroll. You can hide a link (temporarily or permanently) by choosing "Keep this link private". Editing Links To edit a link, in case of an error or change in the link information, WordPress provides an Edit Link option. This is only viewable when hovering over an entry in the link's table row. Clicking on Edit brings you to the Edit a Link subpanel. This mode is essentially the same as the Add Link SubPanel. The only difference is that the button to save your work is called "Update Link" instead of "Add Link." Deleting a Link To delete a link, go to the Manage Links screen. From the table list of links, identify the link you wish to delete. Hover over this entry and click the Delete link for that link to delete it. Remember, you will not have a chance to recover from this delete. It makes a permanent change to the database. A popup window with a confirmation should appear. Choose OK or Cancel if you hit the Delete link by accident. Remember, this is the only chance you have. After making your choice, you will be directed back to the Manage Links page. To delete multiple links you can select the tick box of link entries that you want to delete on the Manage Links screen and then select Delete from the Bulk Actions drop down menu and then click on the Apply button. Link Categories Links in WordPress can be organized into categories, all the better for organization. The default installation of WordPress automatically sets one category, Blogroll. You are given the ability to add, edit and delete categories. Note: There must always be at least one (default) link category. If you want to delete the Blogroll category, first set another link category as the default in the Settings Writing Screen. Adding a Category To add a Link Category navigate to the Links Link Categories Screen using the side menu Enter the name and other details of your category. Click on the Add New Link Category button. A full description of how to add, edit and delete Link Categories is on the page on the Links Link Categories Screen Formatting Beginning with WordPress 2.0, you can alter how WordPress displays the list of links from this category by modifying the text found in the following three text boxes. However, these options are only used by some themes. The following template tags are used only with Link Manager: wp_list_bookmarks() Before Link This string of characters or HTML tags which will be inserted before every link in the list of links from this category. Example: Between Link and Description When a category is set to show the description with the link, this is what separates them. Example: After Link This string of characters or HTML tags which will be inserted after every link in the list of links from this category. Example: To actually add the category, just click Add Category or Save Category Settings to save the information you've entered. Removing the Link Manager If you upgraded from a version prior to 3.5, you may still have the link manager in the sidebar, even if it is not needed. To remove this, edit the "Link Manager Enabled" field from 1 (on) to 0 (off) in /wp-admin/options.php or through any database manager. Adding the Link Manager To re-enable the link manager, add the following line to your theme's functions.php file: add_filter( 'pre_option_link_manager_enabled', '__return_true' ); Working with WordPress atachibana — Mon, 11 Jul 2016 22:07:03 +0000 [codex_languages en="Working with WordPress" es_codex="Working with WordPress" it_codex="Lavorare con WordPress" mk_codex="Ракување со Wordpress" pt_codex="Trabalhar com o WordPress" th_codex="ทำงานกับเวิร์ดเพรส" zhcn_codex="使用 WordPress" zhtw_codex="使用 WordPress"] WordPress Features WordPress Features Migrating Plugins and Themes to the Latest Version Using Themes Using Pages Writing Posts Design and Layout WordPress Feeds Advanced WordPress Topics Understanding the WordPress Loop The Loop in Action FAQ About WordPress FAQ New To WordPress User and Author Features What Registered Users Can Do Roles and Capabilities (WP 2.0+) User Levels (WP 1.x) Writing Posts Using Image and File Attachments (WP 2.0+) Administration Features Understanding WordPress Administration Resetting Your Password Creating and Using Individual Pages Using Permalinks Custom Fields Discussion options Editing Files Blog by Email Using Plugins Managing Plugins Links Manager Backing Up Your Database Restoring Your Database From Backup FAQ Working with WordPress Moving WordPress Site Development WordPress Site Reviews WordPress Theme List Working With Templates Working With Theme Templates Editing Files in WordPress Creating an Archive Index Stepping Into Template Tags Template Hierarchy Understanding the WordPress Loop Customizing the WordPress Loop Meta Tags in WordPress Accessibility Linking to Posts, Pages, and Categories Validating a Website WordPress Housekeeping WordPress Site Maintenance Advanced Techniques Search Engine Optimization for Wordpress FAQ Themes, Layout and Design FAQ Using WordPress FAQ Advanced Topics Using an FTP client WordPress Media Podcasting with WordPress Using Images Photoblogs and Galleries Fighting Comment Spam Introduction to Dealing with Comment Spam Moderating Comments Combating Comment Spam Common Spam Words Denying Access to Comment Spammers with .htaccess International Features WordPress in Languages Other than English Translate WordPress to Your Language More Articles and Information Glossary Technical Articles FAQ - Frequently Asked Questions Users Your Profile Screen atachibana — Tue, 12 Jul 2016 14:05:02 +0000 Users → Your Profile The Users Your Profile Screen is accessible from both the main navigation menu under Users and by clicking on your name link at the top of the WordPress screen. Here you can specify your name and how it will be displayed on your site, your e-mail address (for administrative purposes), other personal information, and personal options. Back to Administration Screens. Your Profile and Personal Options The only pieces of information WordPress requires you to include in your Profile are your e-mail address and a nickname. It should be noted that WordPress requires your email address only for your blog's administration purposes. The email address is never sent to any other site (not even to the people at WordPress headquarters), and it is never displayed on your site (unless you put it there manually). Only the other registered users of your blog have access to the e-mail address you provide. Also, remember that each user's email address must be unique. Note: it is possible for a theme to display your e-mail address (and the e-mail addresses of your other registered users) on your site, since the the_author_meta('user_email') template tag can be used for such purposes. This would be a poorly conceived theme, however, if it didn't inform you of that before you downloaded it. None of the themes included with WordPress display any e-mail address anywhere on the public side of your site by default. All of the other personal information asked for here is optional, and, again, it is never sent to any other site or person. It may be displayed on your site, however, depending on the theme you use, so you should test things out with your particular theme if you're at all paranoid (and a bit of paranoia regarding your personal information is healthy). See the_author and related template tags for information on how to display this information on your site (and, consequently, how to ensure the theme you use does/does not display any of this information). Typically, themes only display the information you enter in the Display name publicly as field, however the Authors username is also often included in the URL (for Author Archives) and in the CSS classes for per-author targeted stylings. Personal Options : Visual Editor - Checking this box Disables the visual editor when writing, and uses the plain HTML editor. Syntax Highlighting - Checking this box Disable syntax highlighting when editing code. Admin Color Scheme - Check this radio button next to the color scheme desired for the Administration Screens. The left two colors are menu background colors and the right two are roll-over colors. Keyboard Shortcuts - Checking this box Enables keyboard shortcuts for comment moderation. Keyboard shortcuts are designed to allow you to rapidly navigate and perform actions on comments. The Keyboard Shortcuts article describes the various shortcuts in detail. Toolbar - Check the box to display the Toolbar when you are viewing your site. Language - You can select the language you wish to use while using the Administration Screen without affecting the language site visitors see. Name : Username - You cannot edit your Username because it is used as your Username during the login process. Even an Administrator cannot change your Username. Usually, no one else ever needs to see your Username. First name - Enter your first name in this text box. Last name - Enter your last name in this text box. Nickname - Enter the nickname as it is a required for every user. It may be the same as your User Name or it can be different. If you don’t supply a Nickname, then the User Name will be placed in this field. Display name publicly as - Select, from the drop-down, how your name is cited on your blog. This defaults to your first and last name. You can choose from several of the above pieces of information: Nickname, Login name, First Name, Last Name, "First Last", or "Last First". If you prefer "Last, First", insert a comma after your last name in the Last Name text box above and choose the last option from this dropdown. Contact Info : E-mail - All users are required to list an e-mail address in their respective Profiles. The E-mail address must be unique for each user. Your blog will use this address to notify you of new comments to your posts and for other administrative purposes. To reiterate what was said above, only other registered users of your blog will have access to this e-mail address. It is never sent anywhere. Website - Enter your website address. About Yourself : Biographical Info - Enter a short description or profile of yourself here. This optional information can be displayed by your theme if so configured by the theme author. See the_author_meta('description') template tag. Profile Picture - Your picture in Gravatar is shown here. To change it, access to the https://en.gravatar.com/. See also Using Gravatars. Account Management : Generate Password - You can click this button to generate a new password for the account. This will show you a new field with the generated password. If you choose to change this password, a checkbox will appear to confirm that you want to use a weak password. You can check this box to confirm that you want to use your own password instead of a secure one. Strength Indicator This indicates if the password you entered is Very Weak, Weak, Medium, or Strong (displayed in green). The stronger the password the more secure your login. Hint: The password should be at least seven characters long. To make it stronger, use upper and lower case letters, numbers and symbols like !"?$%^&). Log Out Everywhere Else - You can click this button to log out of other devices, such as your phone or a public computer. Update Profile Remember to click this button to save the changes you have made to your Profile and Personal Options. After clicking this button you should see a splash message at the top of the screen saying User Updated. If you don't see that message, then your changes are not saved! Integrating WordPress with Your Website juhisaxena — Tue, 12 Jul 2016 05:18:57 +0000 Introduction By nature, WordPress is very powerful. It can be as complex or as simple as you wish. With that in mind, how much you want to use WordPress with your existing website is totally up to you. There may be only a few features of WordPress you want to use when integrating it with your site, or you may want your entire site run with WordPress. This tutorial will guide you through making your WordPress site look like your current design. We will start with how to make a WordPress blog look like the rest of your site. Then we can move on to making your entire site running on WordPress. These directions will not work on a MultiSite Network. Begin the transformation First, assume you have an existing site at http://myexample.com. Next, create a new sub-directory (folder) at your site and call it 'blog' (you could use something other than blog, but you must create this sub-directory). So you now have an empty sub-directory at http://myexample.com/blog/. Now, download WordPress and upload all of its files into this new folder, and install WordPress. Grab the header In order to transform regular PHP pages into ones that utilize WordPress, you need to add either of the following code snippets to the start of each page. [code language="php"] [/code] [code language="php"] [/code] The Loop It is necessary to include The Loop in your pages to effectively take advantage of the multitude of Template Tags or plugins available. Familiarize yourself with The Loop and the basics of The Loop in Action to get underway with integrating the power of WordPress into your website. Examples Generate a list In the event you want to show ten posts sorted alphabetically in ascending order on your web page, you could do the following to grab the posted date, title and excerpt: [code language="php"] "; ?> [/code] Last three posts Display titles of the last three posts on your web page. [code language="php"] 3 ); $myposts = get_posts( $args ); foreach( $myposts as $post ) : setup_postdata($post); ?> [/code] Making a theme The first portion of this tutorial described how to take components of WordPress and integrate them into your existing site. You may wish to stop right now, but perhaps you would like to create a WordPress theme that would eventually replace web pages on your site. You will need to create a custom theme. A theme is a set of files used to tell WordPress how to display the site and Using_Themes is fundamental to WordPress. You may create your own theme from scratch, but you should consider to create the Child Theme of existing theme as the first step. The child theme can enhance or customize the limited portions of existing theme. Refer Child Theme for more detail. A little known, but very helpful HTML element, is going to help you out a lot. It instructs the browser to use a specified URL for relative paths: [code language="php"] [/code] Normally, the would be your current URL. For example, the default at your blog will be http://myexample.com/blog/. By changing it with the element, you tell the browser to look for files at http://myexample.com/. Why is this useful? When copying and pasting HTML from your current site, you will have references to something like: [code language="php"] [/code] When you copy this HTML to your theme, the browser will be looking for http://myexample.com/blogs/me.jpg, when the file actually exists at http://myexample.com/me.jpg. Using , the browser is told the right place to find the files and you do not have to edit every reference to every file that you copied from your main site. Performance Although WordPress is fast, it does contain a substantial quantity of code that needs to be loaded each time a page is displayed. This may or may not affect performance depending on the hosting environment, but on a shared hoasting environment using SuPhp (and thus without op code caching) it can add several seconds to each page load. External links WP Integration plugin - helps you to integrate WP with any of the supported web apps Moshu Blog - Integrating WP in an existing site wp-hackers email list discussion on "deprecating" direct calls to wp-config.php Fixing false 404 headers on external pages including wp-blog-header.php Post Status juhisaxena — Tue, 12 Jul 2016 09:53:03 +0000 Posts in WordPress can have one of a number of statuses. The status of a given post determines how WordPress handles that post. For instance, public posts viewable by everyone are assigned the publish status, while drafts are assigned the draft status. The status is stored in the post_status field in the wp_posts table. WordPress provides 8 built-in statuses you can use. WordPress 3.0 gave you the capability to add your own custom post status and to use it in different ways. Workflow WordPress provides built-in features that empower some users (based on their Roles and Capabilities) to review content submitted to the website before it is published. This is commonly called "workflow." WordPress's workflow features rely on the value of a post's post_status field to know which step in the workflow process the post is currently held in. Most users are already familiar with at least two workflow states: Posts that are published and visible to everyone (including users who are logged out) are given the publish status. Drafts that are not yet published are assigned the draft status. Internally, WordPress sets the post status to publish when you click the "Publish" button, and WordPress sets the post status to draft when you click the "Save Draft" button. Similarly, if your website has users granted the edit_posts capability but not the publish_posts capability, then when those users start writing a new post, WordPress will display a "Submit for Review" button instead of a "Publish" button. Likewise, WordPress then assigns the post that user created the pending status when they press that button. The status of a post can also be set in the Administration Screen and Add New Posts Screen by any user with the capability needed to assign the post to the given status. Internally, all of these posts are stored in the same place (the wp_posts table), and are differentiated by a column called post_status. Default Statuses There are 8 major post statuses that WordPress uses by default. Publish Viewable by everyone. (publish) Future Scheduled to be published in a future date. (future) Draft Incomplete post viewable by anyone with proper user role. (draft) Pending Awaiting a user with the publish_posts capability (typically a user assigned the Editor role) to publish. (pending) Private Viewable only to WordPress users at Administrator level. (private) Trash Posts in the Trash are assigned the trash status. (trash) Auto-Draft Revisions that WordPress saves automatically while you are editing. (auto-draft) Inherit Used with a child post (such as Attachments and Revisions) to determine the actual status from the parent post. (inherit) Custom Status NOTICE: This function does NOT add the registered post status to the Administration Screen. This functionality is pending future development. Please refer to Trac Ticket #12706. Consider the action hook post_submitbox_misc_actions for adding this parameter. A Custom Status is a Post Status you define. Adding a custom status to WordPress is done via the register_post_status() function. This function allows you to define the post status and how it operates within WordPress. Here's a basic example of adding a custom post status called "Unread": [code language="php"] function custom_post_status(){ register_post_status( 'unread', array( 'label' => _x( 'Unread', 'post' ), 'public' => true, 'exclude_from_search' => false, 'show_in_admin_all_list' => true, 'show_in_admin_status_list' => true, 'label_count' => _n_noop( 'Unread (%s)', 'Unread (%s)' ), ) ); } add_action( 'init', 'custom_post_status' ); [/code] Resources WordPress Post Status Generator Related Roles and Capabilities Code Documentation Function: get_post_status() - Retrieve the post status based on the Post ID. Wrapping Text Around Images atachibana — Thu, 14 Jul 2016 11:11:53 +0000 [codex_languages en="Wrapping Text Around Images" ko_codex="Wrapping Text Around Images"] Current versions of WordPress now have image alignment built-in. WordPress adds CSS classes to align the image to the right, left, and center of a paragraph, so the text will wrap around the image. Important Theme Code In order to take advantage of these new CSS classes for image alignment and the text wrapping around the image, the WordPress Theme must include the following in the style.css found in the WordPress Theme directory. [code language="php"]img.alignright { float: right; margin: 0 0 1em 1em; } img.alignleft { float: left; margin: 0 1em 1em 0; } img.aligncenter { display: block; margin-left: auto; margin-right: auto; } .alignright { float: right; } .alignleft { float: left; } .aligncenter { display: block; margin-left: auto; margin-right: auto; }[/code] When adding the image in your WordPress blog, select the image alignment as right, left, or center in the Image/Media Panel. The image will be embedded into your blog post with the selected style for alignment such as: [code language="php"] <img src="http://example.com/images/leaf.jpg" alt="leaf graphic" title="leaf graphic" class="alignright size-medium wp-image-3109" height="25" width="30"/> [/code] Image Style There are times when you want an image on your post to fill the screen, or sit in the middle of text with writing above and below it, but most of the time you want your image to sit on one side or the other of the text and have the text flow or wrap around the image. While the styles above will float the image left and right, you may want to add more design elements to your image. Let's start from the beginning with a simple guide to using images in your WordPress blog. First, here is a look at a typical image tag in your post, without the instructions for wrapping the text around the image. Note that we've added both the title and alt attributes to the tag; alt is important for accessibility, title is for the image tooltip. [code language="php"] <img src="http://example.com/images/leaf.jpg" alt="leaf graphic" title="leaf graphic" /> [/code] To begin the process of setting your image up to be wrapped, there are a few changes that you may need to make to the style sheet that controls your WordPress site. CSS offers a great list of resources for creating and editing Cascading Style Sheets. From your WordPress Theme folder, open the style.css file in a text-editor. Important! Save a back up copy somewhere before you do any edits! Now, do a search for img. Hopefully, all your image selectors will be grouped together. If not, find them all and cut and paste them into one group to make this process easier. Borders You'll need to decide if you want a border around your images and, if you do, what size, color, and type it should be. For no border, you would use the following: [code language="php"] img {border:0} [/code] For 1 pixel solid red line border, add: [code language="php"] img {border:solid red 1px} [/code] If you create a link around an image, some browsers will put a border around the image to let the visitor know it's a link. If you don't want that, use the following: [code language="php"] a img {border:0} [/code] You can still add a hover around the image so when the visitor moves their mouse over the image, not only will the mouse pointer turn into a hand, the image will get a colorful border: [code language="php"] a:hover img { border:solid red 1px; } [/code] Padding and Image Width Let's clean up one more thing to make the image in your content work better with the rest of the styles we will use. We want to clear all the padding around the images within your content and make sure that the whole width of the image shows up rather than just a part of it. If it isn't in your style sheet, add the following: [code language="php"] p img { padding: 0; max-width: 100%; } [/code] Image Left, Right, and Center When an image sits on the sides of your text, it helps to have space between the text and the image so the words aren't right up against the edge. As some browsers treat the margins and padding differently, the following styles will accommodate most browser's "space requirements" so the image doesn't overlap the text or any lists that appear inline with the image. [code language="php"]img.alignright { padding: 4px; margin: 0 0 2px 7px; display: inline; } img.alignleft { padding: 4px; margin: 0 7px 2px 0; display: inline; }[/code] The declaration of display:inline keeps the image inline with the text that you placed it with. Now, it is time to add the float declaration to the images. BUT WAIT. Why should we waste our left and right floats on just images? Why not use them on anything that we want to sit on the right or left of the page and have the text float around it? You can do that, you know. But that's for another tutorial. We're not going to waste this, so if it isn't there in your style sheet already, add the following: [code language="php"].alignright { float: right; } .alignleft { float: left; }[/code] Note: The Default/Kubrick Theme uses this technique but names the classes alignleft and alignright. Using alignleft and alignright seems easier to remember and use, but either name sets may be used to make this work. So what about centering the image? Yes, you can still do that too. The center tag isn't valid any more, so you can create a style for centering things: [code language="php"] img.aligncenter { display: block; margin-left: auto; margin-right: auto; } [/code] Left, Right, and Centered Examples This sounds like a lot of complicated stuff, but once this is done, you will never have to mess with it again. We hope. To use it, create the link to your image and add class="alignright", class="alignleft", or class="aligncenter" and the image will move to the right, left, or center and the text will wrap around it. It's just that simple. This is some text that will wrap around the image that sits on the right side of the text that you are writing about the leaf that is there. That is, if you are writing about leaves in the first place and you want to write about this specific leaf. This is some text that will wrap around the image that sits on the right side of the text that you are writing about the leaf that is there. That is, if you are writing about leaves in the first place and you want to write about this specific leaf. This is text that sits above the leaf image that you might be writing about in your post if you were to write about leaves. This is some text that will sit below the text image and you can continue to write about the leaf that is there. This is text that sits above the leaf image that you might be writing about in your post if you were to write about leaves. This is some text that will sit below the text image and you can continue to write about the leaf that is there. Alternative Text Size Some browsers will now allow you to control the size of the text created by the ALT tag. This is the text that appears when you hold your mouse over an image or when the the image fails to load. You can set it to any size, but something much smaller than your content's font size would be a good idea. [code language="php"] img {font-size:60%} [/code] Captioning The Image Images tend to just sit there, looking pretty. The alt and title properties say a little something about what the image looks like, but other than that, unless you add some text around it, it just sits there. So create a caption style that adds some "spice." .wp-caption { margin: 5px; padding: 5px; border: solid 1px #E5E5FF; background: #E5F2FF; font-size:90%; color: black } In the above example, we've added a border and a little hint of background color, but you can style it however you want. We recommend that you at least make the text a difference size and padding to the overall container so it is distinguished from the rest of the post's content. http://example.com/images/leaf.jpg" alt="leaf graphic" title="leaf graphic"> Red Leaf [caption id="attachment_433" align="alignright" width="37"] Red Leaf[/caption] This is text that wraps around the leaf image that features a caption. You might want a caption under the picture of the leaf if you were writing about leaves in your post. The caption sits below the text and helps the user to understand what the picture is about. In the example above, we just added the alignright class to the container which will position it as a float to the right, allowing the text to flow around it. Using the alignleft class would float it to the left, and aligncenter would give you the text, image centered, text effect. Clear The Display In the event that the image is larger than the amount of text that would otherwise surround it, causing the image to hang like a flag over some element below it, then at some point in the text, you'll want to clear the display. Note that there is no text inside this division. However, if you use the WYSIWYG editor, it's necessary to put something inside the division (like a hard rule), otherwise the WYSIWYG editor will remove the div entirely (due to an idosyncracy/bug in TinyMCE editor that the WYSIWYG editor uses). To clear the display in a way that works for both the "Text" and "Visual" editors, add this while in the text tab: Resources Using Images WordPress Theme CSS FAQ Installation atachibana — Thu, 14 Jul 2016 15:27:27 +0000 Installation How do I install WordPress? Under most circumstances, installing WordPress is a very simple process and takes less than five minutes to complete. Many web hosts offer tools to automatically install WordPress for you. If you prefer a manual installation you can take a look at the Installation Guide. How do I find a good host for my WordPress website? Any host that supports the requirements for WordPress can be used for hosting your website. If you're not sure if your host can run WordPress the best thing to do would be to contact them and ask if they meet the requirements for running WordPress. How do I install using cPanel / cPanel X? If you want to perform a manual installation using cPanel you can follow the guide on using cPanel. How do I configure the wp-config.php file? The wp-config.php file is one of the most important files of your website. It's located in the root of your WordPress installation and contains most of the website's coniguration details. Editing this file can be done in any plain-text editor. Usually this isn't necessary unless you're installing WordPress manually. See also: Editing wp-config.php What are the requirements for installing WordPress? The current requirements for running WordPress can be found on the requirements page at WordPress.org. How do I get WordPress to use my language? If you want to change the language that WordPress is using, you can select your preferred language in the Administration Screen. To do this you can go the Settings > General, and choose your preferred language from Site Language dropdown menu. Do I need to create a database? Yes. WordPress requires access to a MySQL or MariaDB database to store information. So you'll need a database. You should create a new database if: You have not already created one on the server Your generous host offers you more than one database, and you wish to have a separate database for the website you are setting up. It is not essential to create a new database for each WordPress installation. If you are using the same database for multiple WordPress installations, take care to edit the wp-config.php file ensuring that each installation has a unique database prefix. If you are setting up a new database for a new website, edit wp-config.php, and be sure to get the database name, and other details correct. See also: Installation, Detailed Instructions Why is my website showing a 403 Error? If the following (or similar) message appears after uploading your website a couple of things can be happening: You are not authorized to view this page You might not have permission to view this directory or page using the credentials you supplied. If you believe you should be able to view this directory or page, please try to contact the Web site by using any e-mail address or phone number that may be listed on the personal.fredsmith.com home page. You can click Search to look for information on the Internet. HTTP Error 403 - Forbidden'' If your account is hosted on a Apache based server the following things can be happening: server permissions aren't allowing the request from being executed your index.php isn't configured to be an allowed directory index the underlying filesystem isn't allowing Apache access to the files requested If you have checked all these settings and everything seems to be set up correctly you'd best contact your hosting provider for support. Can I rename the WordPress folder? If you have not already installed WordPress, you can rename the folder with the WordPress files, before, or even after uploading the files. If you have WordPress installed already, and you want to rename the folder, login to your website as an administrator and change the following settings in Settings > General: WordPress Address (URL): Site Address (URL): Once you have done this, you can rename the directory or folder with the WordPress files in it. See also: Moving WordPress Why is my upload directory “C:apachehtdocswordpress”? When you specified the upload path, you used backslashes. Use forward slashes “/” to specify the path to the directory. Can I install WordPress on Windows Server? Yes you can! As long as you have PHP installed you shouldn't have any trouble getting started with WordPress. Both Apache and Microsoft IIS are capable of serving your WordPress website. Advanced Installation How do I install WordPress with the files in different directories? This also answers the questions: How can I have my blog in one folder but my index at root? How can I have people see my blog at www.example.com but keep all the files in www.example.com/wordpress? How do I install WordPress in a different directory than where the index.php resides? See also: Giving WordPress Its Own Directory Moving WordPress How can I hide my blog from people? Whether you are testing a new version of WordPress, setting up a new blog or have some other reason to limit access, the following information may help you keep unwanted visitors out. Apache There is no guaranteed way to do this. You can use the .htaccess file (which also contains your permalink code) to check for certain IP addresses and prevent them from viewing your site. This will only stop the IP address, not the person, so if they have access to an allowed IP address, they can get to your page. One tutorial for this is located at Clockwatchers.com An .htaccess file can also be used to prevent others from "hot-linking" to your images (bandwidth theft) or to set up a password protected blog. Apache Basic Authentication To require a password to access your site using .htaccess and .htpasswd. Tools that help you create the files necessary to password protect your site: Htpasswd generator, htaccess Tools and Clockwatchers.com .htaccess And .htpasswd Tools Note: When your site is accessed the password is encoded weakly using Base64 and can be easily intercepted and decoded. Search Engines: Spiders and Bots Search Engines will index your site and cache your content. If you do not want this to happen, you can go to the Settings > Reading from Administration Screen, and Click Check the 'Discourage search engines from indexing this site' box to ask search engines not to index this site. Note: It is up to search engines to honor your request. You may use a file called robots.txt. More details can be found at Affilorama.com and elsewhere on the web. How can I solve login problems? See also: Login Trouble How can I get WordPress working when I'm behind a reverse proxy? In some setups, it's necessary to use something other than the HTTP_HOST header to generate URLs. Reverse proxies take the original request and send it to one of a group of servers. To do so, it overwrites the HTTP_HOST with the internal server's domain. When that domain is not publicly accessible, at best your images might not load correctly, at worst, you'll be stuck in a redirect loop. To fix this, figure out which header has the right domain name and add a line to your wp-config.php file that overwrites HTTP_HOST with the correct hostname. If you need to use SERVER_NAME, add this line to wp-config.php: [code language="php"]$_SERVER['HTTP_HOST'] = $_SERVER['SERVER_NAME'];[/code] If you need to use HTTP_X_FORWARDED_HOST, add this line to wp-config.php: [code language="php"]$_SERVER['HTTP_HOST'] = $_SERVER['HTTP_X_FORWARDED_HOST'];[/code] FTP How do I FTP? See also: Using FileZilla and FTP Clients How do I use FileZilla? See also: Using FileZilla How do I upload the files and folders? See also: Uploading WordPress to a remote host How do I CHMOD files? See also: Changing File Permissions MySQL or MariaDB Do I really need MySQL/MariaDB? Yes. You certainly need the MySQL or MariaDB database servers to power your WordPress blog. In fact, WordPress only supports the MySQL and MariaDB database servers. See also: Requirements for WordPress Can I use a database other than MySQL/MariaDB? No. Other databases are not supported at the moment. There are several other excellent database storage engines, such as PostgreSQL and SQLite that WordPress is interested in supporting in the future. Supporting multiple databases is trickier than it sounds and is not under active development, although there are plenty of architectural discussions about the best approach to take. Approaches for increasing the number of supported databases are discussed at Using Alternative Databases. Why does WordPress use MySQL/MariaDB? MySQL and MariaDB are extremely fast. It is also the most widely available database server in the world. Open-source and free, MySQL and MariaDB are supported by thousands of low-cost Linux (and Windows!) hosts, which means a very low barrier to entry for anyone wanting to start a WordPress (or database-driven) website. MySQL's documentation is useful, cogent and thorough. (Note: it may be intimidating if you are new to all this.) Add to all that the fact that users are able to directly manipulate MySQL and MariaDB with phpMyAdmin, developed expressly for that purpose, and it is obvious that MySQL and MariaDB are the best choice. PHP What is phpMyAdmin? phpMyAdmin is a tool written in PHP intended to handle the administration of MySQL/MariaDB over the Web. See also: phpMyAdmin Do I need to know PHP to use WordPress ? No. The only time you would modify your WordPress blog with PHP would be when integrating some of the plugins. In most cases clear instructions are given within a text file that accompanies the plugin. Other than that, you will not be changing any of the PHP files. Will WordPress run in PHP Safe Mode? Most definitely! There are no known issues with any version of WordPress when PHP is running in Safe Mode. Do I really need PHP? Yes. You certainly need PHP to power your WordPress blog. PHP is the scripting language that drives all of WordPress, and without PHP, your server will not be able to interpret the pages that create your weblog. For supported PHP version, refer Requirements for WordPress. How do I find out which version of PHP I have? To get information about your server, you can use the phpinfo() function. This will also give you information about your Apache and PHP version and mod_rewrite. See also: Finding Server Info Importing How can I import posts from my current weblog which uses a different blogging tool such as b2, Movable Type MT, Blogger, etc.? See also: Importing Content Advanced Topics atachibana — Thu, 14 Jul 2016 15:31:13 +0000 [codex_languages en="Advanced Topics" zhtw_codex="進階主題" ja_codex="Advanced Topics"] WordPress Plugins and Customization Managing Plugins - How to install and manage WordPress Plugins WordPress Plugins - Where to find WordPress Plugins Plugin Resources - Comprehensive list of resources for WordPress Plugin developers Templates - Comprehensive list of resources related to Themes and Templates, how to customize them, and how to create them Photoblogs and Galleries - How to use WordPress as a photo blog or photo gallery Podcasting - How to podcast audio and video content using WordPress Using Images - How to use images in your WordPress blog WordPress Advanced Techniques WordPress in Your Language - Description of how to find and install a non-English blog in WordPress Importing Content - How to import posts and comments from your previous blog software Editing Files - How to edit your theme and other WordPress PHP files from within the WordPress administrative menus Using Javascript - Description of how and why to use JavaScript in themes and posts AJAX - Description of AJAX technology and how it is used in WordPress WordPress Cookies - Description of how WordPress uses Cookies Writing Code in Your Posts - How to put programming and HTML code into a post, and get it to format the way you expect WordPress Feeds - Introduction to RSS and other types of content feeds in WordPress, with links to other feed-related resources Using Permalinks - How to customize permalink structure in WordPress XML-RPC Support in WordPress - Short note on XML-RPC support in WordPress, which allows you to post using external programs Enable Sending Referrers - How to fix browser issues in the Administration Panels of WordPress, related to your browser not sending "referring page" information Nginx - Serving WordPress sites with the Nginx web server, an alternative to the Apache web server Protection From Harvesters - How to protect your email address on a WordPress site from being harvested by a spammer Troubleshooting - Comprehensive list of resources for troubleshooting problems in WordPress Developer Documentation - Resources for developers of Themes, Plugins, and the core of WordPress FAQ Advanced Topics - Answers to frequently-asked questions WordPress Semantics - The jargon of WordPress Technical Articles - List of mostly outside references about WordPress Server and Database Information Finding Server Info - How to get information about the server and software versions you are using for WordPress Database Description - Description of the tables in the WordPress database Switching to PHP5 - About the move from previous versions of PHP to PHP5 Integrating WordPress with Your Website - How to integrate WordPress into the rest of your web site Moving WordPress - How to move your WordPress blog to a new location Changing The Site URL - How to change the URL of your WordPress blog Upgrading WordPress - How to upgrade WordPress to a new version High Traffic Tips For WordPress - How to prepare your blog for a lot of visitors, and evaluate whether it will work well WordPress Optimization - General overview of optimizing WordPress for high traffic sites Hardening WordPress - Discussion of WordPress security phpMyAdmin - Short description of the phpMyAdmin administrative tool for MySQL, and where to get it Backing Up Your Database - How to back up your WordPress database Restoring Your Database From Backup - How to restore a previous backup of your WordPress database UNIX Shell Skills - Basic UNIX commands you can use when you log in to the server WordPress is installed on Installing/Updating WordPress with Subversion - How to download old versions and the current development version of WordPress from the source code repository Running a Development Copy of WordPress - A hack to run two copies of WordPress with the same WordPress database (articles, categories, settings, etc.) MacOS X Local Mirror - Set up a Local Mirror of Your WordPress Blog on MacOS X Image Size and Quality atachibana — Thu, 14 Jul 2016 21:44:48 +0000 The size and quality of an image for use on a web page is determined by a variety of things. Physical Size The physical size of an image is based upon two things: The size of the image on the screen and the file size. Generally, the file size is treated as a different issue. File Size This is the size of the file on your hard drive or server. Resolution Resolution refers to the number of pixels in an image. Resolution is sometimes identified by the width and height of the image as well as the total number of pixels in the image. File Type There are basically X image types popularly found on the Internet: jpeg,gif,png and (for favicons (the icons next to the address)) ico. The physical size of the image is information we need to know in order to determine how much "space" will the image occupy on a web page. If your WordPress Theme features a fixed width content area of 600 pixels and the image you want to use is 800, the image will push the sidebar and layout of your web page around, messing up your design. Images within that 600 pixel width need to be restricted to that maximum width in order to protect the layout of your page. It's up to you to determine what size they should be from there, matching the image to your overall layout and styles. File size dictates the time it takes to load your page, the larger the file size, often increased because of a high image resolution quality, the longer it will take to load. People often don't have the patience to wait through long web page loads, so keeping your file sizes low speeds up your web page access times. Typically, large high quality images should be kept between 100K and 60K. Smaller images should be closer to 30K and lower. The resolution of the image dictates its clarity. The higher the resolution, though, the larger the file size, so you have to make a compromise between quality and file size. Luckily, the various file types most commonly used on the Internet have compression features. When you save the file as one of these types, it condenses or compresses the data information in the image file. Internet browsers can decompress this information to display the image on the screen. Some graphic software programs allow you to set the compression rate to control the quality of the image (and file size) at the time you save it. Depending upon your use of the images on your site, you may have to experiment with this to get the right ratio that keeps the resolution quality good while maintaining a small file size. Websites use four common file types. The end of a filename (called the extension) tells what type it is. One type, ico, is to make a favicon file -- but this is usually only done when a website is first set up. The other three types are used for general images: jpg (JPEG) is good for photographs. Saving a photo as jpg removes detail from the photo. Good photo editors let you control how much detail is removed (the "compression"). Different photos need different compression; doing this carefully and viewing the result can give you a usable photo with a small file size. gif can be poor for photographs. It's better for line art, like logos, with solid areas of the same color. png is for both photographs and line art. It compresses photos without losing detail, but usually makes larger photo files than JPEGs. Some older browsers don't completely support png, though. If you aren't sure which file type is best for a particular image, try saving the image in more than one type and comparing the file sizes. Using the right type can make a big difference! There's more information in Sitepoint's GIF-JPG-PNG What's the Difference article. Resizing Images Not all graphic software packages allow you to resize images, though most should. Check your graphics software table of contents or index for resize, size, transform, reduce, or enlarge, all synonyms for the for the same thing. If they don't have the feature, you may have to find different software. The process of resizing images is fairly simple. There are usually two methods: 1) You can resize an image through the use of tools provided which allow you to manually shift the edges of an image to deform or resize the image. The best way is to grab a corner, not the edge, to resize the image. The corner "handle" will usually resize the image maintaining the overall height-width ratio. Check your manual for specific instructions. 2) The other method involves simply specifying the image's final size. The advanced graphics programs allow you to set it by exact dimensions or a percentage of reduction or enlargement. After resizing the image, the image may be smaller, but it may also be slightly out of focus. You can sharpen the focus of the small image by using the sharpen feature in your software. When you have fine-tuned your small sized image or new thumbnail, export the image as a jpg, gif, or png. Resources Image File Formats on the Web GIF, JPG and PNG – What’s the Difference? Troubleshooting atachibana — Thu, 14 Jul 2016 21:48:45 +0000 [codex_languages en="Troubleshooting" de_codex="Fehlersuche" fax_codex="ایرادیابی" zhcn_codex="疑难解答" th_codex="Troubleshooting" zhtw_codex="疑難解答" ko_codex="Troubleshooting" ja_codex="Troubleshooting" ptbr_codex="Solução de problemas"] Finding Answers Getting More WordPress Help Using the Support Forums New To WordPress - Where to Start First Steps With WordPress Introduction to Blogging WordPress Semantics - Learning the Jargon WordPress Support Forum How to Write a Great Support Request IRC Freenode WordPress Support on channel #wordpress WordPress IRC Live Help FAQ - Frequently Asked Questions Installation Problems Getting Started With WordPress - Installation Common Installation Problems Moving WordPress Importing Posts and Comments from Another Blog Software I've Lost My Password I Can't Login Help for WordPress Beginners FAQ Installation FAQ Working with WordPress Design and Layout Troubleshooting CSS Fixing_Browser Bugs CSS Troubleshooting Finding Your CSS Styles Troubleshooting Nested Lists Site Design and Layout WordPress Lessons FAQ Themes, Layout and Design FAQ Using WordPress Comment Spam Moderating Comments Spammers Have Overwhelmed My Comments Combating Comment Spam Common Spam Words FAQ Working with WordPress Frequently Asked Questions FAQ About WordPress FAQ Installation FAQ New To WordPress FAQ Working with WordPress FAQ Themes, Layout and Design FAQ Using WordPress FAQ Advanced Topics FAQ Troubleshooting FAQ Developer Documentation FAQ About the WordPress Codex Solving Common Problems FAQ Troubleshooting Enabling Sending Referrers The Layout is All Messed Up I Make Changes and Nothing Happens Permalinks Won't Work Pagination is broken WordPress Backups Backing Up Your Database Restoring Your Database From Backup My Plugin Won't Work Solving MySQL Database Error 28 Using Your Browser to Diagnose JavaScript Errors Using Password Protection atachibana — Thu, 14 Jul 2016 22:21:03 +0000 [codex_languages en="Using Password Protection" ko_codex="Using Password Protection"] Post Visibility Settings Once you publish a WordPress post (or Page), it is visible to the public (by default). In WordPress terms, this means a post with a Published status has a default visibility of Public, based on the settings in the Publish box of a Edit Post Screen. WordPress also offers two less public options for your post's Content Visibility. Clicking the "Edit" link next to Visibility: Public reveals three radio buttons: Public is selected by default. Checking Password protected reveals a text field for entering a password, that will be required to view that post. The password is limited to 20 characters. Checking Private makes your post visible only to your site's Users with the role of Administrator or Editor. When you're done editing the post's visibility, click the "OK" button. You should now see your post's new setting, e.g., Visibility: Password Protected. Remember: a setting change does not take effect until you click the "Publish" button (or "Update" if the post is already published.) Finding or Changing a Password Only an Administrator, Editor, or the post's Author can change a post's password or visibility setting. To do so, use the "Visibility: Edit" link again. These settings are also available using the post's Quick Edit link in the All Posts Screen. The Visibility "Edit" link (or "Quick Edit") is also a good way to reveal a forgotten post password. Password Protected Posts WordPress displays a password-protected post differently. It makes these changes to the post's: Title– Adds the text "Protected: " before the post Title. Excerpt– Instead of the post Excerpt, prints this text: "There is no excerpt because this is a protected post." Content– Instead of the post Content, prints a password form with this text: "This post is password protected. To view it please enter your password below:" So, a password-protected post with a title of "My Post" would display like this: Password Protecting Many Posts and Pages WordPress stores this password in a browser cookie so readers don't have to re-enter passwords if they visit the same page multiple times. Furthermore, if multiple posts use the same password, the reader will only have to enter the password once to access every post (see caveat below). WordPress will only track one password at a time. Therefore, if two posts use two different passwords, entering the password for post A, then entering the password for post B means that revisiting post A (or any post which shares its password) will require the user to re-enter the password for post A. Protect Custom Fields WordPress does not print a password-protected post's Content or Excerpt until the correct password is entered. But a post's Custom Field(s) data is not protected, and can still show. To stop CFs from printing, wrap your get_post_meta calls (e.g., in single.php or page.php) with a conditional statement using: post_password_required. This one WordPress function checks both whether your post requires a password and whether the correct password has been provided: [code language="php"] ID, 'key_1', true ); echo $key_1_value_1; } ?> [/code] The post_password_required function within in an if statement is also handy for other customizations, such as preventing password-protected posts from displaying in a list. Customize the Protected Text With WordPress Filters you can: change the default text in the password form, change the default text for the password-protected post Excerpt, and insert the password form into the post Excerpt. To do so, add the following code to your custom plugin file. Password Form Text The password form displays this default message: "This post is password protected. To view it please enter your password below:" The following code will return the form with different text and different html structure — in this example the custom message is: "To view this password protected post, enter the password below:" [code language="php"] ID ) ? rand() : $post->ID ); $o = ' ' . __( "To view this protected post, enter the password below:" ) . ' ' . __( "Password:" ) . ' '; return $o; } add_filter( 'the_password_form', 'my_password_form' ); ?> [/code] Please note: the my_password_form function must return a value: don't use print or echo. Password Size Limitation Make sure to set the maxlength parameter to a value of 20 when replacing the password protection form as WordPress will only save the first 20 characters due to database constraints. Protected Excerpt Text The default Excerpt of a password-protected post is: "There is no excerpt because this is a protected post." This code will replace that text with your own — HTML allowed: [code language="php"] [This is password-protected.]'; return $excerpt; } add_filter( 'the_excerpt', 'my_excerpt_protected' ); ?> [/code] Replace "[This is password-protected.]" with your custom password-protected Excerpt message. Add the Password Form to the Excerpt Another option for your protected Excerpts is to print out the password form instead of the Excerpt message. That way people enter the password right from an index or archive page. Then, when they click the Title link, they'll see the Content. With the get_the_password_form function, you can make the password form be the Excerpt for a password-protected post: [code language="php"] [/code] This will get the default Wordpress password form and text or any customizations you've made. For a better understanding of how post_password_required() and get_the_password_form() work, read their function definitions in {{Trac|wp-includes/post-template.php}}. In this same WordPress core file you'll also find the the_excerpt and the_password_form filters, and the functions get_the_excerpt(), get_the_title(), and get_the_content(). These functions control how a post's title, excerpt and content display, depending on its visibility setting. Hiding Password Protected Posts Sometimes, you don't want your password protected posts to show up on other places around your site, like on the home page or archive pages. To effectively hide them from these pages without affecting your pagination, place the following code in your custom plugin file: [code language="php"] posts}.post_password = '' "; } // Decide where to display them function exclude_protected_action($query) { if( !is_single() && !is_page() && !is_admin() ) { add_filter( 'posts_where', 'exclude_protected' ); } } // Action to queue the filter at the right time add_action('pre_get_posts', 'exclude_protected_action'); ?> [/code] This code works in two parts: the first part effectively removes any password protected posts directly from any SQL query that WordPress is running, using the posts_where filter. The second part adds this filter to all pages except single posts, pages, and admin pages. For more information on why pre_get_posts is the right action for this function, see the pre_get_posts action reference. Changing the cookie lifetime See https://developer.wordpress.org/reference/hooks/post_password_expires/ Using Your Browser to Diagnose JavaScript Errors atachibana — Sat, 16 Jul 2016 12:25:05 +0000 If you're experiencing issues with your interactive functionality this may be due to JavaScript errors or conflicts. For example, your flyout menus may be broken, your metaboxes don't drag, or your add media buttons aren't working. In order to formulate your support request it helps the team to know what the JavaScript error is. This guide will show you how to diagnose JavaScript issues in different browsers. Step 1: Try Another Browser To make sure that this is a JavaScript error, and not a browser error, first of all try opening your site in another browser. if the site is not having the same issue in the new browser you know that the error is browser specific if the site is having the same error it is not an error that is specific to one browser Make note of any browsers you are experiencing the error in. You can use this information when you are making a support request. Step 2: Enable SCRIPT_DEBUG You need to turn on script debugging. Open wp-config.php and add the following line before "That's all, stop editing! Happy blogging". [code language="php"] define('SCRIPT_DEBUG', true); [/code] Check to see if you are still having an issue. Issue is fixed - turn off script debugging and report the issue on the support forum, telling the volunteers that you turned on script debugging and it solved the problem. Issue persists - proceed to Step 3. Step 3: Diagnosis Now that you know which browsers you are experiencing issues in you can start to diagnose the issue. Firefox 1. Open the Console Go to the screen where you are experiencing the error. In Firefox, navigate to Tools > Web Developer > Error Console or press Ctrl + Shift + J. 2. Identify the Error The error console will open. If you don't see any errors try reloading the page. The error may be generated when the page loads. The console will provide you with the error type, the location of the error and the line number The image above shows the error to be in jquery.js on line 2. Internet Explorer Bear in mind, IE behaves vastly differently from other browsers when it comes to JS errors, and reports on them in disparate ways. The first thing to check when facing a problem in IE is if the problem only exists in IE. Also note that the debugging tools built into some IE versions are limited, and may not be available. 1. Open the Console Go to the screen where you are experiencing the error. In Internet Explorer, navigate to Settings > F12 Developer Tools. Or click F12 Click on the Console tab. 2. Identify the Error The error console will open. If you don't see any errors try reloading the page. The error may be generated when the page loads. The console will provide you with the error type, the location of the error and the line number The image above shows the error to be in jquery.js on line 2. Chrome 1. Open the Console Go to the screen where you are experiencing the error. In Chrome, navigate to View > Developer > JavaScript Console or More Tools > JavaScript Console or press Ctrl + Shift + J. 2. Identify the Error The error console will open. If you don't see any errors try reloading the page. The error may be generated when the page loads. The console will provide you with the error type, the location of the error and the line number The image above shows the error to be in jquery.js on line 2. Safari 1. Enable Developer Tools Navigate to Safari > Preferences > Advanced and check the box that says Show Develop menu in menu bar 2. Open the Console Go to the screen where you are experiencing the error. In Safari, navigate to Develop > Show Error Console 3. Identify the Error The error console will open. If you don't see any errors try reloading the page. The console show you the error, the error location and the line number: The image above shows the error to be in jquery.js on line 2. Note: If you cannot see the error click the back button within the console. Opera 1. Open the Console Go to the screen where you are experiencing the error. In Chrome, navigate to Tools > Advanced > Error Console. 2. Identify the Error The error console will open. Select JavaScript and Errors from the two drop downs. To find the error location, expand one of the errors. You'll see the error and the location. The image above shows the error to be in jquery.js on line 2, however remember to copy the whole stack information! Just saying what line is less helpful that showing context. Step 4: Reporting Now that you have diagnosed your error, you should make your support forum request. Go to the troubleshooting forum. If your problem is with a specific theme or plugin, you can access their dedicated support forum by visiting http://wordpress.org/extend/plugins/PLUGINNAME/support or http://wordpress.org/extend/themes/THEMENAME/support Please include the below information: the browsers that you are experiencing the problem in whether SCRIPT_DEBUG fixed the error or not the JavaScript error the location of the error - both the file name and the line number the context of the error - including the whole error stack will help developers How to Use Gravatars atachibana — Sat, 16 Jul 2016 13:22:21 +0000 What is a Gravatar? When browsing different web sites, you may notice that many users have a picture next to their name. These pictures are called "avatars." WordPress, however, uses a specific type of avatar called "Gravatars"--short for "Globally Recognized Avatar." Unlike standard avatars, Gravatars follow you around the web and automatically appear when you post a comment on a WordPress site. WordPress integrates Gravatars into every WordPress site. Once registered with Gravatar, the service matches your WordPress profile information to the email address registered with Gravatar and displays your custom Gravatar image next to comments and (optionally) elsewhere on the WordPress site. If you choose not to sign up with Gravatar, the default icon set by the Administrator appears next to your name. Why use Gravatars? Providing your users with avatars has become a convention in web-publishing. Enabling Gravatars on your WordPress site simplifies the process for everyone involved. While it is possible to use a WordPress Plugin to manage user avatars on your WordPress-run site, using Gravatars on your site makes less work for both you and your site’s users. Benefits for Administrators You can add user Gravatars with very little effort You don’t need to maintain an additional Plugin You don’t have to manage user accounts, or their images, for commenters to use Gravatars on your site Benefits for Users You don’t need to register for every site you visit just to use a Gravatar You can update the Gravatar you use across multiple sites by uploading a single image in a single place Using Gravatars on your Site To start using Gravatars on your site: Log in as an administrator to your site Navigate to Settings > Discussion and scroll down to the “Avatar” Section The “Avatar” section presents you with several options: Avatar Display: Toggle Gravatars on and off for your site. Maximum Rating: When users create a profile on Gravatar, they are given the opportunity to rate their Gravatar image as G, PG, R, X based on its appropriateness. Select the radio button for the maximum rating you would like displayed on your site. Default Avatar: WordPress allows for you to select what image you would like to display when a commenter does not have a Gravatar account. Selecting one of the “generated” icons give you and your users some of the benefits of a Gravatar without requiring them to have a Gravatar account. The icons that say “generated” next to them take the email of the commenter and link it to an auto-generated image. Now, every time that commenter posts to your site, they will have the same unique image next to their name. For Developers Starting with WordPress 2.7, when you retrieve the comments on a post or page using wp_list_comments, WordPress will automatically retrieve your users' Gravatars. If you would like to retrieve a user's Gravatar without retrieving comments, you can use get_avatar. Customizing how Gravatars are displayed Using wp_list_comments allows you to customize how WordPress outputs your comments in your theme. It also controls the size of the Gravatar attached to the comments. By default, Gravatars are displayed at 32px x 32px. To change the size of the Gravatar, you can use the ‘avatar_size’ argument with wp_list_comments. For example, to return a 50px x 50px Gravatar, you would call wp_list_comments like this: [code language="php"] '50' ) ); ?>[/code] get_avatar works slightly different. The first argument you pass it must be a user's ID, email address or the comment object. You can then specify the size of the returned Gravatar, the URL for the default image you want to display if a user does not have a Gravatar, and the alternate text for the Gravatar image. This will return a 50px x 50px Gravatar: [code language="php"][/code] Customizing Gravatars with CSS Because you can retrieve Gravatars with or without comments, you need to be specific with your CSS classes when styling Gravatars. When WordPress returns Gravatars, it assigns them the .avatar class. However, you don’t want to only target the class .avatar because it is generated in different contexts. For example, when you hover over the Gravatar in the WordPress admin bar, the Gravatar that appears has the .avatar class. If you were to change the CSS for the .avatar class, you would alter the style of both the Gravatar in your theme's comments and admin bar. As the Twenty Eleven theme demonstrates, you can simply use an additional class to target a specific instance of a Gravatar. This will change the display of Gravatars only in the Twenty Eleven theme's comments: [code language="php"] .comment-list .avatar { /*Insert Your Styling Here */ } [/code] Create a Custom Default Avatar If you don’t want to use any of the default images for users not registered with Gravatar, you can easily add your own by adding a filter to the avatar_defaults hook. After uploading the new image to your theme files, add this to your theme’s function.php file: [code language="php"] >Discussion $avatar_defaults[$new_avatar_url] = 'Your New Default Avatar'; return $avatar_defaults; } ?> [/code] Now, go to Settings > Discussion and select your new avatar from the list. From now on, all your users that don't use Gravatar will have this avatar next to their comments. Using Gravatar’s Hovercards If you want to use Gravatar’s Hovercard feature, like on WordPress.com, you can install the Jetpack Plugin. Resources Introducing Gravatar Gravatar Profiles Using Gravatars Gravatar Developer Resources HiDPI Gravatars Uploading Files atachibana — Sat, 16 Jul 2016 14:20:47 +0000 About Uploading Files with WordPress To upload files, you can use WordPress's online interface, the Media Dashboard in the left sidebar in the backend of WordPress, the page with the media button or one of the recommended editors and upload your files via FTP. The Media Dashboard lets you upload files in the following ways: Uploading by the Media Dashboard If you use the Media Dashboard, - in case you use the image later - please follow the following steps: Go to Media --> Library (in the left sidebar) Add New file Drag files to library or select files from our computer After you log in to WordPress go to Dashboard --> Media --> New file at the top of the screen, you can drag files from your computer or you can use the Browser uploader . Maximum size is by default 100 mb. Uploading into a post of page If you use the Media button, - in case of uploading in specific post or page - please follow the following steps: To Upload a File in a Post or page On the Dashboard menu, click Posts or page, and then click Add New to display the "Add New Post or page" page. Click the Add Media button. [picture to be place] In the dialog box, the Media Library appears. Select the file you want to upload and click on it. Add meta data at the right side of the window. Choose alignment, link to page and filesize. [picture to be place] Finally Click insert into post or page. When the upload of the image into the post or page is complete, click on the button Save or Update at the right side of the page. This article tells you how to upload files using the Media Dashboard. To upload files via FTP, read Uploading WordPress to a Remote Host. Supported media file types WordPress supports uploading the following file types: [Editor notes: I think there are more file types possible] Images .jpg .jpeg .png .gif .ico Documents .pdf (Portable Document Format; Adobe Acrobat) .doc, .docx (Microsoft Word Document) .ppt, .pptx, .pps, .ppsx (Microsoft PowerPoint Presentation) .odt (OpenDocument Text Document) .xls, .xlsx (Microsoft Excel Document) .psd (Adobe Photoshop Document) [editor's note: in my opinion psd files are not allowed] Audio .mp3 .m4a .ogg .wav Video .mp4, .m4v (MPEG-4) .mov (QuickTime) .wmv (Windows Media Video) .avi .mpg .ogv (Ogg) .3gp (3GPP) .3g2 (3GPP2) Not all webhosts permit these files to be uploaded. Also, they may not permit large file uploads. If you are having issues, please check with your host first. Note: If the file does not open, then the file type is not supported, the chosen format may not match the file’s true format or the file may be damaged. Please contact your webhost. [Editor note: below items to be changed as well] Resources Using Images Using Image and File Attachments Inserting Images into Posts and Pages Media Library Screen See Also Changing File Permissions Dashboard Screen Settings General Screen atachibana — Sat, 16 Jul 2016 14:27:54 +0000 Settings → General This Settings General Screen is the default Screen in the Settings Administration Screen and controls some of the most basic configuration settings for your site: your site's title and location, who may register an account at your site, and how dates and times are calculated and displayed. General Settings Site title Enter the name of your site (or blog) here. Most themes will display this title, at the top of every page, and in the reader's browser titlebar. WordPress also uses this title as the identifying name for your Syndication feeds. Tagline In a few words, explain what your site is about. Your sites's slogan, or tagline, might be entered here. A tagline is short phrase, or sentence, used to convey the essence of the site and is often funny or eye-catching. WordPress Address (URL) Enter the full URL of the directory containing your WordPress core application files (e.g., wp-config.php, wp-admin, wp-content, and wp-includes). For example, if you installed WordPress into a directory called "blog", then the WordPress address would be http://example.net/blog (where example.net is your domain). If you installed WordPress into your web root, this address will be the root URL http://example.net. WordPress will trim a slash (/) from the end. If you defined the WP_SITEURL constant in your wp-config.php file, that value will appear in this field and you will not be able to make changes to it from the WordPress administration screen. Site Address (URL) Enter the address you want people to type in their browser to reach your WordPress site. This is the directory where WordPress's main index.php file is installed. The Site address (URL) is identical to the WordPress address (URL) (above) unless you are giving WordPress its own directory. WordPress will trim a slash (/) from the end. If you defined the WP_HOME constant in your wp-config.php file, that value will appear in this field and you will not be able to make changes to it from the WordPress administration screen. E-mail Address Enter the e-mail address to which you want WordPress to send messages regarding the administration and maintenance of your WordPress site. For example, if you allow new users to register as a member of your site (see Membership below), then a notification will be sent through e-mail to this address. In addition, if the option, An administrator must always approve the comment, is set in Administration > Settings > Discussion, this e-mail address will receive notification that the comment is being held for moderation. Please note this is different than the address you supplied for the admin user account; the admin account e-mail address is sent an e-mail only when someone submits a comment to a post by admin. The address you enter here will never be displayed on the site. You can send messages to multiple admins by using an email address which forwards email to multiple recipients. Membership: Anyone can register - Check this checkbox if you want anyone to be able to register an account on your site. New User Default Role This pull-down box allows you to select the default Role that is assigned to new users. This Default Role will be assigned to newly registered members or users added via the Administration > Users > Users Screen. Valid choices are Administrator, Editor, Author, Contributor, or Subscriber. Timezone From the pulldown box, choose a city in the same timezone as you. For example, under America, select New York if you reside in the Eastern Timezone of the United States that honors daylight savings times. If you can't identify a city in your timezone, select one of the Etc GMT settings that represents the number of hours by which your time differs from Greenwich Mean Time. Click the Save Changes button and the UTC time and "Local time" will display to confirm the correct Timezone was selected. Date Format The format in which to display dates on your site. The Date Format setting is intended to be used by theme designers in displaying dates on your site, but does not control how the date is displayed in the Administrative Screens (e.g. Manage Posts). Click the Save Changes button and the "Output" example below will show the current date in the format entered. See Formatting Date and Time for some of the formats available. Time Format The format in which to display times on your site. The Time Format setting is intended to be used by theme designers in displaying time on your site, but does not control how the time is displayed in the Administrative Screens (e.g. Write Post edit of timestamp). Click the Save Changes button and the "Output" example below will show the current time in the format entered. See Formatting Date and Time for some of the formats available. Week Starts On Select your preferred start date for WordPress calendars from the drop-down box. Monday is the default setting for this drop-down, meaning a monthly calendar will show Monday in the first column. If you want your calendar to show Sunday as the first column, then select Sunday from the drop-down. Site Language The WordPress dashboard language. Save Changes Click the Save Changes button to ensure any changes you have made to your Settings are saved to your database. Once you click the button, a confirmation text box will appear at the top of the page telling you your settings have been saved. Installing on Microsoft IIS atachibana — Sun, 17 Jul 2016 02:50:37 +0000 Install Internet Information Services 8.5 and WordPress 3.x by Using the Microsoft Web Platform Installer 5.0 This article describes how to install and configure WordPress 3.x on Windows clients and servers (see Prerequisites) using the Microsoft Web Platform Installer (Web PI) version 5.0. As of May 28, 2014, the latest version of WordPress is 3.9.1. The Web PI is a free tool that makes getting the latest components of the Microsoft Web Platform—including Internet Information Services (IIS), MySQL, PHP, the Microsoft .NET Framework, and Visual Web Developer—quick and easy. The Web PI also lets you install web applications such as WordPress with the built-in Windows Web App Gallery. To install WordPress on IIS 8.5 by using the Web PI 5.0, follow these steps: Prerequisites Step 1. Install Microsoft Web Platform Installer 5.0 Step 2. Select the products and applications to install Step 3. Review and configure the selected products and applications Step 4. Complete the installation and configuration Step 5. Enable clean URLs (Pretty Permalinks) Step 6. Running Microsoft WebMatrix with WordPress Prerequisites The supported operating systems for the Microsoft Web Platform Installer (Web PI) 5.0 are Windows 8.1, Windows 8, Windows 7, Windows Vista Service Pack 1 (SP1), Windows Vista, Windows XP Service Pack 2 (SP2) and later versions, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, and Windows Server 2003 Service Pack 1 (SP1) and later versions. For this guide, it is assumed that you have either Windows Server 2012 R2 or Windows 8.1 Pro client installed on your computer. You will also need an Internet connection and administrator privileges for your computer. It is a good idea to confirm that your system meets the hardware requirements for IIS 8.5. See http://technet.microsoft.com/en-us/library/dn303418.aspx for more information. Step 1. Install Microsoft Web Platform Installer 5.0 In this step you download, install, and launch the MS Web Platform Installer (Web PI 5.0, which is a 1.4 MB download). Log into your Windows machine as a user with administrative privileges. Launch Internet Explorer (other browsers work too). Go to http://www.microsoft.com/web/downloads/platform.aspx, and then click the Free Download button. Click Run. Click Run again. Wait a few seconds for the Web PI 5.0 to start. Step 2. Select the products and applications to install In this step, you select the version of WordPress that you want to install. WordPress 3.9.1 is used in this guide. On the "Web Platform Installer" start screen click the Applications tab, and then click the Add button associated to the right with "WordPress". Click Install. Step 3. Review and configure the selected products and applications In this step, you review and configure what you have added. Additionally, you add the database and configure the password for it. When you are asked which type of database you want to use, leave MySQL (Not installed) selected. Note: This will install MySQL 5.1 for Windows to handle all the database transactions that are required by WordPress. In password fields, type in a password for your database, and then click Continue. Review the files to be downloaded and installed, as well as the license agreements, and then click I Accept. Allow the Web PI installation to complete. Configure Security Keys. The WordPress Security Keys section describes what these keys and how they're used. The keys don't need to be remembered, they should just be long, random and complicated. An easy way to generate the keys is to use the online key generator. Each time you click browser refresh, the online key generator creates a new set of keys. Note: The online key generator produces keys that may contain dollar signs ('$') which cannot be used with keys entered into Web-PI. Until this Web-PI issue is resolved, a simple solution is to check for dollar sign characters and simply replace '$' with 'S' (any alpha character will work). Here's an example set of keys - don't use these, use the online key generator to create your own unique keys! Finish. On the FINISH dialog click the copy to clipboard link (this copies your database settings and password to the clipboard), paste and save this information in a file for future reference, and then click the Finish button. Microsoft WebMatrix will open, allowing you to configure additional settings related to your WordPress site: Step 4. Complete the installation and configuration In this step, you complete the installation. Switch to Internet Explorer. Go to your WordPress website. For example, go to http://localhost/myWordPress. In the Site Title box, type the name of your site. In the Password, twice boxes, type a password for the admin account. In the Your E-mail box, type the email address for the admin account. Click Install WordPress. Click Log In. Type admin, type the password, and then click Log In. Step 5. Enable clean URLs (Pretty Permalinks) In this step, you enable Pretty Permalinks now that WordPress has been installed. In the Dashboard menu, click Settings. Scroll down, and then click Permalinks. Under Common settings, select a common Permalink setting or select Custom Structure to create your own Permalink, and then click Save Changes. The installation is now complete, and you are ready to use WordPress! Step 6. Running Microsoft WebMatrix with WordPress The Microsoft Web Platform Installer (Web PI) installs WordPress to run in a localhost configuration in combination with Microsoft WebMatrix (which was also installed as part of the Web PI installation). When WebMatrix is not running (e.g., after a reboot or if you terminate WebMatrix) you will not be able to access your localhost WordPress site until WebMatrix is restarted. Use the following steps to start WebMatrix and launch your localhost WordPress site. Click Start, click All Programs, click-open the Microsoft WebMatrix folder, and then click to launch the Microsoft WebMatrix app. On the WebMatrix start page, click the My Sites button to display the installed sites, and then click your wordpress site that displays in the pop-up context menu. After the site opens, click the lower-left Site tab to display links for the WordPress launch URL and file Path. Click on the site URL link to launch your localhost WordPress site. At this point WebMatrix will open a browser window to your localhost WordPress site which you can customize and add content to. Remember: WebMatrix must be left running while you interact with your localhost WordPress site. Additional Information WordPress is free, open-source content management system (CMS) software that lets individuals or communities of users easily publish, manage, and organize a wide variety of content on a website. For more information about WordPress, visit these websites: http://www.wordpress.org/ http://codex.wordpress.org/Main_Page IIS URL Rewrite 2.0 lets you create powerful rules to implement URLs that are easier for users to remember and easier for search engines to find. For more information, visit these websites: http://www.iis.net/download/urlrewrite http://learn.iis.net/page.aspx/734/url-rewrite-module/ Windows Cache Extension for PHP is a PHP accelerator that is used to increase the speed of PHP applications that are running on Windows and on Windows Server. After Windows Cache Extension for PHP is enabled and loaded by the PHP engine, PHP applications can take advantage of the functionality without any code modifications. For more information, visit this website: http://www.iis.net/download/wincacheforphp PHP Manager for IIS is a tool for managing one or many PHP installations on IIS 7.0 servers. For more information, visit these websites: http://www.iis.net/community/default.aspx?tabid=34&g=6&i=2007 http://learn.iis.net/page.aspx/944/using-php-manager-for-iis-to-setup-and-configure-php/ For more general information about PHP, visit these websites: http://www.php.net/manual/en/install.windows.manual.php http://www.php.net/manual/en/install.windows.iis6.php http://www.php.net/manual/en/install.windows.iis7.php Other useful links: http://php.iis.net/ http://windows.php.net/ http://forums.iis.net/1102.aspx For information on media upload permission errors, or 500 errors when loading uploaded images, visit these sites: https://www.bluevalleytech.com/techtalk/blog/iis-500-errors-when-loading-a-static-image-in-wordpress.aspx http://www.amixa.com/blog/2011/04/29/iis-wordpress-images-500-error/ Before You Create A Network atachibana — Sun, 17 Jul 2016 03:08:14 +0000 This section outlines some requirements to consider before you begin creating a multisite network. Do you really need a network? The sites in a multisite network are separate, very much like the separate blogs at WordPress.com. They are not interconnected like things in other kinds of networks (even though plugins can create various kinds of interconnections between the sites). If you plan on creating sites that are strongly interconnected, that share data, or share users, then a multisite network might not be the best solution. For example, if all you want is for different collections of web pages to look very different, then you can probably achieve what you want in a single site by using a plugin to switch themes, templates, or stylesheets. For another example, if all you want is for different groups of users to have access to different information, then you can probably achieve what you want in a single site by using a plugin to switch capabilities, menus, and link URLs. This guide describes how to install manually WordPress Multisite in your current WordPress installation. There are also available ready-to-run packages from BitNami. Types of multisite network You can choose between several different types of multisite network depending on how you want your network to handle URLs, and on whether it will allow end users to create new sites on demand. Different types of network have different server requirements, which are described in a section below. If you do not have full control over your server then certain types of multisite network might not be available to you. For example, you might not have full control over your server because you use a shared hosting environment. In that case you will have to negotiate the requirements with whoever operates the hosting environment. The sites in a network have different URLs. You can choose one of two ways for the URL to specify the site: Each site has a different subdomain. For example: site1.example.com, site2.example.com. Each site has a different path. For example: example.com/site1, example.com/site2 Additionally, you can map domains like example1.com, example2.com, etc, however a plugin is suggested. You can make the changes directly in the network settings, but it's considered advanced administration. You can also choose whether or not to allow end users to create new sites on demand. Domain-based on-demand sites are normally only possible using subdomains like site1.example.com and site2.example.com. Path-based on-demand sites are also possible. The multisite installation process uses different terminology. A sub-domain install creates a domain-based network, even though you might use separate mapped domains, and not subdomains, for your sites. A sub-directory install creates a path-based network, even though it does not use file system directories. If you want to use a sub-domain install, you must install WordPress in the root of your webpath (i.e. domain.com) however it does not need to be installed in the root (i.e. /public_html/) if you choose to run WordPress from it's own directory. After the multisite network installation is complete, WordPress uses the terminology domain and path for each site's domain and path in the Network Admin user interface. A super admin (that is, a multisite network administrator) can edit sites' domain and path settings, although it is unusual to do this to established sites because it changes their URLs. Plugins can extend the options available and help with administration. Search Plugin Directory by 'multiste' or click this link. Admin Requirements To create a multisite network you must be the administrator of a WordPress installation, and you normally need access to the server's file system so that you can edit files and create a directory. For example, you could access the server's file system using FTP, or using the File Manager in cPanel, or in some other way. You do not necessarily need any knowledge of WordPress development, PHP, HTML, CSS, server administration or system administration, although knowledge of these things might be useful for troubleshooting or for customizing your multisite network after installation. Server Requirements When you are planning a network, it can sometimes be helpful to use a development server for initial testing. However, setting up a development server that exactly matches your production server is not always possible, and transferring an entire network to a production server may not be easy. A test site on your production server is sometimes a more useful way to test your planned network. In all cases, you will need to make sure your server can use the more complex .htaccess (or nginx.conf or web.config) rules that Multisite requires. Multisite requires mod_rewrite to be loaded on the Apache server, support for it in .htaccess files, and Options FollowSymLinks either already enabled or at least not permanently disabled. If you have access to the server configuration, then you could use a Directory section instead of a .htaccess file. Also make sure that your httpd.conf file is set for "AllowOverride" to be "All" or "Options All" for the vhost of the domain. You can ask your webhost for more information on any of this. Some server requirements depend on the type of multisite network you want to create, as follows. Domain-based Also known as 'Subdomain' installs, a Domain-based network uses URLs like http://subsite.example.com A domain-based network maps different domain names to the same directory in the server's file system where WordPress is installed. You can do this in various ways, for example: by configuring wildcard subdomains by configuring virtual hosts, specifying the same document root for each by creating addon domains or subdomains in cPanel or in a similar web hosting control panel On-demand domain-based sites require the wildcard subdomains method. You can create additional sites manually in the same network using other methods. Whichever methods you use, you will need to configure your DNS (to map the domain name to the server's IP address) and server (to map the domain name to the WordPress installation directory). WordPress will then map the domain name to the site. WordPress should be run from the root of your webfolder (i.e. public_html) for subdomains to work correctly. Making subdomains work from a non-root directory requires experience with Virtual Hosts and redirects. External links: Wildcard DNS record (Wikipedia) Apache Virtual Host (Apache HTTP Server documentation) cPanel Domains (cPanel documentation) For some examples of how to configure wildcard subdomains on various systems, see: Configuring Wildcard Subdomains Path-based Also known as 'Subfolder' or 'Subdirectory' installs, a path-based network uses URLs like http://example.com/subsite If you are using pretty permalinks in your site already, then a path-based network will work as well, and you do not need any of the other information in this section. That said, be aware that your main site will use the following URL pattern for posts: http://example.com/blog/[postformat]/ At this time, you cannot remove the blog slug without manual configuration to the network options in a non-obvious place. It's not recommended. WordPress Settings Requirements When you install a multisite network you start from an existing WordPress installation. If it is a fresh install with its own domain name, then you do not need to read this section. If it is an established site, or not reachable using just a domain name, then the following requirements apply to allow it to be converted to a multisite network. Be Aware Giving WordPress its own directory works with Multisite as of 3.5, however you must make the 'own directory' changes before you activate Multisite. While it's not recommended to use www in your domain URL, if you chose to do so and plan to use subdomains for multisite, make sure that both the site address and the WordPress address are the same. Also keep in mind some hosts will default to showing this sort of URL: For this, and many other reasons, we do not suggest you use www in your domain name whenever possible. If you plan on changing them to domain.com or www.domain.com, do so before you begin the rest of the setup for multisite, as changing the domain name after the fact is more complicated. Restrictions You cannot create a network in the following cases: "WordPress address (URL)" uses a port number other than ':80', ':443'. You cannot choose Sub-domain Install (for a domain-based network) in the following cases: The WordPress URL contains a path, not just a domain. (That is, WordPress is not installed in a document root, or you are not using the URL of that document root.) "WordPress address (URL)" is localhost. "WordPress address (URL)" is IP address such as 127.0.0.1. (Note that you can create a domain-based network on your local machine for testing purposes by using your hosts file to map some other hostnames to the IP address 127.0.0.1, so that you never have to use the hostname localhost.) You cannot choose Sub-directory Install (for a path-based network) if your existing WordPress installation has been set up for more than a month, due to issues with existing permalinks. (This problem will be fixed in a future version. See Switching network types for more information.) (See wp-admin/network.php for more detail) Optimization Sun, 17 Jul 2016 03:41:33 +0000 Whether you run a high traffic WordPress installation or a small blog on a low cost shared host, you should optimize WordPress and your server to run as efficiently as possible. This article provides a broad overview of WordPress optimization with specific recommended approaches. However, it's not a detailed technical explanation of each aspect. If you need a quick fix now, go straight to the Caching section, you'll get the biggest benefit for the smallest hassle there. If you want to get started on a more thorough optimization process immediately, go to How Do You Improve Performance in WordPress. A broad overview of the topic of performance is included below in What Affects Performance and How Do You Measure Performance. Many of the techniques discussed here also apply to WordPress Multisite (MU). Performance factors Several factors can affect the performance of your WordPress blog (or website). Those factors include, but are not limited to, the hosting environment, WordPress configuration, software versions, number of graphics and their sizes. Most of these performance degrading factors are addressed here in this article. Hosting The optimization techniques available to you will depend on your hosting setup. Shared Hosting This is the most common type of hosting. Your site will be hosted on a server along with many others. The hosting company manage the web server for you, so you have very little control over server settings and so on. The areas most relevant to this type of hosting are: Caching, WordPress Performance and Content Offloading Virtual Hosting and Dedicated Servers In this hosting scenario you have control over your own server. The server might be a dedicated piece of hardware or one of many virtual servers sharing the same physical hardware. The key thing is, you have control over the server settings. In addition to the areas above (caching and WordPress performance, the key areas of interest here are: Server Optimization and Content Offloading Number of Servers When dealing with very high traffic situations it may be necessary to employ multiple servers. If you're at this level, you should already have employed all of the applicable techniques listed above. The WordPress database can be easily moved to a different server and only requires a small change to the config file. Likewise images and other static files can be moved to alternative servers (see content offloading). Amazon's Elastic Load Balancer can help spread traffic across multiple web servers but requires a higher level of expertise. If you're employing multiple database servers, the HyperDB class provides a drop-in replacement for the standard WPDB class, and can handle multiple database servers in both replicated and partitioned structures. Hardware Performance Your hardware capability will have a huge impact on your site performance. The number of processors, the processor speed, the amount of available memory and disk space as well as the disk storage medium are important factors. Hosting providers generally offer higher performance for a higher price. Geographical distance The distance between your server and your website visitors also has an impact on performance. A Content Delivery Network or CDN can mirror static files (like images) across various geographic regions so that all your site visitors have optimal performance. Server Load The amount of traffic on your server and how it's configured to handle the load will have a huge impact as well. For example, if you don't use a caching solution, performance will slow to a halt as additional page requests come in and stack up, often crashing your web or database server. If configured properly, most hosting solutions can handle very high traffic amounts. Offloading traffic to other servers can also reduce server load. Abusive traffic such as login Brute Force attacks, image hotlinking (other sites linking to your image files from high traffic pages) or DoS attacks can also increase server load. Identifying and blocking these attacks is very important. Software version & performance Making sure you are using the latest software is also important, as software upgrades often fix bugs and enhance performance. Making sure you're running the latest version of Linux (or Windows), Apache, MySQL/MariaDB and PHP is very important. WordPress Configuration Your theme will have a huge impact on the performance of your site. A fast, lightweight theme will perform much more efficiently than a heavy graphic-laden inefficient one. The number of plugins and their performance will also have a huge impact on your site's performance. Deactivating and deleting unnecessary plugins is a very important way to improve performance. Keeping up with WordPress upgrades is also important. Size of Graphics Making sure the images in your posts are optimized for the web can save time, bandwidth and increase your search engine ranking. Performance testing tools Webpagetest is a tool for testing real life website performance from different locations, browsers and connection speeds. Google PageSpeed Insights is way to measure your WordPress site's performance and receive clear, specific feedback on how to make improvements. The built-in browser developer tools (ie. Firefox or Chrome) all have performance measurement tools. How to improve performance in WordPress Optimizing Your WordPress Website Minimizing Plugins The first and easiest way to improve WordPress performance is by looking at the plugins. Deactivate and delete any unnecessary plugins. Try selectively disabling plugins to measure server performance. Is one of your plugins significantly affecting your site's performance? Look at the plugin documentation or ask for support in the appropriate plugin support forum. Optimizing content Image Files Are there any unnecessary images? (e.g. Can you replace some of the images with text?) Make sure all image files are optimized. Choose the correct format (JPG/PNG/GIF) and compression for each image. Total File Number/Size Can you reduce the number of files needed to display the average page on your site? When still using HTTP1, it's recommended to combine multiple files in a single optimized file. Minify CSS and JavaScript files. You can also offload content to optimize your theme. Upgrade Hardware Paying more for higher service levels at your hosting provider can be very effective. Increasing memory (RAM) or switching to a host with Solid State Drives (SSD) e.g. Digital Ocean can make a big difference. Increased number of processors and processor speed will also help. Where possible, try to separate services with different functions - like HTTP and MySQL - on multiple servers or VPS-es. Optimize Software Make sure you are running the latest operating system version e.g. Linux, Windows Server and the latest web server e.g. Apache or IIS, database e.g. MySQL server and PHP. Perhaps you are unable to perform the tasks, and follow up on the tips, below. Just ask your hosting provider to do them for you. A good hosting provider will upgrade or move your account to an upgraded server, to match the recommendations. If needed you can switch to a managed WordPress hosting solution. DNS: Don't run a DNS on your WordPress server. Use a commercial service for DNS such as Amazon's Route 53 or your domain registrar's free offering. Using a service such as Amazon can also make switching between backup servers during maintenance or emergencies much easier. It also provides a degree of fault tolerance. If you host your DNS on external servers this will reduce the load on your primary web server. It's a simple change, but it will offload some traffic and cpu load. Web Server: Your web server can be configured to increase performance. There are a range of techniques from web server caching to setting cache headers to reduce load per visitor. Search for your specific web server optimizations (for example, search for "apache optimization" for more info). Some web servers have higher speed versions you can pay for such as Apache Litespeed. There are also a number of ways to tune Apache for higher performance based on your particular hosting and site configuration, e.g. Memcache. PHP: There are various PHP accelerators available which can dramatically improve performance of your PHP files. This will apply to all PHP files, not just your WordPress installation. Search for PHP optimization for more information, f.e. APC or OPcache. The W3 Total Cache plugin, described below, offers integrated support for Memcache, APC and other Opcode caching. MySQL/MariaDB: MySQL or MariaDB optimization is a black art in itself. A few simple changes to the query cache settings can have a dramatic effect on WordPress performance because WordPress repeats a lot of queries on every request. Nowadays, with InnoDB being the default storage engine for MySQL, you have to make sure to use that. InnoDB can be optimized and fine-tuned, search for "mysql optimization", "mysql innodb performance" or "innodb optimization" or for more information and examples. Search for "mysql convert myisam to innodb" for information on how to convert older MyISAM tables to InnoDB. A great example of how WordPress has been optimized was presented by Iliya Polihronov at WordCamp San Francisco 2012. Iliya does, among other things, server optimization for WordPress.com. Don't run a mail server on your WordPress server. For your contact form, use something like Contact Form 7 with free Mailgun. Caching Caching Plugins Plugins like W3 Total Cache or WP Super Cache can be easily installed and will cache your WordPress posts and pages as static files. These static files are then served to users, reducing the processing load on the server. This can improve performance several hundred times over for fairly static pages. When combined with a system level page cache such as Varnish, this can be quite powerful. If your posts/pages have a lot of dynamic content configuring caching can be more complex. W3 Total Cache W3 Total Cache (W3TC) is the latest generation in WordPress performance plugins, combining the research of web development authorities to provide an optimal user experience for WordPress sites. These detailed guides walk you through W3TC is unique in its ability to optimize server side and client side performance, adding functionality otherwise unavailable natively: Page Caching: W3TC helps to decrease response time by creating static HTML versions of pages, allowing web servers to serve them without invoking PHP. It automatically updates the cache when comments are made or pages are edited. Minification: Removes unnecessary characters from HTML, CSS and JavaScript files, then respectively combines them before applying HTTP compression on the cached files. Database Caching: Database queries (objects) are also cached, allowing many sites to reduce the time needed to generate new pages. This is especially useful for sites that receive a lot of comments. Headers: W3TC manages the headers (entity tag, cache-control, expires) which control the caching of files in web browsers, reducing server load and improving the user's perceived performance. Content Delivery Network (CDN): Using a CDN allows you to Offloading resources from your hosting account. W3TC moves the requests for images, CSS, JavaScript and other static files to a network of high performance servers. The server closest to the visitor is automatically used to download the files, providing the fastest downloads possible. W3TC can be used to optimize WordPress in both single- and multi-server environments through either shared or dedicated hosting. WP Super Cache WP Super Cache is a static page caching plugin for WordPress. It generates HTML files that are served directly by Apache without processing comparatively heavy PHP scripts, helping you to make significant speed gains on your WordPress blog. Using WP Super Cache allows your server to serve cached HTML pages at the same speed it serves regular graphic files. Consider WP Super Cache if your site is struggling to cope with its daily number of visitors, or if it appears on Digg.com, Slashdot.org or any other popular site. Server-side Caching Web server caching' is more complex but is used in very high traffic sites. A wide range of options are available, beyond the scope of this article. The simplest solutions start with the server caching locally while more complex and involved systems may use multiple caching servers (also known as reverse proxy servers) "in front" of web servers where the WordPress application is actually running. Adding an opcode cache like Alternative PHP Cache (APC) to your server will improve PHP's performance by many times. Varnish Cache works in concert with W3 Total Cache to store pre-built pages in memory and serve them quickly without requiring execution of the Apache, PHP, WordPress stack. As described within, using a plugin for comments such as Disqus instead of native WordPress comments can assist Varnish by not requiring your readers to login to WordPress and increasing the number of page views that Varnish can serve out of the cache. Browser Caching Browser caching can help to reduce server load by reducing the number of requests per page. For example, by setting the correct file headers on files that don't change (static files like images, CSS, JavaScript etc) browsers will then cache these files on the user's computer. This technique allows the browser to check to see if files have changed, instead of simply requesting them. The result is your web server can answer many more 304 responses, confirming that a file is unchanged, instead of 200 responses, which require the file to be sent. Look into HTTP Cache-Control (specifically max-age) and Expires headers, as well as Entity Tags for more information. W3 Total Cache integrates support for browser caching and ETags. Further Reading W3 Total Cache Plugin (by Dougal Campbell) Holy Shmoly!: WP Super Cache Best Practices for Speeding Up Your Web Site - Expires / Cache-Control Header and ETags (by Yahoo! Developer Network) WebSiteOptimization.com: Use Server Cache Control to Improve Performance Content Offloading Use a content Delivery Network (CDN) Using a CDN can greatly reduce the load on your website. Offloading the searching and delivery of images, javascript, css and theme files to a CDN is not only faster but takes great load off your WordPress server's own app stack. A CDN is most effective if used in conjunction with a WordPress caching plugin such as W3TC, described above. CloudFlare is a popular Content Delivery Network, which also offers Internet Security services. Plans start from free, but additional features are available for extra costs. CloudFlare is a fixed-cost CDN, meaning they charge by features instead of usage. CloudFlare allows you to route your sites traffic through their network before coming back to your origin host. Amazon Cloudfront uses the Amazon S3 service to provide Content Delivery Network (CDN) functionality for your static files. A CDN is a service which caches your static files on numerous web servers around the world. Providing faster download performance for your users no matter where they are. It's recommended that you use Cloudfront in tandem with S3 and not only S3 alone; the costs are not significantly different. MaxCDN is a pay-per-usage Content Delivery Network (CDN) similar to Amazon Cloudfront. Among the differences are support for Video-on-demand as well as "mirroring" (no uploading required) of files, although you can upload them if you prefer. Another alternative CDN provider is KeyCDN. They provide step-by-step WordPress integration guides on their support page. KeyCDN and MaxCDN are among the most affordable CDN options available, they're able to beat the pricing of competitors like Amazon because they are a division of a much larger CDN Providers. Static Content Any static files can be offloaded to another server. For example, any static images, JavaScript or CSS files can be moved to a different server. This is a common technique in very high performance systems (Google, Flickr, YouTube, etc) but can also be helpful for smaller sites where a single server is struggling. Also, moving this content onto different hostnames can lay the groundwork for multiple servers in the future. Some web servers are optimized to serve static files and can do so far more efficiently than more complex web servers like Apache, for example lighttpd. Amazon Simple Storage Service (S3) is a dedicated static file hosting service on a pay-per-usage basis. With no minimum costs, it might be practical for lower traffic sites which are reaching the peak that a shared or single server can handle. Multiple Hostnames There can also be user improvements by splitting static files between multiple hostnames. Most browser will only make 2 simultaneous requests to a server, so if you page requires 16 files they will be requested 2 at a time. If you spread that between 4 host names they will be requested 8 at a time. This can reduce page loading times for the user, but it can increase server load by creating more simultaneous requests. Also, known is "pipelining" can often saturate the visitor's internet connection if overused. Offloading images is the easiest and simplest place to start. All images files could be evenly split between three hostnames (assets1.yoursite.com, assets2.yoursite.com, assets3.yoursite.com for example). As traffic grows, these hostnames could be moved to your own server. Note: Avoid picking a hostname at random as this will affect browser caching and result in more traffic and may also create excessive DNS lookups which do carry a performance penalty. Likewise any static JavaScript and CSS files can be offloaded to separate hostnames or servers. Feeds Your feeds can quite easily be offloaded to an external service. Feed tracking services like Google FeedBurner will do this automatically, the Feedburner servers will handle all the feed traffic and only update the feed from your site every few minutes. This can be a big traffic saver. Likewise you could offload your own feeds to a separate server (feeds.yoursite.com for example) and then handle your own feed stats / advertising. Further Reading Using Amazon S3 / Cloudfront to offload images: Amazon S3 and CloudFront with WordPress, Reducing Your Website's Bandwidth Usage Compression There are a number of ways to compress files and data on your server so that your pages are delivered more quickly to readers' browsers. W3 Total Cache described above integrates support for most of the common approaches to compression. W3 Total Cache supports Minify and Tidy to compress and combine your style sheets and javascript files. It also supports output compression such as zlib, see also Output Compression. It's also important to compress your media files - namely images. The WP Smushit plugin can help with this. Database Tuning Cleaning Your Database The WP Optimize plugin can help you reduce extra clutter in your database. You can also instruct WordPress to minimize the number of revisions that it saves of your posts and pages. Adding Servers While it requires additional expertise, adding servers can be a powerful way to increase performance. I highly recommend reading Architecting a Highly Scalable WordPress Site in AWS A guide for building a more expensive, highly scalable AWS implementation using Amazon's Relational Data Store (RDS). You can use Amazon's Elastic Load Balancer to spread traffic across multiple web servers and you can use HyperDB or Amazon's RDS to run more scalable or multiple database servers. Additional Resources Further Reading High Traffic Tips for WordPress 10 Practical Tips To Optimize WordPress hosting 16 Quick Tips to Improve WordPress Performance – INFOGRAPHIC 17 Ways to Optimize and Speed Up WordPress Sites 11 Ways to Speed Up WordPress On a quest for ultimate website performance WordPress Optimization Infographic 21 easy tweaks to make your WP site load faster How to Speed Up WordPress Website with Image Optimization Speeding up WordPress load from 4.23s to 1.33s (Case Study) 10 tips for better WordPress optimization How To Make Your Site Lightning Fast* By Compressing (deflate/gzip) Your HTML, Javascript, CSS, XML, etc In Apache Yahoo! Developer Network: Exceptional Performance WordCamp Performance Presentations High Performance WordPress = Iliya Polihronov WordPress Optimization from WordCamp Israel 2013 WordCamp 2007 Video of the Presentation on HyperDB and High Performance Copy of the Slides on HyperDB and High Performance 50 tips su Web Performance Optimization per siti ad alto traffico WordCamp Bologna (Italy) 2013 Optimization - Caching atachibana — Sun, 17 Jul 2016 04:06:00 +0000 This article is part of a series on WordPress Optimization. WordPress caching is the fastest way to improve performance. If your site is getting hit right now install W3 Total Cache, WP Super Cache or Cache Enabler. Caching Plugins Plugins like W3 Total Cache, WP Super Cache and Cache Enabler can be easily installed and will cache your WordPress posts and pages as static files. These static files are then served to users, reducing the processing load on the server. This can improve performance several hundred times over for fairly static pages. When combined with a system level page cache such as Varnish, this can be quite powerful. If your posts/pages have a lot of dynamic content configuring caching can be more complex. Search for "WordPress cache plugin" for more info. Browser Caching Browser caching can help to reduce server load by reducing the number of requests per page. For example, by setting the correct file headers on files that don't change (static files like images, CSS, JavaScript etc) browsers will then cache these files on your visitor's computer. This technique allows the browser to check to see if files have changed, instead of simply requesting them. The result is your web server can answer many more 304 responses, confirming that a file is unchanged, instead of 200 responses, which require the file to be sent. Look into HTTP Cache-Control (specifically max-age) and Expires headers, as well as Entity Tags for more information. Server Caching Web server caching is more complex but is used in very high traffic sites. A wide range of options are available, beyond the scope of this article. The simplest solutions start with the server caching locally while more complex and involved systems may use multiple caching servers (also known as reverse proxy servers) "in front" of web servers where the WordPress application is actually running. Adding an opcode cache like Opcache, or WinCache on IIS, to your server will improve PHP's performance by many times. Varnish cache is very powerful when used with a WordPress caching plugin such as W3TC. Further Reading W3 Total Cache Plugin (by Dougal Campbell) Holy Shmoly!: WP Super Cache Core Caching Concepts in WordPress Best Practices for Speeding Up Your Web Site - Expires / Cache-Control Header and ETags (by Yahoo! Developer Network) WebSiteOptimization.com: Use Server Cache Control to Improve Performance Twenty Fifteen atachibana — Sun, 17 Jul 2016 04:14:46 +0000 Twenty Fifteen is the default theme for WordPress in 2015. It is super-clean, content-focused, and designed to bring a little more simplicity to our blogs. Its careful attention to typography, featuring the expertly-designed Noto font set in elegant and harmonious margins, makes it beautiful in multiple languages around the world. Twenty Fifteen looks great on devices of all sizes, from desktop to mobile and everything in between. The theme adapts to any screen without sacrificing usability or design integrity. Quick Specs (all measurements in pixels) The main content width is 660px. The sidebar width is 248px. Featured Images are 825px wide by 510px high. There are a few ways that you can customize Twenty Fifteen, all from WordPress' Customizer. This short guide will show you how to: choose a featured color scheme add descriptions to your menus add social icons in your menu Choose a Featured Color Scheme Twenty Fifteen has six color schemes you can use to change the look of your blog. The Default color scheme is a light gray, but you can also choose from Dark, Yellow, Pink, Purple, and Blue. To choose your color scheme, go to Appearance > Customize. Under "Colors", select your preferred color scheme from the drop down: You'll see the color scheme change in the preview pane to the right. When you're done, click Save and Publish. Add Menu Descriptions Twenty Fifteen has a menu design that’s easy to navigate, especially when you add menu descriptions. To start adding descriptions to your menus, go to Appearance > Menus and click the Screen Options tab in the upper right of the screen. In the "Show advanced menu properties" section, check the box next to Description. Now you can begin adding descriptions to any link in a menu. When you're done, click Save Menu. Add Social Icons Twenty Fifteen also allows you to display links to your social media profiles with crisp, perfectly-sized icons. You can see these icons at the bottom of the menu displayed in the previous section. The first step is to go to Appearance > Menus and create a new menu - you can name your menu anything you like. You will then add the URL for each social profile to your menu as a custom link. When you have added all desired links, click Save Menu. Now that you have created your menu and added your social links, go to the Manage Locations tab and next to "Social Links Menu", select the social icons menu you just created from the drop down. Click Save Changes when you’re done. Available icons Linking to any of the following sites will automatically display its icon in your menu: CodePen Digg Dribbble Dropbox Email (mailto: links) Facebook Flickr Foursquare GitHub Google+ Instagram LinkedIn Path Pinterest Pocket Polldaddy Reddit RSS Feed (URLs with /feed/ Spotify Skype StumbleUpon Tumblr Twitch Twitter Vimeo WordPress YouTube What else can you do? You can also use the Customizer to make the following changes to your website: Change your Custom Header image Featured Images: works best with images that are 825px wide by 510px high Change the background image or color Set a static front page Links Twenty Fifteen Demo and Download Twenty Fifteen Changelog Uploading WordPress to a remote host atachibana — Sun, 17 Jul 2016 04:55:26 +0000 [codex_languages en="Uploading WordPress to a remote host" fr_codex="Charger_WordPress_sur_un_serveur_distant" it_codex="Caricare WordPress su un host remoto" ja_codex="Uploading WordPress to a remote host" ptbr_codex="Enviando o WordPress para o servidor"] (This is part 2 of the Using FileZilla guide.) To upload (or delete) files and folders to your web host, you will need an FTP application. One of many free options that are at your disposal is FileZilla. Though written using screenshots from a Windows XP machine, using FileZilla, the following instructions carry over to just about every FTP client with a GUI (Graphical User Interface). You may want to read how to Set up FileZilla for your server, before you read the following. Uploading Files How your server is setup differs from host to host. The screen shots you see here show two generic hosts: [caption id="attachment_1137" align="alignnone" width="300"] Figure 1: Host example #1[/caption] [caption id="attachment_1136" align="alignnone" width="300"] Figure 2: Host example #2[/caption] Your screen could have htdocs or public_html where the screenshots show mainwebsite_html. To install WordPress double-click the one that is web-root directory for webpages on your server. This is usually named htdocs, public_html, mainwebsite_html, www, web, or something very similar. The other folders are not of consequence in installing WordPress. You should now see listing of files and folders that are contained inside your server's root folder. Just how many there are depends on what and how much you have on your website. The point of this exercise is to upload WordPress, so let us continue down that road: Right click in the Remote Site window: [caption id="attachment_1135" align="alignnone" width="400"] Figure 3 : Server window[/caption] Click Create Directory, enter the name you want, and click Okay. NOTE: The name you choose will be where your WordPress weblog will appear, and although it can be changed later, it's much better to avoid that by choosing what you want now. For example, if your website has the URL http://example.com and you want your weblog to be located at http://example.com/blog, then name the new folder blog. In this example, we have created the directory blog. [caption id="attachment_1134" align="alignnone" width="256"] Figure 4 : Newly created directory[/caption] Now the directory blog has been made, double-click on it to open it. [caption id="attachment_1133" align="alignnone" width="406"] Figure 5 : The new and empty directory[/caption] Nothing there yet ... but note the folder with the dots following it -- clicking that takes you back up a folder level. Upload WordPress Before you begin to upload WordPress, it is essential to have downloaded WordPress, and unzipped it, on your local computer. When you unzip the downloaded .zip file, a folder called wordpress will be created. Please note the location of this folder in your computer. You may also want to prepare the downloaded files for installation, by reading Installing WordPress and completing the relevant steps, such as editing wp-config-sample.php. In the top window of Local Site group, find your way to where you have the WordPress folder on your computer after unzipping the zip file that you downloaded. [caption id="attachment_1132" align="alignnone" width="383"] Figure 6 : Folder navigation - top window[/caption] When you have found it and clicked the wordpress folder, the window underneath that will show the contents of said folder: [caption id="attachment_1131" align="alignnone" width="382"] Figure 7 : Folder navigation - bottom window[/caption] Hold the SHIFT key , and press the DOWN arrow on the keyboard to highlight all the files and folders in that window. Now RIGHT-click, and choose Upload from the menu. Now watch ...... everything should be uploaded straight to your website. Once that has happened, then whatever is in the server window should be on your computer window. The blog folder on the server, and the wordpress folder on your computer should be identical with regards to the contents. Click on folders -- such as wp-admin -- in both windows and check that each window has the same list of files and folders. [caption id="attachment_1130" align="alignnone" width="509"] Figure 8 : Files in each folder should be the same[/caption] This concludes the guide for uploading files to your server, using an FTP client, FileZilla, especially with regard to installing WordPress. You may want to read more about Changing File Permissions and seeing hidden files on the server. Upgrading WordPress - Extended Instructions atachibana — Sun, 17 Jul 2016 06:42:49 +0000 This page contains a more detailed version of the upgrade instructions. Detailed Instructions Overview of the Upgrade Process Backup your database. Read Backing Up Your Database for a detailed explanation. Backup ALL your WordPress files in your WordPress directory. Don't forget your .htaccess file. Verify the backups you created are there and usable. This is essential. Deactivate ALL your Plugins. Ensure first four steps are completed. Do not attempt the upgrade unless you have completed the first four steps. Download and extract the WordPress package from http://wordpress.org/download/. Delete the old WordPress files on your site, but DO NOT DELETE *wp-config.php file; *wp-content folder; Special Exception: the wp-content/cache and the wp-content/plugins/widgets folders should be deleted. *wp-images folder; *wp-includes/languages/ folder--if you are using a language file do not delete that folder; *.htaccess file--if you have added custom rules to your .htaccess, do not delete it; *robots.txt file--if your blog lives in the root of your site (ie. the blog is the site) and you have created such a file, do not delete it. Upload the new files from your computer's hard drive to the appropriate WordPress folder on your site. Run the WordPress upgrade program and follow the instructions on the screen. Update Permalinks and .htaccess. Update your Permalink Structure and merge the custom rules, if necessary, into your .htaccess file. Install updated Plugins and Themes. Please review the list of Plugins that work in Version {{CurrentVersion}}. Check for Theme Compatibility with {{CurrentVersion}} and ask your Theme author for any new version. Reactivate Plugins Add security key definitions to the wp-config.php file Review what has changed in WordPress. That's the overview of the upgrade process. Please continue reading the Detailed Upgrade Instructions. Remember, if you do encounter problems, re-read the Instructions below to insure you've followed the proper procedures and consult Troubleshooting: Common Installation Problems. Upgrading Across Multiple Versions While the methodology given below is the "safe" approach, as long as you have proper backups, then it is indeed possible to upgrade directly from the very first version of WordPress to the very latest version in one-easy-step. WordPress does support this process, and WordPress is extremely backwards compatible in this respect. That said, if you have a large site, the upgrade process may take longer than expected, in which case an incremental approach may help. Just remember to retain a backup of a working site so that you always have a fallback position. If you plan on upgrading across more than two major releases, you should consider upgrading incrementally to avoid potential conflicts and minimize the risks of database damage. For example, if you plan on upgrading from 2.5 to {{CurrentVersion}}, upgrade to 2.7 first, followed by 2.9, then 3.1, and so on. Essentially, it's okay to skip one release, but never skip TWO when upgrading. Older versions of WordPress can be downloaded from the release archive. Please note that WordPress 3.7 introduced an easy to use one-button updater which will take you directly to {{CurrentVersion}}. This update step is safe, and it is possible to one-click update from 3.7 to any later version. Step 1: Back up your database Perform a backup of your database. All of your WordPress data, such as Users, Posts, Pages, Links, and Categories, are stored in your MySQL database. Please read Backing Up Your Database for a detailed explanation of this process. It is extremely important to back up your database before beginning the upgrade. If, for some reason, you find it necessary to revert back to the 'old' version of WordPress, you may have to restore your database from these backups. Step 2: Back up ALL your WordPress files Back up ALL of your files in your WordPress directory and your .htaccess file. Typically, this process involves using an FTP program to download ALL your WordPress files from your host to your local computer. Please read Backing Up Your WordPress Site for further explanation. If you have made changes to any core WordPress files, or if you've got customized Plugins or Themes, you will want to have a good backup of those files. It is extremely important to back up your files before beginning the upgrade. If for some reason you find it necessary to revert back to the 'old' version of WordPress you will need to upload these files. Step 3: Verify the backups Verify that the backups you created are there and usable. This is the most important step in the upgrade process! The verification process involves making sure you can see the backup files on your local computer (or wherever you've stored them) and that you can navigate into any sub-folders. If the files are in a zip file, make sure you can open the zip file. Also consider opening a .sql file in an editor to see if the tables and data are represented. Step 4: Deactivate ALL your Plugins In your Administration Screen, under the Plugins choice, deactivate any Plugins. Because of the changes to WordPress, some Plugins may conflict with the upgrade process. If you're not able to access the administrative menus you can deactivate all plugins by resetting the plugins folder. Step 5: Ensure first four steps are completed If you have not completed the first four procedures, STOP, and do them! Do not attempt the upgrade unless you have completed the first four steps. The best resource for problems with your upgrade is the WordPress Support Forums, and if you have problems, the volunteers at the WordPress Support Forums will likely ask if you have completed the first four steps. Step 6: Download and extract the WordPress package Download and unzip the WordPress package from https://wordpress.org/download/. If you will be uploading WordPress to a remote web server, download the WordPress package to your computer with your favorite web browser and unzip the package. If you have shell access to your web server, and are comfortable using console-based tools, you may wish to download WordPress directly to your web server. You can do so using wget , lynx or another console-based web browser, which are valuable if you want to avoid FTPing. Place the package in a directory parallel to your current wordpress directory (like "uploads," for example). Then, unzip it using: gunzip -c wordpress-{{CurrentVersion}}.tar.gz | tar -xf - or by using: tar -xzvf latest.tar.gz The WordPress package will be extracted into a folder called wordpress. Step 7: Delete the old WordPress files Why Delete? Generally, it is a good idea to delete whatever is possible because the uploading (or upgrading through cPanel) process may not correctly overwrite an existing file and that may cause problems later. DO NOT DELETE these folders and files: wp-config.php file; wp-content folder; wp-includes/languages/ folder--if you are using a language file, and it is here rather than in wp-content/languages/, do not delete this folder (you might want to move your language files to wp-content/languages/ for easier upgrading in the future);. .htaccess file--if you have added custom rules to your .htaccess, do not delete it; Custom Content and/or Plugins--if you have any images or other custom content or Plugins inside the wp-content folder, do NOT delete them. Delete these Files and Folders: wp-* (except for those above), readme.html, wp.php, xmlrpc.php, and license.txt; files; Typically files in your root or wordpress folder. Again, don't delete the wp-config.php file. Note: some files such as wp.php may not exist in later versions such as 2.7. wp-admin folder; wp-includes folder; If you have a language file here, remember not to delete the wp-includes/languages/ folder wp-content/cache folder; You only see this folder if you are upgrading FROM WordPress 2.0. wp-content/plugins/widgets folder; You only see this folder if you previously installed the Sidebar Widgets plugin. The Sidebar Widgets code conflicts with the built-in widget ability. How to Delete? There are several ways to delete the files from your WordPress site. You can use your FTP Client, or if you have access to Telenet or SSH you can use that. Some host providers also provide the ability to delete files and folders. Using FTP to delete files and folders The same FTP client you use for uploading can be used to delete files and folders. If your FTP client does not appear to permit you to delete non-empty folders, check the available options for your FTP client. You'll usually find an option that permits deleting non-empty folders. Deleting non-empty folders is a quick and thorough method cleaning out an old installation of WordPress. It is recommended that once the deleting is done, you switch back to the original setting for safety reasons. Using Telnet or SSH to delete file If you have a command-line login (telnet or ssh), you can enter the following commands to make backup copies of the files you need to keep and to delete ONLY the wordpress files in your directory (plus .htaccess). If you've customized other files (like index.php) not included by the cp commands below, copy them as well: * mkdir backup * cp wp-config.php .htaccess backup * cp -R wp-content backup * rm wp*.php .htaccess license.txt readme.html xmlrpc.php * rm -rf wp-admin wp-includes * cp backup/wp-config.php . * After you have finished with the upgrade, you can restore any customizations to your templates or plugins from your backup directory. For example, use cp backup/index.php . to restore index.php. Alternatively, using SSH, you could copy wp-config.php, .htaccess, and any content files you've added or altered into the new wordpress directory. Then, rename the old one (to archive it), and move the new one into its place. Step 8: Upload the new files With the new upgrade on your local computer, and using FTP, upload the new files to your site server just as you did when you first installed WordPress. See Using FileZilla and Uploading WordPress to a remote host for detailed guidelines in using an FTP Client to upload. NOTE: If you did not delete the wp-content folder, you will need to overwrite some files during the upload. The wp-content folder holds your WordPress Themes and Plugins. These should remain. Upload everything else first, then upload only those WordPress files that are new or changed to your new wp-content folder. Overwrite any old versions of default plugins with the new ones. The WordPress default theme has changed so you will want to upload the wp-content/themes/default folder. If you have custom changes to the default theme, those changes will need to be reviewed and installed after the upgrade. Step 9: Run the WordPress upgrade program Using a web browser, go to the WordPress admin pages at the normal /wp-admin location. WordPress will check to see if a database upgrade is necessary, and if it is, it will give you a new link to follow. This link will lead you to run the WordPress upgrade script by accessing wp-admin/upgrade.php. Follow the instructions presented on your screen. Note: Make sure the database user name registered to WordPress has permission to create, modify, and delete database tables before you do this step. If you installed WordPress in the standard way, and nothing has changed since then, you are fine. If you want to run the upgrade script manually: If WordPress is installed in the root directory, point your browser to: http://example.com/wp-admin/upgrade.php If WordPress is installed in its own subdirectory called blog, for example, point your browser to: http://example.com/blog/wp-admin/upgrade.php If you experience difficulties with login after your upgrade, it is worth clearing your browser's cookies. Step 10: Update Permalinks and .htaccess In your Administration Screen > Settings > Permalinks screen update your Permalink Structure and, if necessary, place the rules in your .htaccess file. Also see Using Permalinks for details regarding Permalinks and the .htaccess file. Step 11: Install updated Plugins and Themes Please review the Plugin Compatibility List and Theme Compatibility List, or plugin/theme authors, to find plugins and themes compatible with your new WordPress version. Upload and install new versions of your Plugins and Themes, if necessary. Step 12: Reactivate Plugins Use your Administration Screen, Plugins, to activate your Plugins. If your plugins do not appear on the Plugin Compatibility List and you are not sure if they will work correctly with the new version, activate each plugin, one at a time, and test that there are no problems before continuing. Step 13: Add security key definitions to the ''wp-config.php'' file Beginning with WordPress Version 2.6, three (3) security keys, AUTH_KEY, SECURE_AUTH_KEY, and LOGGED_IN_KEY, are used to insure better encryption of information stored in the user's cookies. Beginning with Version 2.7 a fourth key, NONCE_KEY, was added to this group. If you don't find the keys in your wp-config.php file, add the keys definitions with reference to Editing wp-config.php - Security Keys, and upload to your server. Step 14: Review what has changed in WordPress Please review these resources to see what's new in WordPress: Version {{CurrentVersion}} Details Complete version history including Development News Special note for Fantastico Upgrades When using the Fantastico upgrade process to upgrade from a pre-Version 2.2, Fantastico will use the wp-config-sample.php file to regenerate a new wp-config.php file. By doing this, two new values, DB_CHARSET and DB_COLLATE, are placed into the wp-config.php file. Those lines should be deleted from your wp-config.php if you are upgrading from a pre-Version 2.2 (like 2.0.10 or 2.1.3) to Version {{CurrentVersion}}. A detailed explanation about DB_CHARSET and DB_COLLATE can be found in Editing wp-config.php. Troubleshooting Scrambled Layout or Errors If your blog looks scrambled now or features line errors, an old plugin that doesn't work with the new code may be the culprit. In your WordPress Administration Screen, deactivate all plugins that do not come with WordPress by default. Re-activate them one by one. Made Custom Changes/Hacks? If you have made changes to other WordPress files ("hacked" WordPress), you are supposed to keep track of your changes. You will have to transfer your edits into the new code. WordPress Versions lists the files that have changed in each release. Resist Using Old Code Upgrading gives you the newest and best code. Using your old code, no matter how much you have customised it, almost certainly will cause problems. The temptation just to use your old modified code will be great, but the chances of errors are much greater. Can I Go Back to Old Versions You can, but it is usually not recommended to rollback (revert) your current version to an older version. That is because newer versions often include security updates and a rollback may put your site at risk. Second, the change between the database structure between versions may cause complications in maintaining your site content, posts, comments, and plugins that are dependent upon the information stored in the database. If you are still intent on this, proceed at your own risk. Please note, that without a backup of your entire site and your database, made prior to your upgrade attempt, a successful rollback is near impossible. Delete all WordPress files except for wp-config. Upload the files from your backup to your server and restore your database backup. Remember, you must have good backups for the rollback to work. For older WordPress versions, a rollback might not work. Get More Help If you get any errors following an upgrade, check Troubleshooting: Common Installation Problems, Troubleshooting, and the Codex Installation Category of Articles. If you can't find an answer, post a clear question on the WordPress Suppport Forums. You will be asked if you have used any old code. You'll be told to change it then, so you may as well change it now :) Search Engine Optimization atachibana — Sun, 17 Jul 2016 06:59:20 +0000 WordPress, straight out of the box, comes ready to embrace search engines. Its features and functions guide a search engine through the posts, pages, and categories to help the search engine crawl your site and gather the information it needs to include your site within its database. WordPress comes with several built in search optimization tools, including the ability to use .htaccess to create apparently static URLs called permalinks, blogrolling, and pinging. There are also a number of third party plugins and hacks which can be used for search engine optimization (SEO). However, once you start using various WordPress Themes and customizing WordPress to meet your own needs, you may break some of those useful search engine friendly features. To maintain your WordPress site's optimal friendliness towards search engine spiders and crawlers, here are a few tips: Good, Clean Code Make sure your site's code validates. Errors in your code may prevent a search engine from moving through the site successfully. Content Talks Search engines can't "see" a site. They can only "read" a site. Looks do not talk to a search engine. What "talks" to a search engine are the words, the content, the material in your site that explains, shares, informs, educates, and babbles. Make sure you have quality word content for a search engine to examine and compare with all the parts and pieces to give you a good "score". Write Your Content with Searchers in Mind How do you find information on the Internet? If you are writing something that you want to be "found" on the Internet, think about the words and phrases someone would use to find your information. Use them more than once as you write, but not in every sentence. Learn how search engines scan your content, evaluate it, and categorize it so you can help yourself get in good favor with search engines. Content First A search engine enters your site and, for the most part, ignores the styles and CSS. It just plows through the site gathering content and information. Most WordPress Themes are designed with the content as close to the top of the unstyled page as possible, keeping sidebars and footers towards the bottom. Few search engines scan more than the first third of the page before moving on. Make sure your Theme puts the content near the top. Keywords, Links, and Titles Meet Content Search engines do not evaluate your site on how pretty it is, but they do evaluate the words and put them through a sifter, giving credit to certain words and combinations of words. Words found within your document are compared to words found within your links and titles. The more that match, the better your "score." Content in Links and Images Your site may not have much text, mostly photographs and links, but you have places in which to add textual content. Search engines look for alt and title in link and image tags. While these have a bigger purpose of making your site more accessible, having good descriptions and words in these attributes helps provide more content for search engines to digest. Link Popularity It is not how good your site is, it is how good the sites are that link to you. This still holds weight with search engine favoritism. It's about who links to you. Blogrolls, pingbacks, and trackbacks are all built into WordPress. These help you link to other people, which gives them credit, but it also helps them link to you, connecting the "links." The number of incoming links your site has that have been recognized by Google can be checked by typing link:www.yoursite.com into Google (other search engines have similar functions). Other ways to generate incomming links to your site include: Add your site's url to your signature on forum posts on other sites. Submit your site to directories (see below). Note: Leaving comments on blogs will not help with this, since all modern blogging tools use the rel="nofollow" attribute. Don't be a comment spammer. Good Navigation Links A search engine crawls through your site, moving from page to page. Good navigational links to the categories, archives, and various pages on your site will invite a search engine to move gracefully from one page to another, following the connecting links and visiting most of your site. Get the Blog Indexed in Google Search Before getting to the details on how you can get Google to recognize you, we need to first understand these three terms: The Googlebot: This is the software used to search that is used by Google to gather new information that has been uploaded online so that it can be fed on Google pages. Once information that you had uploaded is picked up by this software, then it can be found on Google pages. Crawling: This is the process where the above named software, Googlebot, roams from site to site detecting any new information to be uploaded on Google. This software works by going through new links that have been uploaded recently and which are generating a lot of traffic. Indexing: Once the information has been gathered by the Googlebot through the process called crawling, it is processed through another process called indexing. It is through this process that the quality of content is determined so that they can be placed appropriately on Google pages. The question now is, how exactly does Googlebot find this information? Firstly, it starts by siting the web pages that it had cited in the previous search. It then detects new pages associated with those old ones or just new ones all together. More details on the same would be found on Search Console help for those who are interested in the same. Any new information is cited with the help of sitemaps and links that lead to those articles. Read more on How to Get Your Blog Indexed in Google Search Search Engine Site Submissions There are many resources that will "help" you submit your site to search engines. Some are free, some for a fee. Or you can manually submit your site to search engines yourself. Whatever method you choose to use, once your site has been checked for errors and is ready to go, search engines will welcome your WordPress site. Here are some tips for successful site submissions: Make sure you have content for search engines to scan. In general, have more than 10 posts on your site to give the search engines something to examine and evaluate. Do not submit your site to the same search engine more than once a month or longer, depending upon their criteria, not your anxiousness to be listed. Have ready to type, or copy and paste, the title of the site, and the categories your site may belong to in a search engine directory. Have a list of your website's various "addresses/URLs" ready. You can submit your root directory as well as specific categories and feeds to search engines, expanding your search engine coverage. Keep a list of the various search engines and directories you submit to so you do not accidentally resubmit too soon, and you can keep track of how they include you among their pages and results. Directory Sites It is also useful for traffic generation and search optimization purposes to submit your site to directories. Both comprehensive directory sites and those specific to the subject or localisation of your site can be used. Search Engine Optimization Resources While WordPress comes ready for search engines, the following are more resources and information you may want to know about preparing and maintaining your site for search engines' robots and crawlers. Meta Tags Meta Tags contain information that describes your site's purpose, description, and keywords used within your site. The meta tags are stored within the head of your header.php template file. By default, they are not included in WordPress, but you can manually include them and the article on Meta Tags in WordPress takes you through the process of adding meta tags to your WordPress site. The WordPress Custom Fields option can also be used to include keywords and descriptions for posts and Pages. There are also several WordPress Plugins that can also help you to add meta tags and keyword descriptions to your site found within the Official WordPress Plugin Directory. Robots.txt Optimization Search Engines read a file at yourdomain.com/robots.txt to get information on what they should and shouldn't check. Adding entries to robots.txt to help SEO is popular misconception. Google says you are welcome to use robots.txt to block parts of your site but these days prefers you don't. Use page-level noindex tags instead, to tackle low-quality parts of your site. Since 2009, Google has been evermore vocal in its advice to avoid blocking JS & CSS files, and Google's Search Quality Team has been evermore active in promoting a policy of transparency by webmasters, to help Google verify we're not "cloaking" or linking to unsightly spam on blocked pages. Therefore the ideal robots file disallows nothing whatsoever, and may link to an XML Sitemap if an accurate one has been constructed (which itself is rare though!). WordPress by default only blocks a couple of JS files but is nearly compliant with Google's guidance here. See also: How Google Crawls My Site How do I use a robots.txt file to control access to my site? WordPress Robots.txt example and explanation from Yoast Using robots.txt for SEO Removing duplicate search engine content using robots.txt wikipedia - Robots.txt KB Robots.txt plugin for WordPress (Last updated 2007-8-14, WordPress 2.5 or below) Feed Submissions WordPress comes built-in with various feeds, allowing your site to be viewed by various feed readers. Many search engines are now accepting feed submissions, and there are many site which specialize in directories of feeds and feed services. To submit your site's feeds, you need to know the link to the various feeds your site provides. The article WordPress Feeds lists the various links of the feeds that come built into WordPress. For information on customizing these links, see the article on Customizing Feeds. Pingomatic MyPagerank Feed Shark Robin Good's RSSTop55 - Best Blog Directory And RSS Submission Sites Ari Paparo's Big List of Blog Search Engines and Feed Services Wordpress compressed all inclusive ping list Technorati Tags Technorati is a "real-time search engine that keeps track of what is going on in the blogosphere — the world of weblogs." According to the site, "Technorati tracks the number of links, and the perceived relevance of blogs, as well as the real-time nature of blogging. Because Technorati automatically receives notification from weblogs as soon as they are updated, it can track the thousands of updates per hour that occur in the blogosphere, and monitor the communities (who's linking to whom) underlying these conversations." Technorati tags are used to categorize the different topics and information used by blogs. Technorati uses WordPress categories as tags automatically. You can add more tags by adding a rel="tag" to any link on your site. For example: [code language="php"] WordPress Codex [/code] There are also several WordPress plugins for maximizing Technorati tags. Note: In WordPress v1.5.x, Technorati will automatically recognize your category names as tags. Note: For optimal Technorati listing, you should include the Atom feed in the header of your theme. For this you may use the following code, which you can add somewhere between the and tags: [code language="php"] [/code] Without adding the Atom feed to your header, your posts in Technorati will most likely be displayed wrongly. Which can result in the post content on Technorati duplicating the post title and listing other (meta) information, which is displayed between the post title and the real post content on your weblog. Permalinks Permalinks are enhancements to your existing URLs which can improve search engine optimization by presenting your post, page, and archive URLs as something like http://example.com/2003/05/23/my-cheese-sandwich/ rather than http://example.com/index.php?p=423. See Using Permalinks for more information. As search engines use links and the title as part of their information gathering, links to posts and articles within your site gain importance with Permalinks. As an added bonus, enable the Permalink Redirect plugin. This plugin "replies a 301 permanent redirect, if request URI is different from entry’s (or archive’s) permalink. It is used to ensure that there is only one URL associated with each blog entry." Sitemaps A sitemap or "site map" is a single page listing of all the posts on your website. It is intended for your visitors to get a good overview on what your site is about and to find a blog post quickly but it also has great benefits in the search engines as a good link is always pointing to all your blog posts. By having a link to your sitemap on all your sites pages both visitors and search engines will easily get to it and find all your posts. Here is a tutorial with three different examples of sitemaps with demos and how to set them up: Tutorial: Automatic Sitemap for WordPress See also: XML sitemaps and WordPress website optimization Google Sitemaps As of June 2005, Google is now accepting sitemaps of your site as part of their website submissions. Google needs to have this sitemap formatted in a special way using XML. You can find more information about Google's Sitemap Submissions from Google, and the discussion on the WordPress Forum about WordPress and Google Site maps. Some utilities have been created to help the WordPress user to create a Google site map of their site for submission to Google. For more information on these and Google sitemaps: Inside Google Sitemaps (Official Google Blog) Google Sitemap Generator Plugin for WordPress Make your sitemap human readable Simple Sitemap Generator Link Relationships There is some debate over whether listing the link relations actually effect search engine ranking however it is simple to implement. World Wide Web Consortium (W3C) Link rel Plugin More Resources and Tutorials There is a lot to learn about search engine optimization and site submission. Here are just a few sites to help you learn more about how this works: 200+ Google's Ranking Factors The Blogger's guide to SEO Beginners Guide to Search Engine Optimization WordPress SEO - The Definitive Guide to Higher Rankings for your Blog WordPress SEO - Presentation by Joost de Valk 31 Ways to Boost The SEO of Your WordPress Site SEO for WordPress Blogs - The Complete Guide More WordPress Codex Articles on Website Development All About Search Indexing Robots and Spiders 40 Actionable SEO Tips and Tricks from The Best SEO's – INFOGRAPHIC Getting Ready for Search Engine Submissions Search Engine Robots that Search Your Site Understanding Search Results Pages On-Page SEO: Anatomy of a Perfectly Optimized Page Website Development Step-by-Step The Important SEO Elements of a Web Page Blog SEO - Whitehat SEO for Bloggers in a Nutshell WordPress SEO techniques - Page sculpting Performing Effective Keyword Research On-Page SEO Checklist Translations If you have translated this article or have some similar one on your blog post a link here. Please mark Full Translated articles with (t) and similar ones with (s). WordPress için Arama Motoru Optimizasyonu (SEO) - (Türkçe) (t) SøgeMaskineOptimering (SEO) for WordPress (t) سئو و بهینه سازی وردپرس in Persian(فارسی). (t) Weblog Optimierung Suchmaschinen WP (s) Ottimizzazione delle ricerche per Wordpress (t) Оптимизация за търсачки на Wordpress ( Bulgarian Version ) (t) Search Engine Optimizacija za WordPress Platformu - Serbian version (t) پنج قدم تا شروع بهینه سازی سایت (وردپرس) برای موتورهای جست‌وجو in Persian(فارسی). (s) FAQ Layout and Design atachibana — Sun, 17 Jul 2016 07:05:59 +0000 Back to FAQ CAUTION! Many of the answers provided on this FAQ refer to outdated versions of WordPress. Use caution when following some instructions, as some specifics may have changed. In particular, be wary of instructions that direct you to edit WordPress core files. We don't do things that way any more. The best way to alter how your website looks and works is by creating your own Child Theme that overrides only the settings you want to change and interacts only as needed with WordPress (just like a Plugin does) through action and filter hooks. Since all your customizations are contained in your Child Theme, you don't have to worry about all your changes being overwritten during the next upgrade cycle. Layout and Styles I am having trouble with my CSS so where can I find help? The following are articles that will help you troubleshoot and solve many of your CSS problems: Site Design and Layout Finding Your CSS Styles CSS Fixing Browser Bugs CSS Troubleshooting WordPress CSS Information and Resources How can I choose different styles or colours for my comments? There are a variety of WordPress Plugins that change the look, layout, and colors of your comments and comment form. Look for various Comments Plugins in the Official WordPress Plugin Directory. How do I change the size of the popup comments window? To change the look of the Popup Comments window in WordPress version 1.5, make changes to the comment-functions.php file where it shows the following line: function comments_popup_script($width=400, $height=400, $file='') {. To change the look of the Popup Comments window in WordPress version 1.2.1 Mingus, make the following change to the template-functions-comment.php on line 50: [code language="php"]function comments_popup_script($width=400, $height=400, $file='wp-comments-popup.php')[/code] You can also change Line 81 of wp-comments-popup.php to alter the textarea size for people entering comments. Where can I find some other Themes and templates to use for styling my site? Official WordPress Free Themes Directory Blogging Pro features a whole category of WordPress Themes Commercially Supported GPL Themes Where can I find information about styling lists and nested lists? See Styling Lists with CSS How do I change the way menu links are listed? See Styling Lists with CSS How do I get rid of the bullet points next to my links? See Styling Lists with CSS How can I create horizontal menus? See Creating Horizontal Menus How can I get my categories to display in the order I want? See wp_list_categories(). How can I get my links to open in a new window? Opening links in a new window is considered bad form in today's web as it has been abused. Yet, it still serves a purpose for demonstration sites that require more than one window open at a time. This method will work for those links that you enter into the body of a post. After entering the link using the Quicktags button for "link", add target="_blank" to the individual*- link you want to have open in a new window when clicked. Consider adding text indicating that this link will open a new window, as required by web accessibility standards. [code language="php"] Page Title (Opens in new window) [/code] Is there a tool to encode ''HTML'' entities and tags so I can display code on my site? The article Writing Code in Your Posts will help you write programming code and code examples in your posts. The Encode tool will convert your HTML/XHTML code into a form that can be displayed on your blog without it being treated as HTML by browsers. There are also WordPress http://wordpress.org/extend/plugins/search.php?q=syntax+highlighter Plugins and other tools available to help integrate this process into your site if you use it frequently to display code. See also: Fun Character Entities How do I do a ''dropcaps'' on the first letter of a post? DropCaps is the name for the effect where the first letter of the first paragraph in an article drops below the line of text, and is displayed in a larger font-size than the other normal letters. This can be done using BBCode quicktags. First, add this to your style sheet: [code language="php"] #fp:first-letter { font-size : 300%; font-weight : bold; float : left; margin-right: 3px; } [/code] then add following code to file /wp-includes/js/quicktags.js and put them among edButtons: [code language="php"] edButtons[edButtons.length] = new edButton('ed_capdrop' ,'CapDrop' ,'' ,'' ,'c' ); [/code] You will now see a CapDrop quicktag in your edit window. See also: drop caps support question Where should I look for more information on CSS? See CSS Text and Content Display How do I show only the titles of articles on the site homepage? To show only the title of posts on the site homepage, using the WordPress Default theme as an example, in the wp-content/themes/default/index.php file you will find code similar to this: [code language="php"] [/code] So, in this case, you would replace: [code language="php"] [/code] with something like: [code language="php"] [/code] This will cause only the post title to display on your homepage, but show the post content on the individual posts page. Note if your theme uses another template, such as single.php, to display individual posts, then this change may not affect your individual post pages. See also: Template Hierarchy Stepping Into Template Tags Stepping Into Templates How do I show an excerpt, teaser, or summary, for an article on the site homepage? A teaser should not be confused with the excerpt. A teaser refers to the first few sentences or paragraphs of a post. When typing a long post, you can insert the Quicktag after a few sentences, and that acts as a cut-off point for the teaser. When the post is displayed on a home page, category page, or an archive page, the teaser is displayed, followed by a hyperlink (such as Read the rest of this entry...). Visitors can click on that link to see the full version of your post. Note that some Themes may not support the more ability. Additional information on how to present the more can be found in the the_content() and Customizing the Read More articles. As stated before, the teaser (the more) feature should not be confused with the Excerpt field that is completed when writing or editing a post. The Template Tag, the_excerpt(), can be used to display the post's excerpt field. The excerpt you enter when writing a post will not be displayed on your site unless the_excerpt() template tag is specified in your theme. Also, if you choose the "Summary" option For each article in a feed in Administration > Settings > Reading, the excerpt will be used for feeds. How do I show a summary rather than the full content of posts? Here's two possible ways to show a summary, rather than full content of posts on a site main page: Use the Quicktag in your posts, and it will display the text of the post up to that point, and then provide a link, such as "Continue reading...", to allow the reader to see the complete post. The article, Customizing the Read More, discusses changing the text (e.g. Continue reading...) of the link. Change your theme's index.php Template to use the Template Tag, the_excerpt(), instead of the_content(). See also: Stepping Into Template Tags Stepping Into Templates Template Hierarchy How do I customise the text shown in "(more.....)" on my site? See Customizing the Read More How do I use the blogroll links rating feature to display the ratings? Go to the Links Panel. Click on the Link you wish to feature in your blogroll. Scroll to the bottom to Advanced and select the rating number for that site. The dropdown menu permits a rating of 0 - 10. To get your link ratings to display, you may need to edit your Theme. See the documentation for the wp_list_bookmarks() or get_links() Template Tags for more information. Images and Graphics How to add a favicon to your site To add a favicon to your site in WordPress 2.0 or later, place your favicon.ico file inside your theme folder (for example: wp-content/themes/default/) then add this line to header.php: [code language="php"] [/code] Be sure to add it somewhere within the section. See Creating and Installing a Favicon for more detailed instructions. Where can I get some buttons for my site? Buttons are like badges you display on your website to show your affection for something, or to display information regarding your cultural, social, political or technical leanings. To add a WordPress button to your site showing support for the WordPress Community: Contributing to WordPress, Show you Care For more buttons, see: GtmcKnight's Steal these Buttons Adam Kalsey's Buttonmaker How do I get WordPress to generate links to the thumbnail of an uploaded picture? See: Using Images Photoblogs and Galleries How can I use a custom image for my list bullets? See: Styling Lists with CSS Customizing Your Sidebar How do I rotate/cycle/randomize the image in the header of the site? See: Designing Headers, Rotating Header Images How do I link to my own images? You can use absolute or relative URI/URLs addresses. To use a relative link, set the address from the root folder of your site by using a slash in front of the folder in the root directory. [code language="php"] /images/balloons/image.jpg" alt="balloons" /> [/code] To use an absolute link: [code language="php"] http://www.example.com/images/balloons/image.jpg" alt="balloons" /> [/code] How can I display images in my category and archive pages? For current versions of WordPress, see Post Thumbnails. When using the default theme, you'll notice images (and links) do not appear when visiting category and archive query pages. This has to do with how the default theme displays post content in those sections of your site. To change this behavior, edit the default theme's Archive Template (archive.php). You can do this online through the Theme Editor, or offline by downloading and opening the default theme's archive.php in any text editor. Once in the Archive Template, look for this section: [code language="php"] <div class="entry"> </div> [/code] Here, change the_excerpt() template tag, which displays a summary of a post's content while filtering out all HTML tags. To display each post's whole content (and HTML tags), use the_content() template tag: [code language="php"] <div class="entry"> </div> [/code] From 2.9, you can also make use of the_post_thumbnail() template tag. Where can I find more information on images, Photosites, and photo galleries? See: Using Images Photoblogs and Galleries Template Tags How do I change the time stamp for each post from an AM/PM mode to a 24 hour mode? You set the Default Time Format for your site via the Administration > Settings > General under the Date and Time section. See also: Formatting Date and Time How can I have the date/time displayed on every entry I make? To put the date and time on every post title on your site, you may have to change more than one template file. They may include index.php, single.php, category.php, and archives.php. From among the various template files, find all references to the title of your post like this (your Theme version may be slightly different): [code language="php"] by [/code] Rearrange it so the time information goes in front (or in back) of your Post Title: [code language="php"] - by [/code] See also: Formatting Date and Time How do I change the "Permanent Link to" in my Title link? The title of your links includes text that explains what the link is to, in concordance with web accessibility standards. By default, your title may look like this example, which uses the title attribute with the words "Permanent Link to" and the template tag that displays the title of the post. [code language="php"] [/code] To change the "Permanent Link to" text, simply delete it and replace it with your own words: [code language="php"] [/code] Or remove it completely, leaving only the title tag. [code language="php"] [/code] How do I make my categories appear in a drop down list ? In some cases it may be necessary to change sidebar.php. Find this line in the theme: [code language="php"]Categories'); ?>[/code] and replace it with this line instead: [code language="php"]Categories [/code] See also: Template_Tags/wp_dropdown_categories How do I exclude one or more categories from being listed in the list of categories? Use the following function to list your categories but exclude category 1: [code language="php"][/code] Of course, change the 1 to the ID of the category you want to exclude. To exclude multiple categories, use this: [code language="php"][/code] Change 1 and 2 to the categories you want excluded. You can exclude more of them by adding their IDs separated by commas. See also: Template Tags/wp_list_categories How do I hide posts belonging to a certain category on the front page ''index.php''? If you need to hide (exclude) posts belonging to a certain category from displaying on the front page, you can place code that does the exclusion inside The Loop of your theme's index.php file. The Loop starts something like this: [code language="php"] [/code] To exclude category 4 from the front page, just inside The Loop, add this condition : [code language="php"] [/code] The Loop ends something like this: [code language="php"] [/code] Just before that line, add this: [code language="php"] [/code] In the end, it will look like: [code language="php"] [/code] [code language="php"] [/code] [code language="php"] [/code] This means that if on the front page, the post will be presented if it's not in category 4. On pages other than the front ( home ) page, all posts are presented. See also: Exclude Posts From Some Category How do I make my Archives appear in a drop-down list? Put this code into your index.php where you wish the item to appear: [code language="php"] Archives: [/code] How do I get rid of the "No Comments" message displayed with every post? If you do not allow comments on your site you may want to get rid of the "No Comments" (or Comments are off) message displayed with each post. If you are using the WordPress Default theme you would delete the following code from wp-content/themes/default/index.php [code language="php"] [/code] Note that if you use a different theme the information to delete may be slightly different. See also: comments_popup_link() Templates Why can I see only n posts on the site, where are the other entries? Make sure that you have the correct settings in the Show at most posts or days fields in the Administration > Settings > Reading Panel. If you are not seeing all your entries and you modified the default index.php, make sure you have an equal number of opening and closing tags, and that they are in the right places. How do I create an archives page, with all the entries sortable by different methods? Creating an Archive Index shows you how to use WordPress template tags to create a custom archive Page for your WordPress site. There are WordPress Plugins that will also help create customized archive pages. What do the __() and _e() functions in WordPress do? In the simplest of terms, they "print" what you tell them to do. They are abbreviations for the PHP term "echo" which displays text. In WordPress, they are used to identify strings in the php files marked for translation to other languages, and localization using two "tags" which are actually functions. They are: __() _e() These accept a string as an argument. For example: [code language="php"] __("Translate Me") _e("Translate Me") [/code] The only functional difference between the two methods is that _e() echoes the string and __() simply returns the string. __() is used when you want to supply a string to a function. _e() is used when you want to output the string as part of your XHTML. We have a tool which goes through all of the php files, extracting strings that are marked by __() and _e(). See also: I18n for WordPress Developers How to easily display links to both Pages and Categories in the blog navigation header? In your blog's admin interface, go to Design → Menus At the top of the page, select the primary menu for editing (this is the menu that appears in the header) In the accordion menu in the left column, open Categories Select the categories you want to display in the header and add them to the menu. They will appear in the right column. How to display posts in a Page? There's several ways to do display posts in a Page. The simplest way is described in the FAQ: How can I have a static front page and posts display on a page called Blog? A more complex method is to first create a Page Template with a WP query, and a loop, that retrieve and display the posts. Then via Administration > Pages > Add New, add a new Page with that Page Template designated in the Template field. Here's an example developed using the WordPress Default theme: 1. Create a file called wp-content/themes/default/pageofposts.php that has this code: [code language="php"] $showposts, 'caller_get_posts' => $do_not_show_stickies, ); $my_query = new WP_Query($args); ?> have_posts() ) : ?> have_posts()) : $my_query->the_post(); ?> in_the_loop = true; ?> id="post-"> '); ?> Posted in | Not Found Sorry, but you are looking for something that isn't here. [/code] 2. In Administration > Pages > Add New, create a new Page, title the Page whatever you want, and in the Template field select PageOfPosts. 3. That's it, now visit that Page on your site and you should see your posts. See also: Why is there no Page Template option when writing or editing a Page? How to delete duplicate navigation bar references to Home? If your theme displays Pages for navigation, and there is more than one instance of Home in the navigation bar, here's several ways to fix that. Typically the duplicate problem occurs after someone has created a Page called Home. Many theme authors 'hard-code' a reference to Home in the theme's header.php and use template tag, wp_list_pages, to display all the other Pages. But, if you've created a Page called Home, that likely causes the duplicate navigation item. To delete the duplication, you would edit your theme's header.php and: Find and delete the hard-coded reference to Home. Or, use the exclude=x argument with wp_list_pages() and replace the x with the Page ID of your Home Page. How to get rid of encoding in a theme's footer? Some theme authors embed links in an encoded footer making it difficult to understand what is happening in the footer. Note: this type of encoded content could be malicious as well as just a copyright banner! The best course of action is to avoid using encrypted themes entirely. There are a large number of free themes available without such potentially malicious code in them. Nevertheless, here's a method to decode (figure out) and correct the footer so there is no encoding. In your index.php find the line that says . Above and below it add marker text like this: [code language="php"] [/code] Now visit your site, view source (e.g. View->Page Source in Firefox), and copy the HTML between those two markers. Rename your footer.php and make a new copy of footer.php with that HTML code. Then change it to your hearts content. Remember to insert the before tag. Keep in mind that if your theme's license does not permit this, then don't do it. If that's the case please consider finding a new theme. Other methods The above is useful, but only shows you the HTML output, rather than any dynamic PHP code. To see the PHP code, you might try using an online decoder. This page will let you decode the encryption that seems most commonplace, the one that looks like $o=whatever: http://ottodestruct.com/decoder.php That interface was based on this page, which will decode the type of encryption that starts with $_F=__FILE__: http://www.tareeinternet.com/scripts/byterun.php Another one is here, for those that look like eval(gzinflate(base64_decode('...')));: http://www.tareeinternet.com/scripts/decrypt.php There are also decoders available at http://cyko.decodethe.net/ and http://base64-encoder-online.waraxe.us/ See also: List of various online decoders http://wordpress.org/support/topic/237083 http://wordpress.org/support/topic/235287 How to Remove Footer Encryption Theme Authentication Checker plug to check your theme files Themes Which files do I modify when I start to design my site? See: Working with WordPress, Site Development How do I tell which file is making which output? You can put e.g., [code language="php"] [/code] at the top and bottom of your files, which will be printed in the HTML output. How do you create a screenshot.png for your Theme? Create a screenshot image using the Print Screen button on your keyboard and pasting it into your graphics program, or use the screen capture feature found in many popular graphics programs. Resize the image to 880x660 pixels. Save the image as a PNG file in your Theme's folder with the name screenshot.png. WordPress looks for that file name automatically. Back to FAQ Post Meta Data Section atachibana — Sun, 17 Jul 2016 07:10:56 +0000 [codex_languages en=" Post Meta Data Section" ja_codex=" Post Meta Data Section"] The post meta data is the "administrative" information you provide to viewers about each post. This information usually includes the author of the post, when it was written (or posted), and how the author categorized that particular post. This lesson will show you some different ways to change your Theme design to display these important pieces of information in the manner you desire. In many cases, the post meta data is positioned immediately following the post itself, though some Themes are designed to place this information at the top of the post, other designs feature the post meta data in the top or bottom of the sidebar, and some designs even place the information in the footer. Essentially, post meta data can be styled in many different ways and with a variety of details. Default Usage The default WordPress Theme places the post meta data basic information and tags below the post in a box, before the comments. A condensed version of the code looks like this: [code language="php"]This entry was posted on at and is filed under . You can follow any responses to this entry through the feed.[/code] The output result looks like this: This entry was posted on Monday, February 12, 2003 at 11:32 and is filed under WordPress Lessons, Things to Know. You can follow any responses to this entry through the RSS 2.0 feed. There are three template tags used in the post meta data. One, the_time(), is used twice with different results. The other two tags get the information about the categories and the link to the RSS feed from the database. The template tag for the_time() can be set up with a variety of parameters to tell the time and date of the post from information drawn from the database. In the first usage, the parameters l, F jS, Y pull the post's date into a format that gives the weekday, month, date, and year. In the second usage, there are no parameters, therefore it just returns the time when the post was saved. You will experiment with these below in Changing the Time and Date. The template tag the_category() displays the categories that the post belongs to. This template tag can be modified to feature different text, graphics and symbols between the graphics, and may even use a plugin to display graphics in place of the words. There are many ways to style these. In this example, the categories are listed with a comma to separate them. The last tag is the comments_rss_link() which uses the parameter RSS 2.0 to identify the type of feed being used. You can also customize the feed tag, changing the way it displays the link information about the feed and type, or even have it feature feed icons instead of text. Changing the Text Let's start to rearrange your post meta data with small steps. The first step is to change the text but not the tags. After all, this is your website and you want it to say things your way, right? This example makes the post meta data a little more conversational: [code language="php"]I slaved away at the computer on at the ridiculous time of when I could have been doing something much more productive. I slapped this thing into the categories, just to make you think I have some organizational skills. If you can really be bothered, you can keep track of what people have to say about my silly writings through the feed, but I wouldn't bother. No one else who reads this babble has anything worthwhile to say.[/code] This would result in: I slaved away at the computer on Monday, February 12, 2003 at the ridiculous time of 11:32. when I could have been doing something much more productive. I slapped this thing into the WordPress Lessons and Things to Know. categories, just to make you think I have some organizational skills. If you can really be bothered, you can keep track of what people have to say about my silly writings through the RSS 2.0 feed, but I wouldn't bother. No one else who reads this babble has anything worthwhile to say. Okay, there is a small change. Did you catch it? The usage of the_category() template tag, the parameter that sets the separator between the list of categories where the post belongs, was changed from a comma (,) to the word "and". It makes more sense in this situation. Now, you can also cut the chatter and make your post meta data short and sweet: [code language="php"]POSTED: FILED AS: COMMENTS FEED: [/code] Here is a very short list of your post meta data: POSTED: 05/12/04 9:35 AM FILED AS: News, Answers COMMENTS FEED: RSS 2.0 Changing the Time and Date There are many ways to change the time and date within your post meta data to reflect a more appropriate use for your website or your cultural timekeeping methods. For example, in much of the world, the date is not month day, year but day month year. In the post meta data, you would change the template tag the_time() so the parameters would show "Monday, 21 February 2005": [code language="php"] [/code] To add more interesting information to your post meta data there are several plugins available which generate the date the post was last modified. Two such plugins are Kaf Oseo's Post Updated and Nick Momrik's Last Modified. In the following example, using various ways of manipulating time with PHP tags, we'll add Nick Momrik's plugin to the mix, mdv_last_modified(): [code language="php"]This post was written on what I think was a , but I know it was the day in the month of in the year of , though I messed around with this on the day of in , a not-so-busy when I had nothing better to do.[/code] Which would result in: This post was written on what I think was a Tuesday, but I know it was the 15th day in the month of February in the year of 2004, though I messed around with this on the 10th day of August in 2004, a not-so-busy Thursday when I had nothing better to do. Adding Template Tags So far, you've covered only three of the many template tags you can add to your post meta data. You can add the the_title() to get the title of the post. If you want the author's name, you can add the_author() and even the author's email with the_author_email(). Want a link to all the posts written by a specific author? That can be arranged with the the_author_posts_link(). What if you want to include more basic information like the title of the website using bloginfo(), or navigation help like the previous_post() and next_post()? We're using the next and previous post template tags to list posts within the same category, available to users of WordPress 1.5.1.3+. These are just a few examples of the many possible uses of template tags in your post meta data In the most simplest of usages, the post meta data could be listed as: [code language="php"]POST TITLE: AUTHOR: POSTED: FILED AS: COMMENT FEED: PREVIOUS: NEXT: [/code] And would look like this: POST TITLE: WordPress Makes Me Smile AUTHOR: Harriet Smith POSTED: 20 April 2004 FILED AS: WordPress, News COMMENT FEED: RSS 2.0 PREVIOUS: Things to Do With WordPress NEXT: Why I Like WordPress If you want this in your sidebar, and you want a more conversational style, then in your template file, sidebar.php, find a good spot to put the following: [code language="php"]You are reading the article, , on our website, . This article was written on , in Seattle, Washington, and you can find similar articles in the categories, or more articles by , if you enjoyed this article. If you have any comments about this article, you can contact by email, or leave a comment below. You can also follow comments made on this article via our feed. If you would like to continue reading more, . Thank you for visiting our site.[/code] This example, if styled in a narrow column found on most sidebars, would look like this: You are reading the article, WordPress Makes Me Smile, on our website, Talking Blog. This article was written on May 15, 2004, in Seattle, Washington, and you can find similar articles in the WordPress and Blog categories, or more articles by Harriet Smith, if you enjoyed this article. If you have any comments about this article, you can contact Harriet Smith by email, or leave a comment below. You can also follow comments made on this article via our RSS 2.0 feed. If you would like to continue reading more, the previous article on our site is called Things To Do With WordPress and the next article is called Why I Like WordPress. Thank you for visiting our site. This is just the beginning. There are many ways you can style your post meta data; by putting it in a box, by making it part of the text, by having it in a list...it's up to your imagination how you want to style your post meta data, and what information you want to share with your public about your posts. More Resources Stepping Into Template Tags Formatting Date and Time Separating Categories Template Tags Styling Lists with CSS Good Navigation Links Next and Previous Links WordPress Feeds Test Driving WordPress atachibana — Sun, 17 Jul 2016 15:29:33 +0000 There are times when you need to test changes to your WordPress powered site out of the public eye. Making changes to a live site could adversely affect your readers. You have several choices. Creating a Sandbox Do this for test driving your WordPress Theme and style sheet, allowing you to develop your WordPress Theme on your computer. This limits you to only working on CSS and not using plugins and other power features of WordPress. This is best for just styling a page. Hiding Your WordPress Test Area You can also close off access to your WordPress test site on your website server. This involves some familiarity with .htaccess and Apache, but it allows you to continue working on the Internet while not exposing your test site to the public. Install WordPress on Your Computer If you are determined to put WordPress through its paces, you can install WordPress on your own computer with a few modifications. This allows you total control over the actions and capabilities of WordPress. You can still use plugins, template files, Themes, and redesign everything as if it were on the Internet without using bandwidth or suffering with slow Internet access times. We have two sets of explanation for this: Installing a New Installation on Your Computer and Installing an Existing WordPress Site. We also cover Moving WordPress Onto Your Website after you have finished developing your site on your computer. Creating a Sandbox A Sandbox is a term related to the sandbox you might have played in and built sand castles in as a child. It is a playground for working on concepts and exploring your imagination. A WordPress Sandbox is basically a copy of a generated page on a WordPress site that is saved to your hard drive for you to play with as you develop your final theme and look for your site. WordPress uses different template files to generate different views on your site. In general, there is the front page view, the single post view, and the multi-post view, used for categories, archives, and search. For more information on the structure of WordPress Themes, see Site Architecture 1.5. As different page views use different CSS styles, at the least you need to put three page views in your sandbox following these instructions. Choose the WordPress Theme you want to work from in your Appearance screen of your Administration Screen. From your initial or test WordPress site, view one of the following page views: * Front Page * Single Post * Mult-Post Page From your browser: # Choose File > Save As. # Name the saved page with one of the above "titles." # Save each page's file to your sandbox folder. From your Theme's folder, copy the style.css style sheet file to your sandbox folder. Open each of the three files you have saved in a text editor and change the following: [code language="php"][/code] to [code language="php"][/code] Lastly, find all the image files and graphics associated with the style sheet, like background images, icons, bullets, or others, and copy them to your sandbox folder. Links to these items from within your style sheet should have no folders in their links, or link to a subfolder within your sandbox folder, such as: [code language="php"]header {margin:5px; padding:10px; background:url(images/background.jpg)....}[/code] To test this, double click on one of the pages in that folder to view it in your browser. If the the styles and graphics are visible, it worked. If not, check the link to your style sheet. Now, you have a sandbox to play in. To use your sandbox, have two programs open. One is your text editor with the style.css file and the other is your browser with the page you are working on in view. Make a change in your style sheet, save it, then do a total refresh or your browser screen and look at what changes. Then repeat the process. When you are done with one page, go to the next page and check those changes and add more if necessary. Sandbox Tips Here are a few tips for playing in your sandbox. Backup Frequently As you work, copy the files in the folder before making major renovations to a backup folder. Or you can use a file compression utility like a zip program to save the entire folder. If the changes you make do not work, you have recent backups to work from. Trace DIVS and CLASSES Before you begin, go through the source code file of each of the three page views in your text editor and add a comment as to where each division begins and ends. These often cross lines between template files and can be difficult to trace. Make your life easier by documenting where these begin and end. Make Notes Before making a huge change, write down what you are changing. This way you have notes to refer to when things do not work later and you are trying to trace the history of the changes. Make Notes Inside When making significant changes to the style sheet or to the web page source code, add notes or comments to the code. This will also help you to keep track of the changes you've made. Make Small Steps Making a lot of changes at once makes it harder to find the small change that made things go out of whack. A good approach would be to take small steps and check, then make additional, small modifications and check again. Avoid Changing the Template Files Begin by staying with the site architecture and style references already in place. If you will be releasing your Theme to the public, modifications to the template files must be seriously reconsidered and done carefully. If you are rebuilding your site for your private use, then you can make those changes to your HTML saved pages source code, then move those changes into the template files later. Moving Your Sandbox To Your Theme When you have made all your changes and are satisfied with the results, it is time to move your sandbox back into your WordPress Theme. Upload the style.css style sheet file to your WordPress Theme folder on your site, replacing the old file. Upload all graphics and images to the Theme folder or subfolder. View your site in your browser. The changes should be immediate. If you made changes to the source code of any of the three pages, track those down to their specific template file and make the changes in those template files on your site. Install another Blog Install WordPress again, but in the wp-config.php file, use a different table-prefix. In Options > Writing > Update Services, clear the box. Tell no one where your blog is located. If you go to another site from your blog, then your site could be discovered because of the referer in the browser. To prevent this, go to your real blog, then to another site. This method is useful toward the end of testing as you can ask for people to test using other browsers / screen resolutions. Hiding Your WordPress Test Area To hide your WordPress test folder from others, you can use the .htaccess file on an Apache web server. The .htaccess file is a file that stores server directives, instructions which tell the server what to do in specific situations. You could also use the Apache config file (httpd.conf) or other methods, but the .htaccess file can apply only to the folder in which the .htaccess file resides, and all the folders under that one, allowing you to restrict access to a specific folder. Remember, this will only work on servers that support .htaccess. If you are unsure that your server supports .htaccess, contact your hosting provider. You may or may not be able to do this depending upon the access permissions you have with your host server. You may need their assistance. If you are running your own server, or if your hosting provider is clue-free, consult the AllowOverride documentation. Using the .htaccess file, you need to provide instructions to tell the server to restrict or deny access to your WordPress test site. In the folder or directory in which WordPress is installed, do the following: Using a text editor create a blank text file called .htaccess. You need the following information: * The full path of a directory on your site server that is not accessible to the public (like http://example.com/public_html/ is accessible but http://example.com/private/ is not. Use the latter. * The name of the secured area such as "Enter Password" or "Secure Area" (this is not important, just simple). In the file type the following, replacing /full/path/of/directory/ and Security Area with the above information: AuthUserFile /full/path/of/directory/.htpasswd AuthName "Security Area" AuthType Basic require valid-user Save this .htaccess file and upload it to the directory on your server you want hidden and secured. This would be the installation directory for WordPress such as /wordpress/ or blog. Using Telnet, cPanel, or another way to access your server's command panel, go to the directory specified as AuthUserFile. Type the following command, where user_name is the user name for the access: htpasswd -c .htpasswd user_name When prompted, enter the password, and confirm it. Write down your password and user name and keep it in a safe place. When you are ready to open your site to the public and remove the protection, delete the password and .htaccess files from their locations. It is highly recommended that you remove the default ping URL to Ping-o-Matic!, otherwise your test posts will ping and your test blog will be made public though not accessible. Htaccess Resources .htaccess files howto Authentication, Authorization and Access Control Installing WordPress on a Mac Use these instruction for setting up a local server environment for testing and development on a Mac. Installing_WordPress_Locally_on_Your_Mac_With_MAMP Installing WordPress on Your Windows Desktop In order for WordPress to work, it must have access to an Apache server, MySQL/MariaDB, and phpMyAdmin. Installing these separately can be painful. Luckily for us, XAMPP installs all of these with one program, allowing you to run WordPress on your computer. There are two versions of the program, Basic and Lite. The Lite version is usually adequate. Download and install XAMPP. This installs by default into C:/xampplite or C:\xampp. Start XAMPP from c:\xampplite or c:\xampp. You may need to restart your computer to allow apache services to start. In your browser, go to http://localhost/xampp. In the left column under Tools, click phpMyAdmin. Login is admin. In Create new database enter wordpress. In the next box, select utf8 unicode ci. Click Create button. Unzip your WordPress download into the htdocs directory - c:\xampp\htdocs\. From the folder, open wp-config-sample.php in a text editor. The connection details you need are as follows:// ** MySQL settings ** // define('DB_NAME', 'wordpress'); // The name of the database define('DB_USER', 'root'); // Your MySQL username define('DB_PASSWORD', ''); // ...and password define('DB_HOST', 'localhost'); // 99% chance you won't need to change this Save as wp-config.php. Install by going to http://localhost/wordpress/wp-admin/install.php IMPORTANT: It is possible to use this to actually host your blog if you have a good enough connection. If you want to do this, you MUST increase the security level. This description is NOT SECURE if you allow web access to your blog. Installing an Existing WordPress Site With the help of XAMPP, you can install WordPress directly on your computer and play with it to your heart's content. This way, it is totally isolated from public exposure and all your mistakes are hidden. When you are ready, you can then move it onto your website, ready for all to see. Requirements Access to your server database. Ability to download your entire WordPress installation to your computer. Basic XAMPP for Windows Enough room on your hard drive to accommodate your database, WordPress installation, and XAMPP. Backup WordPress [caption id="attachment_1161" align="alignnone" width="216"] Choose your database file[/caption]Begin by backing up your WordPress site completely, the files and the database. This will ensure that you have a good copy to fall back on, just in case. A second backup is then required of your database, but it requires you do a little housekeeping. As the WordPress database normally stands, there are statistics tables which contain a huge amount of data which add to the overall size of the database, and slow down the process of backing up and downloading this backup copy of your database. You do not have to clear these, but it is generally considered a good idea. Login to PHPMyAdmin on your website server. From the main login screen, select Databases. Choose the name of your WordPress database. From the tags at the top of the screen, choose Export. In the frame at the top of the Export section you will see a list of tables in your database. You will need to choose only those tables that correspond to your WordPress install. They will be the ones with the table_prefix found in your wp-config.php file. If you only have WordPress installed, then choose Select All from the left column. Make sure the SQL button is selected. On the right side of the panel, make sure the following boxes are checked.[caption id="attachment_1159" align="alignnone" width="379"] phpMyAdmin Export Screen[/caption] * Structure * Add AUTO_INCREMENT value * Enclose table and field names with backquotes * Data Tick the Save as file option, and leave the template name alone. For Compression, select None. Click Go. You should be prompted for a file to download. Save the file to your computer. Depending on the database size, this may take a few moments. Download WordPress Now, download your entire WordPress site to your computer. This is usually done with an FTP client program. Make sure you include all core WordPress files within your root or WordPress directory, including the index.php. You should now have in your computer two items: One or more database backups. All your WordPress files, folders, and images directories. Copy the backup files again to somewhere safe on your machine so you work on a copy of the backup for the next stage. Install Basic XAMPP Install XAMPP. By default, it will install to C:\xampp. Go to C:\xampp\apache\conf and open the file called httpd.conf in a text editor. About line 166 you will find: #LoadModule rewrite_module modules/mod_rewrite.so. Remove the # and save the file (this switches mod_rewrite on). Create a folder inside C:\xampp\htdocs. This will be for WordPress. Copy all your downloaded WordPress files (not the sql backup) into that directory. With a text editor, open the file wp-config.php on your WordPress install. Change the details for your new MySQL connection:// ** MySQL settings ** // define('DB_NAME', 'wordpress'); // The name of the new database you made define('DB_USER', 'root'); // keep this as is define('DB_PASSWORD', ''); // keep this empty define('DB_HOST', 'localhost'); // 99% chance you won't need to change this Your main index.php should be in the /htdocs folder or in a subdirectory such as /htdocs/wordpress/. Write that down. Start XAMPP by clicking the orange xampp_start.exe or using the console program from Program Files\ApacheFriends\XAMPP\XAMPP Control Panel. Once it is working, click on link in the left side bar for phpMyAdmin. Create a database. The name should match the one used in your wp-config.php file. Importing Your SQL Backup File Before you begin to import your SQL backup file, you need to change some information inside your .SQL file. Using your text editor, open the .sql backup database file you downloaded. Find and replace all the instances of your old URL with your new URL. For instance if your blog address is at http://example.com/wordpress/, and your files on your computer are at /htdocs/wordpress/, replace it with http://127.0.0.1/wordpress/. Click Save - Do not use Save as. [caption id="attachment_1157" align="alignnone" width="306"] phpMyAdmin SQL tab[/caption] Now it is time to import your sql file. From within the phpMyAdmin on your computer, click on your database name, then choose the SQL tab. From this screen, click Browse and find your backup files on your computer. Click Go. This can take a few minutes to import. [Image:phpmyadmin-sql-screen.jpg|thumb|left|phpMyAdmin SQL Screen]] [caption id="attachment_1158" align="alignnone" width="330"] phpMyAdmin Import Successful Screen[/caption] Once the procedure is complete, your database will be restored and will work just as it did before. If something goes wrong with this last part of the process, it could be that either your backup was corrupted in some way, or something went wrong with the database itself. Keep your backup files safe! If everything so far has gone well, it is now time to visit your blog! In your browser, type in http://127.0.0.1/wordpress/index.php or the actual name of the folder you created for your WordPress files. If you get a 404, check you have the right place. You do not need to put htdocs or xampp or anything else after the http://127.0.0.1/ except use your directory name. WordPress should now function just as it did on the web. You do not need to use the built-in editor in WordPress to alter your files. Just open the files directly in a text editor and edit them as you would any other file. Refreshing your browser's web page will then show the effects. Moving Your Test WordPress Site to Your Website Coming soon - how to move your test site from your computer back live onto your host server site. Resources Test themes on a live blog with Theme Test Drive qSandbox.com - Create a free WordPress test site to try (new) plugins and themes Validating a Website atachibana — Sun, 17 Jul 2016 15:37:05 +0000 Validating a website is the process of ensuring that the pages on the website conform to the norms or standards defined by various organizations. Validation is important, and will ensure that your web pages are interpreted in the same way (the way you want it) by various machines, such as search engines, as well as users and visitors to your webpage. Conforming to standards and regulations is one of the many ways you can make your website universally understood. Make sure your codes and styles validate across the board. That means they have to meet the "strict" standards set by the W3C Organization and pass a variety of validations for CSS and XHTML. Not all validators check for the same things. Some only check CSS, others XHTML, and others for accessibility. If you are sincere in presenting standardized pages to the public, test them with several validators. The World Wide Web Consortium sets the standards and also hosts a variety of web page validators. In simple terms, validation ensures that your website complies with the standards accepted by most web designers. That also means that it will be accessible to more people, across more web browsers and operation systems. Having an accessible website is also regarded as good web design practice. As you can see, having a validated website has its definite plus points. Validation Techniques Validators detect problems in your web page and style sheet. It could be a tag that was opened and never closed. It could be a misspelled piece of code or forgotten element the tag or style requires to work properly. You become a detective, hunting and solving the little problems occurring in your web page. The resources and articles on validation below will help you learn more about validating your web page. Validating your WordPress site means more than just checking the front page for errors. With the modular Themes and template files in WordPress, while you may fix all the errors associated with the index.php and sidebar.php when viewing your front page, errors may still lie within any other template files such as single.php, page.php, archives.php, or category.php. Validate these page views as well to make sure you cover all the template files. Validation errors aren't limited to your template files. They can also happen inside of a post. When you are writing a post and using HTML, WordPress might not recognize the HTML and convert it to a character entity, or you may have entered it wrong. If you have a page with a lot of HTML coding, validate it to make sure you have it all correct. And occasionally check random posts to make sure everything is still okay from time to time as part of your general housekeeping. Validation doesn't just mean putting your pages through some web driven testers. It also means test-driving it with friends, relatives, co-workers, and strangers. Everyone has a different system and way of working, so ask for others to test-drive your styles or themes before you make them public. Validation Checklist To help you validate your WordPress site, here is a quick checklist: Validate HTML/XHTML Validate CSS Validate for Section 508 Standards (accessibility) Validate for WAI standards (accessibility) Validate Links (check for dead links) Validate Feeds Check across different browsers (include handheld computers, Mac, PC, and cellphones, too) Re-validate HTML and CSS Have friends, relatives, co-workers check your site When ready, you can post your site on the WordPress Forum's Your WordPress for review HTML - Validation The W3C's HTML Validation Service (URL and upload) W3C's Collection of Validators W3C Tidy Online Silk Tide Online Validator for Errors and Accessibility Windows GUI Interface for TIDY Site Report Card Validator Valet Webthing.com Watson Addy's Validator AnyBrowser's HTML Validation Cynthia Says Validator Doctor-HTML Validator HTMLvalidator.com's Validator Software QA and Testing Resource Center HTML Tag Checker W3.org Tidy Validator CSS - Validation W3.org's CSS Validator (URL, upload, and direct paste in) WDG and HTMLhelp.com's CSS Validator and Checker Validation by Uploading Files W3.org's CSS Validator WDG and HTMLhelp.com's CSS Validator and Checker (URL, upload, and direct paste) The W3C's HTML Validation Service (URL and upload) HTMLHelp's File Upload HTML Validator Feeds Validation Feedvalidator.org - for Atom and RSS feeds. Experimental RSS 1.0 Validator Redlands RSS 1.0 Validator Validation Resources and Articles Writing Code in Your Posts Squarefree's Bookmarketlets (JavaScript for web page testing) Walidator.com Understanding How HTML Validators Work You Call That Web Site Testing? Related Accessibility Files atachibana — Sun, 17 Jul 2016 15:43:17 +0000 Note: The file descriptions on this page are for WordPress Version 4.7 Each file appearing in this list has been sorted into its directory of origin. A description of the purpose of the file and its possible dependencies appear after each. WordPress Root Directories: wp-admin/ wp-content/ wp-includes/ Files: index.php Core WordPress index. This is the file that produces the blog output. license.txt The WordPress GPL license file. readme.html Pre-install information about WordPress. wp-blog-header.php Decides what to display based on the parameters that are passed to the blog. Included from any page that wants to display WordPress content. wp-cron.php Runs a virtual cron job, or scheduled task in order to automate things like publishing scheduled posts, checking for plugin or theme updates, sending email notifications and more. wp-comments-post.php Receives posted comments and adds them to the database. wp-config-sample.php A sample configuration file for connecting WordPress to your MySQL database. wp-config.php The actual configuration file used to connect WordPress to your MySQL database. This is not included in the default install, but must exist for successful operation of WordPress. You may need to edit this file to modify certain configuration settings. wp-links-opml.php Produces OPML output of Links that were added to the blog via the WordPress admin menu. wp-load.php Bootstrap file for setting the ABSPATH constant and loading the wp-config.php file, which will set up the WordPress environment. wp-login.php The WordPress login page for registered users. wp-mail.php Used for obtaining blog posts that were submitted via email. The URL of this file is usually added to a cron job so that it is regularly retrieved, so that new email posts are accepted. wp-settings.php Performs various pre-execution routines, including checking for correct installation, including auxiliary functions, applying user plugins, initializing execution timers, etc. wp-signup.php Used for redirecting unknown requests in Multisite to have the user sign up to create that blog. wp-trackback.php Handles incoming trackback requests. xmlrpc.php Handles incoming xmlrpc commands. Among other things, this allows posting without using the built-in web-based administrative interface. wp-admin This directory contains all needed administration files. Directories: wp-admin/css wp-admin/images wp-admin/includes wp-admin/js wp-admin/maint wp-admin/network wp-admin/user Files: wp-admin/about.php About page, useful information wp-admin/admin-ajax.php Needed for TinyMCE, inline wp-admin/admin-footer.php Contains the bottom of the admin console. Included from each of the console pages. wp-admin/admin-functions.php Contains various functions used by the admin console. wp-admin/admin-header.php Contains the top half of the admin console. Includes menu-header.php for menu logic. wp-admin/admin-post.php WordPress Generic Request (POST/GET) Handler. Intended for form submission handling in themes and plugins. wp-admin/admin.php The core of the admin files. Connects to the database, integrates the dynamic menu data, displays non-core console (dashboard) pages, etc. wp-admin/async-upload.php Server-side file upload handler from wp-plupload, swfupload or other asynchronous upload methods. wp-admin/comment.php Comment Management Screen wp-admin/credits.php Credits administration panel. wp-admin/custom-background.php The custom background script. wp-admin/custom-header.php The custom header image script. wp-admin/customize.php Theme Customize Screen. wp-admin/edit-comments.php Edit Comments Administration Screen wp-admin/edit-form-advanced.php Post advanced form for inclusion in the administration panels. wp-admin/edit-form-comment.php Edit comment form for inclusion in another file. wp-admin/edit-link-form.php Edit links form for inclusion in administration panels. wp-admin/edit-tag-form.php Edit tag form for inclusion in administration panels. wp-admin/edit-tags.php Edit Tags Administration Screen. wp-admin/edit.php Edit Posts Administration Screen. wp-admin/export.php WordPress Export Administration Screen wp-admin/freedoms.php Your Rights administration panel. wp-admin/import.php Import WordPress Administration Screen wp-admin/index.php Dashboard Administration Screen wp-admin/install-helper.php Plugins may load this file to gain access to special helper functions for plugin installation. This file is not included by WordPress and it is recommended, to prevent fatal errors, that this file is included using require_once(). wp-admin/install.php WordPress Installer wp-admin/link-add.php Add Link Administration Screen. wp-admin/link-manager.php Link Management Administration Screen. wp-admin/link-parse-opml.php Parse OPML XML files and store in globals. wp-admin/link.php Manage link administration actions. This page is accessed by the link management pages and handles the forms and Ajax processes for link actions. wp-admin/load-scripts.php Admin file to load scripts wp-admin/load-styles.php Admin file to styles wp-admin/media-new.php Manage media uploaded file. There are many filters in here for media. Plugins can extend functionality by hooking into the filters. wp-admin/media-upload.php Manage media uploaded file. There are many filters in here for media. Plugins can extend functionality by hooking into the filters. wp-admin/media.php Media management action handler. wp-admin/menu-header.php Displays Administration Menu. wp-admin/menu.php Builds Administration Menu. wp-admin/moderation.php Comment Moderation Administration Screen. Redirects to edit-comments.php?comment_status=moderated. wp-admin/ms-admin.php Multisite administration panel. wp-admin/ms-delete-site.php Multisite delete site panel. wp-admin/ms-edit.php Action handler for Multisite administration panels. wp-admin/ms-options.php Multisite network settings administration panel wp-admin/ms-sites.php Multisite sites administration panel. wp-admin/ms-themes.php Multisite themes administration panel. wp-admin/ms-upgrade-network.php Multisite upgrade administration panel. wp-admin/ms-users.php Multisite users administration panel. wp-admin/my-sites.php My Sites dashboard. wp-admin/nav-menus.php WordPress Administration for Navigation Menus wp-admin/network.php Network installation administration panel. A multi-step process allowing the user to enable a network of WordPress sites. wp-admin/options-discussion.php Discussion settings administration panel. wp-admin/options-general.php General settings administration panel. wp-admin/options-head.php WordPress Options Header. Displays updated message, if updated variable is part of the URL query. wp-admin/options-media.php Media settings administration panel. wp-admin/options-permalink.php Permalink Settings Administration Screen. wp-admin/options-reading.php Reading settings administration panel. wp-admin/options-writing.php Writing settings administration panel. wp-admin/options.php Options Management Administration Screen. If accessed directly in a browser this page shows a list of all saved options along with editable fields for their values. Serialized data is not supported and there is no way to remove options via this page. It is not linked to from anywhere else in the admin. This file is also the target of the forms in core and custom options pages that use the Settings API. In this case it saves the new option values and returns the user to their page of origin. wp-admin/plugin-editor.php Edit plugin editor administration panel. wp-admin/plugin-install.php Install plugin administration panel. wp-admin/plugins.php Plugins administration panel. wp-admin/post-new.php New Post Administration Screen. wp-admin/post.php Edit post administration panel. Manage Post actions: post, edit, delete, etc. wp-admin/press-this.php Press This Display and Handler. wp-admin/profile.php User Profile Administration Screen. wp-admin/revision.php Revisions administration panel. Requires wp-admin/includes/revision.php. wp-admin/setup-config.php Retrieves and creates the wp-config.php file. The permissions for the base directory must allow for writing files in order for the wp-config.php to be created using this page. wp-admin/term.php Edit Term Administration Screen. wp-admin/theme-editor.php Theme editor administration panel. wp-admin/theme-install.php Install theme administration panel. wp-admin/themes.php Themes administration panel. wp-admin/tools.php Tools Administration Screen. wp-admin/update-core.php Update Core administration panel. wp-admin/update.php Update/Install Plugin/Theme administration panel. wp-admin/upgrade-functions.php WordPress Upgrade Functions. Old file, must not be used. Include wp-admin/includes/upgrade.php instead. wp-admin/upgrade.php Upgrade WordPress Page. wp-admin/upload.php Media Library administration panel. wp-admin/user-edit.php Edit user administration panel. wp-admin/user-new.php New User Administration Screen. wp-admin/users.php User administration panel wp-admin/widgets.php Widget administration panel wp-admin/images This directory holds images associated and used by WordPress in the Administration Panels. wp-admin/images/align-center-2x.png wp-admin/images/align-center.png wp-admin/images/align-left-2x.png wp-admin/images/align-left.png wp-admin/images/align-none-2x.png wp-admin/images/align-none.png wp-admin/images/align-right-2x.png wp-admin/images/align-right.png wp-admin/images/arrows-2x.png wp-admin/images/arrows.png wp-admin/images/browser-rtl.png wp-admin/images/browser.png wp-admin/images/bubble_bg-2x.gif wp-admin/images/bubble_bg.gif wp-admin/images/comment-grey-bubble-2x.png wp-admin/images/comment-grey-bubble.png wp-admin/images/date-button-2x.gif wp-admin/images/date-button.gif wp-admin/images/generic.png wp-admin/images/icons32-2x.png wp-admin/images/icons32-vs-2x.png wp-admin/images/icons32-vs.png wp-admin/images/icons32.png wp-admin/images/imgedit-icons-2x.png wp-admin/images/imgedit-icons.png wp-admin/images/list-2x.png wp-admin/images/list.png wp-admin/images/loading.gif wp-admin/images/marker.png wp-admin/images/mask.png wp-admin/images/media-button-2x.png wp-admin/images/media-button-image.gif wp-admin/images/media-button-music.gif wp-admin/images/media-button-other.gif wp-admin/images/media-button-video.gif wp-admin/images/media-button.png wp-admin/images/menu-2x.png wp-admin/images/menu-vs-2x.png wp-admin/images/menu-vs.png wp-admin/images/menu.png wp-admin/images/no.png wp-admin/images/post-formats-vs.png wp-admin/images/post-formats.png wp-admin/images/post-formats32-vs.png wp-admin/images/post-formats32.png wp-admin/images/resize-2x.gif wp-admin/images/resize-rtl-2x.gif wp-admin/images/resize-rtl.gif wp-admin/images/resize.gif wp-admin/images/se.png wp-admin/images/sort-2x.gif wp-admin/images/sort.gif wp-admin/images/spinner-2x.gif wp-admin/images/spinner.gif wp-admin/images/stars-2x.png wp-admin/images/stars.png wp-admin/images/w-logo-blue.png wp-admin/images/w-logo-white.png wp-admin/images/wheel.png wp-admin/images/wordpress-logo-white.svg wp-admin/images/wordpress-logo.png wp-admin/images/wordpress-logo.svg wp-admin/images/wpspin_light-2x.gif wp-admin/images/wpspin_light.gif wp-admin/images/xit-2x.gif wp-admin/images/xit.gif wp-admin/images/yes.png wp-admin/includes wp-admin/includes/admin-filters.php wp-admin/includes/admin.php wp-admin/includes/ajax-actions.php wp-admin/includes/bookmark.php wp-admin/includes/class-automatic-upgrader-skin.php wp-admin/includes/class-bulk-plugin-upgrader-skin.php wp-admin/includes/class-bulk-theme-upgrader-skin.php wp-admin/includes/class-bulk-upgrader-skin.php wp-admin/includes/class-core-upgrader.php wp-admin/includes/class-file-upload-upgrader.php wp-admin/includes/class-ftp-pure.php wp-admin/includes/class-ftp-sockets.php wp-admin/includes/class-ftp.php wp-admin/includes/class-language-pack-upgrader-skin.php wp-admin/includes/class-language-pack-upgrader.php wp-admin/includes/class-pclzip.php wp-admin/includes/class-plugin-installer-skin.php wp-admin/includes/class-plugin-upgrader-skin.php wp-admin/includes/class-plugin-upgrader.php wp-admin/includes/class-theme-installer-skin.php wp-admin/includes/class-theme-upgrader-skin.php wp-admin/includes/class-theme-upgrader.php wp-admin/includes/class-walker-category-checklist.php wp-admin/includes/class-walker-nav-menu-checklist.php wp-admin/includes/class-walker-nav-menu-edit.php wp-admin/includes/class-wp-ajax-upgrader-skin.php wp-admin/includes/class-wp-automatic-updater.php wp-admin/includes/class-wp-comments-list-table.php wp-admin/includes/class-wp-filesystem-base.php wp-admin/includes/class-wp-filesystem-direct.php wp-admin/includes/class-wp-filesystem-ftpext.php wp-admin/includes/class-wp-filesystem-ftpsockets.php wp-admin/includes/class-wp-filesystem-ssh2.php wp-admin/includes/class-wp-importer.php wp-admin/includes/class-wp-internal-pointers.php wp-admin/includes/class-wp-links-list-table.php wp-admin/includes/class-wp-list-table-compat.php wp-admin/includes/class-wp-list-table.php wp-admin/includes/class-wp-media-list-table.php wp-admin/includes/class-wp-ms-sites-list-table.php wp-admin/includes/class-wp-ms-themes-list-table.php wp-admin/includes/class-wp-ms-users-list-table.php wp-admin/includes/class-wp-plugin-install-list-table.php wp-admin/includes/class-wp-plugins-list-table.php wp-admin/includes/class-wp-post-comments-list-table.php wp-admin/includes/class-wp-posts-list-table.php wp-admin/includes/class-wp-press-this.php wp-admin/includes/class-wp-screen.php wp-admin/includes/class-wp-site-icon.php wp-admin/includes/class-wp-terms-list-table.php wp-admin/includes/class-wp-theme-install-list-table.php wp-admin/includes/class-wp-themes-list-table.php wp-admin/includes/class-wp-upgrader-skin.php wp-admin/includes/class-wp-upgrader-skins.php wp-admin/includes/class-wp-upgrader.php wp-admin/includes/class-wp-users-list-table.php wp-admin/includes/comment.php wp-admin/includes/continents-cities.php wp-admin/includes/credits.php wp-admin/includes/dashboard.php wp-admin/includes/deprecated.php wp-admin/includes/edit-tag-messages.php wp-admin/includes/export.php wp-admin/includes/file.php wp-admin/includes/image-edit.php wp-admin/includes/image.php wp-admin/includes/import.php wp-admin/includes/list-table.php wp-admin/includes/media.php wp-admin/includes/menu.php wp-admin/includes/meta-boxes.php wp-admin/includes/misc.php wp-admin/includes/ms-admin-filters.php wp-admin/includes/ms-deprecated.php wp-admin/includes/ms.php wp-admin/includes/nav-menu.php wp-admin/includes/network.php wp-admin/includes/noop.php wp-admin/includes/options.php wp-admin/includes/plugin-install.php wp-admin/includes/plugin.php wp-admin/includes/post.php wp-admin/includes/revision.php wp-admin/includes/schema.php wp-admin/includes/screen.php wp-admin/includes/taxonomy.php wp-admin/includes/template.php wp-admin/includes/theme-install.php wp-admin/includes/theme.php wp-admin/includes/translation-install.php wp-admin/includes/update-core.php wp-admin/includes/update.php wp-admin/includes/upgrade.php wp-admin/includes/user.php wp-admin/includes/widgets.php wp-admin/js wp-admin/js/accordion.js wp-admin/js/accordion.min.js wp-admin/js/bookmarklet.js wp-admin/js/bookmarklet.min.js wp-admin/js/color-picker.js wp-admin/js/color-picker.min.js wp-admin/js/comment.js wp-admin/js/comment.min.js wp-admin/js/common.js wp-admin/js/common.min.js wp-admin/js/custom-background.js wp-admin/js/custom-background.min.js wp-admin/js/custom-header.js wp-admin/js/customize-controls.js wp-admin/js/customize-controls.min.js wp-admin/js/customize-nav-menus.js wp-admin/js/customize-nav-menus.min.js wp-admin/js/customize-widgets.js wp-admin/js/customize-widgets.min.js wp-admin/js/dashboard.js wp-admin/js/dashboard.min.js wp-admin/js/edit-comments.js wp-admin/js/edit-comments.min.js wp-admin/js/editor-expand.js wp-admin/js/editor-expand.min.js wp-admin/js/editor.js wp-admin/js/editor.min.js wp-admin/js/farbtastic.js wp-admin/js/gallery.js wp-admin/js/gallery.min.js wp-admin/js/image-edit.js wp-admin/js/image-edit.min.js wp-admin/js/inline-edit-post.js wp-admin/js/inline-edit-post.min.js wp-admin/js/inline-edit-tax.js wp-admin/js/inline-edit-tax.min.js wp-admin/js/iris.min.js wp-admin/js/language-chooser.js wp-admin/js/language-chooser.min.js wp-admin/js/link.js wp-admin/js/link.min.js wp-admin/js/media-gallery.js wp-admin/js/media-gallery.min.js wp-admin/js/media-upload.js wp-admin/js/media-upload.min.js wp-admin/js/media.js wp-admin/js/media.min.js wp-admin/js/nav-menu.js wp-admin/js/nav-menu.min.js wp-admin/js/password-strength-meter.js wp-admin/js/password-strength-meter.min.js wp-admin/js/plugin-install.js wp-admin/js/plugin-install.min.js wp-admin/js/post.js wp-admin/js/post.min.js wp-admin/js/postbox.js wp-admin/js/postbox.min.js wp-admin/js/press-this.js wp-admin/js/press-this.min.js wp-admin/js/revisions.js wp-admin/js/revisions.min.js wp-admin/js/set-post-thumbnail.js wp-admin/js/set-post-thumbnail.min.js wp-admin/js/svg-painter.js wp-admin/js/svg-painter.min.js wp-admin/js/tags-box.js wp-admin/js/tags-box.min.js wp-admin/js/tags-suggest.js wp-admin/js/tags-suggest.min.js wp-admin/js/tags.js wp-admin/js/tags.min.js wp-admin/js/theme.js wp-admin/js/theme.min.js wp-admin/js/updates.js wp-admin/js/updates.min.js wp-admin/js/user-profile.js wp-admin/js/user-profile.min.js wp-admin/js/user-suggest.js wp-admin/js/user-suggest.min.js wp-admin/js/widgets.js wp-admin/js/widgets.min.js wp-admin/js/word-count.js wp-admin/js/word-count.min.js wp-admin/js/wp-fullscreen-stub.js wp-admin/js/wp-fullscreen-stub.min.js wp-admin/js/xfn.js wp-admin/js/xfn.min.js wp-admin/maint repair.php Database Repair and Optimization Script. wp-admin/network wp-admin/network/about.php wp-admin/network/admin.php wp-admin/network/credits.php wp-admin/network/edit.php wp-admin/network/freedoms.php wp-admin/network/index.php wp-admin/network/menu.php wp-admin/network/plugin-editor.php wp-admin/network/plugin-install.php wp-admin/network/plugins.php wp-admin/network/profile.php wp-admin/network/settings.php wp-admin/network/setup.php wp-admin/network/site-info.php wp-admin/network/site-new.php wp-admin/network/site-settings.php wp-admin/network/site-themes.php wp-admin/network/site-users.php wp-admin/network/sites.php wp-admin/network/theme-editor.php wp-admin/network/theme-install.php wp-admin/network/themes.php wp-admin/network/update-core.php wp-admin/network/update.php wp-admin/network/upgrade.php wp-admin/network/user-edit.php wp-admin/network/user-new.php wp-admin/network/users.php wp-admin/user wp-admin/user/about.php wp-admin/user/admin.php wp-admin/user/credits.php wp-admin/user/freedoms.php wp-admin/user/index.php wp-admin/user/menu.php wp-admin/user/profile.php wp-admin/user/user-edit.php wp-content This directory is typically not upgraded. The /wp-content/ directory is for user-supplied content. WordPress upgrades are supposed to specifically avoid doing anything to any of the contents of this directory, unless the user wants the latest version of the default WordPress Themes. WordPress Themes and WordPress Plugins are stored in this directory. Directories: wp-content/plugins/ wp-contents/themes/ Files: wp-content/index.php This is a mostly blank file used to hide the the inner file structure in case the web server is not configured to do so. wp-content/plugins All WordPress plugins are placed in this directory. The default plugin shipped with WordPress is an example plugin mostly for plugin developers, the Hello Dolly plugin, which displays random lines of the song "Hello Dolly." Current versions also include the Akismet comment spam fighting WordPress Plugin as an option. Lastly there is another copy of the mostly blank index.php to help hide file structure. wp-content/plugins/akismet/ wp-content/plugins/hello.php wp/content/plugins/index.php wp-content/themes All WordPress Theme data is placed within this directory in its own folder such as example.com/wp-content/themes/themedir/. Included themes within the core 4.7 are: wp-content/themes/twentyeleven/ wp-content/themes/twentyfifteen/ wp-content/themes/twentyfourteen/ wp-content/themes/twentyseventeen/ wp-content/themes/twentyten/ wp-content/themes/twentythirteen/ wp-content/themes/twentytwelve/ wp-content/themes/themedir All files associated with a WordPress Theme are stored in their own directory under the wp-content/themes/themedir directory. As an example of the Theme files, the typical files included in the WordPress Default Theme under /wp-content/themes/default/ might be (but not limited to): wp-content/themes/themedir/comments.php Used to manage how the comments are displayed. wp-content/themes/themedir/footer.php Used to manage the footer of the pages. wp-content/themes/themedir/header.php Used to manage the header of every page. wp-content/themes/themedir/index.php Used to manage how the posts are displayed in your homepage. wp-content/themes/themedir/search.php Used to display a search form to search for entries. wp-content/themes/themedir/sidebar.php Used to manage the sidebar. wp-content/themes/themedir/style.css The main CSS file of WordPress. wp-content/themes/themedir/assets Some WordPress Themes store images in a subdirectory under their Theme folder. For example, images used by the default theme are in wp-content/themes/default/assets/. wp-includes Directories wp-includes/ID3/ wp-includes/IXR/ wp-includes/Requests/ wp-includes/SimplePie/ wp-includes/Text/ wp-includes/certificates/ wp-includes/css/ wp-includes/customize/ wp-includes/fonts/ wp-includes/images/ wp-includes/js/ wp-includes/pomo/ wp-includes/random_compat/ wp-includes/rest-api/ wp-includes/theme-compat/ wp-includes/widgets/ Files: wp-includes/admin-bar.php wp-includes/atomlib.php wp-includes/author-template.php wp-includes/bookmark-template.php wp-includes/bookmark.php wp-includes/cache.php wp-includes/canonical.php wp-includes/capabilities.php wp-includes/category-template.php wp-includes/category.php wp-includes/class-IXR.php wp-includes/class-feed.php wp-includes/class-http.php wp-includes/class-json.php wp-includes/class-oembed.php wp-includes/class-phpass.php wp-includes/class-phpmailer.php wp-includes/class-pop3.php wp-includes/class-requests.php wp-includes/class-simplepie.php wp-includes/class-smtp.php wp-includes/class-snoopy.php wp-includes/class-walker-category-dropdown.php wp-includes/class-walker-category.php wp-includes/class-walker-comment.php wp-includes/class-walker-nav-menu.php wp-includes/class-walker-page-dropdown.php wp-includes/class-walker-page.php wp-includes/class-wp-admin-bar.php wp-includes/class-wp-ajax-response.php wp-includes/class-wp-comment-query.php wp-includes/class-wp-comment.php wp-includes/class-wp-customize-control.php wp-includes/class-wp-customize-manager.php wp-includes/class-wp-customize-nav-menus.php wp-includes/class-wp-customize-panel.php wp-includes/class-wp-customize-section.php wp-includes/class-wp-customize-setting.php wp-includes/class-wp-customize-widgets.php wp-includes/class-wp-dependency.php wp-includes/class-wp-editor.php wp-includes/class-wp-embed.php wp-includes/class-wp-error.php wp-includes/class-wp-feed-cache-transient.php wp-includes/class-wp-feed-cache.php wp-includes/class-wp-hook.php wp-includes/class-wp-http-cookie.php wp-includes/class-wp-http-curl.php wp-includes/class-wp-http-encoding.php wp-includes/class-wp-http-ixr-client.php wp-includes/class-wp-http-proxy.php wp-includes/class-wp-http-requests-hooks.php wp-includes/class-wp-http-requests-response.php wp-includes/class-wp-http-response.php wp-includes/class-wp-http-streams.php wp-includes/class-wp-image-editor-gd.php wp-includes/class-wp-image-editor-imagick.php wp-includes/class-wp-image-editor.php wp-includes/class-wp-list-util.php wp-includes/class-wp-locale-switcher.php wp-includes/class-wp-locale.php wp-includes/class-wp-matchesmapregex.php wp-includes/class-wp-meta-query.php wp-includes/class-wp-metadata-lazyloader.php wp-includes/class-wp-network-query.php wp-includes/class-wp-network.php wp-includes/class-wp-oembed-controller.php wp-includes/class-wp-post-type.php wp-includes/class-wp-post.php wp-includes/class-wp-query.php wp-includes/class-wp-rewrite.php wp-includes/class-wp-role.php wp-includes/class-wp-roles.php wp-includes/class-wp-session-tokens.php wp-includes/class-wp-simplepie-file.php wp-includes/class-wp-simplepie-sanitize-kses.php wp-includes/class-wp-site-query.php wp-includes/class-wp-site.php wp-includes/class-wp-tax-query.php wp-includes/class-wp-taxonomy.php wp-includes/class-wp-term-query.php wp-includes/class-wp-term.php wp-includes/class-wp-text-diff-renderer-inline.php wp-includes/class-wp-text-diff-renderer-table.php wp-includes/class-wp-theme.php wp-includes/class-wp-user-meta-session-tokens.php wp-includes/class-wp-user-query.php wp-includes/class-wp-user.php wp-includes/class-wp-walker.php wp-includes/class-wp-widget-factory.php wp-includes/class-wp-widget.php wp-includes/class-wp-xmlrpc-server.php wp-includes/class-wp.php wp-includes/class.wp-dependencies.php wp-includes/class.wp-scripts.php wp-includes/class.wp-styles.php wp-includes/comment-template.php wp-includes/comment.php wp-includes/compat.php wp-includes/cron.php wp-includes/date.php wp-includes/default-constants.php wp-includes/default-filters.php wp-includes/default-widgets.php wp-includes/deprecated.php wp-includes/embed-template.php wp-includes/embed.php wp-includes/feed-atom-comments.php wp-includes/feed-atom.php wp-includes/feed-rdf.php wp-includes/feed-rss.php wp-includes/feed-rss2-comments.php wp-includes/feed-rss2.php wp-includes/feed.php wp-includes/formatting.php wp-includes/functions.php wp-includes/functions.wp-scripts.php wp-includes/functions.wp-styles.php wp-includes/general-template.php wp-includes/http.php wp-includes/kses.php wp-includes/l10n.php wp-includes/link-template.php wp-includes/load.php wp-includes/locale.php wp-includes/media-template.php wp-includes/media.php wp-includes/meta.php wp-includes/ms-blogs.php wp-includes/ms-default-constants.php wp-includes/ms-default-filters.php wp-includes/ms-deprecated.php wp-includes/ms-files.php wp-includes/ms-functions.php wp-includes/ms-load.php wp-includes/ms-settings.php wp-includes/nav-menu-template.php wp-includes/nav-menu.php wp-includes/option.php wp-includes/pluggable-deprecated.php wp-includes/pluggable.php wp-includes/plugin.php wp-includes/post-formats.php wp-includes/post-template.php wp-includes/post-thumbnail-template.php wp-includes/post.php wp-includes/query.php wp-includes/registration-functions.php wp-includes/registration.php wp-includes/rest-api.php wp-includes/revision.php wp-includes/rewrite.php wp-includes/rss-functions.php wp-includes/rss.php wp-includes/script-loader.php wp-includes/session.php wp-includes/shortcodes.php wp-includes/taxonomy.php wp-includes/template-loader.php wp-includes/template.php wp-includes/theme.php wp-includes/update.php wp-includes/user.php wp-includes/vars.php wp-includes/version.php wp-includes/widgets.php wp-includes/wlwmanifest.xml wp-includes/wp-db.php wp-includes/wp-diff.php wp-includes/ID3/ wp-includes/ID3/getid3.lib.php wp-includes/ID3/getid3.php wp-includes/ID3/license.commercial.txt wp-includes/ID3/license.txt wp-includes/ID3/module.audio-video.asf.php wp-includes/ID3/module.audio-video.flv.php wp-includes/ID3/module.audio-video.matroska.php wp-includes/ID3/module.audio-video.quicktime.php wp-includes/ID3/module.audio-video.riff.php wp-includes/ID3/module.audio.ac3.php wp-includes/ID3/module.audio.dts.php wp-includes/ID3/module.audio.flac.php wp-includes/ID3/module.audio.mp3.php wp-includes/ID3/module.audio.ogg.php wp-includes/ID3/module.tag.apetag.php wp-includes/ID3/module.tag.id3v1.php wp-includes/ID3/module.tag.id3v2.php wp-includes/ID3/module.tag.lyrics3.php wp-includes/ID3/readme.txt wp-includes/IXR/ wp-includes/IXR/class-IXR-base64.php wp-includes/IXR/class-IXR-client.php wp-includes/IXR/class-IXR-clientmulticall.php wp-includes/IXR/class-IXR-date.php wp-includes/IXR/class-IXR-error.php wp-includes/IXR/class-IXR-introspectionserver.php wp-includes/IXR/class-IXR-message.php wp-includes/IXR/class-IXR-request.php wp-includes/IXR/class-IXR-server.php wp-includes/IXR/class-IXR-value.php wp-includes/Requests/ Directories wp-includes/Requests/Auth/ wp-includes/Requests/Cookie/ wp-includes/Requests/Exception/ wp-includes/Requests/Proxy/ wp-includes/Requests/Response/ wp-includes/Requests/Transport/ wp-includes/Requests/Utility/ Files: wp-includes/Requests/Auth.php wp-includes/Requests/Cookie.php wp-includes/Requests/Exception.php wp-includes/Requests/Hooker.php wp-includes/Requests/Hooks.php wp-includes/Requests/IDNAEncoder.php wp-includes/Requests/IPv6.php wp-includes/Requests/IRI.php wp-includes/Requests/Proxy.php wp-includes/Requests/Response.php wp-includes/Requests/SSL.php wp-includes/Requests/Session.php wp-includes/Requests/Transport.php wp-includes/Requests/Auth/ wp-includes/Requests/Auth/Basic.php wp-includes/Requests/Cookie/ wp-includes/Requests/Cookie/Jar.php wp-includes/Requests/Exception/ Directories: wp-includes/Requests/Exception/HTTP wp-includes/Requests/Exception/Transport Files: wp-includes/Requests/Exception/HTTP.php wp-includes/Requests/Exception/Transport.php wp-includes/Requests/Exception/HTTP wp-includes/Requests/Exception/HTTP/304.php wp-includes/Requests/Exception/HTTP/305.php wp-includes/Requests/Exception/HTTP/306.php wp-includes/Requests/Exception/HTTP/400.php wp-includes/Requests/Exception/HTTP/401.php wp-includes/Requests/Exception/HTTP/402.php wp-includes/Requests/Exception/HTTP/403.php wp-includes/Requests/Exception/HTTP/404.php wp-includes/Requests/Exception/HTTP/405.php wp-includes/Requests/Exception/HTTP/406.php wp-includes/Requests/Exception/HTTP/407.php wp-includes/Requests/Exception/HTTP/408.php wp-includes/Requests/Exception/HTTP/409.php wp-includes/Requests/Exception/HTTP/410.php wp-includes/Requests/Exception/HTTP/411.php wp-includes/Requests/Exception/HTTP/412.php wp-includes/Requests/Exception/HTTP/413.php wp-includes/Requests/Exception/HTTP/414.php wp-includes/Requests/Exception/HTTP/415.php wp-includes/Requests/Exception/HTTP/416.php wp-includes/Requests/Exception/HTTP/417.php wp-includes/Requests/Exception/HTTP/418.php wp-includes/Requests/Exception/HTTP/428.php wp-includes/Requests/Exception/HTTP/429.php wp-includes/Requests/Exception/HTTP/431.php wp-includes/Requests/Exception/HTTP/500.php wp-includes/Requests/Exception/HTTP/501.php wp-includes/Requests/Exception/HTTP/502.php wp-includes/Requests/Exception/HTTP/503.php wp-includes/Requests/Exception/HTTP/504.php wp-includes/Requests/Exception/HTTP/505.php wp-includes/Requests/Exception/HTTP/511.php wp-includes/Requests/Exception/HTTP/Unknown.php wp-includes/Requests/Exception/Transport wp-includes/Requests/Exception/Transport/cURL.php wp-includes/Requests/Proxy/ wp-includes/Requests/Proxy/HTTP.php wp-includes/Requests/Response/ wp-includes/Requests/Response/Headers.php wp-includes/Requests/Transport/ wp-includes/Requests/Transport/cURL.php wp-includes/Requests/Transport/fsockopen.php wp-includes/Requests/Utility/ wp-includes/Requests/Utility/CaseInsensitiveDictionary.php wp-includes/Requests/Utility/FilteredIterator.php wp-includes/SimplePie/ Directories: wp-includes/SimplePie/Cache/ wp-includes/SimplePie/Content/Type/ wp-includes/SimplePie/Decode/HTML/ wp-includes/SimplePie/HTTP/ wp-includes/SimplePie/Net/ wp-includes/SimplePie/Parse/ wp-includes/SimplePie/XML/Declaration/ Files: wp-includes/SimplePie/Author.php wp-includes/SimplePie/Cache.php wp-includes/SimplePie/Caption.php wp-includes/SimplePie/Category.php wp-includes/SimplePie/Copyright.php wp-includes/SimplePie/Core.php wp-includes/SimplePie/Credit.php wp-includes/SimplePie/Enclosure.php wp-includes/SimplePie/Exception.php wp-includes/SimplePie/File.php wp-includes/SimplePie/IRI.php wp-includes/SimplePie/Item.php wp-includes/SimplePie/Locator.php wp-includes/SimplePie/Misc.php wp-includes/SimplePie/Parser.php wp-includes/SimplePie/Rating.php wp-includes/SimplePie/Registry.php wp-includes/SimplePie/Restriction.php wp-includes/SimplePie/Sanitize.php wp-includes/SimplePie/Source.php wp-includes/SimplePie/gzdecode.php wp-includes/Text/ wp-includes/certificates/ wp-includes/css/ wp-includes/customize/ wp-includes/fonts/ wp-includes/images/ wp-includes/js/ wp-includes/pomo/ wp-includes/random_compat/ wp-includes/rest-api/ wp-includes/theme-compat/ wp-includes/widgets/ --------------------------------------------------- OLD wp-includes/images wp-includes/images/smilies This is the directory that holds the smilies (emoticons) used in WordPress if the option is turned on. See Using Smilies for the full list. wp-includes/js wp-includes/js/quicktags.js Javascript file that contains functions to manage the tags toolbox when editing posts or pages. wp-includes/js/tinymce This directory includes the files that run the Rich Text Editor in the Write Post panel. wp-includes/languages See: WordPress Localization OLD wp-includes/cache.php wp-includes/capabilities.php wp-includes/class-IXR.php The Incutio XML-RPC Library. Contains XML RPC support functions. Supplied by http://scripts.incutio.com/xmlrpc/ wp-includes/classes.php Contains basic classes including the core post-fetching mechanism, WP_Query, and the rewrite manger, WP_Rewrite. wp-includes/class-pop3.php Contains a support class for accessing POP mailboxes. Used by wp-mail.php wp-includes/class-snoopy.php Snoopy is a PHP class that simulates a web browser. It automates the task of retrieving web page content and posting forms, for example. wp-includes/comment-functions.php wp-includes/default-filters.php wp-includes/feed-functions.php wp-includes/functions-compat.php Contains support functions that are present in newer PHP versions that are used only when running on older PHP versions. wp-includes/functions-formatting.php Contains support functions for cleaning XHTML and formatting text correctly in certain character sets. wp-includes/functions-post.php Contains support functions for managing posts in the database, querying user capabilities, fetching and writing comments, etc. wp-includes/functions.php Contains numerous vital support functions. Largest file in WordPress -- almost double the next largest file. wp-includes/gettext.php Part of the PHP-gettext GPL translation library. wp-includes/kses.php Contains functions that are used to render and filter HTML in posts or comments. wp-includes/links.php Contains functions that are used to manage and use the Links feature of WordPress. wp-includes/locale.php Contains functions to replace default weekdays and months values. wp-includes/pluggable-functions.php wp-includes/registration-functions.php wp-includes/rss-functions.php wp-includes/streams.php Contains a class to wrap file streams, string streams. wp-includes/template-functions-author.php Contains theme functions related to the author of a post or a comment. wp-includes/template-functions-category.php Contains theme functions related to categories. wp-includes/template-functions-comment.php Contains theme functions related to comments. wp-includes/template-functions-general.php Contains general theme functions. wp-includes/template-functions-links.php Contains theme functions related to links wp-includes/template-functions-post.php Contains theme functions related to posts. wp-includes/template-functions.php Contains all the "template-" files above. wp-includes/template-loader.php wp-includes/vars.php Used to set miscellaneous variables. wp-includes/version.php Used to set the currently used WordPress version. wp-includes/wp-db.php Contains functions used to connect to the MySQL database. wp-includes/wp-l10n.php Contains functions used in multi-language support. -------------------------------------- Giving WordPress Its Own Directory mikevanlohuizen — Tue, 16 Aug 2016 10:38:40 +0000 Many people want WordPress to power their website's root (e.g. http://example.com) but they don't want all of the WordPress files cluttering up their root directory. WordPress allows you to install it into a subdirectory, but have your website served from the website root. As of Version 3.5, Multisite users may use all of the functionality listed below. If you are running a version of WordPress older than 3.5, please update before installing a Multisite WordPress install on a subdirectory. Note to theme/plugin developers: this will not separate your code from WordPress. Themes and plugins will still reside under wp-content folder. Moving a Root install to its own directory Let's say you've installed wordpress at `example.com`. Now you have two different methods to move wordpress installations into subdirectory: 1) Without change of SITE-URL (remains `example.com` 2) With change in SITE-URL (it will redirect to `example.com/subdirectory`) Method I (Without URL change) 1) After Installing the wordpress in root folder, move EVERYTHING from root folder into subdirectory. 2) Create a `.htaccess` file in root folder, and put this content inside (just change example.com and my_subdir): <IfModule mod_rewrite.c> RewriteEngine on RewriteCond %{HTTP_HOST} ^(www.)?example.com$ RewriteCond %{REQUEST_URI} !^/my_subdir/ RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ /my_subdir/$1 RewriteCond %{HTTP_HOST} ^(www.)?example.com$ RewriteRule ^(/)?$ my_subdir/index.php [L] </IfModule> That's all :) Method II (With URL change) Moving process (p.s. If you've already installed WP in subdirectory, some steps might be already done automatically). Create the new location for the core WordPress files to be stored (we will use /wordpress in our examples). (On linux, use mkdir wordpress from your www directory. You'll probably want to use chown apache:apache on the wordpress directory you created.) Go to the General Screen. In WordPress address (URL): set the address of your main WordPress core files. Example: http://example.com/wordpress In Site address (URL): set root directory's URL. Example: http://example.com Click Save Changes. (Do not worry about the errors that happen now! Continue reading) Now move your WordPress core files (from root directory) to the subdirectory. Copy (NOT MOVE!) the index.php and .htaccess files from the WordPress directory into the root directory of your site (Blog address). The .htaccess file is invisible, so you may have to set your FTP client to show hidden files. If you are not using pretty permalinks, then you may not have a .htaccess file. If you are running WordPress on a Windows (IIS) server and are using pretty permalinks, you'll have a web.config rather than a .htaccess file in your WordPress directory. For the index.php file the instructions remain the same, copy (don't move) the index.php file to your root directory. The web.config file, must be treated differently than the .htaccess file so you must MOVE (DON'T COPY) the web.config file to your root directory. Open your root directory's index.php file in a text editor Change the following and save the file. Change the line that says: require( dirname( __FILE__ ) . '/wp-blog-header.php' ); to the following, using your directory name for the WordPress core files: require( dirname( __FILE__ ) . '/wordpress/wp-blog-header.php' ); Login to the new location. It might now be http://example.com/wordpress/wp-admin/ If you have set up Permalinks, go to the Permalinks Screen and update your Permalink structure. WordPress will automatically update your .htaccess file if it has the appropriate file permissions. If WordPress can't write to your .htaccess file, it will display the new rewrite rules to you, which you should manually copy into your .htaccess file (in the same directory as the main index.php file.) .htaccess modification In some cases, some people like to install separate versions in a subdirectory (such as /2010, /2011, /latest and etc..), and want that website (by default) used the latest version, then Install WordPress in a subdirectory, such as /my_subdir and in your root folder's .htaccess file add the following (just change the words as you need): RewriteEngine On RewriteCond %{HTTP_HOST} ^(www.)?example.com$ RewriteRule ^(/)?$ my_subdir[L] Now when users to go your root domain (example.com), it will automatically redirect to the subdirectory you specified. Note: This code comes from Site 5's post here: How to Redirect Your Domain to a Subfolder Using .htaccess. Moving Specific WordPress Folders The following links explains how to change specific directories within WordPress: Moving wp-content folder Moving Plugin Folder Moving Themes Folder Moving Uploads Folder Using Permalinks mikevanlohuizen — Tue, 16 Aug 2016 05:58:47 +0000 Permalinks are the permanent URLs to your individual weblog posts, as well as categories and other lists of weblog postings. A permalink is what another weblogger will use to link to your article (or section), or how you might send a link to your story in an e-mail message. The URL to each post should be permanent, and never change — hence permalink. Permalink Types There are three basic types of WordPress permalinks: Default: "Ugly" The default looks like http://example.com/?p=N where N is the Post ID number. It works on all server environments, but it doesn't look as nice as some of the other options. mod_rewrite: "Pretty Permalinks" Using mod_rewrite or lighttpd you can produce much nicer permalinks (see Pretty Permalinks). There are many different formats, but the most common, and most versatile looks like http://example.com/2012/post-name/ or http://example.com/2012/12/30/post-name Pretty permalinks are available under: Apache web server with the mod_rewrite module Nginx using try-files, e.g. according to this tutorial Hiawatha web server with UrlToolkit support enabled. Lighttpd using a 404 handler or mod_rewrite Caddy using rewrite, e.g. according to this tutorial PATHINFO: "Almost Pretty" PATHINFO permalinks look very much like mod_rewrite permalinks but for one exception: they have /index.php inserted before them, like so: http://example.com/index.php/yyyy/mm/dd/post-name/ Otherwise, they are the same as the "pretty" mod_rewrite permalinks, and are similarly flexible. Anything that mod_rewritepermalinks can do, PATHINFO permalinks can do, with the help of that /index.php part. Choosing your permalink structure In the Settings → Permalinks Screen, you can choose one of the more common permalink structures or enter your own in the "Custom structure" field using the structure tags. Please note: You do not put your site url in the permalinks fields. You only use one of the structure tags, or a combination of tags. To activate PATHINFO permalinks, start your permalink structure with index.php/. Structure Tags You can use these tags to customize your "Pretty" or "Almost Pretty" permalinks. A few hints: You do not put your site url in the permalinks fields. You only use one of the structure tags, or a combination of tags. Make sure to end your structure with either %post_id% or %postname% (e.g. /%year%/%monthnum%/%day%/%postname%/) so that each permalink points to an individual post. %year% The year of the post, four digits, for example 2018 %monthnum% Month of the year, for example 05 %day% Day of the month, for example 28 %hour% Hour of the day, for example 15 %minute% Minute of the hour, for example 43 %second% Second of the minute, for example 33 %post_id% The unique ID # of the post, for example 423 %postname% A sanitized version of the title of the post (post slug field on Edit Post/Page panel). So “This Is A Great Post!” becomes this-is-a-great-post in the URI. %category% A sanitized version of the category name (category slug field on New/Edit Category panel). Nested sub-categories appear as nested directories in the URI. %author% A sanitized version of the author name. Category base and Tag base The Category base and Tag base are prefixes used in URLs for category and tag archives, which look like this: example.net/wp/category_base/category_name example.net/wp/tag_base/tag_name The default values for these are category and tag. You can change them, but you can't remove them from the URLs altogether. Custom permalinks work on most systems without any problems, but there are still some conditions where problems occur. Using %category% with multiple categories on a post When you assign multiple categories to a post, only one can show up in the permalink. The categories are ordered alphabetically. In each group of sub-categories the order will also be alphabetical. (see Manage Categories). The post will still be accessible through all the categories as normal. Try the WP Category Permalink plugin if you want to choose which category shows up in the permalink. Using "Pretty" permalinks Requirements: Apache web server with the mod_rewrite module installed In WordPress's home directory, The FollowSymLinks option enabled FileInfo directives allowed (e.g. AllowOverride FileInfo or AllowOverride All) An .htaccess file (if this file is missing, WordPress will try to create it when you activate "pretty" permalinks) If you want WordPress to update the .htaccess file automatically, WordPress will need write access to the file. For nginx, a web server aimed at high concurrency, high performance and low memory usage, add the following location block within the server block: location / { try_files $uri $uri/ /index.php?$args; } For Hiawatha, a web server with a strong focus on security, use the following UrlToolkit rule: UrlToolkit { ToolkitID = wordpress RequestURI exists Return Match .*\?(.*) Rewrite /index.php?$1 Match .* Rewrite /index.php } Mac Users running WordPress locally must edit their httpd.conf file editing the AllowOverride line to read AllowOverride All in theDirectory "/Library/WebServer/Documents" host instructions. For Mac OS X 10.5.x and up this file is located in/private/etc/apache2/users/[your-username].conf, otherwise it is located at /etc/httpd/httpd.conf. When you create or update a "pretty" permalink structure, WordPress will generate rewrite rules and attempt to insert them into the proper .htaccess file. If it can't, it will say something like You should update your .htaccess now and print out the rules for you to copy and paste into the file (put them at the end). You'll probably need to do this only once, because WordPress does the rewriting internally. If you ever move your WordPress home directory (Site address), you'll need to repeat this step. WordPress will play nice with an existing .htaccess and will not delete any existing RewriteRules or other directives. If you have other mod_rewrite rules, put yours before WordPress's. Where's my .htaccess file? WordPress's index.php and .htaccess files should be together in the directory indicated by the Site address (URL) setting on your General Options page. Since the name of the file begins with a dot, the file may not be visible through an FTP client unless you change the preferences of the FTP tool to show all files, including the hidden files. Some hosts (e.g. Godaddy) may not show or allow you to edit .htaccess if you install WordPress through the Godaddy Hosting Connection installation. Creating and editing .htaccess If you do not already have a .htaccess file, create one. If you have shell or ssh access to the server, a simple touch .htaccesscommand will create the file. If you are using FTP to transfer files, create a file on your local computer, call it 1.htaccess, upload it to the root of your WordPress folder, and then rename it to .htaccess. You can edit the .htaccess file by FTP, shell, or (possibly) your host's control panel. The following permalink rewrite code should be included in your .htaccess file: # BEGIN WordPress RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] # END WordPress If your .htaccess file contains errors that bring down your site ("Internal Server Error (500)"), you will need to use FTP or your host'scontrol panel to delete the rogue .htaccess file. Automatically updating .htaccess If WordPress can't update your .htaccess file automatically, it will tell you something like If your .htaccess file were writable, we could do this automatically, but it isn’t… near the bottom of the Settings → Permalinks Screen. If you want to let WordPress do this, you'll need to give WordPress write access to the .htaccess file. The exact permissions necessary depend on your server setup. Try adding write permissions for the owner, then group, then world, testing after each change; once WordPress has edited the file successfully, don't add any further write permissions. After applying the permalinks, you should change the permissions to something stronger like 660 or 644 to prevent others on the server from potentially having access to it. Fixing Permalink Problems Fixing .htaccess Generation Issues If your installation of WordPress does not generate a .htaccess file or if it does not write the new rules onto your existing .htaccess file then there are a couple reasons that could be causing this. Work step by step and continue to the next step only if the previous step does not work. Change File Permissions: You must chmod the .htaccess file to 666 to edit it with the WordPress template editor, but this is not recommended, since if you do that, any user of your blog, who can edit templates will be able to edit it. You can change the permissions to 660 to make it server-writable, which again will have the same limitation. Server Blockage: Your host might have blocked the SERVER_SOFTWARE variable and this will cause WordPress' .htaccess generation to fail. If you are sure that your server is running Apache, you can force WordPress to believe that your server is running Apache by changing your wp-includes/vars.php file. Follow the steps below to implement these changes. Open the wp-includes/vars.php file using the built in file editor in your WordPress Admin panel. To navigate to this panel, login to WordPress, click on "Manage", then on "Files", scroll to the bottom and type in wp-includes/vars.php into the text box under the "Other Files" title. Look for $is_apache = strstr($_SERVER['SERVER_SOFTWARE'], 'Apache') ? 1 : 0; and replace it with // $is_apache = strstr($_SERVER['SERVER_SOFTWARE'], 'Apache') ? 1 : 0; Add a new line under // $is_apache = strstr($_SERVER['SERVER_SOFTWARE'], 'Apache') ? 1 : 0; and type in $is_apache = 1; Users of XAMPP (Windows): Some versions of XAMPP do not enable mod_rewrite by default (though it is compiled in Apache). To enable it — and thus enable WordPress to write the .htaccess file needed to create pretty permalinks — you must open apache/conf/httpd.conf and uncomment the line LoadModule rewrite_module modules/mod_rewrite.so(i.e., delete the hash/pound sign at the front of the line). Users of WAMP (Windows): Some versions of WAMP (all versions?) do not enable mod_rewrite or permit following SymLinks by default. To enable the required functionality navigate to the apache/conf/httpd.conf file, open with a text editor and uncomment the line LoadModule rewrite_module modules/mod_rewrite.so (i.e., delete the hash/pound sign at the front of the line). Then further down in the same file there is a section that starts with the line "Options FollowSymlinks". Change the second line in that section from "AllowOverride none" to AllowOverride all. Save edited httpd.conf and restart all WAMP modules. Your permalinks should now work. Tips and Tricks Avoiding interpretation as an archive link Note that even though one might never make more than one posting a day, and thus wishes to use e.g., %year%%monthnum%%day%, links so generated will however be interpreted as the archive of all posts for that day. One needs at least %year%%monthnum%%day%%hour% to target an individual post. Check for permalink structure A way to check if the blog has a permalink structure is: See Also User:Lazyking/Using Permalinks (Saetta Web Server) Linking Posts Pages and Categories for how to link from one article to another Resetting Your Password mikevanlohuizen — Tue, 16 Aug 2016 06:00:51 +0000 In WordPress, there is more than one way to reset your password. (Normally, the easiest way to reset it is through the "Lost your password?" link on the main login page for your blog or website.) However, there are certain times (especially if your email isn't working correctly) that you may have to take different steps to reset your password. Here's a list of different ways to reset a password. The method that you use depends on the type of access that you still have to your website. To Change Your Password To change your password in current versions: In the Administration Screen, menu, go to Users > All Users. Click on your username in the list to edit it. In the Edit User screen, scroll down to the New Password section and click the Generate Password button. If you want to change the automatically generated password, you can overwrite it by typing a new password in the box provided. The strength box will show you how good (strong) your password is. Click the Update User button. Your new password becomes active immediately. Through the automatic emailer If you know your username or the email account in your profile, you can use the "lost password" feature of WordPress. Go to your WordPress Login page (something like http://yoursite.com/wordpress/wp-login.php) Click on the "Lost your password?" link You will be taken to a page to enter some details. Enter your username or the email address on file for that account. Wait happily as your new password is emailed to you. Once you get your new password, login to your profile page and change this password to something you can remember. Through MySQL Command Line Get an MD5 hash of your password. Visit md5 Hash Generator, or... Create a key with Python, or... On Unix/Linux: Create a file called wp.txt, containing nothing but the new password. tr -d '\r\n' < wp.txt | md5sum | tr -d ' -' rm wp.txt On Mac OS X: Create a file called wp.txt, containing nothing but the new password. Then enter either of the lines below md5 -q ./wp.txt; rm ./wp.txt (If you want the MD5 hash printed out.) md5 -q ./wp.txt | pbcopy; rm ./wp.txt (If you want the MD5 hash copied to the clipboard.) "mysql -u root -p" (log in to MySQL) enter your mysql password "use (name-of-database)" (select WordPress database) "show tables;" (you're looking for a table name with "users" at the end) "SELECT ID, user_login, user_pass FROM (name-of-table-you-found);" (this gives you an idea of what's going on inside) "UPDATE (name-of-table-you-found) SET user_pass="(MD5-string-you-made)" WHERE ID = (id#-of-account-you-are-reseting-password-for);" (actually changes the password) "SELECT ID, user_login, user_pass FROM (name-of-table-you-found);" (confirm that it was changed) (type Control-D to exit mysql client) Note: if you have a recent version of MySQL (version 5.x?) you can have MySQL compute the MD5 hash for you. Skip step# 1 above. Do the following for step# 7 instead. "UPDATE (name-of-table-you-found) SET user_pass = MD5('(new-password)') WHERE ID = (id#-of-account-you-are-reseting-password-for);" (actually changes the password) Note that even if the passwords are salted, meaning they look like $P$BLDJMdyBwegaCLE0GeDiGtC/mqXLzB0, you can still replace the password with an MD5 hash, and WordPress will let you log in. Through phpMyAdmin This article is for those who have phpMyAdmin access to their database. Note: use phpMyAdmin at your own risk. If you doubt your ability to use it, seek further advice. WordPress is not responsible for loss of data. 1. Begin by logging into phpMyAdmin and clicking databases. 2. A list of databases will appear. Click on your WordPress database. 3. All the tables in your database will appear. If not, click Structure. 4. Look for wp_users in the Table column. 5. Click on the icon for browse. 6. Locate your username under user_login 7. Click edit (may look like a pencil icon in some versions of phpMyAdmin). 8. Your user_id will be shown. Click on Edit. 9. Next to the user_pass is a long list of numbers and letters. 10. Select and delete these and type in your new password. 11. Type in the password you want to use. You can type it in normally--but remember, it is case-sensitive. 12. In this example, the new password will be 'rabbitseatcarrots.' 13. Once you have done that, click the dropdown menu indicated, and select MD5 from the menu. 14. Check that your password is actually correct, and that MD5 is in the box. 15. Click the 'Go' button to the bottom right. 16. Test the new password on the login screen. If it doesn't work, check that you've followed these instructions exactly. Other Tutorials using phpMyAdmin Reset a WordPress password from phpMyAdmin Through FTP There is also an easy way to reset your password via FTP, if you're using the admin user. 1. Login to your site via FTP and download your active theme's functions.php file. 2. Edit the file and add this code to it, right at the beginning, after the first wp_set_password( 'password', 1 ); Enter your own new password for the main admin user. The "1" is the user ID number in the wp_users table. 3. Upload the modified file back to your site. 4. Once you are able to login, make sure to go back and remove that code. It will reset your password on every page load until you do so. Through WP CLI WP CLI is a command line tool for managing your WordPress installation. 1. Move into the /wordpress directory and type $ wp user list to see all users. Find the ID of the user you'd like to update. 2. Then, update the user $ wp user update 1 --user_pass=$UP3RstrongP4$$w0rd replacing "1" with the id of the user you want to update. More on wp cli Using the Emergency Password Reset Script If the other solutions listed above won't work, then try the Emergency Password Reset Script. Please note that it's not a plugin, it's a PHP script. A Word of Caution: The Emergency Password Reset Script requires that you know the administrator's username. It updates the administrator password and sends an email to the administrator's email address. Even if you don't receive the email, the password will still be changed. You do not need to be logged in to use it. (After all, if you could login, you wouldn't need the script.) Place the script in the root of your WordPress installation. Do not upload it to your WordPress Plugins directory. For security reasons, remember to delete the script when you are done. Directions for Use: Copy the emergency script from Emergency Password Script and put into a file called emergency.php in the root of your WordPress installation (the same directory that contains wp-config.php). In your browser, open http://example.com/emergency.php. As instructed, enter the administrator username (usually admin) and the new password, then click Update Options. A message is displayed noting the changed password. An email is sent to the blog administrator with the changed password information. Delete emergency.php from your server when you are done. Do not leave it on your server, as someone else could use it to change your password. Additional Reference Here is another password reset script that can be used without knowing the username or email. Roles and Capabilities mikevanlohuizen — Tue, 16 Aug 2016 06:01:56 +0000 WordPress uses a concept of Roles, designed to give the site owner the ability to control what users can and cannot do within the site. A site owner can manage the user access to such tasks as writing and editing posts, creating Pages,creating categories, moderating comments, managing plugins, managing themes, andmanaging other users, by assigning a specific role to each of the users. WordPress has six pre-defined roles: Super Admin, Administrator, Editor, Author, Contributor and Subscriber. Each role is allowed to perform a set of tasks called Capabilities. There are many capabilities including "publish_posts", "moderate_comments", and "edit_users". A default set of capabilities is pre-assigned to each role, but other capabilites can be assigned or removed using the add_cap() andremove_cap() functions. New roles can be introduced or removed using the add_role() and remove_role() functions. The Super Admin role allows a user to perform all possible capabilities. Each of the other roles has a decreasing number of allowed capabilities. For instance, the Subscriber role has just the "read" capability. One particular role should not be considered to be senior to another role. Rather, consider that roles define the user's responsibilities within the site. Summary of Roles Super Admin – somebody with access to the site network administration features and all other features. See the Create a Network article. Administrator (slug: 'administrator') – somebody who has access to all the administration features within a single site. Editor (slug: 'editor') – somebody who can publish and manage posts including the posts of other users. Author (slug: 'author') – somebody who can publish and manage their own posts. Contributor (slug: 'contributor') – somebody who can write and manage their own posts but cannot publish them. Subscriber (slug: 'subscriber') – somebody who can only manage their profile. Upon installing WordPress, an Administrator account is automatically created. The default role for new users can be set in Administration Screens > Settings > General. Roles A Role defines a set of tasks a user assigned the role is allowed to perform. For instance, the Super Admin role encompasses every possible task that can be performed within a Network of virtual WordPress sites. The Administrator role limits the allowed tasks only to those which affect a single site. On the other hand, the Author role allows the execution of just a small subset of tasks. The following sections list the default Roles and their capabilities: Super Admin Multisite Super Admins have, by default, all capabilities. The following Multisite-only capabilities are therefore only available to Super Admins: create_sites delete_sites manage_network manage_sites manage_network_users manage_network_plugins manage_network_themes manage_network_options upgrade_network setup_network In the case of single site WordPress installation, Administrators are, in effect, Super Admins. As such, they are the only ones to have access to additional admin capabilities. Administrator The capabilities of Administrators differs between single site and Multisite WordPress installations. All administrators have the following capabilities: activate_plugins delete_others_pages delete_others_posts delete_pages delete_posts delete_private_pages delete_private_posts delete_published_pages delete_published_posts edit_dashboard edit_others_pages edit_others_posts edit_pages edit_posts edit_private_pages edit_private_posts edit_published_pages edit_published_posts edit_theme_options export import list_users manage_categories manage_links manage_options moderate_comments promote_users publish_pages publish_posts read_private_pages read_private_posts read remove_users switch_themes upload_files customize delete_site Additional Admin Capabilities Only Administrators of single site installations have the following capabilities. In Multisite, only the Super Admin has these abilities: update_core update_plugins update_themes install_plugins install_themes delete_themes delete_plugins edit_plugins edit_themes edit_files edit_users add_users create_users delete_users unfiltered_html Editor delete_others_pages delete_others_posts delete_pages delete_posts delete_private_pages delete_private_posts delete_published_pages delete_published_posts edit_others_pages edit_others_posts edit_pages edit_posts edit_private_pages edit_private_posts edit_published_pages edit_published_posts manage_categories manage_links moderate_comments publish_pages publish_posts read read_private_pages read_private_posts unfiltered_html (not with Multisite) upload_files Author delete_posts delete_published_posts edit_posts edit_published_posts publish_posts read upload_files Contributor delete_posts edit_posts read Subscriber read Special Cases The following capabilities are special cases: unfiltered_upload - This capability is not available to any role by default (including Super Admins). The capability needs to be enabled by defining the following constant: define( 'ALLOW_UNFILTERED_UPLOADS', true ); With this constant defined, all roles on a single site install can be given the unfiltered_upload capability, but only Super Admins can be given the capability on a Multisite install. Capability vs. Role Table Note that the capabilities of Administrators differs between single site and Multisite WordPress installations, as described above . Capability Super Admin Administrator Editor Author Contributor Subscriber create_sites Y delete_sites Y manage_network Y manage_sites Y manage_network_users Y manage_network_plugins Y manage_network_themes Y manage_network_options Y upload_plugins Y upload_themes Y upgrade_network Y setup_network Y Capability Super Admin Administrator Editor Author Contributor Subscriber activate_plugins Y Y (single site or enabled by network setting) create_users Y Y (single site) delete_plugins Y Y (single site) delete_themes Y Y (single site) delete_users Y Y (single site) edit_files Y Y (single site) edit_plugins Y Y (single site) edit_theme_options Y Y edit_themes Y Y (single site) edit_users Y Y (single site) export Y Y import Y Y Capability Super Admin Administrator Editor Author Contributor Subscriber install_plugins Y Y (single site) install_themes Y Y (single site) list_users Y Y manage_options Y Y promote_users Y Y remove_users Y Y switch_themes Y Y update_core Y Y (single site) update_plugins Y Y (single site) update_themes Y Y (single site) edit_dashboard Y Y customize Y Y delete_site Y Y Capability Super Admin Administrator Editor Author Contributor Subscriber moderate_comments Y Y Y manage_categories Y Y Y manage_links Y Y Y edit_others_posts Y Y Y edit_pages Y Y Y edit_others_pages Y Y Y edit_published_pages Y Y Y publish_pages Y Y Y delete_pages Y Y Y delete_others_pages Y Y Y delete_published_pages Y Y Y delete_others_posts Y Y Y delete_private_posts Y Y Y edit_private_posts Y Y Y read_private_posts Y Y Y delete_private_pages Y Y Y edit_private_pages Y Y Y read_private_pages Y Y Y unfiltered_html Y Y (single site) Y (single site) unfiltered_html Y Y Y Capability Super Admin Administrator Editor Author Contributor Subscriber edit_published_posts Y Y Y Y upload_files Y Y Y Y publish_posts Y Y Y Y delete_published_posts Y Y Y Y edit_posts Y Y Y Y Y delete_posts Y Y Y Y Y Capability Super Admin Administrator Editor Author Contributor Subscriber read Y Y Y Y Y Y Capabilities switch_themes Since 2.0 Allows access to Administration Screens options: Appearance Appearance > Themes edit_themes Since 2.0 Allows access to Appearance > Theme Editor to edit theme files. edit_theme_options Since 3.0 Allows access to Administration Screens options: Appearance > Widgets Appearance > Menus Appearance > Customize if they are supported by the current theme Appearance > Header install_themes Since 2.8 Allows access to Administration Screens options: Appearance > Add New Themes activate_plugins Since 2.0 Allows access to Administration Screens options: Plugins edit_plugins Since 2.0 Allows access to Administration Screens options: Plugins > Plugin Editor install_plugins Since 2.7 Allows access to Administration Screens options: Plugins > Add New edit_users Since 2.0 Allows access to Administration Screens options: Users edit_files Since 2.0 Note: No longer used. manage_options Since 2.0 Allows access to Administration Screens options: Settings > General Settings > Writing Settings > Reading Settings > Discussion Settings > Permalinks Settings > Miscellaneous moderate_comments Since 2.0 Allows users to moderate comments from the Comments Screen (although a user needs the edit_posts Capability in order to access this) manage_categories Since 2.0 Allows access to Administration Screens options: Posts > Categories Links > Categories manage_links Since 2.0 Allows access to Administration Screens options: Links Links > Add New upload_files Since 2.0 Allows access to Administration Screens options: Media Media > Add New import Since 2.0 Allows access to Administration Screens options: Tools > Import Tools > Export unfiltered_html Since 2.0 Allows user to post HTML markup or even JavaScript code in pages, posts, comments and widgets. Note: Enabling this option for untrusted users may result in their posting malicious or poorly formatted code. Note: In WordPress Multisite, only Super Admins have the unfiltered_html capability. edit_posts Since 2.0 Allows access to Administration Screens options: Posts Posts > Add New Comments Comments > Awaiting Moderation edit_others_posts Since 2.0 Allows access to Administration Screens options: Manage > Comments (Lets user delete and edit every comment, see edit_posts above) user can edit other users' posts through function get_others_drafts() user can see other users' images in inline-uploading [no? see inline-uploading.php] See Exceptions edit_published_posts Since 2.0 User can edit their published posts. This capability is off by default. The core checks the capability edit_posts, but on demand this check is changed to edit_published_posts. If you don't want a user to be able to edit their published posts, remove this capability. publish_posts Since 2.0 See and use the "publish" button when editing their post (otherwise they can only save drafts) Can use XML-RPC to publish (otherwise they get a "Sorry, you can not post on this weblog or category.") edit_pages Since 2.0 Allows access to Administration Screens options: Pages Pages > Add New read Since 2.0 Allows access to Administration Screens options: Dashboard Users > Your Profile Used nowhere in the core code except the menu.php publish_pages Since 2.1 edit_others_pages Since 2.1 edit_published_pages Since 2.1 delete_pages Since 2.1 delete_others_pages Since 2.1 delete_published_pages Since 2.1 delete_posts Since 2.1 delete_others_posts Since 2.1 delete_published_posts Since 2.1 delete_private_posts Since 2.1 edit_private_posts Since 2.1 read_private_posts Since 2.1 delete_private_pages Since 2.1 edit_private_pages Since 2.1 read_private_pages Since 2.1 delete_users Since 2.1 create_users Since 2.1 Allows creating new users. Without other capabilities, created users will have your blog's New User Default Role. unfiltered_upload Since 2.3 edit_dashboard Since 2.5 customize Since 4.0 Allows access to the Customizer. delete_site Since 4.0 Allows the user to delete the current site (Multisite only). update_plugins Since 2.6 delete_plugins Since 2.6 update_themes Since 2.7 update_core Since 3.0 list_users Since 3.0 Allows access to Administration Screens options: Users remove_users Since 3.0 add_users Since 3.0 Replaced in 4.4 with promote_users promote_users Since 3.0 Enables the "Change role to..." dropdown in the admin user list. This does not depend on 'edit_users' capability. Enables the 'Add Existing User' to function for multi-site installs. delete_themes Since 3.0 export Since 3.0 edit_comment Since 3.1 create_sites Since 3.1 Multi-site only Allows user to create sites on the network delete_sites Since 3.1 Multi-site only Allows user to delete sites on the network manage_network Since 3.0 Multi-site only Allows access to Super Admin menu Allows user to upgrade network manage_sites Since 3.0 Multi-site only Allows access to Network Sites menu Allows user to add, edit, delete, archive, unarchive, activate, deactivate, spam and unspam new site/blog in the network manage_network_users Since 3.0 Multi-site only Allows access to Network Users menu manage_network_themes Since 3.0 Multi-site only Allows access to Network Themes menu manage_network_options Since 3.0 Multi-site only Allows access to Network Options menu manage_network_plugins Multi-site only Allows access to Network Plugins menu upload_plugins Since 4.0 Multi-site only Allows user to upload plugin ZIP files from the Network Plugins -> Add New menu upload_themes Since 4.0 Multi-site only Allows user to upload theme ZIP files from the Network Themes -> Add New menu upgrade_network Since 4.8 Multi-site only is used to determine whether a user can access the Network Upgrade page in the network admin. Related to this, the capability is also checked to determine whether to show the notice that a network upgrade is required. The capability is not mapped, so it is only granted to network administrators. See #39205 for background discussion. setup_network Since 4.8 Multi-site only is used to determine whether a user can setup multisite, i.e. access the Network Setup page. Before setting up a multisite, the capability is mapped to the `manage_options` capability, so that it is granted to administrators. Once multisite is setup, it is mapped to `manage_network_options`, so that it is granted to network administrators. See #39206 for background discussion. Resources Plugins Members Plugin User Access Manager Advanced Access Manager User Role Editor WordPress User Role Editor Simple Membership Plugin View Admin As (manage & test roles) Information WordPress Capabilities WordPress Roles and Capabilities at a Glance - A simplified visual representation of WordPress roles and capabilities Formatting Date and Time mikevanlohuizen — Tue, 16 Aug 2016 06:03:28 +0000 Customizing the Time and Date Format Certain WordPress tag functions are used to display or return date and time information; the_date() and the_time() are examples of this. By default, these functions will display or return date and time in format as it is set in Administration > Settings > General. This is the place where customizing format for Date and Time will take effect throughout the whole WordPress installation. [caption id="attachment_2083" align="alignnone" width="883"] Formatting Date and Time[/caption] Notice the string of characters next to each Date and Time formatting in screenshot. This string is called a format string. Each letter represents specific part of Date or Time. For example, the format string: l, F j, Y creates a date that look like this (note that commas are read literally): Friday, September 24, 2004 Here is what each format character in the string above represents: l = Full name for day of the week (lower-case L). F = Full name for the month. j = The day of the month. Y = The year in 4 digits. (lower-case y gives the year's last 2 digits) Format characters are standardized and globally used in PHP programming language. As WordPress is written in PHP programming language you can use the table of Date and Time format characters directly from the PHP website. Here is a table of some of the more useful items found there: Day of Month d Numeric, with leading zeros 01–31 j Numeric, without leading zeros 1–31 S The English suffix for the day of the month st, nd or th in the 1st, 2nd or 15th. Weekday l Full name (lowercase 'L') Sunday – Saturday D Three letter name Mon – Sun Month m Numeric, with leading zeros 01–12 n Numeric, without leading zeros 1–12 F Textual full January – December M Textual three letters Jan - Dec Year Y Numeric, 4 digits Eg., 1999, 2003 y Numeric, 2 digits Eg., 99, 03 Time a Lowercase am, pm A Uppercase AM, PM g Hour, 12-hour, without leading zeros 1–12 h Hour, 12-hour, with leading zeros 01–12 G Hour, 24-hour, without leading zeros 0-23 H Hour, 24-hour, with leading zeros 00-23 i Minutes, with leading zeros 00-59 s Seconds, with leading zeros 00-59 T Timezone abbreviation Eg., EST, MDT ... Full Date/Time c ISO 8601 2004-02-12T15:19:21+00:00 r RFC 2822 Thu, 21 Dec 2000 16:01:07 +0200 U Unix timestamp (seconds since Unix Epoch) 1455880176 Format String Examples Here are some examples of date format with the result output. F j, Y g:i a - November 6, 2010 12:50 am F j, Y - November 6, 2010 F, Y - November, 2010 g:i a - 12:50 am g:i:s a - 12:50:48 am l, F jS, Y - Saturday, November 6th, 2010 M j, Y @ G:i - Nov 6, 2010 @ 0:50 Y/m/d \a\t g:i A - 2010/11/06 at 12:50 AM Y/m/d \a\t g:ia - 2010/11/06 at 12:50am Y/m/d g:i:s A - 2010/11/06 12:50:48 AM Y/m/d - 2010/11/06 Overriding General Settings Formatting Functions for Time and Date accept format string as a parameter in order to override default Date and Time formatting for certain places in theme or plugin files. Just the same as in General Settings, this format string is a template of characters where each character represents specific part of Date or Time. Inside the template file, setting the Date and Time format string as a parameter for the_time() template tag, would look something like this: [php]Posted on .[/php] Which will render on the frontend of your site as following: Posted on Friday, September 24th, 2004. Localization To localize Date and Time, use the date_i18n() function. The date_i18n() function basically behaves like the PHP date() function, except that it also translates things like month names and weekdays and similar into the current locale for the site. You can replace a call to date() with a call to date_i18n(), using the same arguments. [php] $date = date_i18n( 'F j, Y' ); $time = date_i18n( 'g:i a' ); [/php] Alternatively, you can wrap your predefined format in __() or _e() in order to allow translators to adjust the Date and Time to the proper local format. If you do so, then you should also include a translator comment, to let the translators know what the date format is referring to and where it is used, so they can convert it accurately. [php] __( 'Y/m/d g:i:s a', 'textdomain' ); [/php] Escaping Some letters do not have an associated format in the PHP date function. For example x passed in the format string will currently return a literal x. However, this can change at some point in the future and x may have a format associated with it. This is why you should always escape literal character in a date formatted string with \. Note that, in following example, every letter of word of is escaped. [php] date_i18n( __( 'l jS \o\f F Y', 'textdomain' ) ); [/php] This example will render as following on the frontend of your site: Saturday 25th of February 2017 Create A Network mikevanlohuizen — Thu, 28 Jul 2016 23:59:31 +0000 As of WordPress 3.0, you have the ability to create a network of sites by using the multisite feature. This article contains instructions for creating a multisite network. It is advised to read the post "Before you Create a Network" first, as it contains important information about planning your network. A multisite network can be very similar to your own personal version of WordPress.com. End users of your network can create their own sites on demand, just like end users of WordPress.com can create blogs on demand. If you do not have any need to allow end users to create their own sites on demand, you can create a multisite network in which only you, the administrator, can add new sites. A multisite network is a collection of sites that all share the same WordPress installation core files. They can also share plugins and themes. The individual sites in the network are virtual sites in the sense that they do not have their own directories on your server, although they do have separate directories for media uploads within the shared installation, and they do have separate tables in the database. NOTE: Upgraded and can't find the Network Admin menu? Step 0: Before You Begin Compared with a typical single WordPress installation a network installation has additional considerations. You must decide if you want to use subdomains or subfolders and how you want to manage them. Installing themes and plugins is different: for example, each individual site of a network can activate both, but install neither. This guide describes how to install manually WordPress Multisite in your current WordPress installation. There are also available ready-to-run packages from BitNami. Please read Before You Create A Network in full before continuing. Step 1: Prepare Your WordPress Your existing WordPress site will be updated when creating a network. Unless this is a fresh install and you have nothing to lose, please backup your database and files. Verify that Pretty Permalinks work on your single WP instance. Also deactivate all active plugins. You can reactivate them again after the network is created. If you plan to run WordPress out of its own directory, do that before activating Multisite. Step 2: Allow Multisite To enable the Network Setup menu item, you must first define multisite in the wp-config.php file. Open up wp-config.php and add this line above where it says /* That's all, stop editing! Happy blogging. */. If it doesn't say that anywhere, then add the line somewhere above the first line that begins with require or include: /* Multisite */ define( 'WP_ALLOW_MULTISITE', true ); You will need to refresh your browser to continue. Step 3: Installing a Network The previous step enables the Network Setup item in your Tools menu. Use that menu item to go to the Create a Network of WordPress Sites screen. To see an example of the Create a Network of WordPress Sites screen, look at Administration >Tools > Network Setup. The screen does not look exactly the same in all circumstances. The example shown is for an installation on localhost, which restricts the options available. Addresses of Sites in your Network You are given the choice between sub-domains and sub-directories, except when existing settingsrestrict your choice. You must choose one or the other. You can reconfigure your network to use the other choice after installation, despite the advice on the screen, but reconfiguring it might not be easy. You only need wildcard DNS for on-demand domain-based sites, despite the advice that may be on the screen. Once more: See Before You Create A Network. Sub-domains — a domain-based network in which on-demand sites use subdomains Sub-directories — a path-based network in which on-demand sites use paths Network Details These are filled in automatically, but you can make changes. Server Address The domain of the URL you are using to access your WordPress installation. Network Title The title of your network as a whole. Admin E-mail Address Your email address as super admin of the network as a whole. Double-check the details and press the Install button. Note: The installer may perform a check for wildcard subdomains when you have not configured them yet, or when you do not need them at all. Ignore the warning if it does not apply to your network. See the Server Requirements section in Before You Create A Network for information about wildcard subdomains. Step 4: Enabling the Network To enable your network, follow the instructions on the Create a Network of WordPress Sites screen. The instructions that you see are customized for your installation. They might not be the same as the examples you see here. Back up your existing wp-config.php and .htaccess files, unless this is a fresh install and you have nothing to lose. There are two steps: 1. Add the specified lines to your wp-config.php file The extra lines go just after where you added the line in Step 1: Prepare Your WordPress. 2. Add the specified lines to your .htaccess file If you do not have a .htaccess file, then create it in the same directory as your wp-config.php file. If you ALREADY have a .htaccess file, replace any existing WP lines with these new ones. In some cases you might also have to add Options FollowSymlinks at the start of the file. After completing these steps, log in again using the link provided. You might have to clear your browser's cache and cookies in order to log in. Step 5: Network Admin Settings At the left of your WordPress toolbar, My Sites is now the second item. There, all your sites are listed, with handy fly-out menus, as well as a Network Admin menu item. Under Network Admin you can use the Dashboard item to go to the Network Dashboard screen. Go to the Settings Screen to configure network options, and the Sites Screen to manage your sites. For more information, see: Network Admin Upgraded and can't find the Network Admin menu? Step 6: Administration There are some additional things you might need to know about advanced administration of the network, due to the additional complexity of a Multisite. Even if you're familiar with WordPress, the location and behavior of Multisite Network Administration can be confusing. Read Multisite Network Administration for more information. For help troubleshooting: Debugging a WordPress Network Migrating Multiple Blogs into WordPress 3.0 Multisite Related Articles Hosting WordPress Installing Multiple Blogs How to adapt my plugin to Multisite? Using Themes mikevanlohuizen — Tue, 16 Aug 2016 10:32:11 +0000 What is a Theme? Fundamentally, the WordPress Theme system is a way to "skin" your WordPress site. Yet, it is more than just a "skin". Skinning your site implies that only the design is changed. WordPress Themes can provide much more control over the visual presentation of your content and other data on your WordPress site, as well as behavior of certain site's elements while interacting with visitors. A WordPress Theme is a collection of files that work together to produce a graphical interface with an underlying unifying design for a website. These files are called template files. A Theme modifies the way the site is displayed, without modifying the underlying software. Themes may include customized template files, image files (*.jpg, *.png, *.gif), style sheets (*.css), custom Pages, as well as any necessary code files (*.php). For an introduction to template files, see Template Files. Let's say you write a lot about cheese and gadgets. Through the use of the WordPress Loop and template files, you can customize your Cheese category posts to look different from your Gadgets category posts. With this powerful control over what different pages and categories look like on your site, you are limited only by your imagination. For information on how to create custom look for various templates in your theme, take a look at Template Hierarchy. [caption id="attachment_2167" align="alignnone" width="2880"] Template Hierarchy - the structure of WordPress theme files[/caption] To better understand this diagram, you can interact with it. Default Themes WordPress currently comes with three themes: the default Twenty Seventeen theme (demo), and previous defaults Twenty Sixteen theme (demo) and Twenty Fifteen theme (demo). You can switch between Themes using the Appearance in the Administration Screen. Themes you add to the theme directory will appear in the Administration Screen > Appearance > Themes as additional selections. [caption id="attachment_2220" align="alignnone" width="1911"] Themes Administration Screen - Installed Themes[/caption] Get New Themes The WordPress Theme Directory is the official site for WordPress Themes. Every theme in this directory is reviewed by a dedicated team and tested against wide range of rules, all of which are ensuring secure and pleasant experience for theme user. Among almost 2,900 themes in directory, you can easily find the right one for your site with advanced search feature using filters for layout, subject and specific theme's features. [caption id="attachment_2223" align="alignnone" width="971"] Themes Directory - Feature Filter[/caption] If you need more than screenshot and features list to decide whether the theme fits your needs, you can see the demo for the theme with Preview feature on theme's info page. [caption id="attachment_2224" align="alignnone" width="953"] Theme Info Page[/caption] Adding New Themes Most of themes in WordPress Theme Directory come with installation instructions, especially the ones that may require more steps than the usual theme installation. Be sure to read through and follow those instructions for the successful installation of the Theme. If your Theme does not work after following any provided instructions, please contact the Theme author for help. Adding New Themes using the Administration Screens You can download any theme from WordPress Theme Directory directly to your site by using the Add New option in the Appearance sub-menu. Log in to the WordPress Administration Screens. Select the Appearance screen, then Themes. Select Add New. Either use the Search or Filter options to locate a Theme you would like to use. Click on the Preview link to preview the Theme or the Install link to upload the Theme to your site, Or use the Upload Theme button at the top of page to upload a zipped copy of a Theme that you have previously downloaded to your machine. [caption id="attachment_2227" align="alignnone" width="800"] Install New Theme - Administration Screens[/caption] When the Theme is already downloaded but not activated Live Preview option will give you preview of your site with your own, existing content. Adding New Themes by using cPanel If your host offers the cPanel control panel, you can use its Upload option to upload the Theme files to your site. For this you will need Theme files in an compressed archive (.zip or .gz). Download the Theme .zip file to your machine. In cPanel File Manager, navigate to your Themes folder. Depending on your hosting, path to Themes folder can differ a bit but essentially you are looking for public_html inside which you'll find /wp-content/themes/. Once you're inside the Themes folder in cPanel File Manager, click on Upload and upload that .zip file you saved in Step 1. Once the .zip file is uploaded, right click on the name of that file in cPanel and select Extract from the context menu. When Theme files are successfully extracted, follow the instructions below for activating the new Theme. [gallery size="medium" columns="4" ids="2244,2245,2246,2247"] Adding New Themes Manually (FTP) To add a new Theme to your WordPress installation via FTP protocol, you'll need FTP client and extracted Theme files. Download the Theme archive (.zip) and extract the files it contains. You should have a folder named as theme itself, containing theme files. Using an FTP client to access your host web server and navigate to /wp-content/themes/ directory. Upload the Theme folder to this directory on your host server. Follow the instructions below for activating the new Theme. Activating the Theme Now that new Theme is in /wp-content/themes/ directory (whether you used Administration Screens, cPanel or FTP method), this new Theme is ready to be activated. All themes in /wp-content/themes/ directory are available for Activation and Update (when update is provided by theme author), but only one theme from this directory can be Active. When theme is Activated it means that this theme's style and functionality (look and behavior) will be applied on your site. You will be informed by Administration notification about successful activation of the Theme. [caption id="attachment_2263" align="alignnone" width="543"] Activated Theme Notice[/caption] To activate a Theme for your site: Log in to the WordPress Administration Screens. Select the Appearance screen, then Themes. You should see here all themes from your /wp-content/themes/ directory and from here you can see details for each of them by clicking on Theme Details (rollover the Theme thumbnail). Live Preview option will give you preview of your site with your site's content. To activate the Theme click the Activate button. Your selection will immediately become active. Note: If the Theme preview is blank, do NOT activate the new Theme without investigating further. Your site may not be displayed correctly, otherwise. If you do not see Theme's thumbnail at all, your new Theme might be corrupted or broken. Take a look below installed theme's thumbnails if there is any info about broken themes. In this case contact the Theme author for help. [caption id="attachment_2253" align="alignnone" width="1920"] Broken Theme[/caption] Creating Themes If you are interested in creating your own Theme for distribution, or learning more about the architecture of Themes, please review the documentation regarding Theme Development. If you simply want to customize your current Theme for your own use, consider creating a Child Theme. Whichever the case, you are welcome to join Theme Review Team and their dedicated #themereview Slack channel. Here you can ask for help on developing themes for WordPress Theme Directory or even start reviewing themes yourself. Creating a Static Front Page mikevanlohuizen — Tue, 16 Aug 2016 10:33:46 +0000 Goal: you will know what is a Static Front page, and you will be able to set up a Static Front Page on your WordPress site. Pre-requisites: you need to know the difference between Page and Post. What is a Static Front Page By default, WordPress displays a list of Posts on the home page of your site. This list of posts is automatically updated as soon as new posts are published, thus this is not static. Also, there is no need to create any page in order to have WordPress displaying this list of posts. A Static Front Page is a specific Page used as the Home Page of the site. How to create a Static Front Page Reminder: to create a page, go to Pages > Add New Front Page: (if not already created) create the Page you want to use as the Static Front Page. Posts Page: (if not already created) create an empty page. Give it a Title that will be used on top of your posts list. This step is mandatory as you are modifying WordPress default setting. Any other content other than Title will no be diplayed at all on this specific page. Setting: go to Settings > Reading, then 'Front page displays'. Static Page setting: select A static page (instead of the default Your latests posts). Front Page setting: in 'Front page' list, select the page you want for Static Front Page. Posts Page setting: in 'Posts page' list, select the empty page you created. Do not select any page with content, as it will not be displayed. Save your settings by clicking 'Save Changes' button. Connect to your site home page: you should now see the Page you selected. Introduction to Blogging mikevanlohuizen — Tue, 02 Aug 2016 10:49:13 +0000 What is a "blog"? "Blog" is an abbreviated version of "weblog," which is a term used to describe websites that maintain an ongoing chronicle of information. A blog features diary-type commentary and links to articles on other websites, usually presented as a list of entries in reverse chronological order. Blogs range from the personal to the political, and can focus on one narrow subject or a whole range of subjects. Many blogs focus on a particular topic, such as web design, home staging, sports, or mobile technology. Some are more eclectic, presenting links to all types of other sites. And others are more like personal journals, presenting the author's daily life and thoughts. Generally speaking (although there are exceptions), blogs tend to have a few things in common: A main content area with articles listed chronologically, newest on top. Often, the articles are organized into categories.An archive of older articles. A way for people to leave comments about the articles. A list of links to other related sites, sometimes called a "blogroll". One or more "feeds" like RSS, Atom or RDF files. Some blogs may have additional features beyond these. Watch this short video for a simple explanation for what a blog is. Here are some professional bloggers' point of view on what is a blog. What is a "blogger"? A blogger is a person who owns or runs a blog or a person who maintains the blog. That is, posting articles or new posts, information, sharing the most up-to-date news, opinions and case studies to name but a few. Such entries are known as blog posts. The Blog Content Content is the raison d'être for any website. Retail sites feature a catalog of products. University sites contain information about their campuses, curriculum, and faculty. News sites show the latest news stories. For a personal blog, you might have a bunch of observations, or reviews. Without some sort of updated content, there is little reason to visit a website more than once. On a blog, the content consists of articles (also sometimes called "posts" or "entries") that the author(s) writes. Yes, some blogs have multiple authors, each writing his/her own articles. Typically, blog authors compose their articles in a web-based interface, built into the blogging system itself. Some blogging systems also support the ability to use stand-alone "weblog client" software, which allows authors to write articles offline and upload them at a later time. Comments Want an interactive website? Wouldn't it be nice if the readers of a website could leave comments, tips or impressions about the site or a specific article? With blogs, they can! Posting comments is one of the most exciting features of blogs. Most blogs have a method to allow visitors to leave comments. There are also nifty ways for authors of other blogs to leave comments without even visiting the blog! Called "pingbacks" or "trackbacks", they can inform other bloggers whenever they cite an article from another site in their own articles. All this ensures that online conversations can be maintained painlessly among various site users and websites. The Difference Between a Blog and CMS? Software that provides a method of managing your website is commonly called a CMS or "Content Management System". Many blogging software programs are considered a specific type of CMS. They provide the features required to create and maintain a blog, and can make publishing on the internet as simple as writing an article, giving it a title, and organizing it under (one or more) categories. While some CMS programs offer vast and sophisticated features, a basic blogging tool provides an interface where you can work in an easy and, to some degree, intuitive manner while it handles the logistics involved in making your composition presentable and publicly available. In other words, you get to focus on what you want to write, and the blogging tool takes care of the rest of the site management. WordPress is one such advanced blogging tool and it provides a rich set of features. Through its Administration Screen, you can set options for the behavior and presentation of your weblog. Via these Administration Screen, you can easily compose a blog post, push a button, and be published on the internet, instantly! WordPress goes to great pains to see that your blog posts look good, the text looks beautiful, and the html code it generates conforms to web standards. If you're just starting out, read Getting Started with WordPress, which contains information on how to get WordPress set up quickly and effectively, as well as information on performing basic tasks within WordPress, like creating new posts or editing existing ones. Things Bloggers Need to Know In addition to understanding how your specific blogging software works, such as WordPress, there are some terms and concepts you need to know. Archives A blog is also a good way to keep track of articles on a site. A lot of blogs feature an archive based on dates (like a monthly or yearly archive). The front page of a blog may feature a calendar of dates linked to daily archives. Archives can also be based on categories featuring all the articles related to a specific category. It does not stop there; you can also archive your posts by author or alphabetically. The possibilities are endless. This ability to organize and present articles in a composed fashion is much of what makes blogging a popular personal publishing tool. Feeds A Feed is a function of special software that allows "Feedreaders" to access a site automatically looking for new content and then post updates about that new content to another site. This provides a way for users to keep up with the latest and hottest information posted on different blogging sites. Some Feeds include RSS (alternately defined as "Rich Site Summary" or "Really Simple Syndication"), Atom or RDF files. Dave Shea, author of the web design weblog Mezzoblue has written a comprehensive summary of feeds. Syndication A feed is a machine readable (usually XML) content publication that is updated regularly. Many weblogs publish a feed (usually RSS, but also possibly Atom and RDF and so on, as described above). There are tools out there that call themselves "feedreaders". What they do is they keep checking specified blogs to see if they have been updated, and when the blogs are updated, they display the new post, and a link to it, with an excerpt (or the whole contents) of the post. Each feed contains items that are published over time. When checking a feed, the feedreader is actually looking for new items. New items are automatically discovered and downloaded for you to read, so you don't have to visit all the blogs you are interested in. All you have to do with these feedreaders is to add the link to the RSS feed of all the blogs you are interested in. The feedreader will then inform you when any of the blogs have new posts in them. Most blogs have these "Syndication" feeds available for the readers to use. Managing Comments One of the most exciting features of blogging tools are the comments. This highly interactive feature allows users to comment upon article posts, link to your posts, and comment on and recommend them. These are known as trackbacks and pingbacks. We'll also discuss how to moderate and manage comments and how to deal with the annoying trend in "comment spam", when unwanted comments are posted to your blog. Trackbacks Pingbacks Using Pingbacks and Trackbacks Comment Moderation Comment Spam Trackbacks Trackbacks were originally developed by SixApart, creators of the MovableType blog package. SixApart has a good introduction to trackbacks: In a nutshell, TrackBack was designed to provide a method of notification between websites: it is a method of person A saying to person B, "This is something you may be interested in." To do that, person A sends a TrackBack ping to person B. A better explanation is this: Person A writes something on their blog. Person B wants to comment on Person A's blog, but wants her own readers to see what she had to say, and be able to comment on her own blog Person B posts on her own blog and sends a trackback to Person A's blog Person A's blog receives the trackback, and displays it as a comment to the original post. This comment contains a link to Person B's post The idea here is that more people are introduced to the conversation (both Person A's and Person B's readers can follow links to the other's post), and that there is a level of authenticity to the trackback comments because they originated from another weblog. Unfortunately, there is no actual verification performed on the incoming trackback, and indeed they can even be faked. Most trackbacks send to Person A only a small portion (called an "excerpt") of what Person B had to say. This is meant to act as a "teaser", letting Person A (and his readers) see some of what Person B had to say, and encouraging them all to click over to Person B's site to read the rest (and possibly comment). Person B's trackback to Person A's blog generally gets posted along with all the comments. This means that Person A can edit the contents of the trackback on his own server, which means that the whole idea of "authenticity" isn't really solved. (Note: Person A can only edit the contents of the trackback on his own site. He cannot edit the post on Person B's site that sent the trackback.) SixApart has published an official trackback specification. Pingbacks Pingbacks were designed to solve some of the problems that people saw with trackbacks. That is why the official pingback documentation sounds so much like the description of a trackback: For example, Yvonne writes an interesting article on her Web log. Kathleen reads Yvonne's article and comments about it, linking back to Yvonne's original post. Using pingback, Kathleen's software can automatically notify Yvonne that her post has been linked to, and Yvonne's software can then include this information on her site. The best way to think about pingbacks is as remote comments: Person A posts something on his blog. Person B posts on her own blog, linking to Person A's post. This automatically sends a pingback to Person A when both have pingback enabled blogs. Person A's blog receives the pingback, then automatically goes to Person B's post to confirm that the pingback did, in fact, originate there. The pingback is generally displayed on Person A's blog as simply a link to Person B's post. It is commonly believed that pingbacks do not send any content, as trackbacks do. This is not correct. If you get a pingback, you will see an excerpt from that blog in the Edit Comments section of your dashboard. The issue is that very few themes display these excerpts from pingbacks. The default Wordpress themes, for example, do not display pingback excerpts. In fact, there is only one significant difference between pingbacks and trackbacks: Pingbacks and trackbacks use drastically different communication technologies (XML-RPC and HTTP POST, respectively). But that difference is important because trackbacks have become the target of so much spam. The automatic verification process introduces a level of authenticity, making it harder to fake a pingback. Some feel that trackbacks are superior because readers of Person A's blog can at least see some of what Person B has to say, and then decide if they want to read more (and therefore click over to Person B's blog). Others feel that pingbacks are superior because they create a verifiable connection between posts. Using Pingbacks and Trackbacks Comments on blogs are often criticized as lacking authority, since anyone can post anything using any name they like: there's no verification process to ensure that the person is who they claim to be. Trackbacks and Pingbacks both aim to provide some verification to blog commenting. To enable trackbacks and pingbacks, in the Disscussion Settings of your Administration Screen, select these items under 'Default article settings': Attempt to notify any blogs linked to from the article. Allow link notifications from other blogs (pingbacks and trackbacks) on new articles. Selecting one option and not the other would not be very neighborly ;) Once enabled, trackbacks and pingbacks from other sites will appear in your Administration Screen just like other comments, but on your post pages, they will appear according to your theme's design. Once enabled, pingbacks are sent automatically when you publish your post, you don't have to do anything. To send trackbacks, you will need to find the trackback URL somewhere on the post page you are linking to. If you can't find one, try to determine if the site supports pingbacks. If it does, you should not send trackbacks as well. Copy/paste the trackback URL into the Send Trackbacksfield on your Add New Post screen. If you don't see this field, go to the screen options and select the Send Trackbacks option. Note that selecting this does not send trackbacks, it only displays the field called Send Trackbacks. When you publish your post, trackbacks will be sent to the URLs you pasted into the field. This field will also show the status of trackbacks and pingbacks on your Edit Post screen. If there is someone that wants to send a trackback to your WordPress blog because their blogging software does not support pingbacks, your trackback URL they should insert into their post edit screen is your blog post's permalink with "trackback/" appended to the end. If their software supports pingbacks, they do not need to do anything, the process is automatic. Comment Moderation Comment Moderation is a feature which allows the website owner and author to monitor and control the comments on the different article posts, and can help in tackling comment spam. It lets you moderate comments, & you can delete unwanted comments, approve cool comments and make other decisions about the comments. Comment Spam Comment Spam refers to useless comments (or trackbacks, or pingbacks) to posts on a blog. These are often irrelevant to the context value of the post. They can contain one or more links to other websites or domains. Spammers use Comment Spam as a medium to get higher page rank for their domains in Google, so that they can sell those domains at a higher price sometime in future or to obtain a high ranking in search results for an existing website. Spammers are relentless; because there can be substantial money involved, they work hard at their "job." They even build automated tools (robots) to rapidly submit their spam to the same or multiple weblogs. Many webloggers, especially beginners, sometimes feel overwhelmed by Comment Spam. There are solutions, though, to avoiding Comment Spam. WordPress includes many tools for combating Comment Spam. With a little up front effort, Comment Spam can be manageable, and certainly no reason to give up weblogging. Pretty Permalinks Permalinks are the permanent URLs to your individual weblog posts, as well as categories and other lists of weblog postings. A permalink is what another weblogger will use to refer to your article (or section), or how you might send a link to your story in an e-mail message. Because others may link to your individual postings, the URL to that article shouldn't change. Permalinks are intended to bepermanent (valid for a long time). "Pretty" Permalinks is the idea that URLs are frequently visible to the people who click them, and should therefore be crafted in such a way that they make sense, and not be filled with incomprehensible parameters. The best Permalinks are "hackable," meaning a user might modify the link text in their browser to navigate to another section or listing of the weblog. For example, this is how the default Permalink to a story might look in a default WordPress installation: /index.php?p=423 How is a user to know what "p" represents? Where did the number 423 come from? In contrast, here is a well-structured, "Pretty" Permalink which could link to the same article, once the installation is configured to modify permalinks: /archives/2003/05/23/my-cheese-sandwich/ One can easily guess that the Permalink includes the date of the posting, and the title, just by looking at the URL. One might also guess that hacking the URL to be /archives/2003/05/ would get a list of all the postings from May of 2003 (pretty cool). For more information on possible Permalink patterns in WordPress, see Using Permalinks. Blog by email Some blogging tools offer the ability to email your posts directly to your blog, all without direct interaction through the blogging tool interface. WordPress offers this cool feature. Using email, you can now send in your post content to a pre-determined email address & voila! Your post is published! Post Slugs If you're using Pretty Permalinks, the Post Slug is the title of your article post within the link. The blogging tool software may simplify or truncate your title into a more appropriate form for using as a link. A title such as "I'll Make A Wish" might be truncated to "ill-make-a-wish". In WordPress, you can change the Post Slug to something else, like "make-a-wish", which sounds better than a wish made when sick. Excerpt Excerpts are condensed summaries of your blog posts, with blogging tools being able to handle these in various ways. In WordPress,Excerpts can be specifically written to summarize the post, or generated automatically by using the first few paragraphs of a post or using the post up to a specific point, assigned by you. Plugins Plugins are cool bits of programming scripts that add additional functionality to your blog. These are often features which either enhance already available features or add them to your site. WordPress offers simple and easy ways of adding Administration Screen, there is a Plugins Screen. You can easily search, install and activate Plugins from this Screen. Basics - A Few Blogging Tips Starting a new blog is difficult and this can put many people off. Some may get off to a good start only to become quickly discouraged because of the lack of comments or visits. You want to stand out from this crowd of millions of bloggers, you want to be one of the few hundred thousand blogs that are actually visited. Here are some simple tips to help you on your way to blogging mastery: Post regularly, but don't post if you have nothing worth posting about. Stick with only a few specific genres to talk about. Don't put 'subscribe' and 'vote me' links all over the front page until you have people that like your blog enough to ignore them (they're usually just in the way). Use a clean and simple theme if at all possible. Enjoy, blog for fun, comment on other peoples' blogs (as they normally visit back). Have fun blogging and remember, there are no rules to what you post on your blog! Excerpt mikevanlohuizen — Tue, 02 Aug 2016 09:06:25 +0000 Goal: you will know what an Excerpt is, and you will be able to setup your Posts page to display Excerpts. Pre-requisites: you need to know about Post. What is an Excerpt Excerpt is an optionnal text associated to a Post. Most of the time, it is used as the Post summary. No finding the Excerpt editing box? Check your Post's Screen Options. Regarding the Theme you are using on your site, Excerpts can be displayed on differents pages (search results, archives, etc.). If Excerpt is empty, WordPress automatically creates an excerpt using the first 55 words of the post. How to display Excerpts on the Posts page Go to Settings > Reading. Scroll to For each article in a feed, show. Select Summary. Embeds mikevanlohuizen — Tue, 16 Aug 2016 10:36:56 +0000 It's super easy to embed videos, images, tweets, audio, and other content into your WordPress site. Usage To embed a video or another object into a post or page, place its URL into the content area. Make sure the URL is on its own line and not hyperlinked (clickable when viewing the post). For example: // NOTE: Remove space between 'http://' and 'www.youbute.com' when you try. Check out this cool video: http:// www.youtube.com/watch?v=dQw4w9WgXcQ That was a cool video. WordPress will automatically turn the URL into a YouTube embed and provide a live preview in the visual editor. Another option is to wrap the URL in the "embed" Shortcode. // NOTE: Remove space between '[' and 'embed' when you try. [ embed width="123" height="456"]http://www.youtube.com/watch?v=dQw4w9WgXcQ[/embed] If WordPress fails to embed the URL, the post will contain a hyperlink to the URL. oEmbed The easy embedding feature is mostly powered by oEmbed, a protocol for site A (such as your blog) to ask site B (such as YouTube) for the HTML needed to embed content from site B. oEmbed was designed to avoid the need to copy and paste HTML from the site hosting the media you wish to embed. It supports videos, images, text, and more. Does This Work With Any URL? No, not by default. WordPress will only embed URLs matching an internal whitelist. This is for security purposes. Okay, So What Sites Can I Embed From? You can use all of these: Service Embed Type Since Animoto Videos WordPress 4.0 Blip Videos WordPress 2.9 Cloudup Videos, Galleries, Images WordPress 4.4 CollegeHumor Videos WordPress 4.0 DailyMotion Videos WordPress 2.9 Facebook post, activity, photo, video, media, question, note WordPress 4.7 Flickr Videos & Images WordPress 2.9 FunnyOrDie.com Videos WordPress 3.0 Hulu Videos WordPress 2.9 Imgur Images WordPress 3.9 Instagram Images WordPress 3.5 Issuu Documents WordPress 4.0 Kickstarter Projects WordPress 4.2 Meetup.com Various WordPress 3.9 Mixcloud Music WordPress 4.0 Photobucket Images WordPress 2.9 PollDaddy Polls & Surveys WordPress 3.0 Reddit Posts & Comments WordPress 4.4 ReverbNation Music WordPress 4.4 Scribd Documents WordPress 2.9 SlideShare Presentation slideshows WordPress 3.5 SmugMug Various WordPress 3.0 SoundCloud Music WordPress 3.5 Speaker Deck Presentation slideshows WordPress 4.4 Spotify Music WordPress 3.6 TED Videos WordPress 4.0 Tumblr Various WordPress 4.2 Twitter Tweet, profile, list, collection, likes, Moment WordPress 3.4 VideoPress Videos WordPress 4.4 Vimeo Videos WordPress 2.9 Vine Videos WordPress 4.1 WordPress plugin directory Plugins WordPress 4.4 WordPress.tv Videos WordPress 2.9 YouTube Videos WordPress 2.9 Notes Twitter - older versions of WordPress have issues with https embeds, just remove the s from the https to fix. YouTube - only public and "unlisted" videos and playlists - "private" videos will not embed. Tumblr - only posts (name.tumblr.com/post/etc) are recognized, not standalone images (name.tumblr.com/image) How Can I Add or Change Support For Websites? Adding support for an additional website depends on whether the site supports oEmbed. Adding Support For An oEmbed-Enabled Site If a site supports oEmbed, you'll want to call wp_oembed_add_provider() to add the site and URL format to the internal whitelist. Adding Support For A Non-oEmbed Site You'll need to register a handler using wp_embed_register_handler() and provide a callback function that generates the HTML. Removing Support for An oEmbed-Enabled Site If you wish to remove an oEmbed-enabled provider, you'll want to call wp_oembed_remove_provider. What About oEmbed Discovery? As of version 4.4, WordPress supports oEmbed discovery, but has severe limitations on what type of content can be embedded via non-whitelisted sites. Specifically, the HTML and Video content is filtered to only allow links, blockquotes, and iframes, and these are additionally filtered to prevent insertion of malicious content. The HTML is then modified to be sandboxed and to have additional security restrictions placed on them as well. However, if you feel you are knowledgeable enough to not require this level of safety, you can give unfiltered_html users (Administrators and Editors) the ability to embed from websites that have oEmbed discovery tags in their . The oEmbed discovery content for "link" and "photo" types is not quite so heavily filtered in this manner, however it is properly escaped for security and to prevent any malicious content from being displayed on the site. External Resources oEmbed.com - Official oEmbed website with technical details of the spec Get Started With OEmbed - by Webmonkey.com WordPress oEmbed Providers Registration Generator - by GenerateWP.com Easy Embeds For WordPress 2.9 - by Alex Mills (Viper007Bond) How to Set oEmbed Max Width in WordPress 3.5 with $content_width? - by wpbeginner.com Changelog 2.9 : Introduction of the builtin Embeds support. 3.0 : Added: SmugMug, FunnyOrDie 3.4 : Added: Twitter 3.5 : Embed options were removed from the Settings Media Screen. Added: Instagram, SoundCloud, SlideShare 3.6 : Added: Rdio, Spotify 3.9 : Removed: Qik (the service shutting down in April 2014) 4.0 : Major reworking of the preview code showing embeds within the editor wp.mce.views. Added: CollegeHumor, Issuu, Mixcloud, YouTube playlists, TED talks Removed: Viddler (removed due to the service shutting down their oEmbed endpoint) 4.1 : Added: Vine 4.2 : Added: Kickstarter, Tumblr Removed: Revision3 4.4 : Added: ReverbNation, Cloudup, Reddit, SpeakerDeck, VideoPress Removed: Blip 4.4.1 : Removed: Rdio (Service shut down) 4.5 : Added: Twitter Moment, collection 4.7 : Added: Twitter profile, list, likes Added: Facebook post, activity, photo, video, media, question, note Sidebars juhisaxena — Tue, 16 Aug 2016 05:43:13 +0000 Sidebar is a theme feature introduced with Version 2.2. It's basically a vertical column provided by a theme for displaying information other than the main content of the web page. Themes usually provide at least one sidebar at the left or right of the content. Sidebars usually contain widgets that an administrator of the site can customize. Function Reference Register Sidebar register_sidebar() register_sidebars() unregister_sidebar() Show Sidebars is_active_sidebar() is_dynamic_sidebar() dynamic_sidebar() Define Sidebars The functions listed below are used to add functioning sidebars to a theme. Register Several Sidebars register_sidebars( $count, $args ); Registers one or more sidebars to be used in the current theme. Many themes have only one sidebar. For this reason, the count parameter is optional and defaults to one. The $args parameter will be passed to register_sidebar() and follows its format, with the exception of the name, which is treated with sprintf() to insert or append a unique number to each sidebar if count is plural. For example, the following line will create sidebars name "Foobar 1" and "Foobar 2": register_sidebars( 2, array( 'name' => 'Foobar %d' ) ); Register Single Sidebar register_sidebar( $args ); The optional $args parameter is an associative array that will be passed as a first argument to every active widget callback. (If a string is passed instead of an array, it will be passed through parse_str() to generate an associative array.) The basic use for these arguments is to pass theme-specific HTML tags to wrap the widget and its title. Here are the default values: [code language="php"] $args = array( 'name' => sprintf( __( 'Sidebar %d' ), $i ), 'id' => "sidebar-$i", 'description' => '', 'class' => '', 'before_widget' => '', 'after_widget' => "\n", 'before_title' => '', 'after_title' => "\n", ); [/code] There are times you might need to call this function instead of register_sidebars(). An example of this would be when you want to give unique names to the sidebars, such as "Right Sidebar" and "Left Sidebar", or when they should be marked up differently. The names appear in the admin interface and are used as an index for saving sidebar arrangement. Please note: sidebar arrangements can be reused and overwritten when another theme is chosen that uses the same sidebar names. The default before and after values are intended for themes that generate a sidebar marked up as a list with "h2" titles. This is the recommended convention for themes. Themes built using this structure can simply register sidebars without issues in regard to the before and after tags. If a theme cannot be marked up in this way, these tags must be specified when registering sidebars. It is recommended to copy the id and class attributes verbatim so that an internal sprintf call can work and CSS styles can be applied to individual widgets. Display Sidebar on Theme [code language="php"] [[Function Reference/dynamic_sidebar|dynamic_sidebar]]( $sidebar ); [/code] This function calls each of the active widget callbacks in order, which prints the markup for the sidebar. If you have more than one sidebar, you should give this function the name or number of the sidebar you want to print. This function returns true on success, false on failure. The return value should be used to determine whether to display a static sidebar. This ensures your theme will look good when the Widgets plug-in is not active. Along with a sanity test to prevent fatal errors, below is the recommended use of this function: [code language="php"] {static sidebar item 1} {static sidebar item 2} [/code] If your sidebars were registered by number, they should be retrieved by number. If they had names when you registered them, you will use their assigned names to retrieve them. Resources WordPress Sidebar Generator Related Customizing Your Sidebar Stepping Into Templates Audio Shortcode ankitguptaindia — Wed, 20 Jul 2016 13:40:36 +0000 The Audio feature allows you to embed audio files and play them back using a simple Shortcode. This was added as of WordPress 3.6 and is used like this: [[audio]] You can also use build in embeds and simply put the media file on it's own line: My cool content http://my.mp3s.com/cool/songs/coolest.mp3 More cool content Usage I have an old post that has an audio file in the Media Library attached to it, and I want to use the new shortcode: [code language="php"] [[audio]] [/code] I have the URL for an MP3, from the Media Library or external, that I want to play: [code language="php"] [[audio src="audio-source.mp3"]] [/code] I have a source URL and fallbacks for other HTML5-supported filetypes: [code language="php"] [[audio mp3="source.mp3" ogg="source.ogg" wav="source.wav"]] [/code] Options The following basic options are supported: src (string) (optional) The source of your audio file. If not included it will auto-populate with the first audio file attached to the post. You can use the following options to define specific filetypes, allowing for graceful fallbacks: 'mp3', 'm4a', 'ogg', 'wav', 'wma' Default: First audio file attached to the post loop (string) (optional) Allows for the looping of media. "off" - Do not loop the media."on" - Media will loop to beginning when finished and automatically continue playing. Default: "off" autoplay (string) (optional) Causes the media to automatically play as soon as the media file is ready. "off" - Do not automatically play the media. "on" - Media will play as soon as it is ready. Default: "off" preload (string) (optional) Specifies if and how the audio should be loaded when the page loads. Defaults to "none" "none" - The audio should not be loaded when the page loads. "auto" - The audio should be loaded entirely when the page loads. "metadata" - Only metadata should be loaded when the page loads. Default: "none" Source File The audio shortcode is located in wp-includes/media.php. Related Function wp audio shortcode WordPress Shortcodes: [[audio]], [[caption]], [[embed]], [[gallery]], [[playlist]], [[video]] Settings Readings Screen geoffreyshilling — Tue, 02 Aug 2016 06:29:07 +0000 Settings → Reading The options in the Settings Reading Screen are few in number, but still important. You can decide if you want posts or a "static" Page displayed as your blog's front (main) page. You can also adjust how many posts are displayed on that main page. In addition, you can adjust syndication feed features to determine how the information from your site is sent to a reader's web browser or other applications. Back to Administration Screens. Reading Settings Front page displays Use this setting to determine if your posts or a "static" Page displays as your blog's front (main) page. This setting displays only if you have one or more Pages defined. Please note: static front page plugins and other 'posts display' control/restriction plugins may affect how these features work! Your latest posts - Check this radio button so your latest posts are displayed on the blog's front page. Remember, the number of posts you display is controlled by the "Blog pages show at most" setting. A static page (select below) - Check this radio button to cause a "static" Page to be displayed as your blog's front page. At the same time, choose the Page that will display your actual Posts. The Front page and Posts page cannot be the same value. Front page - In the drop-down box, select the actualPage that you want displayed as your front page. If you do not select a choice here, then effectively your blog will show your posts on both the blog's front page and on the Posts page you specify. If you would like to create a static home page template file, do not name it home.php, otherwise you will encounter problems when you try to view the "blog"/"posts" section of your site. To get around this, just name it anything but home.php, for example, myhome.php Posts page - In the drop-down box, select the name of the Page that will now contain your Posts. If you do not select a Page here, your Posts will only be accessible via other navigation features such as category, calendar, or archive links. Even if the selected Page is password protected, visitors will NOT be prompted for a password when viewing the Posts Page. Also, any Template assigned to the Page will be ignored and the theme's index.php (or home.php if it exists) will control the display of the posts. See Creating a Static Front Page for more detail. Blog pages show at most [X] posts - Enter the number of posts to be displayed, per page, on your site. Syndication feeds show the most recent [X] posts - Enter the number of posts people will see when they download one of your site's feeds. For each article in a feed, show Determines whether or not the feed will include the full article or just a summary. Full text - Click this radio button to include the full content of each post. Summary - Click this radio button to include a summary of the post. This could save bandwidth. Encoding for pages and feeds (Removed as of Version 3.5.0) Enter the character encoding to set the choice of languages in which you, the other authors, and your commenters, can write. The default (and safe choice) is "UTF-8" (see Unicode), as that encoding supports a wide variety of languages. If you wish to use some other character encoding (for example you have imported or will import articles written using a different character encoding) then specify that here. Caution should be used when changing this field as it may change the way information is displayed on your blog. For a more in-depth article on character encoding see Wikipedia:Character encoding. Search Engine Visibility (New as of Version 3.5.0) Note: the Settings → Privacy screen has been removed from WordPress as of Version 3.5.0). Check the Discourage search engines from indexing this site box to ask search engines not to index this site. When the option is checked, the following happens: Causes "" to be generated into the section (if wp_head is used) of your site's source, causing search engine spiders to ignore your site. Causes hits to robots.txt to send back: User-agent: * Disallow: / Note: The above only works if WordPress is installed in the site root and no robots.txt exists. Stops pings to ping-o-matic and any other RPC ping services specified in the Update Services of Administration > Settings >Writing. This works by having the function privacy_ping_filter() remove the sites to ping from the list. This filter is added by having add_filter('option_ping_sites','privacy_ping_filter'); in the default-filters. When the generic_pingfunction attempts to get the "ping_sites" option, this filter blocks it from returning anything. Hides the Update Services option entirely on the Administration > Settings > Writing screen with the message "WordPress is not notifying any Update Services because of your blog's privacy settings." Allows normal visitors. *Note: Neither of these options blocks access to your site — it is up to search engines to honor your request. Save Changes Click the Save Changes button to ensure any changes you have made to your Settings are saved to your database. Once you click the button, a confirmation text box will appear at the top of the page telling you your settings have been saved. Changelog 3.5 : Charset encoding option removed (defaults to UTF-8), Search Engine Visibility option moved from Settings Privacy Screen See also Administration Screens and Network Admin. WordPress Cookies atachibana — Sun, 17 Jul 2016 15:46:39 +0000 WordPress uses cookies, or tiny pieces of information stored on your computer, to verify who you are. There are cookies for logged in users and for commenters. This page is a partial work in progress. Users Users are those people who have registered an account with the WordPress blog in question. WordPress > 2.4 When you log into WordPress from http://example.com/wp-login.php, WordPress stores the following two cookies: Your user name A double-hashed copy of your password The cookies are set to expire two weeks from the time they are set. (Details of how to change this time). WordPress > 3.0 On login, wordpress uses the wordpress_[hash] cookie to store your authentication details. Its use is limited to the admin console area, /wp-admin/ After login, wordpress sets the wordpress_logged_in_[hash] cookie, which indicates when you're logged in, and who you are, for most interface use. WordPress also sets a few wp-settings-{time}-[UID] cookies. The number on the end is your individual user ID from the users database table. This is used to customize your view of admin interface, and possibly also the main site interface. The cookies length can be adjusted with the 'auth_cookie_expiration' hook (An example can be found at what's the easiest way to stop wp from ever logging me out). Non-Version-Specific Data The actual cookies contain hashed data, so you don't have to worry about someone gleaning your username and password by reading the cookie data. A hash is the result of a specific mathematical formula applied to some input data (in this case your user name and password, respectively). It's quite hard to reverse a hash (bordering on practical infeasibility with today's computers). This means it is very difficult to take a hash and "unhash" it to find the original input data. WordPress uses the two cookies to bypass the password entry portion of wp-login.php. If WordPress recognizes that you have valid, non-expired cookies, you go directly to the WordPress Administration interface. If you don't have the cookies, or they're expired, or in some other way invalid (like you edited them manually for some reason), WordPress will require you to log in again, in order to obtain new cookies. The functions to set and remove cookies are currently defined in /wp-includes/pluggable.php. wp_set_auth_cookie( $user_id, $remember, $secure ) This function sets the cookie. wp_clear_auth_cookie() This function will delete the cookie from the client browser. This happens when the user clicks on the Logout link in the Administration interface. auth_redirect() This function also utilizes the cookies. Checks whether the cookie is present on the client browser. If it is not, the user is sent to the wp-login.php login screen. After logging in, the user is sent back to the page he or she attempted to access. Commenters When visitors comment on your blog, they too get cookies stored on their computer. This is purely a convenience, so that the visitor won't need to re-type all their information again when they want to leave another comment. Three cookies are set for commenters: comment_author_{HASH} comment_author_email_{HASH} comment_author_url_{HASH} The commenter cookies are set to expire a little under one year from the time they're set. References Wikipedia: Cookies RFC2965 PHP cookie documentation Inserting Images into Posts and Pages juhisaxena — Mon, 18 Jul 2016 06:25:06 +0000 Overview When creating or editing a WordPress page or blog post, you can easily add images at any time using the WordPress Media Uploader tool. Here’s how to add an image, step-by-step, using the media uploader: Step 1 – Placing your cursor In order to add an image to your page or post, you must first insert your cursor in the place in the text where you want the image to appear. By placing your cursor within your text, you can add images inline with your content. You can also place your cursor on a blank line if you want the image to appear by itself instead. Tip: It’s a good idea to place your cursor on the left margin of your text, even if you want the image to appear on the right. That’s because there is a special setting called Alignment that allows you to control whether the image appears on the right or the left side of the text. It even controls how text flows around the image automatically. Step 2 – Click the Add Media button Once you’ve placed your cursor on the line where you want your image to appear, click on the Add Media button to launch the media uploader interface, and then select the Insert Media option from the list of actions in the left side of the media uploader window. Step 3 – Add or Select Your Image You can add or select the image you want to add to your page or post by choosing from either of the following options in the center of the media uploader window: Upload Files: Upload the image you want to use from your computer by dragging it into the upload area. Media Library: Select from any previously uploaded images in the media library by clicking on the one you wish to add to your page or post. Once you have selected or uploaded the image you want to add, You will see a checkbox next to the thumbnail confirming your selection, and see information about it displayed in the Attachment Details pane on the right hand side of the media uploader interface. Step 4 – Attachment Details The Attachment Details pane displays a small un-cropped thumbnail of the image, as well as important information such as the filename, date uploaded, and image dimensions in pixels. There are also action links that allow you to Edit Image, which takes you to the page, or to Delete Permanently to remove the image from your site. In addition, you can edit the following media information: Title: The title of this media. Caption: The caption for this image. The text you enter here will be displayed below the image. Alternate Text: Enter the Alt text for the image, e.g. “The Mona Lisa” to describe the media. Description: A description for this particular media. For more information on these media settings, see the Edit Media page. Step 5 – Attachment Display Settings The Attachment Display Settings pane controls how the image is displayed when viewed on the site. You have options to set how you would like the image aligned on the page (in relation to the text and margins) and what the link behavior of the image will be, In addition you can set what size image you would like to display on your page. Image Alignment The Alignment setting allows you to determine where you would like the image to appear in your content area and how it interacts with any text on the page. You have the following image alignment options to choose from: Left: Aligns the image on the left hand margin, and any text that is on the page wraps (or flows) around the image to the available space on the right. Right: Aligns the image on the right hand margin, and any text that is on the page wraps (or flows) around the image to the available space on the left. Center: Aligns the image to the center of the page, with no text displayed around it. None: Inserts the image in to the page with no alignment Image Link The Link To settings determine the URL/web address to which the image will be linked when clicked on by a visitor to your site. You can specify the following image link settings: Attachment Page: Links your inserted image to its WordPress media attachment page. Media File: Links your inserted image directly to the original, full-size version of the file. Custom URL: Allows you to set a custom link URL for your inserted image to link to when clicked. None: This setting will remove the link completely, rendering the image “un-clickable”. Image Size The Size settings determine the size of the image you are adding to your site. By default WordPress creates a range of four image size for you to choose from: Thumbnail: Displays a small thumbnail-sized version of your image on the page/post. Note, by default the Thumbnail size is a square, so some cropping of your original image may occur. Medium: Displays a medium-sized version of your image on the page/post. This is a good size to use with Left/Right alignments, as it leaves sufficient space for legible text to either side. Large: Displays a large-sized version of your image on the page/post. Note: WordPress will determine the width of the content column of your theme, and display the largest possible image for that space. Full Size: Displays a full-sized version of your image on the page/post. Note: WordPress will determine the width of the content column of your theme, and display the largest possible image for that space. If your original image is larger than this column width, the full size of the image may not be displayed. You can visit the Settings>Media section of your WordPress dashboard to customize the above image sizes. Step 5 – Inserting the image Once you have determined your image settings, click on the blue Insert into post or Insert into the page button, to add the image to your page or post. After the image uploader window closes, you will see the image in the text editor window, including a preview of the alignment of the image, if you have specified an image alignment. At any time, you can edit the image settings by clicking on the Edit Image button in the upper left hand corner. You can remove the image from your page/post by clicking on the Remove Image button. Resources Using Image and File Attachments Embeds - Inserting different medias. Photoblogs and Galleries - Using WordPress as photoalbum, photoblog etc Dashboard Screen ankitguptaindia — Tue, 26 Jul 2016 08:52:11 +0000 Dashboard → Home From the Dashboard's homepage, you can quickly access your site's content and get glimpses into other areas of the WordPress community. The Dashboard screen presents information in blocks called widgets. By default, WordPress delivers five widgets on this page: At a Glance, Activity, Quick Draft, WordPress Events and News, and Welcome. Default Dashboard Widgets The following dashboard widgets are included by default with WordPress: At a Glance The At a Glance widget provides a summary of the number of posts, pages, and comments on your site. Each of these content types are displayed in the form of a link and, when clicked, direct you to the specific area to manage that content. A statement at the bottom of this widget tells you what WordPress version you're running, as well as the current theme that you have activated on your site. Activity This widget shows the upcoming scheduled posts, recently published posts, and the most recent comments on your posts--and allows you to moderate them. A list of the most recent comments on your blog is detailed in this widget. Each comment that is listed has a link to the related post title--clicking this link allows you to edit the post. Hovering the mouse over each comment activates a menu of choices: to approve (or unapprove) the comment, edit the comment, reply to the comment, mark the comment as spam, or delete the comment. QuickDraft The QuickDraft widget allows you to quickly and easily write a new draft. Enter a post title, upload/insert media, enter the post content, add tags, and click the Publish button or click the Save Draft button. It's that easy! WordPress Events and News This Dashboard widget lists upcoming local events and the latest news from the official WordPress blog. Here you can find out an upcoming event near you, or, what WordPress developers have been up to recently, and you can also keep up with the latest WordPress related news. In addition to software developments--such as version announcements and security notices--news about the WordPress community in general is periodically posted. Welcome The Welcome widget shows links for some of the most common tasks when setting up a new site. Screen Options The Screen Options panel allows you to choose which widgets are displayed or not displayed. When you click on the Screen Options tab, the resulting panel shows the various Dashboard widgets, with a checkbox next to each widget. Check the box to display a specific widget, or uncheck the box to hide that widget. Click the Screen Options tab again to close the Screen Options panel. Expanding, Collapsing, and Rearranging Widgets Each widget can be expanded or contracted by clicking on the widget title bar. Widgets can be moved by hovering the mouse cursor over the widget title bar. When the mouse cursor changes to four arrows, hold the left mouse button down, drag the widget to where you want to place it, and then release the mouse button (this cursor motion is called drag and drop). Adding new Dashboard Widgets Plugin or theme developers can make new Dashboard widgets available through the plugin (or functions.php) code. For more information, see the Dashboard Widgets API. See also Administration Screens and Network Admin. Multisite Network Administration bethannon — Thu, 28 Jul 2016 22:19:24 +0000 Once you've created a Multisite Network, there are some additional things you might need to know about advanced administration, due to the additional complexity of a Multisite. Even if you're familiar with WordPress, the location and behavior of Multisite Network Administration can be confusing. User Access & Capabilities By design, all users who are added to your network will have subscriber access to all sites on your network. To allocate a different default role for users on individual sites, you must use a plugin. The capabilities of the site administrator role are also reduced in a WordPress Network. Site admins cannot install new themes or plugins and cannot edit the profiles of users on their site. Only the Network Admin (aka Super Admin) has the ability to perform these tasks in a WordPress network. Permalinks in SubFolder Installs While permalinks will continue to work, the main site (i.e. the first one created) will have an extra entry of blog, making your URLs appear like domain.com/blog/YYYY/MM/POSTNAME. This is by design, in order to prevent collisions with SubFolder installs. Currently there is no easy way to change it, as doing so prevents WordPress from auto-detecting collisions between your main site and any subsites. This will be addressed, and customizable, in a future version of WordPress. Also note that the blog prefix is not used for static pages which will be accessible directly under the base address, e.g. domain.com/PAGENAME. If you try to create a static page in the first site with the name of another existing site on the network, the page's permalink will get a suffix (e.g. domain.com/PAGENAME-2). If you create a new site with the slug of an existing static page, the static page will not be reachable anymore. To prevent this, you can add the names of your static pages to the blacklist so that no site with that name can be created. Uploaded File Path Your first site on a fresh install will put uploaded files in the traditional location of /wp-content/uploads/, however all subsequent sites on your network will be in the /wp-content/uploads/sites/ folder, in their own subfolder based on the site number, designated by the database. These files will be accessible via that URL. This is a change from Multisite 3.0-3.4.2, where images of subsites were stored in /wp-content/blogs.dir/ and were shown in http://example.com/files/ and http://example.com/sitename/files and so on. If you started with a Multisite install older than 3.5, it is not an error if your images show with the URL of /files/. Regardless of WP version, these locations cannot be changed by site admins. Only the network admin can make changes on the site settings page. It is not recommended that you change these without understanding how both the ms-files.php works in conjunction with your .htaccess, as it can easily become non-functional. If the /files/ urls aren't working, it's indicative of a misconfigured .htaccess or httpd.conf file on your server. Plugins Plugins now have additional flexibility, depending upon their implementation across the network. All plugins are installed on the network dashboard's plugin page, and can be activated either per-site or for the entire network. Site Specific Plugins: These plugins are activated from within the plugins page of a single specific site. Some plugins (contact forms, for example) work best when they are single-site activated, so that they can store data and settings in that single site's database tables, instead of the tables for the whole network. WordPress Plugins to be single-site activated/deactivated are stored in the plugins directory. Network Plugins: Network admins may 'network activate' plugins in the Network Admin dashboard for plugins. Once 'network activated', plugins will become active in all sites. 'Network Activated' plugins are indicated as "Network Active" in plugin lists in the dashboards of individual sites. Some plugins only function in a multisite environment when they are network activated. WordPress Plugins that are Network Activated are also stored in the plugins directory. Must-Use Plugins: Plugins to be used by all sites on the entire network may also be installed in the mu-plugins directory as single files, or a file to include a subfolder. Any files within a folder will not be read. These files are not activated or deactivated; if they exist, they are used. These plugins are hidden entirely from per-site plugin lists. Not all plugins in the repository will work in a multisite environment. Consult the plugin's repository page or contact the developer for information about whether a specific plugin will function in a multisite network. If you would like single site administrators to be able to activate/deactivate site-specific plugins for their site, you need to enable the Plugins page for single site administrators from the Network Admin's Settings -> Network Settings menu ("Menu Settings"). Network Admins will always have access to the plugins of every site. Administrators of a single site will be able to activate and deactivate plugins that are not Network Activated, but will see the Network Activated plugins as "Network Active" with no options for deactivation or settings. There are plugins that will assist with mass activating/deactivating plugins for single sites. Themes All themes are installed for the entire network. If you edit the code of one theme, you edit it for all sites using that theme. You can install the plugin WP Add Custom CSS to allow each site to tweak their own CSS without affecting anyone else. Also, individual sites may use the Theme Customizer, and their settings will be stored only in the tables for their site. "Network Activating" a theme does not make it the active theme on each site, but merely makes it available to be activated on all individual sites. To be available for activation in the dashboard of a single site, a theme must be either network activated or enabled in Network Admin - Edit Site - Themes tab. After a theme has been activated in a single site, it may be network deactivated without affecting the single site where it remains activated. By default, WordPress assigns the most recent "Twenty ..." as the theme for all new sites. This can be customized by adding a line like define('WP_DEFAULT_THEME', 'classic'); to your wp-config.php file, where 'classic' is replaced with the folder name of your theme. Categories and Tags Global terms (i.e. sharing tags and categories between sites on the network) is not available in WordPress 3.0. You can use plugin to incorporate global tags on the portal/front page of the site or on specific pages or sites within the network to increase navigation based upon micro-categorized content. Content Sharing Between Sites The sites of a network are separate sites that don't by default share content. Think of your network as a mini version of WordPress.com. There are several plugins which may help you share content between your sites, like this one. Switching network types It's possible to switch between domain-based (sub-domain) and path-based (sub-directory) installations of Multisite. If you have had WordPress installed for longer than a month on a single site, and are attempting to activate that site into a network, you will be told to use Sub-domain sites. This is in order to ensure you don't have conflicts between pages (i.e. example.com/pagename ) and sites (i.e. example.com/sitename ). If you are confident you will not have this issue, then you can change this after you finish the initial setup. In your wp-config.php file, you'll want to change the define call for SUBDOMAIN_INSTALL: For a domain-based network (sub-domain install) define( 'SUBDOMAIN_INSTALL', true ); For a path-based network (sub-directory install) define( 'SUBDOMAIN_INSTALL', false ); You'll also have to change your .htaccess to the new setup. You can go to Network Admin -- Settings -- Network Setup to find the new .htaccess rules, or see below. Note that per the Settings Requirements you cannot switch from Sub-directory to Sub-domain when running on 127.0.0.1 or localhost. This can potentially cause an endless loop of reauth=1 on your root site due to cookie handling. Apache Virtual Hosts and Mod Rewrite To enable mod_rewrite to work within an Apache Virtual host you may need to set some options on the DocumentRoot. DocumentRoot /var/www/vhosts/wordpress AllowOverride Fileinfo Options In some instances, you will need to add All to your AllowOverride for all htaccess rules to be honored. .htaccess and Mod Rewrite Unlike Single Site WordPress, which can work with "ugly" Permalinks and thus does not need Mod Rewrite, MultiSite requires its use to format URLs for your subsites. This necessitates the use of an .htaccess file, the format of which will be slightly different if you're using SubFolders or SubDomains. The examples below are the standard .htaccess entries for WordPress SubFolders and SubDomains, when WordPress is installed in the root folder of your website. If you have WordPress in its own folder, you will need to change the value for RewriteBase appropriately. As a reminder, these are EXAMPLES and work in most, but not all, installs. SubFolder Example WordPress 3.0 through 3.4+ # BEGIN WordPress RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] # uploaded files RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L] # add a trailing slash to /wp-admin RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L] RewriteCond %{REQUEST_FILENAME} -f [OR] RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^ - [L] RewriteRule ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L] RewriteRule ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L] RewriteRule . index.php [L] # END WordPress WordPress 3.5+ ONLY use this if you STARTED Multisite on 3.5. If you upgraded from 3.4 to 3.5, use the old one! RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] # add a trailing slash to /wp-admin RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L] RewriteCond %{REQUEST_FILENAME} -f [OR] RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^ - [L] RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L] RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L] RewriteRule . index.php [L] SubDomain Example WordPress 3.0 through 3.4+ # BEGIN WordPress RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] # uploaded files RewriteRule ^files/(.+) wp-includes/ms-files.php?file=$1 [L] RewriteCond %{REQUEST_FILENAME} -f [OR] RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^ - [L] RewriteRule . index.php [L] # END WordPress WordPress 3.5+ RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] # add a trailing slash to /wp-admin RewriteRule ^wp-admin$ wp-admin/ [R=301,L] RewriteCond %{REQUEST_FILENAME} -f [OR] RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^ - [L] RewriteRule ^(wp-(content|admin|includes).*) $1 [L] RewriteRule ^(.*\.php)$ wp/$1 [L] RewriteRule . index.php [L] Issues with old WPMU installs If you installed WordPress MU in subfolder/subdirectory (not in root folder on your server via ftp) and you have problem with image library, where thumbnails and images do not show, you may need to manually add in rewrite rules for your file directories as follows: RewriteRule ^([_0-9a-zA-Z-]+/)?siteN/files/(.+) wp-content/blogs.dir/N/files/$2 [L] Put those below the normal call for uploaded files. Network Admin Link Location The Network Admin Link has moved with each major release of WordPress, as this is still a work in progress. Depending on which version of WordPress you are using, the link can be found in the following locations: 3.0 - A menu called Super Admin 3.1 - On the admin header by "Howdy, YOURNAME." 3.2 - On the admin header, as a drop-down under "Howdy, YOURNAME." 3.3+ - On the admin bar, as a drop-down under your "My Sites" Domain Mapping Before WordPress 4.5, domain mapping requires a domain mapping plugin. In WordPress 4.5+, domain mapping is a native feature in Multisites. Learn how to use this feature at WordPress Multisite Domain Mapping Moving Multisite Moving Multisite is more complicated than moving a single install. Please read Moving WordPress Multisite before continuing. Importing into a Network When you've created your WordPress Network for importing other sites, you need to look at the Migrating Multiple Blogs into WordPress Multisite article. Using Images juhisaxena — Fri, 19 Aug 2016 07:15:18 +0000 Working with Images Adding images in WordPress is very easy. All of your images will be stored and can be managed in the Media Library, but you can take several different paths to get there. The most common path is adding an image directly to a post or page. This automatically saves the image in the Media Library and displays the image wherever you inserted it. You can also add images directly to the Media Library through the multi-file loader or the single-file loader. For advanced user, you can upload images directly using an FTP Client. Adding Images Through Pages/Posts When writing or editing a post, you can add an image using the Add Media button above the editor box. This opens a window that displays the multi-file uploader. From here you can drag and drop your picture or select it using the file selector. The images you add here will be automatically added to the Media Library. Adding Images Through Pages/Posts When writing or editing a post, you can add an image using the Add Media button above the editor box. This opens a window that displays the multi-file uploader. From here you can drag and drop your picture or select it using the file selector. The images you add here will be automatically added to the Media Library. Adding Images By FTP If you know what an FTP program is, you can upload images directly to the /wp-content/uploads folder. For more information, see FTP Client. Miscellaneous WordPress can resize images and create thumbnails. Refer to the following for more information: Inserting Images into Posts and Pages Wrapping Text Around Images Styling Images in Posts and Pages Using Image and File Attachments In Theme Design [caption id="attachment_1505" align="aligncenter" width="497"] Theme featuring Image in Header[/caption] You can add images to your WordPress site through the use of template tags, Plugins, and in the stylesheet of your Theme as background images. It is really up to your imagination and web design skills on how you include images in WordPress. WordPress Design and Layout Lists Menus Categories Template Tags Graphics Symbols Header Headings Sidebar Special Contents Using Images [caption id="attachment_1507" align="alignright" width="300"] Gravatar in comments[/caption] PhotoBlog or Gallery - Keep a online photo album with plugins, themes and tons of resources. How to Use Gravatars in WordPress - Display avatars in your comment stream. Graphics in Feeds- Display RSS Fed icons. Links and Blogrolls- Icons for your favorite links. Next and Previous Links- Customize your navigation links. Smilies - How to use smilies or emoticons on WordPress. Resources Image Size and Quality Image Compression on Wikipedia WordPress Inspiration - Showcase FAQ My site was hacked atachibana — Tue, 23 Aug 2016 03:50:20 +0000 Help I think I've been hacked Suffering a hack can be one of the more frustrating experiences you'll have on your online journey. Like most things however, taking a pragmatic approach can help you maintain your sanity. While also moving beyond the issues with as little impact as possible. A hack is a very ambiguous term, which in it of itself will provide little insights into what exactly happened. To ensure you get the help you need via the forums, be sure to understand the specific symptoms that lead you to believe you've been hacked. These are otherwise known as Indicators of Compromise (IoC). A couple of IoC's that are clear indicators of a hack include: Website is blacklisted by Google, Bing, etc.. Host has disabled your website Website has been flagged for distributing malware Readers complaining that their desktop AV's are flagging your site Contacted that your website is being used to attack other sites Notice behavior that was not authorized (i.e., creation of new users, etc...) You can visibly see that your site has been hacked when you open it in the browser Not all hacks are created equal, so when engaging in the forums please keep this in mind. If you can better understand the symptoms the teams will be better equipped to provide help. Below you will find a series of steps that are designed to help you start working through the post-hack process. They are not all encompassing as it would be impractical to account for every scenario, but they are designed to help you think through the process. Some steps to take Stay calm. When addressing a security issue, as a website owner, you're likely experiencing an undue amount of stress. It's often the most vulnerable you have found yourself since being on line and it's contrary to what every one told you, "Hey, WordPress is Easy!!" The good news is that all is not lost! Yes, you might lose some money. Yes, you might take a hit against your brand. Yes, you will recover from this. So, yes, take a step back and compose yourself. Doing so will allow you to more effectively take control of the situation and allow you to recover your online presence. Document. The first actionable step you should take post-compromise is documentation. Take a moment to document what you're experiencing, and if possible times. A couple of things you want to keep in mind: What are you seeing that leads you to believe you are hacked? What time did you notice this issue? What timezone? What actions have you taken recently? Was a new plugin installed? Did you make a change to a theme? Modify a widget? You are creating the baseline for what is recognized as an incident report. Whether you are planning to perform the incident response yourself, or engage a professional organization, this document will prove invaluable over time. Recommend taking a moment to annotate details of your host environment as well. It will be required at some point during the incident response process. Scan your website. When scanning your website you have a few different ways to do this, you can use external remote scanners or application level scanners. Each are designed to look and report on different things. No one solution is the best approach, but together you improve your odds greatly. Application Based Scanners (Plugins): Quettera GOTMLS WordFence Sucuri Remote Based Scanners (Crawlers): VirusTotal Sitecheck Aw-Snap Cloaked Link Checker There are also a number of other related security plugins available in the WP repo. The ones annotated above have been around a long time and have strong communities behind each of them. Scan your local environment. In addition to scanning your website, you should start scanning your local environment. In many instances, the source of the attack / infection begins on your local box (i.e., notebook, desktop, etc...). Attackers are running trojans locally that allow them to sniff login access information to things like FTP and /wp-admin that allow them to log in as the site owner. Make sure you run a full anti-virus/malware scan on your local machine. Some viruses are good at detecting AV software and hiding from them. So maybe try a different one. This advice extends to both Windows, OS X and Linux machines. Check with your hosting provider. The hack may have affected more than just your site, especially if you are using shared hosting. It is worth checking with your hosting provider in case they are taking steps or need to. Your hosting provider might also be able to confirm if a hack is an actual hack or a loss of service, for example. One very serious implication of a hack these days is around Email blacklisting. This seems to be happening more and more. As websites are abused to send out SPAM emails, Email Blacklist authorities are flagging the website IP's and those IP's are often associated with the same server being used for email. The best thing you can do is look at Email providers like Google Apps when it comes to your business needs. Be Mindful of Website Blacklists. Google Blacklist issues can be detrimental to your brand. They currently blacklist somewhere in the neighborhood of 9,500 to 10,000 websites a day. This number grows daily. There are various forms of warnings, from large splash pages warning users to stay away, to more subtle warnings that pop up in your Search Engine Result Pages (SERPs). Although Google is one of the more prominent ones, there are a number of other blacklist entities like Bing, Yahoo and a wide range of Desktop AntiVirus applications. Understand that your clients / website visitors may leverage any number of tools and any one of them could be causing the issue. It's recommended that you register your site with the various online webmaster consoles like: Google Search Console Bing Webmaster Yandex Webmaster Norton Webmaster Improve your Access Controls. You will often hear folks talking about updating things like Passwords. Yes, this is a very important piece, but it's one small piece in a much larger problem. We need improve our overall posture when it comes to access control. This means using Complex, Long and Unique passwords for starters. The best recommendation is to use a Password Generator like those found in apps like 1Password and LastPass. Remember that this includes changing all access points. When we say access points we mean things like FTP / SFTP, WP-ADMIN, CPANEL (or any other administrator panel you use with your host) and MYSQL. This also extends beyond your user, and must include all users that have access to the environment. It is also recommended to consider using some form of Two Factor / Multi-Factor authentication system. In it's most basic form, it introduces, and requires, a second form of authentication when logging into your WordPress instance. Some of the plugins available to assist you with this include: Authy Clef Rublon Duo Reset all Access. Once you identify a hack, one of the first steps you will want to do is lock things down so that you can minimize any additional changes. The first place to start is with your users. You can do this by forcing a global password reset for all users, especially administrators. Here is a plugin that can assist with this step: iThemes Security Force Strong Passwods You also want to clear any users that might be actively logged into WordPress. You do this by updating the secret keys in wp-config. You will need to create a new set here: the WordPress key generator. Take those values then overwrite the values in your wp-config.php file with the new ones. This will force anyone that might still be logged in off. Create a Backup. You hopefully have a backup of your website, but if you don't, this will be a good time to create one. Backups are a critical piece of your continuation of operations, and should be something you actively plan for moving forward. You should also ask your host what their policy is as it pertains to backups. If you do have a backup, you should be able to perform a restore and skill right into the forensics work. Side note: It's important you keep regular backups of your database and files. If this ever happens again. Regardless, before you move into the next phase of cleaning, it is recommended you take one more snapshot of the environment. Even if it's infected, depending on the type of hack, the impacts can cause a lot of issues and in the event of catastrophic failure you'll at least have that bad copy to reference. Find and remove the hack. This will be the most daunting part of the entire process. Finding and removing the hack. The exact steps you take will be dictated by a number of factors, including, but not limited to, the symptoms provided above. How you approach the problem will be determined by your own technical aptitude working with websites and web servers. To help in the process though, we've included a number of different resources that should help you in the process: Did Your WordPress Site Get Hacked? How to Clean Your Hacked Install How To Clean a Hacked WordPress Site How to Cope With a Hacked Site Four Malware Infections How to Clean a WordPress Hack It might be tempting to purge everything and start over. In some cases that's possible, but in many instances it's just not possible. What you can do however is reinstall certain elements of the site with little regard to impacting the core of your website. You always want to make sure you reinstall the same version of software your website is using, if you choose an older or newer one you're likely to kill your website. When reinstalling, be sure not to use the reinstall options in your WP-ADMIN. Use your FTP / SFTP application to drag and drop the versions. This will prove much more effective in the long run as those installers often only overwrite existing files, and hacks often introduce new files... You can replace the following directories safely: /wp-admin /wp-includes From there, it's recommended that you be more diligent in updating and replacing files as you move through wp-content as it contains your theme and plugin files. The one file you will definitely want to look at is your .htaccess file. It's one of the more common files, regardless of the type of infection, that is most often updated and used for nefarious activities. This file is often located at the root of your installation folder, but can also be embedded within several other directories on the same installation. Regardless of the type of infection, there are will be some common files you will want to keep an eye on during your remediation process. They include: index.php header.php footer.php function.php If modified, these files can usually adversely affect all page requests, making them high targets for bad actors. Leverage the Community We often forget but we're a community based platform, this means that if you're in trouble someone in the community is likely to give a lending hand. A very good place to start if you're strapped for cash or just looking for a helping hand is the WordPress.org Hacked or Malware forum. Update! Once you are clean, you should update your WordPress installation to the latest software. Older versions are more prone to hacks than newer versions. Change the passwords again! Remember, you need to change the passwords for your site after making sure your site is clean. So if you only changed them when you discovered the hack, change them again now. Again remembering to use Complex, Long and Unique passwords. Forensics. Forensics is the process of understanding what happened. How did the attackers get in? The goal is to understand the attack vector a bad actor used to ensure they're unable to abuse it again. In many instances, it's very difficult for website owners to perform this type of analysis due to lack of technical knowledge and / or available data. If you do have the metadata required, then there are tools like like OSSEC and splunk that can help you synthesize the data. Secure your site. Now that you have successfully recovered your site, secure it by implementing some (if not all) of the recommended security measures. Can't Log Into WordPress Admin Panel There are times that a bad actor will hijack your administrator account[s]. This is not a reason to panic, there are a few different things you can do to regain control of your account. You can follow these steps to reset your password Tools like phpMyAdmin and Adminer are often made available via your hosting provider. They allow you to log into your database directly, bypassing your Administration Screen and resetting your user in the users table wp_users. If you don't want to mess with password hashes or can't figure it out, simply update your email and go back to Login Screen, click forgot password, and wait for the email. Using version control? If you are using version control, it can be very handy to quickly identify what has changed and to rollback to a previous version of the website. From the terminal or command line you can compare your files with the versions stored in the official WordPress repository. $ svn diff . Or compare a specific file: $ svn diff /path/to/filename Other Resources Hacked WordPress Backdoors (OttoPress) WordPress Security - Cutting Through the BS (Sucuri) Security Posts (Perishable Press) Back to FAQ Plugins ankitguptaindia — Tue, 30 Aug 2016 13:17:04 +0000 Introduction Plugins are ways to extend and add to the functionality that already exists in WordPress. The core of WordPress is designed to be lean and lightweight, to maximize flexibility and minimize code bloat. Plugins offer custom functions and features so that each user can tailor their site to their specific needs. For instructions and information on downloading, installing, upgrading, troubleshooting, and managing your WordPress Plugins, see Managing Plugins. If you want to develop your own plugin, there is a comprehensive list of resources in Plugin Resources. Plugin Repositories WordPress Plugins are available from several sources. The most popular and official source for WordPress Plugins is the WordPress.org repo. Official WordPress Plugins Repository Just to note, not all WordPress Plugins make it into the above repository. Search the web for "WordPress Plugin" and the keywords for the type of functionality you are seeking. There is bound to be a solution out there for you. Default Plugins The following two plugins are included with WordPress core: Akismet Akismet checks your comments against the Akismet web service to see if they look like spam or not. You can review the spam it catches under "Manage" and it automatically deletes old spam after 15 days. See all of the features in Akismet here: https://wordpress.org/plugins/akismet/ Hello Dolly This is not just a plugin, it symbolizes the hope and enthusiasm of an entire generation summed up in two words sung most famously by Louis Armstrong. Hello, Dolly. This is, by the way, the world's first official WordPress Plugin. When enabled you will randomly see a lyric from "Hello, Dolly" in the upper right of your Administration Screens on every page. Plugin Development For information on building your own plugins, see: Writing a Plugin Plugin API Plugin Resources Managing Plugins ankitguptaindia — Tue, 30 Aug 2016 13:59:43 +0000 What are plugins? WordPress Plugins are PHP scripts that extend the functionality of WordPress. They enhance the features of WordPress, or add entirely new features to your site. Plugins are often developed by volunteers, and are usually free to the public. Plugins are available via the WordPress Plugin Directory. Although plugins you find here are thoroughly tested and considered safe to use, they are of varying quality and are often works in progress. How do they relate to WordPress core? The WordPress content management system software, or WordPress core, provides the primary functionality for publishing content and managing users. Each WordPress plugin is an additional piece of software that can be easily installed to extend the functionality of WordPress core. This allows you to customize your WordPress site with your desired functionality. Since so much functionality is provided through plugins, WordPress core is full-featured and customizable, without having to include everything for everyone. What are some examples? Some of the more popular plugins in the WordPress Plugin Directory fall into these categories: Spam control SEO Data import and export E-commerce Security Caching This is just a small sample. There are thousands of plugins available in the directory, so there’s a good chance you’ll find some that are useful to you. Finding and Installing Plugins Finding Plugins You can browse and search for plugins in the WordPress Plugin Directory. Each plugin listed there is available for download as a zip file you can upload to your WordPress site. An alternative way to find and install plugins is from within the WordPress admin screens. Navigate to Plugins > Add New, and you can browse and search for plugins from within your dashboard. Each plugin listed there has an "Install Now" button so you can easily add it to your site. Plugin Updates Plugin developers update their plugins occasionally, and those updates will be visible to you on your site’s Plugins page. To find any plugins installed on your site that need to be updated: Click the "Plugins" link in the left nav of your site’s dashboard. Look down the list of installed plugins for any that include a line reading "There is a new version…" Click the "View version…" link in that note to view details about the plugin’s update. Click the "update now" link to update the plugin. Plugin Compatibility If a plugin hasn’t been updated since the most recent update to WordPress core, it may be incompatible, or its compatibility may be unknown. You can view compatibility information about plugins from the Add Plugins page, or from the Installed Plugins list. Compatibility of New Plugins To learn about the compatibility of a plugin before you install it, navigate to Plugins > Add New. Each plugin description on this page includes a note that reads "Compatible with your version of WordPress" or "Untested with your version of WordPress." You can click the "More details" link to see information about this plugin's compatibility. Compatibility of Installed Plugins To learn about the compatibility of plugins you’ve already installed, click the “Plugins” link in the left nav of your site’s dashboard. Each item on this list should contain a “View details” link. Click this to see information about this plugin’s compatibility with different versions of WordPress. Installing Plugins There are 3 ways to install WordPress plugins. Automatic Plugin Installation. Any plugin available on the WordPress Plugins Directory can be installed via the built-in plugin installer. Upload via WordPress Admin. You can easily add a new plugin by uploading a zip archive of the plugin from your local computer. Manual Plugin Installation. In some cases, you may need to manually upload a plugin directly using an SFTP client. Automatic Plugin Installation This is the simplest method of installing a plugin. To add a plugin using the built-in plugin installer: Navigate to Plugins > Add New. Use the search form in the top-right to search by keyword, author or tag. On the search results that appear, click a plugin’s title to read more about it. This page may contain installation notes, plugin documentation or other useful information. Click the Install Now button to install the plugin. Click Activate to activate the plugin. Manual Upload via WordPress Admin If you have a copy of the plugin as a zip file, you can manually upload it and install it through the Plugins admin screen. Navigate to Plugins > Add New. Click the Upload Plugin button at the top of the screen. Select the zip file from your local filesystem. Click the Install Now button. When installation is complete, you'll see "Plugin installed successfully." Click the Activate Plugin button at the bottom of the page. Manual Plugin Installation In rare cases, you may need to install a plugin by manually transferring the files onto the server. This is recommended only when absolutely necessary, for example when your server is not configured to allow automatic installations. This procedure requires you to be familiar with the process of transferring files using an SFTP client. Warning: this process may put your site at risk if you install a WordPress plugin incompatible with the current version or from an unreliable source. Back up your site completely before proceeding. If your plugin is in the form of a zip file, unzip the contents. You should see a single folder named after the plugin. Look in the plugin folder for a readme.txt file. Read the file to confirm that this is the correct plugin, and to look for any special instructions. Connect to your WordPress server with your SFTP client. Copy the plugin folder to the wp-content/plugins folder in your WordPress directory. This installs the plugin to your WordPress site. Navigate to your Plugins admin screen and locate the newly uploaded plugin in the list. Click the plugin’s "Activate" link. If there is one, click the plugin's "View details" link to learn more about the plugin. Plugin Favorites You can add a plugin to your list of favorites, and you can view and easily install another WordPress.org user's favorite plugins. Favorite a Plugin Log in to the WordPress Plugins Directory. While viewing a plugin's page, click the heart icon next to the Download button. Once you have favorited a plugin, it will show up in your WordPress.org public profile. If you have published a review of the plugin, your rating of the plugin will also appear here. View a User's Favorite Plugins To see a WordPress.org user's favorite plugins (including your own): Browse to the Add Plugins admin screen (Plugins > Add New). Click the Favorites tab. Type the user’s name in the "Your WordPress.org username" field. Click Get Favorites. Each of the plugins listed here has an Install Now button you can use to add the plugin to your site. Uninstalling Plugins Plugins have a safe and easy-to-use uninstaller. If that's unavailable to you for some reason, you can also manually uninstall them. Automatic Uninstallation The safe and easy way to uninstall a plugin is via the WordPress admin screen. Navigate to your Plugins admin screen and locate the plugin to be installed. Click the plugin’s "Deactivate" link. Click the plugin’s "Delete" link. Manual Uninstallation In rare cases, you may need to manually uninstall a plugin without using the Plugins admin screen. This is recommended only when absolutely necessary. Warning: The following procedure involves manually deleting files from your WordPress server. This can be dangerous. Back up your site completely before proceeding. Navigate to your Plugins admin screen and locate the plugin to be installed. Click the plugin's "Deactivate" link. If installing the plugin required you to edit your WordPress theme, manually edit the theme files to remove those modifications. Connect to your WordPress server with your SFTP client. Navigate to your WordPress directory, then into the wp-content/plugins folder. Locate the folder named after the plugin to be uninstalled. Note: the folder name will not match the plugin completely, but it should be recognizable. A plugin named The Most Useful Plugin Ever would probably be located at wp-content/plugins/the-most-useful-plugin-ever. Delete the plugin folder and its contents. Navigate to your Plugins admin screen and review the list of plugins to confirm that you have successfully removed the intended plugin. Troubleshooting Occasionally, a WordPress Plugin may not work as expected. There is no defined procedure or recipe for troubleshooting such a problem, but this section may be helpful. Resources Review the plugin’s documentation to confirm that you’ve followed the instructions. See: Plugins > View details Plugins > edit (Click readme.txt under "Plugin Files.") Search the WordPress Support Forums for the name of the plugin and keywords associated with the problem you are experiencing. Search the WordPress Plugins Directory for notes on the plugin and links to issues reported in the Forums. Go to the website of the plugin author and check their blog and plugin page for known issues or advice. Search the web with the name of the plugin and keywords associated with the issue. Post a question on the WordPress Support Forums with the name of the Plugin and specific problems in the title. For advice on how to improve your chances of getting help, see Finding WordPress Help. Possible Resolutions The plugin may be installed, but inactive. Check that the plugin has been activated in your Plugin screen. Deactivate and re-activate the plugin to see if this makes it work. The problem may be caused by a conflict with another WordPress plugin. Try deactivating other plugins to identify the conflict. The plugin may be a buggy or incompatible. Search for similar plugins that you can try instead. Advanced Troubleshooting The information in this section may be unfamiliar or intimidating to anyone new to WordPress. If you are an experienced WordPress user and you have no fear of going “under the hood,” this section may be helpful. If you are experiencing problems with a new plugin or one that stopped working after an update, these steps can help you troubleshoot: If you manually installed the plugin: Check the location of the plugin folder. You should find it under wp-content/plugins. If you are uploading a new version of the plugin, check that any old versions have been deleted or moved. Use your SFTP program to delete the plugin folder, and then re-install it. If you modified your WordPress theme to accommodate the plugin, review your changes. Make sure your code is correct, free of typos, and in the right place (e.g. within the WordPress loop vs. outside of it). If the Plugin does not appear in the Plugins List, view the Plugin's main file in the Plugin Editor to ensure the Plugin's header text exists and is properly formed. If you're using a custom WordPress Theme, try using one of the default WordPress Themes to see if your issue is Theme related. If it is, contact the Theme developer for assistance. Deactivate all your plugins to ensure they're not causing the problem. Reactivate the problematic one. If it works, there may be a conflict. Activate the others one by one to see if the problem returns, which may indicate the conflicting plugin. WordPress Plugin Tips The following are WordPress Plugin tips and techniques for advanced users and developers. Plugin Management Plugins are managed from the Plugins admin screen of your WordPress site. This list shows all installed plugins, whether they are active or inactive. From this screen, you can activate, deactivate and delete plugins. Each plugin on the list also contains links to further information about the plugin. Plugins listed in bold are currently active. The main file in each plugin should have a file header that shows basic information about the plugin. WordPress recognizes the header and, if it's present and correctly formatted, uses it to populate the list of plugins in the admin screen. If a plugin you installed is missing from the list on this admin screen, there could be a problem with its file header. Each plugin should also have a readme.txt file, which includes information about its authors, version, license, installation steps and more. To view this, click the Edit link on the admin screen, then click readme.txt under the Plugin Files list. Must-Use Plugins In a WordPress multisite network, you can install a plugin as must-use, meaning it is active on all sites in the network. By installing one or more plugins as must-use, you can standardize functionality across the sites in your multisite network. Must-use plugins can’t be deactivated using the Plugins screen. WordPress loads these plugins before normal plugins, which means that code and hooked functions registered in a must-use plugin can be assumed available to all other plugins. The information in this section applies to WordPress multisite only. The concept of must-use plugins does not apply in a single-site WordPress instance. See Must Use Plugins and Create A Network for more details. Hiding Plugins When Deactivated When activated, some plugins add code to the WordPress template files. This extra code may remain in place even after the plugin is deactivated, and can affect the look or functionality of the theme, causing errors. Therefore, it is imperative to prevent an inactive plugin from being detected and used. To do this, add PHP code to the template to perform a simple function_exists() check. (See the example, below.) Upload the modified template to your wp-content folder. The if (function_exists()) checks for the plugin, and will only call the plugin's function if the plugin is installed and active. If function_exists() returns FALSE, it will ignore the plugin function and continue loading the page. This example plugin uses a function called alex_get_shoutbox() to print out its contents. Developing Plugins The WordPress community relies on plugin developers to maintain a healthy and growing collection of plugins. A large part what makes WordPress valuable is the extensive and freely available plugins. You can help WordPress users by creating your own plugins for distribution through the WordPress.com plugin directory. If you're new to WordPress plugin development, these resources can be a helpful starting point. Must Use Plugins ankitguptaindia — Tue, 30 Aug 2016 13:46:43 +0000 Must-use plugins (a.k.a. mu-plugins) are plugins installed in a special directory inside the content folder and which are automatically enabled on all sites in the installation. Must-use plugins do not show in the default list of plugins on the Plugins page of wp-admin – although they do appear in a special Must-Use section – and cannot be disabled except by removing the plugin file from the must-use directory, which is found in wp-content/mu-plugins by default. To change the default directory manually, define WPMU_PLUGIN_DIR and WPMU_PLUGIN_URL in wp-config.php. Features Always-on, no need to enable via admin and users cannot disable by accident. Can be enabled simply by uploading file to the mu-plugins directory, without having to log-in. Loaded by PHP, in alphabetical order, before normal plugins, meaning API hooks added in an mu-plugin apply to all other plugins even if they run hooked-functions in the global namespace. Caveats Despite its suitability for many special cases, the mu-plugins system is not always ideal and has several downsides that make it innapropriate in certain circumstances. Below are several important caveats to keep in mind: Plugins in the must-use directory will not appear in the update notifications nor show their update status on the plugins page, so you are responsible for learning about and performing updates on your own. Activation hooks are not executed in plugins added to the must-use plugins folder. These hooks are used by many plugins to run installation code that sets up the plugin initially and/or uninstall code that cleans up when the plugin is deleted. Plugins depending on these hooks may not function in the mu-plugins folder, and as such all plugins should be carefully tested specifically in the mu-plugins directory before being deployed to a live site. WordPress only looks for PHP files right inside the mu-plugins directory, and (unlike for normal plugins) not for files in subdirectories. You may want to create a proxy PHP loader file inside the mu-plugins directory: History and Naming The 'mu-plugins' directory was originally implemented by WPMU (Multi-User) to offer site admins an easy way to activate plugins by default on all blogs in the farm. There was a need for this feature because at the time the multi-user-specific code did not offer ways of achieving this effect using the site admin section (today the renamed "Multisite WordPress" has features to manage plugins from inside the admin). The code handling /mu-plugins/ was merged into the main WordPress code on 03/07/09 with this changeset a full 10 months before the wpmu codebase was initially merged, and all WP sites could take advantage of autoloaded plugins, whether they had MU/Multisite enabled or not. The feature is useful for all types of WP installations depending on circumstances, so this makes sense. In this process the name "mu plugins" became a misnomer because it did not apply exclusively to multisite installs and because "MU" was not even being used anymore to refer to WP installations with multiple blogs. Despite this, the name was kept and re-interpreted to mean "Must-use plugins", i.e. These are plugins that must always be used, thus they are autoloaded on all sites regardless of the settings in the Plugins pane of wp-admin. Thus "Must-Use" is effectively a Backronym, like PHP (which originally meant "Personal Home Page" but was later re-interpreted as meaning "PHP Hypertext Preprocessor", which is also a Recursive Acronym). Source Code get_mu_plugins() is located in wp-admin/includes/plugin.php. wp_get_mu_plugins() is located in wp-includes/load.php. Moving WordPress Mon, 05 Sep 2016 10:06:34 +0000 Whether you are moving WordPress to a new server or to a different location on your server, you don't need to reinstall. WordPress is flexible enough to handle all of these situations. Moving to a New Server If you are moving WordPress from one server to another, begin by backing up your WordPress directory, images, plugins, and other files on your site as well as the database. See WordPress Backups and Backing Up Your Database. Keeping Your Domain Name and URLs Moving your domain without changing the Home and Site URLs of your WordPress site is very simple, and in most cases can be done by moving the files. If database and URL remain the same, you can move by just copying your files and database. If database name or user changes, edit wp-config.php to have the correct values. If you want to test before you switch, you must temporarily change "siteurl" and "home" in the database table "wp_options" (through phpMyAdmin or similar). If you had any kind of rewrites (permalinks) setup you must disable .htaccess and reconfigure permalinks when it goes live. Changing Your Domain Name and URLs Moving a website and changing your domain name or URLs (i.e. from http://example.com/site to http://example.com, or http://example.com to http://example.net) requires the following steps - in sequence. Download your existing site files. Export your database - go in to MySQL and export the database. Move the backed up files and database into a new folder - somewhere safe - this is your site backup. Log in to the site you want to move and go to Settings > General, then change the URLs. (ie from http://example.com/ to http://example.net ) - save the settings and expect to see a 404 page. Download your site files again. Export the database again. Edit wp-config.php with the new server's MySQL database name, user and password. Upload the files. Import the database on the new server. When your domain name or URLs change there are additional concerns. The files and database can be moved, however references to the old domain name or location will remain in the database, and that can cause issues with links or theme display. If you do a search and replace on your entire database to change the URLs, you can cause issues with data serialization, due to the fact that some themes and widgets store values with the length of your URL marked. When this changes, things break. To avoid that serialization issue, you have three options: Use the Velvet Blues Update URLs or Better Search Replace plugins if you can access your Dashboard. Use WP-CLI's search-replace if your hosting provider (or you) have installed WP-CLI. Use the Search and Replace for WordPress Databases Script to safely change all instances on your old domain or path to your new one. (** only use this option if you are comfortable with database administration ** ) Note: Only perform a search and replace on the wp_posts table. Note: Search and Replace from Interconnectit is a 3rd party script Moving Directories On Your Existing Server Moving the WordPress files from one location on your server to another - i.e. changing its URL - requires some special care. If you want to move WordPress to its own folder, but have it run from the root of your domain, please read Giving WordPress Its Own Directory for detailed instructions. Here are the step-by-step instructions to move your WordPress site to a new location on the same server: Create the new location using one of these two options: If you will be moving your WordPress core files to a new directory, create the new directory. If you want to move WordPress to your root directory, make sure all index.php, .htaccess, and other files that might be copied over are backed up and/or moved, and that the root directory is ready for the new WordPress files. Log in to your site. Go to the Administration > Settings > General screen. In the box for WordPress Address (URL): change the address to the new location of your main WordPress core files. In the box for Site Address (URL): change the address to the new location, which should match the WordPress (your public site) address. Click Save Changes. (Do not try to open/view your site now!) Move your WordPress core files to the new location. This includes the files found within the original directory, such as http://example.com/wordpress, and all the sub-directories, to the new location. Now, try to open your site by going to yourdomain.com/wp-admin. Note, you may need to go to yourdomain.com/wp-login.php If you are using Permalinks, go to the Administration > Settings > Permalinks panel and update your Permalink structure to your .htaccess, file, which should be in the same directory as the main index.php file. Existing image/media links uploaded media will refer to the old folder and must be updated with the new location. You can do this with the Better Search Replace or Velvet Blues Update URLs plugins, WP-CLI's search-replace if your hosting provider (or you) have installed WP-CLI, manually in your SQL database, or by using the 3rd party database updating tool Search and Replace Databases Script * Note: this script is best used by experienced developers. In some cases your permissions may have changed, depending on your ISP. Watch for any files with "0000" permissions and change them back to "0644". If your theme supports menus, links to your home page may still have the old subdirectory embedded in them. Go to Appearance > Menus and update them. Sometimes you would need to restart your server, otherwise your server may give out an error. (happens in MAMP software (Mac)). It is important that you set the URI locations BEFORE you move the files. If You Forget to Change the Locations If you accidentally moved the files before you changed the URIs: you have two options. Suppose the files were originally in /path/to/old/ and you moved them to /path/to/new before changing the URIs. The way to fix this would be to make /path/to/old/ a symlink (for Windows users, "symlink" is equivalent to "shortcut") to /path/to/new/, i.e. ln -s /path/to/new /path/to/old and then follow the steps above as normal. Afterwards, delete the symlink if you want. If you forget to change the WordPress Address and Blog Address, you will be unable to change it using the wordpress interface. However, you can fix it if you have access to the database. Go to the database of your site and find the wp_options table. This table stores all the options that you can set in the interface. The WordPress Address and Blog Address are stored as siteurl and home (the option_name field). All you have to do is change the option_value field to the correct URL for the records with option_name=’siteurl‘ or option_name=’home‘. If You Have Accidentally Changed your WordPress Site URL Suppose you accidentally changed the URIs where you cannot move the files (but can still access the login page, through a redirection or something). wp-login.php can be used to (re-)set the URIs. Find this line: require( dirname(__FILE__) . '/wp-load.php' ); and insert the following lines below: //FIXME: do comment/remove these hack lines. (once the database is updated) update_option('siteurl', 'http://your.domain.name/the/path' ); update_option('home', 'http://your.domain.name/the/path' ); You're done. Test your site to make sure that it works right. If the change involves a new address for your site, make sure you let people know the new address, and consider adding some redirection instructions in your .htaccess file to guide visitors to the new location. Changing The Site URL also provides the details of this process. Managing Your Old Site Shutting It Down Download a copy of the main wordpress files from your OLD site to your hard drive and edit wp-config.php to suit the new server. Go back to your OLD site and go to Administration > Settings > General screen and change the URL (both of them) to that of your new site. Login on your server, go to phpMyAdmin, export as file, and save your database (but keep the old one just in case). Now, upload this new database and the copy of the wordpress core files with the edited wp-config.php to your new server. That's it! Keeping it Running Caution: Make sure you have a backup of your old site's WordPress database before proceeding! Part A - Activating Your New Site Download your entire WordPress installation to your hard drive. Name the folder appropriately to indicate that this is your OLD site's installation. Download your database. Go back to your OLD site and go to options and change the url (both of them) to that of your new site. Again, download your entire WordPress installation to your hard drive. Name the folder appropriately to indicate that this is your NEW site's installation. Download your database once again (but keep the old one). Upload this database to your new server. It will be easiest if you use the same database name and you create a user with the same login credentials on your new server as on your old server. If you used a different database name and/or user (see previous step), edit wp-config.php in your NEW site's installation folder appropriately. Upload the NEW site's installation folder to your new site. Presto, your NEW site should be working! Part B - Restoring Your Old Site On the original server, delete your OLD site's database (remember, you should have a copy on your local computer that you made at the very beginning). Upload your OLD site's installation folder to your original server, overwriting the files that are currently there (you may also delete the installation folder on the server and simply re-upload the OLD site's files). Upload your OLD site's database from your local computer to the server. That should do it! Another procedure for making copies of posts, comments, pages, categories and custom field (post status, data, permalinks, ping status, etc.) easy to follow: Install a new WordPress site Go on old site Admin panel. Here, in Manage > Export select "all" in menu Restrict Author. Click on Download Export File In new site go on Manage > Import, choose WordPress item. In the page that will be shown, select the file just exported. Click on Upload file and Import It will appear a page. In Assign Authors, assign the author to users that already exist or create new ones. Click on Submit At the end, click on Have fun Note: using this method, if there are some articles in the new site (like Hello World, Info Page, etc.), these will not be erased. Articles are only added. Using the former procedure, the articles in new site will be deleted. Moving WordPress Multisite Multisite is somewhat more complicated to move, as the database itself has multiple references to the server name as well as the folder locations. If you're simply moving to a new server with the same domain name, you can copy the files and database over, exactly as you would a traditional install. If, instead, you are changing domains, then the best way to move Multisite is to move the files, edit the .htaccess and wp-config.php (if the folder name containing Multisite changed), and then manually edit the database. Search for all instances of your domain name, and change them as needed. This step cannot yet be easily automated. It's safe to search/replace any of the wp_x_posts tables, however do not attempt blanket search/replace without the Search and Replace for WordPress Databases script (aka the interconnectit script). If you're moving Multisite from one folder to another, you will need to make sure you edit the wp_blogs entries to change the folder name correctly. You should manually review both wp_site and wp_blogs regardless, to ensure all sites were changed correctly. Also, manually review all the wp_x_options tables and look for three fields and edit them as needed: home siteurl fileupload_url If you are moving from subdomains to subfolders, or vice-versa, remember to adjust the .htaccess file and the value for SUBDOMAIN_INSTALL in your wp-config.php file accordingly. Related Links How to move WordPress site to another server with zero downtime Moving a blog from wordpress.com to self-hosted blog Moving WordPress to a new domain or server Italian version of this article - Versione italiana dell'articolo How to move a WordPress Blog or Website Search and Replace for WordPress Databases Online WordPress Serialized PHP Search and Replace Cloning a live WordPress site to a local Mac test environment PHP script to replace site url in Wordpress database dump, even with WPML The Duplicator plugin helps administrators move a site from one location to another Technical tutorial on moving your WordPress blog to Bitnami's AWS configuration Brute Force Attacks janr — Fri, 14 Oct 2016 12:39:39 +0000 Unlike hacks that focus on vulnerabilities in software, a Brute Force Attack aims at being the simplest kind of method to gain access to a site: it tries usernames and passwords, over and over again, until it gets in. Often deemed 'inelegant', they can be very successful when people use passwords like '123456' and usernames like 'admin.' They are, in short, an attack on the weakest link in any website's security... you. Due to the nature of these attacks, you may find your server's memory goes through the roof, causing performance problems. This is because the number of http requests (that is the number of times someone visits your site) is so high that servers run out of memory. This sort of attack is not endemic to WordPress, it happens with every webapp out there, but WordPress is popular and thus a frequent target. Protect Yourself A common attack point on WordPress is to hammer the wp-login.php file over and over until they get in or the server dies. You can do some things to protect yourself. Don't use the 'admin' username The majority of attacks assume people are using the username 'admin' due to the fact that early versions of WordPress defaulted to this. If you are still using this username, make a new account, transfer all the posts to that account, and change 'admin' to a subscriber (or delete it entirely). You can also use the plugin Change Username to change your username. Good Passwords The goal with your password is to make it hard for other people to guess and hard for a brute force attack to succeed. Many automatic password generators are available that can be used to create secure passwords. WordPress also features a password strength meter which is shown when changing your password in WordPress. Use this when changing your password to ensure its strength is adequate. You can use the Force Strong Password plugin to force users to set strong passwords. Things to avoid when choosing a password: Any permutation of your own real name, username, company name, or name of your website. A word from a dictionary, in any language. A short password. Any numeric-only or alphabetic-only password (a mixture of both is best). A strong password is necessary not just to protect your blog content. A hacker who gains access to your administrator account is able to install malicious scripts that can potentially compromise your entire server. To further increase the strength of your password, you can enable Two Step Authentication to further protect your blog. Plugins There are many plugins available to limit the number of login attempts made on your site. Alternatively, there are also many plugins you can use to block people from accessing wp-admin altogether. Protect Your Server If you decide to lock down wp-login.php or wp-admin, you may find you get a 404 or 401 error when accessing those pages. To avoid that, you will need to add the following to your .htaccess file. [code language="php"] ErrorDocument 401 default [/code] You can have the 401 point to 401.html, but the point is to aim it at not WordPress. For Nginx you can use the error_page directive but must supply an absolute url. [code language="php"] error_page 401 http://example.com/forbidden.html; [/code] On IIS web servers you can use the httpErrors element in your web.config, set errorMode="custom": [code language="xml"] [/code] Password Protect wp-login.php Password protecting your wp-login.php file (and wp-admin folder) can add an extra layer to your server. Because password protecting wp-admin can break any plugin that uses ajax on the front end, it's usually sufficient to just protect wp-login.php. To do this, you will need to create a .htpasswd file. Many hosts have tools to do this for you, but if you have to do it manually, you can use this htpasswd generator. Much like your .htaccess file (which is a file that is only an extension), .htpasswd will also have no prefix. You can either put this file outside of your public web folder (i.e. not in /public_html/ or /domain.com/, depending on your host), or you can put it in the same folder, but you'll want to do some extra security work in your .htaccess file if you do. Speaking of which, once you've uploaded the .htpasswd file, you need to tell .htaccess where it's at. Assuming you've put .htpasswd in your user's home directory and your htpasswd username is mysecretuser, then you put this in your .htaccess: [code language="php"] # Stop Apache from serving .ht* files Order allow,deny Deny from all # Protect wp-login.php AuthUserFile ~/.htpasswd AuthName "Private access" AuthType Basic require user mysecretuser [/code] The actual location of AuthUserFile depends on your server, and the 'require user' will change based on what username you pick. If you are using Nginx you can password protect your wp-login.php file using the HttpAuthBasicModule. This block should be inside your server block. [code language="php"] location /wp-login.php { auth_basic "Administrator Login"; auth_basic_user_file .htpasswd; } [/code] The filename path is relative to directory of nginx configuration file nginx.conf The file should be in the following format: [code language="php"] user:pass user2:pass2 user3:pass3 [/code] Unfortunately there is no easy way of configuring a password protected wp-login.php on Windows Server IIS. If you use a .htaccess processor like Helicon Ape, you can use the .htaccess example mentioned above. Otherwise you'd have to ask your hosting provider to set up Basic Authentication. All passwords must be encoded by function crypt(3). You can use an online htpasswd generator to encrypt your password. Limit Access to wp-login.php by IP If you are the only person who needs to login to your Admin area and you have a fixed IP address, you can deny wp-login.php (and thus the wp-admin/ folder) access to everyone but yourself via an .htaccess or web.config file. This is often referred to as an IP whitelist. Note: Beware your ISP or computer may be changing your IP address frequently, this is called dynamic IP addressing, rather than fixed IP addressing. This could be used for a variety of reasons, such as saving money. If you suspect this to be the case, find out out how change your computer's settings, or contact your ISP to obtain a fixed address, in order to use this procedure. In all examples you have to replace 203.0.113.15 with your IP address. Your Internet Provider can help you to establish your IP address. Or you can use an online service such as What Is My IP. Examples for multiple IP addresses are also provided. They're ideal if you use more than one internet provider, if you have a small pool of IP addresses or when you have a couple of people that are allowed access to your site's Dashboard. Create a file in a plain text editor called .htaccess and add: [code language="php"]# Block access to wp-login.php. order deny,allow allow from 203.0.113.15 deny from all [/code] You can add more than one allowed IP address using: [code language="php"]# Block access to wp-login.php. order deny,allow allow from 203.0.113.15 allow from 203.0.113.16 allow from 203.0.113.17 deny from all [/code] Are you using Apache 2.4 and Apache module mod_authz_host? Then you have to use a slightly different syntax: [code language="php"]# Block access to wp-login.php. Require ip 203.0.113.15 [/code] If you want to add more than one IP address, you can use: [code language="php"]# Block access to wp-login.php. Require ip 203.0.113.15 203.0.113.16 203.0.113.17 # or for the entire network: # Require ip 203.0.113.0/255.255.255.0 [/code] For Nginx you can add a location block inside your server block that works the same as the Apache example above. [code language="php"] error_page 403 http://example.com/forbidden.html; location /wp-login.php { allow 203.0.113.15 # or for the entire network: # allow 203.0.113.0/24; deny all; } [/code] Note that the order of the deny/allow is of the utmost importance. You might be tempted to think that you can switch the access directives order and everything will work. In fact it doesn't. Switching the order in the above example has the result of denying access to all addresses. Again, on IIS web servers you can use a web.config file to limit IP addresses that have access. It's best to add this in an additional directive. [code language="xml"] [/code] Deny Access to No Referrer Requests Extended from Combatting Comment Spam, you can use this to prevent anyone who isn't submitting the login form from accessing it: [code language="php"] # Stop spam attack logins and comments RewriteEngine On RewriteCond %{REQUEST_METHOD} POST RewriteCond %{REQUEST_URI} .(wp-comments-post|wp-login)\.php* RewriteCond %{HTTP_REFERER} !.*example.com.* [OR] RewriteCond %{HTTP_USER_AGENT} ^$ RewriteRule (.*) http://%{REMOTE_ADDR}/$1 [R=301,L] [/code] Nginx - Deny Access to No Referrer Requests [code language="php"] location ~* (wp-comments-posts|wp-login)\.php$ { if ($http_referer !~ ^(http://example.com) ) { return 405; } } [/code] Windows Server IIS - Deny access to no referrer requests: [code language="xml"] [/code] Change example.com to your domain. If you're using Multisite with mapped domains, you'll want to change example.com to (example.com|example.net|example4.com) and so on. If you are using Jetpack comments, don't forget to add jetpack.wordpress.com as referrer: (example.com|jetpack\.wordpress\com) ModSecurity If you use ModSecurity, you can follow the advice from Frameloss - Stopping brute force logins against WordPress. This requires root level access to your server, and may need the assistance of your webhost. If you're using ModSecurity 2.7.3, you can add the rules into your .htaccess file instead. Fail2Ban Fail2ban is a Python daemon that runs in the background. It checks the logfiles that are generated by Apache (or SSH for example), and on certain events can add a firewall rule. It uses a so called filter with a regular expression. If that regular expression happens for example 5 times in 5 minutes, it can block that IP address for 60 minutes (or any other set of numbers). Installing and setting up Fail2ban requires root access. Blocklists It appears that most brute force attacks are from hosts from Russia, Kazachstan and Ukraine. You can choose to block ip-addresses that originate from these countries. There are blocklists available on the internet that you can download. With some shell-scripting, you can then load blockrules with iptables. You have to be aware that you are blocking legitimate users as well as attackers. Make sure you can support and explain that decision to your customers. Besides blocklists per country, there are lists with ip-addresses of well-known spammers. You can also use these to block them with iptables. It's good to update these lists regularly. Setting up of blocklists and iptables requires root access. Cloud/Proxy Services Services like CloudFlare and Sucuri CloudProxy can also help mitigate these attacks by blocking the IPs before they reach your server. See Also Sucuri: Protecting Against WordPress Brute Force Attacks How to: Protect WordPress from brute-force XML-RPC attacks Liquid Web: ModSecurity Rules To Alleviate Brute Force Attacks HostGator: Password Protecting wp-login Stopping Brute-force Logins Swiss Army Knife for WordPress (SAK4WP) - Free Open Source Tool that can help you protect your wp-login.php and /wp-admin/ but not /wp-admin/admin-ajax.php with one click and much more I Make Changes and Nothing Happens janr — Fri, 14 Oct 2016 12:39:39 +0000 Things are going great. You have figured out how to write a post, how to make a few categories, and maybe even add a plugin or two. Then you notice that you've make a few changes in your WordPress content or your design and when you view your WordPress site, you notice that nothing has changed. Your fix isn't fixed. Your change isn't changed. This can be frustrating. A number of common factors can cause this behavior, including browser caching, server-side caching, caching plugins, changes being made in incorrect locations in the file system and more. The Browser Cache Did you know that a computer is supposed to make your life easier? Less complicated? It is supposed to save you time and energy and actually improve your life. No? Well, maybe not, but your Internet browser does its best to try to make your life a little easier. When you first visit a web page, it often takes a while to load, right? But the next page you visit within that site doesn't take so long to load. This is because, in an effort to be helpful, the browser stores the information on your computer so it reloads it from your computer, not from the actual site. This is called the cache and it is meant to speed up your Internet browsing. The term cache may sound familiar. Remember the pirates and thieves of old who would stockpile their treasures in a cave, hole in the ground, or somewhere "safe". Called the cache, the Internet browser stores files and information for the browser to reuse when the page is refreshed or viewed again. The problem comes when you make a small change to your site and the browser doesn't recognize it as a significant change, so it reloads the same page you just looked at. The solution is to clear or empty your browser's cache. Clearing the Browser Cache Normally, to see the changes on your page, you click the Refresh button on the browser toolbar or press the F5 key on your keyboard. In many cases, this simply reloads the page without clearing the browser's cache. Here are some techniques to wipe clean the browser's cache so you will see the changes when your page reloads. The way you clear the browser cache depends on the particular browser you are using. Here is how you clear the cache on common browsers: Chrome - How to delete your Chrome cache, history, and other browser data Safari - How to clear the Safari browser cache Firefox - How to clear the Firefox cache Internet Explorer - How to clear the Internet Explorer cache Opera - How to clear the Opera cache In addition to clearing the cache, each browser may have a way of stopping or minimizing the caching of web pages. Using this technique will definitely slow down your web page viewing, and it isn't a perfect solution because some caching may still occur, but it does help. Check your Internet browser's help files for the specifics on how to turn off the cache feature. Server-side Caching Be aware that some web hosting services use caching plugins on the backend without letting the user know explicitly. You may be able to turn this off via your webhost's configuration panel. To be sure, you can ask a support member for your webhost if any caching plugins are used, and request that they be turned off if needed. This situation may also occur if you are using a Managed WordPress hosting plan. Many Managed WordPress hosting plans use server-side caching. If you are using a Managed WordPress service from your hosting provider and you are seeing this issue, you may want to see if they have an option to manually flush the cache. In many cases, your changes will immediately show up after flushing the cache. If you are using a caching HTTP reverse proxy such as Varnish on your web server, edits to your files may not appear right away. Edits may become visible after some length of time when the cached version expires. You many need to tune your caching system in order to eliminate this issue. A WordPress Cache Plugin Some WordPress plugins also add cache functionality to your WordPress site. This helps your site load faster because WordPress can retrieve the pages of your blog from the cache instead of generating them all over again. All good cache plugins will clear the cache when a post, page, or comment is published. However, if you make other changes (e.g. to your theme), the cache may not be cleared and the old version may still appear. In this case, check the plugin's instructions to find out how to clear its cache. Note that WordPress does not come with a cache by default, so the above would only apply if you installed a cache plugin yourself. Check Your Source You know, even the very best web page designers, developers, and programmers screw up. It's the little details, the forgotten semi-colon, the misspelled tag, the lack of attention to a detail that screws things up. If the best do it, then it's very possible you have overlooked a little detail. And if you did, well, welcome to the club. It's a part of the process. Let's look at some of the most commonly overlooked details that happen when you aren't paying attention. Check the Address Is the name and folder for the file you "fixed" the same as the one you are viewing? Look at the following two addresses (URLs). wordpress/wp-content/themes/yourtheme/style.css test/wordpress/wp-content/themes/yourtheme/style.css In this case, you can probably see the difference, but when viewed in an address bar or in a text editor, you might miss the word test that sets the folder. Pay very close attention to the difference between style1.css and stylel.css if you are using different style names, too. The first filename is style followed by the digit one, while the second filename is style followed by a lowercase L. If you are working with different but similar files, make sure you give them distinctive names like style-red.css and style-800.css so you can clearly see the difference. Check the Template If you're editing a template, are you sure the page you're viewing is being generated from that template? Remember that many templates have very similar text on them; for example, a post header may appear on a single post page, index page, search page, archive page, and others. See Template Hierarchy if you're having trouble figuring out which template is in use. Check Your Upload When you make a change in a file, it is often on your computer's hard drive and you have to upload the file to your host server in order to view it on the Internet. Did you actually upload it? Did you put it in the right folder? Is it really there? When over-writing the exact same file, it doesn't always do a complete over-write, so consider deleting the original on the host server and then uploading the new version to make sure the right and whole thing is there. Test Yourself If you still can't see the changes you made, and the file is in the right place with the right name, and you are sure it's the right file, then go through these steps: Make a backup of the file you are working on and check that the backup is in a safe place. Make a big change (such as setting the background in your style.css as #ff0000 or even red). View the changed web page in your browser. Make sure you clear the cache to be sure you have the new version. If nothing changes, delete the file (and only that file) from the server and try to view the file again. If nothing continues to change, you and WordPress are looking at completely different files. It's time to get out your detective hat and start tracking down what is going on and where your files went to. Check your URL settings in your Options Panel and also in the database, and if this continues to be unsolvable, post a note explaining what you've done and what's the result on the WordPress Forum and let the experts step in to help. I've tried everything above and my changes still aren't displaying You can check out the following resources for more help: Troubleshooting WordPress Lessons Video Shortcode normalize — Tue, 30 Aug 2016 13:19:33 +0000 The Video feature allows you to embed video files and play them back using a simple shortcode. This was added as of WordPress Version 3.6 and is used like this: [[video]] You can also use built in embeds and simply put the media file on its own line: My cool content [[video src="video-source.mp4"]] More cool content Usage I have an old post that has an audio file in the Media Library attached to it, and I want to use the new shortcode: [[video]] I have the URL for an MP3, from the Media Library or external, that I want to play: [[video src="video-source.mp4"]] I have a source URL and fallbacks for other HTML5-supported filetypes: [[video mp4="source.mp4" ogv="source.ogv" webm="source.webm"]] Options The following basic options are supported: src (string) (optional) The source of your video file. If not included it will auto-populate with the first video file attached to the post. You can use the following options to define specific filetypes, allowing for graceful fallbacks: mp4, m4v, webm, ogv, wmv, flv Default: First video file attached to the post poster Defines image to show as placeholder before the media plays. Default: none loop (string) Allows for the looping of media. Defaults to "off." "off" - ("default") does not loop the media "on" - media will loop to beginning when finished and automatically continue playing Default: "off" autoplay (string) Causes the media to automatically play as soon as the media file is ready. Defaults to "off." "off" - ("default") does not automatically play the media "on" - Media will play as soon as the media is ready Default: "off" preload (string) (optional) Specifies if and how the video should be loaded when the page loads. Defaults to "metadata." "metadata" - ("default") only metadata should be loaded when the page loads "none" - the video should not be loaded when the page loads "auto" - the video should be loaded entirely when the page loads Default: "metadata" height (integer) (required) Defines height of the media. Value is automatically detected on file upload. Default: [Media file height] width (integer) (required) Defines width of the media. Value is automatically detected on file upload. Default: [Media file width] Source File The video shortcode is located in wp-includes/media.php. Related Gallery Shortcode Audio Shortcode Styling Lists with CSS ankitguptaindia — Thu, 25 Aug 2016 13:52:17 +0000 The underlying code for standard lists in WordPress consists of the , and HTML tags. Below is a definition of these tags: Ordered List. The order is important and items are usually styled with numbers. Unordered List. The order is not important and items are usually styled with bullet points. List item. This can belong to an ordered or an unordered list. Most lists in WordPress are identified by id or class attributes, making styling lists easy. With fairly simple changes to the style.css file, you can display the list horizontally instead of vertically, feature dynamic menu highlighting, change the bullet or numbering style, remove the bullets altogether, or any combination of these. Nested Lists Layout Different Themes format lists in different ways. The most common lists users often want to modify in WordPress are the sidebar menu lists. Since many sidebars feature nested lists, let's look at those in more depth. Begin by examining the style.css file found within the Theme's folder you are using. Most WordPress Themes label their sidebar menu section with the words sidebar, menu, or a combination of both. So, look for the sidebar Template file, typically called sidebar.php. This is a sample sidebar.php layout; your version may be different, but the concept will be the same. [code language="php"] Pages About Us Contact Site Map Archives February 2005 January 2005 December 2004 November 2004 Categories Stories Computer Tips WordPress Tips Web Page Design [/code] When you are working with nested lists and you want an individual style for each list, you have to recreate the "nest" in the stylesheet (style.css). [code language="php"]#sidebar ul {attributes} #sidebar li {attributes} #sidebar ul li {attributes} #sidebar ul ul li {attributes} #sidebar ul ul ul li {attributes} #pagenav {attributes} #pagenav ul {attributes} #pagenav ul li {attributes}[/code] ul The first style (#sidebar ul) sets the look for the overall list. It usually contains the margins and padding styles and may contain the font-family, color, and other details for the overall list. li The #sidebar li assigns a style to the actual list item. Here you can set the format to include a bullet or not. You can also change the font, font-size, or color, and you can even add borders. ul li The #sidebar ul li determines the style of the first nested list. Each first level nested list will be customized here, but you can style each of these sub-lists differently if they are contained within a specific CSS ID. In the above example, after the #search section, the first nested list is #pagenav. If you use Pages this is where the list of Pages would be generated. Since Pages work outside of The WordPress Loop, and often highlight specific information like "About Us", "Contact", and "Site Map", you may want to design the Pages style differently than the rest of your lists by putting the specific information about the look of the Pages in the #pagenav. ul ul li The #sidebar ul ul li applies style to the links within the #sidebar ul ul to help customize the look of this list. Again, if you have customized the #pagenav list, it will be different from the rest of your nested list items. ul ul ul li The #sidebar ul ul ul li is the style for the sub-sub-list. If you have a list of categories with subcategories, the category title will be the first level of the list, the categories would be the second level of the list, and any subcategories would be the third level, or sub-sub-list, such as the example below. Some designers like having the third level list feature a smaller font, a different bullet, or even a different color to highlight them from the list items above them: Category Title Category One Category Two Sub-Category One Sub-Category Two Category Three Styling Specific List Items Do you want your Categories List to look different from your Archives List? Then open up the index.php or sidebar.php and carefully add the following style references to the appropriate list item: id="categories">Categories ..... id="archives">Archives .... To customize the Categories and Archives list, add the following to your stylesheet to customize these individually: [code language="php"]#categories {attributes} #categories ul {attributes} #categories ul li {attributes} #archives {attributes} #archives ul {attributes} #archives ul li {attributes}[/code] Go through any other sections of your list and give them a style reference name and add them to your style sheet. When you've identified which part of the list controls which aspect of the list, it's time to start changing the look of the list. Styling individual items If you want to use image replacement techniques to style your list, each tag will need its own class or ID. Try the Classy wp_list_pages plugin. Styling Your Lists An important part of a list is the bullet - an eye catching dot, spot, or graphic that tells viewers "this is a list". The style of bullet or numbering for a list is determined by a list-style-type property in the style sheet. The default value is disc. Other basic values are circle, square, decimal, decimal-leading-zero, lower-roman, upper-roman, and none. Let's change the default value to something else, like a square. [code language="php"]#sidebar li { list-style: square; }[/code] Instead of typing list-style-type, you see a shorthand form of list-style, and instead of using the default disc, the list now features small squares. But not all lists need bullets. By their overall layout, you just know a list is a list. To eliminate the bullet, change the stylesheet to this: [code language="php"]#sidebar li { list-style: none; }[/code] Now, anything tagged with , within the DIV of the ID of #sidebar, would have no bullet. Experiment with different values to see the results you can achieve. HINT: In terms of accessibility, an ordered list is easier to navigate than an unordered list. Using a Custom Image Instead of a Bullet Tired of boring bullets? Let's get rid of the boring with a few CSS techniques. In this case, use list-style-image to instruct the browser to use your bullet image instead of the old boring default bullets. Find some interesting bullet graphics and add the following code in your style sheet to add some jazzy bullets to your lists: [code language="php"]#sidebar ul { list-style-image: url(/wp-images/image.gif); }[/code] Note that you could also use an absolute link rather than a relative link. Simply change the url(/wp-images/image.gif ) to url(http://example.com/wp-images/image.gif). Adding a Border to Your List To add a border, like an underline, after your title, you can simply add a border style to the top of the under the title, rather than on the title itself. [code language="php"]#sidebar ul ul {...; border-top: solid 1px blue; ....}[/code] Go a step further and add a whole box around your list with the title sitting atop it: [code language="php"]#sidebar ul ul {...; border: solid 1px blue; ....}[/code] Add a colored background to your list along with its new border: [code language="php"]#sidebar ul ul {...; border-top: solid 1px blue; background:#CCFFFF; ....}[/code] And your end result would look like this: Category Title Category One Category Two Category Three Or really expand the possibilities to something like this: Category Title Category One Category Two Category Three You can have a lot of fun with your list bullets and list layouts. If you are having trouble with your bullets and lists, check out the resources listed below and then visit the WordPress support forums to get more help. Troubleshooting Nested Lists If you are having trouble with your nested lists, the following might provide the solution. Also check CSS Troubleshooting for more styling help issues. Improper Tag Structure The number one cause of errors or non-validation within a nested list is the lack of proper list structure. Here is a very simplified and correct nested list layout. Note that when a (new) nested list begins, the tag of the current list item is not closed yet. It is left open until the nested list is completed, and then closed. [code language="php"] Category One Category Two <----Note: No Closing List Tag Sub-Category One Sub-Category Two <----Note: No Closing List Tag Sub-Sub-Category One Sub-Sub-Category Two <----Note: Closing List Tag <----Note: Nested List Closed Sub-Category Three <----Note: Nested List Closed Category Three <----Note: End of entire list[/code] Template Tag Lists Different Template Tags used for displaying lists have different ways of using and relying upon HTML list tags. Some template tags automatically include the and tags so all you have to do is include the tag in the list by itself and it will do all the work. Other tags require the to be in place followed by the template tag and it generates its own tags. Other template tags require designating which type of list tags are needed or use none at all if not listed in the tag's parameters. If you are having trouble with your nested lists when using template tags like wp_list_cats or wp_list_pages, check their parameters to see how they use the list tags and compare it with your usage. Parent/Child Relationships Discussed in The CSS Parent and Child Relationship, lists are one of the big culprits. Styles in the child list items are influenced by its "parents". If the parent's list style features the color "red" and you want the children to be in "blue", then you need to specify the color in the children's list styles to be "blue" so they will override the parent's style Nested lists within the WordPress Sidebar typically contain links. Therefore, while you can style the list as much as you want, the style for links will override the list style. You can control the way the links in the list work by giving them a specific style class of their own, including their hover attributes: [code language="php"]#sidebar a {attributes} #sidebar a:hover {attributes} #categories a {attributes} #categories a:hover {attributes} #archives a {attributes} #archives a:hover {attributes}[/code] Resources Creating Horizontal Menus Dynamic Menu Highlighting Customizing Your Sidebar Site Architecture 1.5 Stepping Into Template Tags W3.org's CSS-2 - Generated Content, Automatic Numbering, and Lists


Running a Development Copy of WordPress
justingreerbbi — Tue, 23 Aug 2016 05:10:47 +0000
Having a development instance of WordPress is a good way to update, develop and make modifications to a website while not interrupting the live version of WordPress. There are many ways to setup a development copy of WordPress but this article will cover the basics, best practices, tips and some tools to make running a development copy of WordPress a lot easier.
Two WordPresses, One Database
Note: If you are planing on doing database development, this method is NOT recommended.

A popular approach to running a local copy of your live site is to use the same database for both local and live. Using the same database will allow you to work on you local copy and simply push changes from local to your production with no break in uptime.

Setup of the local copy

Once you have your local files setup, you will need to modify wp-config.php in the root of your local install.

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

ob_start( 'ob_replace_home_url' );
function ob_replace_home_url( $content ) {
	$home_urls = array(
		'http://site.testing.foo.com',
		'http://site.foo.com',
		'http://site.authoring.testing.foo.com',
		'http://site.authoring.foo.com',
	);

	$content = str_replace( $home_urls, WP_HOME, $content );

	return $content;
}


 






Using a Drop-In
What if we don't want to hack core code? (Which is a good practice for easy upgrading and sharing code.) There is even a filter for this (pre_option_siteurl and pre_option_home) but there's a problem: within wp-settings.php,

 	the filter can't be defined until after line 65 when functions.php is included
 	WordPress makes calls to get_option on line 155 of (via wp_plugin_directory_constants())
 	plugins aren't defined until later down around line 194.

However, in between lines 65 and 155, there is something we can use, namely the loading of the drop-in db.php; the filter can be safely defined there. (However, this is perhaps only halfway towards "not core" code.)

Check if you already have an existing wp-content/db.php before trying this technique. It is used by packages like W3 Total Cache for similar reasons.

Old examples (WordPress 2)
You need to add code to your wp-config.php that assigns the right values of WP_HOME and WP_SITEURL to reflect the current location of WordPress, whether it's the live site or a local staging server.

To do this, simply add one of the following code sections to your wp-config.php above the last require_once statement.

Either this function:
function WP_LOCATION () {
    $script_path = realpath(dirname($_SERVER['SCRIPT_FILENAME']));
    $wp_base_path = realpath(dirname(__FILE__) . DIRECTORY_SEPARATOR . '..');
    $web_subfolder = substr( $script_path, strlen($wp_base_path)); 
    $wp_path = $web_subfolder ? substr( dirname($_SERVER['SCRIPT_NAME']), 0, -strlen($web_subfolder) ) : dirname($_SERVER['SCRIPT_NAME']) ;
    $retval = 'http' . ($_SERVER['HTTPS'] ? 's' : null) . '://' . $_SERVER['HTTP_HOST'] . $wp_path ;
    return $retval;
}
$wpLocation = WP_LOCATION();
define('WP_HOME',$wpLocation);
define('WP_SITEURL',$wpLocation);
define('WP_CONTENT_URL',$wpLocation."/wp-content");

Or alternately, you can add the following code, replacing LIVEURL and STAGINGURL with the locations for your live and staging servers:
$currenthost = $_SERVER['HTTP_HOST'];
$mypos = strpos($currenthost, 'localhost');
if ($mypos === false) {
define('WP_HOME','LIVEURL');
define('WP_SITEURL','LIVEURL');
} else {
define('WP_HOME','STAGINGURL');
define('WP_SITEURL','STAGINGURL');
}

WordPress 2.3.1 - WordPress 2.5
Edit the file wp-includes/options.php

In the function get_option, add this hack immediately after the line which says global $wpdb. It should look like the following:
function get_option( $setting ) {

	global $wpdb;

	/* Siteurl hack */

	if( 'siteurl' == $setting or 'home' == $setting )

	{

		$_REAL_SCRIPT_DIR = realpath(dirname($_SERVER['SCRIPT_FILENAME'])); 
		// filesystem path of this page's directory (index.php or whatever)

		$_REAL_BASE_DIR = realpath(dirname(__FILE__) . DIRECTORY_SEPARATOR . '..'); 
		// filesystem path of this file's parent directory 
		// (that wp-includes is within)

		$_MY_PATH_PART = substr( $_REAL_SCRIPT_DIR, strlen($_REAL_BASE_DIR)); 
		// just the subfolder part between  and the page

		$INSTALLATION_PATH = $_MY_PATH_PART
			? substr( dirname($_SERVER['SCRIPT_NAME']), 0, -strlen($_MY_PATH_PART) )
			: dirname($_SERVER['SCRIPT_NAME'])
			; 
		// we subtract the subfolder part from the end of , 
		// leaving us with just  :)

		$value = 'http' . ($_SERVER['HTTPS'] ? 's' : null) .
			'://' . $_SERVER['HTTP_HOST'] . $INSTALLATION_PATH
		;

		return $value;

	}
	/* end Siteurl hack */
		

	// Allow plugins to short-circuit options.
	$pre = apply_filters( 'pre_option_' . $setting, false );
	if ( false !== $pre )
		return $pre;

// ... rest of the function continues (do not copy this line!)

WordPress 2.0 - WordPress 2.3.1
The hack goes in wp-includes/functions.php
/* Options functions */

function get_settings($setting) {
  global $wpdb;

  $value = wp_cache_get($setting, 'options');



    /* Siteurl hack */
    if( 'siteurl' == $setting or 'home' == $setting ) {

    $_REAL_SCRIPT_DIR = realpath(dirname($_SERVER['SCRIPT_FILENAME'])); 
    // filesystem path of this page's directory (index.php or whatever)

    $_REAL_BASE_DIR = realpath(dirname(__FILE__) . 
      DIRECTORY_SEPARATOR . '..'); 
    // filesystem path of this file's parent directory 
    // (that wp-includes is within)

    $_MY_PATH_PART = substr( $_REAL_SCRIPT_DIR, strlen($_REAL_BASE_DIR)); 
    // just the subfolder part between  and the page

    $INSTALLATION_PATH = $_MY_PATH_PART
      ? substr( dirname($_SERVER['SCRIPT_NAME']), 0, -strlen($_MY_PATH_PART) )
      : dirname($_SERVER['SCRIPT_NAME'])
    ; 
    // we subtract the subfolder part from the end of , 
    // leaving us with just  :)

    $value = 'http' . ($_SERVER['HTTPS'] ? 's' : null) .
             '://' . $_SERVER['HTTP_HOST'] . $INSTALLATION_PATH
    ;
  }
  /* end siteurl hack */

  if ( false === $value ) {
    if ( defined('WP_INSTALLING') )
      $wpdb->hide_errors();

With this hack in place, you can now use exactly the same database and exactly the same files for both your local and remote WordPress install. Possibly the only thing you'd need to do is put different settings in wp-config.php if you want to use a remote database.

Note: this hack is untested if your server runs PHP in Safe Mode. If you have any problems, please post them on the Discussion page.





 


New To WordPress - Where to Start
ankitguptaindia — Thu, 25 Aug 2016 13:38:58 +0000
If you are new to WordPress, here is a step-by-step plan for getting started. If you need help along the way, plenty of options for assistance are listed in this article. Welcome to the exciting world of WordPress!
Step One - Read
[caption id="attachment_1531" align="alignright" width="125"] flowchart[/caption]
WordPress is a great product. It's easy-to-use, powerful, and flexible. Creating a website, and maintaining a website, is a science and art that has quickly evolved. In order to fully appreciate this it is important to be well read on the subject. One major thing to keep in mind is your investment of time. Being knowledgeable will without a doubt save you much time in the long run. With that in mind, before you invest your valuable time and energy into installing WordPress, there are some documents you need to read to help you get started.
Suggested reading includes,

Introduction to Blogging
What is WordPress?
WordPress Features
Before You Install WordPress

Step Two - Make a Plan
Based upon the information you've just read, including instructions on installing WordPress, you should have a list of the things you need and things to do. If not, make that list now. You'll want to make sure it includes the following information:

Versions of PHP and MySQL Checked and Verified
Your Website Username and Password
Text Editor Software
An FTP Client Software
Your Web Browser of Choice

The following documents will help you understand more about how WordPress works and how to make a plan for your WordPress site:

WordPress Semantics
First Steps With WordPress
WordPress Lessons

It is important to make a plan about how you want to use WordPress on your site. Here are some questions to ask yourself.

Will you install WordPress in the root directory, subdirectory, or you just want to make a test site to make sure you want to use it?
Have you made a list of your site categories to organize your content by groups?
Have you made a list of Pages you may want to add to your site, such as About, Contact, or Events?
Have you thought about what you want in the header art of the site?
Have you developed a content strategy and list of topics to help start blogging?
Have you thought about how to integrate social media into your WordPress site and workflow?

Step Three - Install WordPress
With this information and your plan, it's time to install WordPress. 

Before You Install WordPress
Installing WordPress
Editing the wp-config.php file
Frequently Asked Questions About Installing WordPress
Using FTP Clients and Software
Changing File Permissions
Updating WordPress
Common Installation Problems
Trouble: I Can't Login

Step Four - Set Up WordPress
With your installation complete, it's time to set up WordPress so it will work the way you want it to work.
To help you understand how all the various features and screens on the WordPress Administration Screens work, check out the Administration Screens guide for a detailed walk-through.
For help on creating your user profile information, of which some or all may appear on your WordPress Theme, see the Users > Your Profile pages for guidance.
To set the site name and other information, go to Administration > Settings > General.
After you've published a few posts, you can experiment with the full edit or quick edit features in the Administration > Posts > Posts screen.
Add your "About," "Contact," and other information Pages by going to Administration > Pages > Add New.
Want to change the look and feel of your WordPress site? Go to Administration > Appearance > Themes.
You'll find helpful information by reading WordPress Lessons, and these helpful documents:

Learn WordPress for WordPress.com and beginning self-hosted WordPress tutorials and guides.
Moderating Comments
Introduction to Dealing with Comment Spam

Appearance and Themes
Changing the look of your WordPress website is easy with just a few clicks.

Using WordPress Themes Introduction
The WordPress Theme Directory features thousands of WordPress Themes
WordPress Widgets can quickly add more information and content to your Theme.

If you want to create a new WordPress Theme from scratch, or do major renovations, or even design WordPress Themes for public release, you should visit WordPress Theme Developer Handbook.
If you want a custom-made WordPress Theme created especially for you by expert web-designers, it is recommended you search for qualified web designers on the Internet, or look in your local community.
Adding WordPress Plugins
There are many "add-on" scripts and programs for WordPress called Plugins that add more capabilities, choices, and options to your WordPress site. WordPress Plugins do many things, including customizing the results of your site information, adding weather reports, adding spell check capability, and presenting custom lists of posts and acronyms. For more on how to work with Plugins and where to find WordPress Plugins for your site:

Managing your WordPress Plugins
WordPress Plugins
The WordPress Plugin Directory

As like as Theme, you can create a new WordPress Plugin from scratch, or do major renovations. Please visit WordPress Plugin Developer Handbook for detail. 
Advanced Use of WordPress
Now that you are familiar with the basic features and functions of how WordPress works, it might be time for you to plunge deeper into the power of WordPress.:

Using Permalinks
WordPress Developer Resources

Need More Help
As simple and easy as it is to use WordPress, if troubles arise, if something is confusing, if things aren't working, don't despair because help is available! Even though WordPress is free and open source, there are literally hundreds of volunteers eager to help you. Here are some helpful official resources for WordPress:

Using the Support Forums
WordPress Forum
FAQ

Giving Back to WordPress
Now that you're a full fledged WordPress user, consider contributing to the WordPress Documentation, Support Forum, Development, and other volunteer efforts that keep WordPress going. WordPress is free and totally supported by volunteers, and your help is needed.






Changing The Site URL
jon_bossenger — Sun, 04 Sep 2016 22:25:52 +0000
Changing The Site URL

On the Settings -> General screen in a single site installation of WordPress, there are two fields named "WordPress Address (URL)" and "Site Address (URL)". They are important settings, since they control where WordPress is located. These settings control the display of the URL in the admin section of your page, as well as the front end, and are used throughout the WordPress code.
 

 	The "Site Address (URL)" setting is the address you want people to type in their browser to reach your WordPress blog.
 	The "WordPress Address (URL)" setting is the address where your WordPress core files reside.

 
Note: Both settings should include the http:// part and should not have a slash "/" at the end.
 
Every once in a while, somebody finds a need to manually change (or fix) these settings. Usually this happens when they change one or both and discover that their site no longer works properly. This can leave the user with no easily discoverable way to correct the problem. This article tells you how to change these settings directly.
 
Additional information is presented here for the case where you are moving WordPress from one site to another, as this will also require changing the site URL. You should not attempt to use this additional information if you're only attempting to correct a "broken" site.
 
Alert! These directions are for single installs of WordPress only. If you are using WordPress MultiSite, you will need to manually edit your database.
 

Changing the Site URL
There are four easy methods to change the Site URL manually. Any of these methods will work and perform much the same function.
Edit wp-config.php
It is possible to set the site URL manually in the wp-config.php file.
 
Add these two lines to your wp-config.php, where "example.com" is the correct location of your site.
 

[php]define( 'WP_HOME', 'http://example.com' );
define( 'WP_SITEURL', 'http://example.com' );[/php]
 
This is not necessarily the best fix, it's just hard-coding the values into the site itself. You won't be able to edit them on the General settings page anymore when using this method.
 
Edit functions.php
If you have access to the site via FTP, then this method will help you quickly get a site back up and running, if you changed those values incorrectly.
 
FTP to the site, and get a copy of the active theme's functions.php file. You're going to edit it in a simple text editor and upload it back to the site.

Add these two lines to the file, immediately after the initial "
[php]update_option( 'siteurl', 'http://example.com' );
update_option( 'home', 'http://example.com' );[/php]

Use your own URL instead of example.com, obviously.

Upload the file back to your site, in the same location. FileZilla offers a handy "edit file" function to do all of the above rapidly; if you can use that, do so.

Load the login or admin page a couple of times. The site should come back up.
 

Important! Do not leave this code in the functions.php file. Remove them after the site is up and running again.
 

Note: If your theme doesn't have a functions.php file create a new one with a text editor. Add the  

[php][/php]
 
Upload this file to your theme directory. Remove the lines or the remove the file after the site is up and running again.

 

Here are some additional details that step you through transfering a LAN-based WordPress site into an externally accessible site as well enabling editing the wordpress site from inside the LAN.
 

Two important keys are router/firewall modifications and the "wait 10+ minutes" after making the changes at the end.
 


using ssh to log into your server (nano is a server preinstalled text editor)
$ nano /var/www/books/wp-content/themes/twentyeleven/functions.php
add lines just after 

[php]update_option( 'siteurl', 'http://your.site.url:port/yourblog ');
update_option( 'home', 'http://your.site.url:port/yourblog ');[/php]

refresh your web browser using your external site URL: http://your.site.url:port/yourblog
$ nano /var/www/books/wp-content/themes/twentyeleven/functions.php
remove those lines you just added (or comment them out)
access your router, these steps are for pfSense, other routers should have similar settings to look for/watch out for
add to firewall/nat table a line like this
wan/tcp/port/LAN.server.IP/80

add to firewall/rules table a line like this
tcp/*/port/LAN.server.IP/port/*
uncheck the box at System/advanced/network address translation/Disable NAT Reflection
"Disables the automatic creation of NAT redirect rules for access to your public IP addresses from within your internal networks. Note: Reflection only works on port forward type items and does not work for large ranges > 500 ports."
 

Then go do something for ten minutes and when you get back see if the external url http://your.site.url:port/yourblog from a LAN browser brings the page up correctly.
 

Relocate method
WordPress supports an automatic relocation method intended to be a quick assist to getting a site working when relocating a site from one server to another.
Code function
When RELOCATE has been defined as true in wp-config.php (see next chapter), the following code in wp-login.php will take action: 

[php]if ( defined( 'RELOCATE' ) AND RELOCATE ) {
  // Move flag is set
  if ( isset( $_SERVER['PATH_INFO'] ) AND ($_SERVER['PATH_INFO'] != $_SERVER['PHP_SELF']) ) $_SERVER['PHP_SELF'] = str_replace( $_SERVER['PATH_INFO'], , $_SERVER['PHP_SELF'] );
  $url = dirname( set_url_scheme( 'http://'. $_SERVER['HTTP_HOST'] . $_SERVER['PHP_SELF'] ) );
  if ( $url != get_option( 'siteurl' ) ) update_option( 'siteurl', $url );
}[/php]
 

Steps

	Edit the wp-config.php file.


	After the "define" statements (just before the comment line that says "That's all, stop editing!"), insert a new line, and type: define('RELOCATE',true);

	Save your wp-config.php file.


	Open a web browser and manually point it to wp-login.php on the new server. For example, if your new site is at http://www.yourdomainname.com, then type http://www.yourdomainname.com/wp-login.php into your browser's address bar.


	Login as per normal.


	Look in your web browser's address bar to verify that you have, indeed, logged in to the correct server. If this is the case, then in the Admin back-end, navigate to Settings > General and verify that both the address settings are correct. Remember to Save Changes.


	Once this has been fixed, edit wp-config.php and either completely remove the line that you added (delete the whole line), comment it out (with //) or change the true value to false if you think it's likely you will be relocating again.





Note: When the RELOCATE flag is set to true, the Site URL will be automatically updated to whatever path you are using to access the login screen. This will get the admin section up and running on the new URL, but it will not correct any other part of the setup. You'll still need to alter those manually.
 

Important! Leaving the RELOCATE constant in your wp-config.php file is insecure, as it allows an attacker to change your site URL to anything they want in some configurations. Always remove the RELOCATE line from wp-config.php after you're done.
 
Changing the URL directly in the database
If you know how to access phpMyAdmin on your host, then you can edit these values directly to get your site up and running again.

 	Backup your database and save the copy off-site.
 	Login to phpMyAdmin.
 	Click the link to your Databases.
 	A list of your databases will appear. Choose the one that is your WordPress database.
 	All the tables in your database will appear on the screen.
 	From the list, look for wp_options. Note: The table prefix of wp_ may be different if you changed it when installing.
 	Click on the small icon indicated as Browse.
 	A screen will open with a list of the fields within the wp_options table.
 	Under the field option_name, scroll down and look for siteurl.
 	Click the Edit Field icon which usually is found at the far left at the beginning of the row.
 	The Edit Field window will appear.
 	In the input box for option_value, carefully change the URL information to the new address.
 	Verify this is correct and click Go to save the information.
 	You should be returned to your wp_options table.
 	Look for the home field in the table and click Edit Field. Note There are several pages of tables inside wp_options. Look for the> symbol to page through them.
 	In the input box for option_value, carefully change the URL information to the new address.
 	Verify this is correct and click Go to save the information.

 
Moving Sites
When moving sites from one location to another, it is sometimes necessary to manually modify data in the database to make the new site URL information to be recognized properly. Many tools exist to assist with this, and those should generally be used instead of manual modifications.

This is presented here as information only. This data may not be complete or accurate.

You should read the Moving WordPress article first, if attempting to move WordPress from one system to another.
 
Altering Table Prefixes
Like many WordPress administrators, you may be running several WordPress installations off of one database using various wp-config.php hacks. Many of these hacks involve dynamically setting table prefixes, and if you do end up altering your table prefix, you must update several entries within the prefix_usermeta table as well.
 
As in the above section, remember that SQL changes are permanent and so you should back up your database first:
 
If you are changing table prefixes for a site, then remember to alter the table prefix in the usermeta tables as well. This will allow the new site to properly recognize user permissions from the old site.
 
[sql]UPDATE `newprefix_usermeta` SET `meta_key` = REPLACE( `meta_key` , 'oldprefix_', 'newprefix_' );[/sql]
 

Changing Template Files
In your WordPress Theme, open each template file and search for any manually entered references to your old domain name and replace it with the new one. Look for specific hand coded links you may have entered on the various template files such as the sidebar.php and footer.php.
 
WordPress uses a template tag called bloginfo() to automatically generate your site address from information entered in yourAdministration > Settings > General panel. The tag in your template files will not have to be modified.
 
Changing the Config file
You will need to update your WordPress configuration file if your database has moved or changed in certain ways.

 	You will only need to modify the config file if:

 	your database has moved to another server and is not running on your localhost
 	you have renamed your database
 	you have changed the database user name


 	Make a backup copy of your wp-config.php file.
 	Open the wp-config.php file in a text editor.
 	Review its contents. In particular, you are looking for the database host entry.
 	Save the file.

 
At this point, your WordPress blog should be working.
 
Verify the Profile

 	In your Administration Panels go to Settings > General . Here you will verify that the changes you made in Changing the URLabove, are correct.
 	Verify that the reference in your WordPress Address (URL) contains the new address.
 	Verify that the reference in your Site Address (URL) contains the new address.
 	If you have made changes, click Save Changes.

 
Changing the .htaccess file
After changing the information in your Administration > Settings > General panel, you will need to update your .htaccess file if you are using Permalinks or any rewrites or redirects.
 

 	Make a backup copy of your .htaccess file. This is not a recommendation but a requirement.
 	Open the .htaccess file in a text editor.
 	Review its contents, looking for any custom rewrites or redirects you entered. Copy these to another text file for safe keeping.
 	Close the file.
 	Follow the instructions on the Permalinks SubPanel for updating your Permalinks to the .htaccess file.
 	Open the new .htaccess file and check to see if your custom rewrites and redirects are still there. If not, copy them from the saved file and paste them into the new .htaccess file.
 	Make any changes necessary in those custom rewrites and redirects to reflect the new site address.
 	Save the file.
 	Test those redirects to ensure they are working.

 
If you make a mistake, you can Restoring Your Database From Backup from your backup and try this again. So make sure it is right the first time.

Additional items of note
There are other things you may wish to change in order to correct URLs when moving sites.

 	Images link: image links are stored in "post_content" in the wp_posts table. You can use the similar code above to update image links.
 	wp_options: Besides the "siteurl" and "home" items mentioned above, there are other option_value which also need revision, such as "upload path", and some plugin items (depends on what you've installed, such as widgets, stats, DMSGuestbook, sitemap, etc.)
 	To fix widgets that contain outdated URL's, you may edit them in Dashboard / Appearance / Widgets.
 	Do a FULL database search for any items left. MAKE SURE you know what you are changing. and go through each item for possible improper replacement.
 	If you a running a network / have multiple sites, you will need to replace instances of the URL in the database. They are stored in many tables, including each one of the sites (blogs). Be careful in what you replace and be sure you know the meaning of the field before changing it. See the Important GUID note below for an example of what not to change.
 	Note, if you find your old url in the database options table under 'dashboard_incoming_links', you can ignore or delete that option. It's unused since WP 3.8.

 
How To: Move Your WordPress Blog to a New Domain - Using the Export/Import feature to move a blog to a new domain.
 

Important GUID Note
When doing the above and changing the URLs directly in the database, you will come across instances of the URL being located in the "guid" column in the wp_posts tables. It is critical that you do NOT change the contents of this field.
 
The term "GUID" stands for "Globally Unique Identifier". It is a field that is intended to hold an identifier for the post which a) is unique across the whole of space and time and b) never, ever changes. The GUID field is primarily used to create the WordPress feeds.
 
When a feed-reader is reading feeds, it uses the contents of the GUID field to know whether or not it has displayed a particular item before. It does this in one of various ways, but the most common method is simply to store a list of GUID's that it has already displayed and "marked as read" or similar.
 
Thus, changing the GUID will mean that many feedreaders will suddenly display your content in the user's reader again as if it was new content, possibly annoying your users.
 
In order for the GUID field to be "globally" unique, it is an accepted convention that the URL or some representation of the URL is used. Thus, if you own example.com, then you're the only one using example.com and thus it's unique to you and your site. This is why WordPress uses the permalink, or some form thereof, for the GUID.
 
However, the second part of that is that the GUID must never change. Even if you shift domains around, the post is still the same post, even in a new location. Feed readers being shifted to your new feeds when you change URLs should still know that they've read some of your posts before, and thus the GUID must remain unchanged.
 
Never, ever, change the contents of the GUID column, under any circumstances.
 
NB: If the default uploads folder needs to be changed to a different location, then any media URLs will need to be changed in thepost_content column of the posts table. For example, if the default uploads folder is changing from wp-content/uploads to images:
 
[sql]UPDATE wp_posts SET post_content = REPLACE(post_content,'www.domain.com/wp-content/uploads','www.domain.com/images');[/sql]
 
Multi-site notes
See Moving WordPress Multisite
 
wp-cli
wp-cli is a super useful shell tool.
[php]wp search-replace 'example.dev' 'example.com' --skip-columns=guid[/php]
 
Or, if you only want to change the option, you can do:
[php]wp option update home 'http://example.com'
wp option update siteurl 'http://example.com'[/php]


Two Step Authentication
atachibana — Mon, 02 Jan 2017 08:16:26 +0000
Also known as Two-Factor Authentication.
In April 2013, WordPress.com announced that they would let users log in with two-step authentication for better security. Two-step authentication is showing up all over the Internet as more sites look for better ways to secure logins, which are the weakest part of anything a user does online.
What is Two-Step Authentication
Passwords are the de-facto standard for logging in on the web, but they’re relatively easy to break. Even if you make good passwords and change them regularly, they need to be stored wherever you’re logging in, and a server breach can leak them. There are three ways to identify a person, things they are, things they have, and things they know.  
Logging in with a password is single-step authentication. It relies only on something you know. Two-step authentication, by definition, is a system where you use two of the three possible factors to prove your identity, instead of just one. In practice, however, current two-step implementations still rely on a password you know, but use your Phone or another device to authenticate with something you have.
Three Possible Factors
There are three possible ways to identify users.
Something You Are
There are a lot of properties that are unique to each user and can be used to identify them. The most popular is fingerprints, but retinas, voice, DNA, or anything else specific to an individual will work. This is called biometric information because these pieces of information all belong to a person’s biology.  
Biometric factors are interesting because they are not easily forged and the user can never lose or forget them. However, biometric authentication is tricky because a lost fingerprint can never be replaced. If hackers were to gain access to a database of fingerprints, there is no way that users could reset them or get a new set.  
In 2013, Apple released TouchID which lets users unlock their iPhones using their fingerprints. This technology is interesting because the fingerprints are stored locally on the phone, not in the cloud where they would be easier for hackers to steal. There are still trade-offs with this kind of approach, but it is the most widespread consumer use of biometric authentication to date.
Something You Have
Also known as the possession factor, users can be identified by the devices which they carry. Traditionally, a company that wanted to enable two-step authentication would distribute secure keychain fobs to users. The keychain fobs would display a new number every 30 seconds, and that number would be needed to be typed along with the password every time a user logged in.  
Modern two-step authentication more frequently relies on a user’s smartphone than on a new piece of hardware. One common model of this uses SMS in order to provide an easy second factor. When the user enters their password, they are sent a text message with a unique code. By entering that code, after the password, they supposedly prove that they also have their phone. Unfortunately, SMS is not a secure communication channel, so smartphone apps and plugins have been developed to create that secure channel.
Something You Know
The most familiar form of authentication is the knowledge factor, or password. As old as Open Sesame, passwords have long been a standard for anonymous authentication. In order for a knowledge factor to work, both parties need to know the password, but other parties must not be able to find or guess it.  
The first challenge is in exchanging the password with the trusted party safely. On the web, when you register for a new site, your password needs to be sent to that site’s servers and might be intercepted in the process (which is why you should always check for SSL when registering or logging in — Administration Over SSL).  
Once the password has been received, it must be kept secret. The user shouldn’t write it down or use it anywhere else, and the site needs to carefully guard its database to ensure that hackers can’t access the passwords.  
Finally, the password needs to be verified. When a user visits the site, they need to be able to provide the password and have it verified against the stored copy. This exchange can also be intercepted (and so should always be done over SSL — Administration Over SSL) and exposes the user to another risk.
Benefits
There are a lot of different places to increase the security of a site, but the WordPress Security Team has said that “The weakest link in the security of anything you do online is your password,” so it makes sense to put energy into strengthening that aspect of your site.  
Two-step is available to all WordPress.com users and is available through free plugins for everyone else.
Drawbacks
As the name implies, two-step authentication is adding a step to a process that can already be long and painful. While most very high-security logins are protected by two-step authentication today, most consumer applications barely offer it as an option if they offer it at all. This is because users are less likely to sign up for and log in to a service if it is more difficult.  
Two-step authentication can also prevent legitimate logins. If a user forgets their phone at home and has two-step authentication enabled, then they won’t be able to access their account. This is one of the main reasons why smartphones have been useful for two-step authentication — users are more likely to be carrying their phones than almost anything else.
Plugins for Two-Step Authentication
You can search for two-step authentication plugins available in the WordPress.org plugin repository. Here are some of the most popular ones to get you started (in alphabetical order):

Duo
Google Authenticator
Rublon
WordFence

Related

Brute Force Attacks
HostGator: Password Protecting wp-login
WordPress Security Checklist



Glossary
normalize — Tue, 30 May 2017 08:55:09 +0000
Glossary
This document is designed to offer definitions of various terms, exclusive to WordPress, that users may not be familiar with.

If you are a contributor please don't add definitions for generic terms (API, PHP, JavaScript, etc...).
Absolute Path
(also known as a full path)

The complete location of a file or directory within a computer filesystem. An absolute path starts at the root directory (or drive letter) and continues up the directory hierarchy until the specific file or directory is reached. This contrasts with a relative path, which does not start at the root directory.

The syntax of absolute paths differs by operating system. On Microsoft Windows, they begin with a drive letter and use a backslash to separate directory names (though forward slashes can be used as well). Absolute paths on macOS and Linux lack drive letters and use a forward slash as the directory separator.

Examples:

 	Windows: C:\Users\Matt\www\blog\images\icecream.jpg
 	macOS: /Users/Matt/www/blog/images/icecream.jpg
 	Linux: /home/Matt/www/blog/images/icecream.jpg

To find the absolute filesystem path of the directory containing a web page, copy the code below into a new text file, save the file as path.php (thus making a simple PHP web page), and move that file to your web server. Then direct your web browser to the URL address of that file (e.g. http://www.example.com/path.php).

[code language="php"]

[/code]

See also: Path (computing) at Wikipedia

Back to the Top
Absolute URI
(also known as a full URI)

A URI that contains the complete location of a resource (as opposed to a relative URI).

Examples:

 	http://www.example.com/blog/images/icecream.jpg
 	ftp://ftp.example.com/users/h/harriet/www/

Back to the Top
Action
In WordPress; an Action is a PHP function that is executed at specific points throughout the WordPress Core.

Developers can create a custom Action using the Action API to add or remove code from an existing Action by specifying any existing Hook. This process is called "hooking".

For example: A developer may want to add code to the footer of a Theme. This could be accomplished by writing new function, then Hooking it to the wp_footer Action.

Custom Actions differ from custom Filters because custom Actions allow you to add or remove code from existing Actions. Whereas custom Filters allow you to replace specific data (such as a variable) found within an existing Action.

 	See also: Filter, Hook, Terminology Confusion
 	Related articles: Actions, Action Reference, add_action()
 	Forum posts: Filters vs. Actions Discussion and Explanation

Admin Bar
An area of the screen just above your site that gives you quick access to features such as adding a new post or editing your profile. It is only visible if you are logged in.

The admin bar concept was added to WordPress in Toolbar_in_WordPress_Version_3.3.__To_turn_it_on_(or_off),_open_the_Dashboard_and_navigate_to_[[Administration_Panels">Administration > Users > Your Profile.

 	Related articles: Toolbar
 	See also: Your Profile Screen

Back to the Top
AJAX
AJAX is a technique that web pages use to have the server perform certain processing without reloading the web page. For example, when you approve a comment in a WordPress blog, WordPress uses AJAX to change the comment's status, and you see the change without having to reload the Comments screen.

 	Related article: AJAX
 	External link: AJAX (Wikipedia)

Back to the Top
Apache
Apache is short for Apache HTTP Server Project, a robust, commercial-grade, featureful, and freely-available open source HTTP Web server software produced by the Apache Software Foundation. It is the most commonly used web server on the internet, and is available on many platforms, including Windows, Unix/Linux, and Mac OS X. Apache serves as a great foundation for publishing WordPress-powered sites.

Back to the Top
API
Please refer to Wikipedia for a definition.
Array
An array is one of the basic data structures used in computer programming. An array contains a list (or vector) of items such as numeric or string values. Arrays allow programmers to randomly access data. Data can be stored in either one-dimensional or multi-dimensional arrays.

A one-dimension array seven (7) elements would be:

+---+---+---+---+---+---+---+
|105|200| 54| 53|102| 13|405|
+---+---+---+---+---+---+---+


The Template Tag wp_list_categories() uses a one-dimensional array for the 'exclude' parameter.

An example of two-dimensional array, 7 by 3 elements in size, would be:

+---+---+---+---+---+---+---+
|105|200| 54| 53|102| 13|405|
+---+---+---+---+---+---+---+
| 15|210| 14|513|  2|313|512|
+---+---+---+---+---+---+---+
|501|500|499|488|552| 75|952|
+---+---+---+---+---+---+---+



 	External links: Array Programming at Wikipedia, Array at freedictionary.com

Back to the Top
ASCII
ASCII (pronounced as "ask ee") is a standard but limited character set containing only English letters, numbers, a few common symbols, and common English punctuation marks. WordPress content is not restricted to ASCII, but can include any Unicode characters.

ASCII is short for American Standard Code for Information Interchange.

 	External links: ASCII (Wikipedia, with character set table)

Back to the Top
Atom
A format for syndicating content on news-like sites, viewable by Atom-aware programs called news readers or aggregators.

 	See also: News reader, RSS, RDF
 	External links: Atom (standard) at Wikipedia

Back to the Top
Autosave
When you are writing or editing your posts and pages, the changes you make are automatically saved every 2 minutes. In the lower right corner of the editor, you’ll see a notification of when the entry was last saved to the database.

Autosaves are automatically enabled for all posts and pages. There is only one autosave for each post/page. Each new autosave overwrites the previous autosave in the database.

 	Related articles: Revision Management
 	External links: WordPress.com Support - Autosave

Back to the Top
Avatar
An avatar is a graphic image or picture that represents a user.

 	See also: Gravatar
 	Related articles: Using Gravatars
 	External links: Avatar (computing) at Wikipedia

Back to the Top
Binaries
Binaries refer to compiled computer programs, or executables. Many open source projects, which can be re-compiled from source code, offer pre-compiled binaries for the most popular platforms and operating systems.

Back to the Top
Blog
A blog, or weblog, is an online journal, diary, or serial published by a person or group of people.

Blogs are typically used by individuals or peer groups, but are occasionally used by companies or organizations as well. In the corporate arena, the only adopters of the blog format so far have tended to be design firms, web media companies, and other "bleeding edge" tech firms.

Blogs often contain public as well as private content. Depending on the functionality of the CMS software that is used, some authors may restrict access — through the use of accounts or passwords — to content that is too personal to be published publicly.

Back to the Top
Blogging
Blogging is the act of writing in one's blog. To blog something is to write about something in one's blog. This sometimes involves linking to something the author finds interesting on the internet.

 	See also: Blogosphere, Blogroll

Back to the Top
Blogosphere
The blogosphere is the subset of internet web sites which are, or relate to, blogs.

 	See also: Blog, Blogroll

Back to the Top
Blogroll
A blogroll is a list of links to various blogs or news sites. Often a blogroll is "rolled" by a service which tracks updates (using feeds) to each site in the list, and provides the list in a form which aggregates update information. The default blogroll (aka links) included in WordPress was removed in version 3.5.

 	See also: Blog, Blogosphere, Feed, News reader
 	External links: News aggregator at Wikipedia

Back to the Top
Bookmarklet
A bookmarklet (or favelet) is a "faux" bookmark containing scripting code, usually written in JavaScript, that allows the user to perform a function.

Examples:

 	The WordPress Press This bookmarklet allows a user to quickly blog whichever website he/she is currently viewing.
 	The delicious.com bookmarklets allow a user to quickly post a link to his/her delicious.com bookmarks list.
 	Tantek's favelets

Back to the Top
Boolean
A variable or expression which evaluates to either true or false.

 	External links: PHP Boolean data type

Back to the Top
Category
Each post in WordPress can be filed under one or more categories. Thoughtful categorization allows posts to be grouped with others of similar content and aids in the navigation of a site.

Please note that a post category should not be confused with a link category, which is used to classify and manage links.

Back to the Top
Capabilities
A capability is permission to perform one or more types of task. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the "edit_posts" capability), but not permission to edit other users' posts (the "edit_others_posts" capability). WordPress comes with six roles and over fifty capabilities in its role-based access system. Plugins can modify the system.

 	Related article: Roles and Capabilities
 	External link: Role-based access control (Wikipedia)

CGI
CGI (Common Gateway Interface) is a specification for server-side communication scripts designed to transfer information between a web server and a web-client (browser). Typically, HTML pages that collect data via forms use CGI programming to process the form data once the client submits it.

Back to the Top
Character Entity
A character entity is a method used to display special characters normally reserved for use in HTML. For example, the less than (<) and greater than (>) are used as part the HTML tag structure, so both symbols are reserved for that use. But, if you need to display those symbols on your site, you can use character entities. For example:
use <  for the less than (<) symbol
use >  for the greater than (>) symbol


 	Related articles: Fun Character Entities

Back to the Top


Character Set
A character set is a collection of symbols (letters, numbers, punctuation, and special characters), when used together, represent meaningful words in a language. Computers use an encoding scheme so members of a character set are stored with a numeric value (e.g. 0=A, 1=B, 2=C, 3=D). In addition, a collation determines the order (i.e alphabetic) to use when sorting the character set.

By default, WordPress uses the Unicode UTF-8 (utf8) character set for the WordPress MySQL database tables created during the installation process. Beginning with Version 2.2, the database character set (and collation) is defined in the wp-config.php file.

 	See also: Collation
 	Related articles: Editing wp-config.php, Converting Database Character Sets
 	External links: Character set at Wikipedia, Unicode at Wikipedia, UTF-8 at Wikipedia, Character sets and collation at MySQL

Back to the Top
chmod
chmod is a Unix/Linux shell command used to change permissions on files. Its name is a contraction of "change mode."

 	Related articles: Changing File Permissions, UNIX Shell Skills, htaccess for subdirectories

Back to the Top
Class
Classes are groupings of CSS styles which can be applied to any HTML element.

For classes in PHP, see the Class (Computing) article at Wikipedia and PHP Manual: Classes and Objects.

 	Related articles: CSS, Blog Design and Layout

Back to the Top
Codex
The Codex is the series of articles that show users how to use WordPress. WordPress users contribute documentation to the codex voluntarily.

 	External links: Codex

Collation
Collation refers to the order used to sort the letters, numbers, and symbols of a given character set. For example, because WordPress, by default, uses the UTF-8 (utf8) character set, and when the WordPress MySQL database tables are created during the installation process, MySQL assigns utf8_general_ci collation to those tables. Beginning with Version 2.2, the collation (and character set) used by WordPress is defined in the wp-config.php file.

 	See also: Character set
 	Related articles: Editing wp-config.php, Converting Database Character Sets
 	External links: Collation at Wikipedia, Character set at Wikipedia, UTF-8 at Wikipedia, Character sets and collation at MySQL

Back to the Top
Comments
Comments are a feature of blogs which allow readers to respond to posts. Typically readers simply provide their own thoughts regarding the content of the post, but users may also provide links to other resources, generate discussion, or simply compliment the author for a well-written post.

You can control and regulate comments by filters for language and content. Comments can be queued for approval before they are visible on the web site. This is useful in dealing with comment spam.

 	See also: Blog
 	Related articles: Comment-related plugins, Dealing with comment spam, Settings Discussion SubPanel
 	External links: Hyperlink at Wikipedia

Back to the Top
Content
Content consists of text, images, or other information shared in posts. This is separate from the structural design of a web site, which provides a framework into which the content is inserted, and the presentation of a site, which involves graphic design. A Content Management System changes and updates content, rather than the structural or graphic design of a web site.

Back to the Top
Content Management System
A Content Management System, or CMS, is software for facilitating the maintenance of content, but not design, on a web site. A blogging tool is an example of a Content Management System.

 	See also: Blog

Back to the Top
cPanel
cPanel is a popular web-based administration tool that many hosting providers provide to allow users to configure their own accounts using an easy-to-use interface.

 	Related articles: Adding New Themes by using cPanel
 	External links: cPanel website

Back to the Top
CSS
CSS, or Cascading Style Sheets, is a W3C open standards programming language for specifying how a web page is presented. It allows web site designers to create formatting and layout for a web site independently of its content.

 	Related articles: CSS, Blog Design and Layout
 	External links: CSS at W3C, Open standards at Wikipedia, W3C.org

Back to the Top
CVS
CVS stands for Concurrent Versions System and is the software that used to be used coordinate WordPress development. As of February 2005, this function is carried out by Subversion (SVN).

For more information on Subversion, see Using Subversion.

Back to the Top
Dashboard
In WordPress a Dashboard is the main administration screen for a site (a weblog), or for a network of sites. It summarizes information about the site or network, and also external information, in one or more widgets that the Dashboard user can enable, disable, and move around.

 	Related articles: Dashboard Screen

Back to the Top
Database
A database in computing terms is software used to manage information in an organized fashion. WordPress uses the MySQL or MariaDB relational databases management system for storing and retrieving the content of your blog, such as posts, comments, and so on.

 	Related articles: Database Description, Backing Up Your Database

Back to the Top
Database version
In WordPress, the database version is a number that increases every time changes are made to the way WordPress organizes the data in its database. It is not the same as the version of the database software, MySQL or MariaDB.

For example, the database version in WordPress 3.3 was 19470, and the database version in WordPress 3.3.1 did not change. This tells anyone planning to use backed-up data from the older version that they do not need to check for changes in the structure of the data.

WordPress stores its database version in the database, as the option named "db_version" in every WordPress site's "wp_options" table. (The table name prefix "wp_" may be missing or different in some cases.)

 	Related articles: How do you force a database upgrade?

Back to the Top
Default theme
Every installation of WordPress has a default theme. The default theme is sometimes called the fallback theme, because if the active theme is for some reason lost or deleted, WordPress will fallback to using the default theme.

The WordPress default themes have been:

 	Up to Version 2.9.2 the default theme was the WordPress Default theme (sometimes called Kubrick) and was located in the wp-content/themes/default folder.
 	Version 3.0 - the Twenty Ten theme
 	Version 3.2 - the Twenty Eleven theme
 	Version 3.5 - the Twenty Twelve theme
 	Version 3.6 - the Twenty Thirteen theme
 	Version 3.8 - the Twenty Fourteen theme
 	Version 4.1 - the Twenty Fifteen theme
 	Version 4.4 - the Twenty Sixteen theme


 	See also: Twenty Ten theme, Twenty Eleven theme, Twenty Twelve theme, Twenty Thirteen theme, Twenty Fourteen theme, Twenty Fifteen theme, Twenty Sixteen theme
 	Related articles: Child Themes

Back to the Top
Deprecated
Deprecated functions or template tags are no longer supported, and will soon be obsolete.

 	Related articles: "Deprecated Functions" Category

Back to the Top
Developer
A developer, or dev, is a computer programmer who is active in creating, modifying, and updating a software product.

 	Related articles: Plugin API

DIV
A DIV element in HTML marks a section of text. DIVs are used extensively in WordPress to apply CSS stylings to particular blog elements.

 	Related articles: CSS, Blog Design and Layout

Back to the Top
DNS
DNS, the domain name system, is the system that maps domain names to IP addresses. When you use a web browser to visit a website, your browser first extracts the site's domain name from the URL. Then it uses the DNS to find the IP address for that domain name. Then it connects to that IP address.

 	External link: Domain Name System (Wikipedia)

Back to the Top
DOM
DOM (Document Object Model) is a standard, platform-independent interface that allows programmers to dynamically access HTML and XML to control the content and structure of documents. DOM connects programming scripts to web pages.

 	External links: DOM at Wikipedia, DOM at W3C.org

Back to the Top
Domain name
A domain name is a name used for identification purposes on the Internet. In WordPress a domain name usually identifies a server where WordPress is installed. To make this work, the Internet's domain name system (DNS) maps the domain name to a server's IP address. For example, the domain name example.com maps to the IP address 192.0.43.10. Many domain names can map to the same IP address, allowing a single server to run many websites. For example, the the domain names www.example.com and example.net also map to the IP address 192.0.43.10.

 	External link: Domain name (Wikipedia)

Back to the Top
Draft
The draft post status is for WordPress posts which are saved, but as yet unpublished. A draft post can only be edited through the Administration Panel, users of equal or greater User Level than the post's author.

Back to the Top
Excerpt
An excerpt is a condensed description of your blog post and refers to the summary entered in the Excerpt field of the Administration > Posts > Add New SubPanel. The excerpt is used to describe your post in RSS feeds and is typically used in displaying search results. The excerpt is sometimes used in displaying the Archives and Category views of your posts. Use the Template Tag the_excerpt() to display the contents of this field. Note that if you do not enter information into the Excerpt field when writing a post, and you use the_excerpt() in your theme template files, WordPress will automatically display the first 55 words of the post's content.

An excerpt should not be confused with the teaser, which refers to words before the %%%%%% in a post's content. When typing a long post you can insert the %%%%%% Quicktag after a few sentences to act as a cut-off point. When the post is displayed, the teaser, followed by a hyperlink (such as Read the rest of this entry...), is displayed. Your visitor can then click on that link to see the full version of your post. The Template Tag, the_content() should be used to display the teaser.

 	Related articles: Customizing the Read More, Excerpt

Back to the Top
Feed
A feed is a function of special software that allows "Feedreaders" to access a site automatically looking for new content and then posting the information about new content and updates to another site. This provides a way for users to keep up with the latest and hottest information posted on different blogging sites. Some Feeds include RSS (alternately defined as "Rich Site Summary" or "Really Simple Syndication"), Atom or RDF files. Dave Shea, author of the web design weblog Mezzoblue has written a comprehensive summary of feeds. Feeds generally are based on XML technology.

Back to the Top
Feed Reader
The role of Feedreader is to gather and display the webfeed from various website to one place.
Filter
In WordPress, a Filter is a function that is associated with an existing Action by specifying any existing Hook.

Developers can create custom Filters using the Filter API to replace code from an existing Action. This process is called "hooking".

Custom Filters differ from custom Actions because custom Actions allow you to add or remove code from existing Actions. Whereas custom Filters allow you to replace specific data (such as a variable) found within an existing Action.

 	See also: Action, Hook, Terminology Confusion
 	Related articles: Filters, Filter Reference, add_filter()

Back to the Top
Footer area
A footer area is a horizontal area provided by a theme for displaying information other than the main content of the web page. Themes may provide one or more footer areas below the content. Footer areas usually contain widgets that an administrator of the site can customize.

In a theme, footer areas are generated by a template file, typically named sidebar-footer.php.

 	See also: Sidebar
 	Related articles: Templates, Customizing Your Sidebar, Stepping Into Templates, Template Hierarchy

Back to the Top
Front End
The front end is what your visitors see and interact with when they come to your website, www.YourSite.com.

Back to the Top
FTP
FTP, or File Transfer Protocol, is a client-server protocol for transferring files. It is one way to download files, and the most common way to upload files to a server.

An FTP client is a program which can download files from, or upload files to, an FTP server.

You may need to use an FTP client to upload your WordPress files to your web server, particularly if you use a hosting provider.

 	Related articles: FTP Clients, Uploading WordPress to a remote host, Using FileZilla

Back to the Top
Gallery
As defined by Andy Skelton, Gallery, introduced with WordPress 2.5, is specifically an exposition of images attached to a post. In that same vein, an upload is "attached to a post" when you upload it while editing a post.

In the uploader there is a "Gallery" tab that shows all the uploads attached to the post you are editing. When you have more than one attachment in a post, you should see at the bottom of the Gallery tab a button marked "Insert gallery". That button inserts a shortcode "

[gallery]

" into the post. WordPress replaces that shortcode with an exposition of all images attached to that post. Non-image file types are excluded from the gallery.

Note: If you don't see the "Insert gallery" button, it may be because you have not attached two images to the post.

The pretty URLs for attachments are made only after you have published the post and should be composed as the post permalink plus the attachment slug.

 	Related articles: Gallery Shortcode, Shortcode API

Back to the Top
gettext
The gettext system is a set of tools and standards for language translation, used by WordPress to provide versions in many languages. In WordPress a text string for translation may have a domain and a context. For example, a plugin might specify its own domain for translations, and a context might help translators to provide different translations of the same English word or phrase in different parts of the user interface.

 	Related articles: WordPress in Your Language, Translating WordPress, I18n for WordPress Developers
 	External links: gettext (Wikipedia), GNU gettext

Back to the Top
GMT
GMT ("Greenwich Mean Time", the time at the Royal Observatory in Greenwich, England) is the old name of the time zone from which all other time zones were measured. It has been replaced by UTC ("Universal Time, Coordinated"), but for most practical purposes UTC and GMT are the same, so the term GMT is still commonly used.

 	External links: Greenwich Mean Time, Time zone, UTC (Wikipedia)

Back to the Top
Gravatar
A gravatar is a globally recognized avatar (a graphic image or picture that represents a user). Typically a user's gravatar is associated with their email address, and using a service such as Gravatar.com. The site owner to can configure their site so that a user's gravatar is displayed along with their comments.

 	See also: Avatar
 	Related articles: How to Use Gravatars in WordPress, Using Gravatars
 	External links: Gravatar at Wikipedia

Back to the Top
GUI
GUI stands for Graphical User Interface, pronounced as "gooey". It is an interface that allows users to point the mouse or cursor to graphical icons.
Hack
A hack is a bit of code written to customize or extend the functionality of a software product. Older versions of WordPress used a hack-based extension system, but versions 1.2 and above of WordPress use a Plugin API with hooks for extensions.

 	See also: Hacking, Plugin
 	Related articles: Changelog, Plugin API
 	External links: Open source at Wikipedia

Back to the Top
Hacking
Hacking is the process of writing code for, or contributing code to, a piece of software.

There is some controversy surrounding the meaning of this term. It began as a benign term meaning "to exercise proficiency" or "to alter or improve," but the popular media have since construed it to mean "to break into a computer system, usually with malicious intent." Many in the computer industry have recently begun trying to 'take back' the word from its popular mutation, and many have adopted the term cracking to replace the malicious interpretation. Because of the desire to reclaim the word, you will often find the term used in conjunction with open source projects, intended in its benign form. For more information about the history of the term, please see Wikipedia's article on Hacker.

 	See also: Hack
 	Related articles: Plugins

Back to the Top
Header Image
A Header Image is a wide picture that appears at the top of a WordPress website.

Back to the Top
Hook
Hooks are specified, by the developer, in Actions and Filters. Here is a (hopefully) complete list of all existing Hooks within WordPress.

Because Hooks are required by Actions and Filter you may hear the phrase "Action Hooks" and "Filter Hooks" used from time to time.

In technical and strict terms: a Hook is an event, i.e. event as understood by Observer pattern, invoked by the do_action() or apply_filters() call that afterwards triggers all the action or filter functions, previously hooked to that event using add_action() or add_filter(), respectively.

 	See also: Action, Filter
 	Related articles: Hooks, Actions and Filters, Plugin API/Hooks

Terminology Confusion
WordPress Codex and source code comments sometimes confuse the terms "actions/filters" and "hooks".

Actions, Filters and Hooks are also occasionally referred to as "action/filter hooks" or "action/filter/hook functions".

Back to the Top
Hosting provider
A hosting provider is a company or organization which provides, usually for a fee, infrastructure for making information accessible via the web. This involves the use of a web server (including web server software such as Apache), and may involve one or more related technologies, such as FTP, PHP, MySQL or MariaDB, and operating system software such as Linux or Unix.

 	Related articles: Hosting WordPress

Back to the Top
.htaccess
A .htaccess file is a granular configuration file for the Apache web server software, used to set or alter the server's configuration settings for the directory in which it is present, and/or its child directories.

WordPress uses an .htaccess file in conjunction with the mod_rewrite Apache module to produce permalinks.

Note that .htaccess is a hidden file in Unix/Linux (as dictated by the preceding period '.'), meaning it may not be visible using the default settings of some FTP clients.

 	See also: chmod
 	Related articles: htaccess for subdirectories, Using Permalinks, UNIX Shell Skills, Changing File Permissions

Back to the Top
HTML
HTML, or Hypertext Markup Language, is a markup language used to describe the semantic content of web pages. It is usually used with CSS and/or JavaScript. WordPress renders web pages to conform to the HTML5 standard. The standard is set by the World Wide Web Consortium (W3C).

Back to the Top
IP address
An IP address is a unique number (e.g. 70.84.29.148) assigned to a computer (or other internet-capable information appliance, such as a network printer) to enable it to communicate with other devices using the Internet Protocol. It is a computer's identity on the internet, and every computer connected to the internet is assigned at least one — although the methods of assigning these addresses, and the permanence and duration of their assignment, differ according to the use of the computer and the circumstances of its internet use.

Every web server is assigned an IP address as well, but often times hosting providers will assign multiple IP addresses to one computer, in the event that multiple web sites reside on the same physical server. This is the case with most inexpensive 'managed' or 'group' hosting packages.

Domain names were created to provide an easier means of accessing internet resources than IP addresses, which are cumbersome to type and difficult to remember. Every domain name has at least one corresponding IP address, but only a small number of IP addresses have a domain name associated with them, since only computers that are servers require domain names. The domain name system (DNS) is what maps domain names to IP addresses.

 	External links: IP address (Wikipedia)

Back to the Top
IDE
Acronym for Integrated Development Environment. Is an application that provides several tools for software development.

An IDE usually includes:

 	source code editor, which is similar to a Text Editor
 	debugger, in the case of WordPress, useful debuggers are those for PHP and Javascript code
 	automated builder

Some examples of IDEs

 	Aptana Studio (Cross platform, Freeware)
 	Codelobster (Windows only, Freeware)
 	Eclipse (Cross platform, Freeware)
 	NetBeans (Cross platform, Freeware)

ISAPI
ISAPI (Internet Server Application Programming Interface) is a set of programming standards designed to allow programmers to quickly and easily develop efficient Web-based applications. Developed by Process Software and Microsoft Corporation, ISAPI is intended to replace CGI programs.

 	External links: ISAPI at Wikipedia

Back to the Top
JavaScript
JavaScript is a programming language that WordPress uses to make certain processing occur in your web browser when it is inconvenient or impossible for the server to do that processing. For example, when you reply to a comment in a WordPress blog, WordPress uses JavaScript to move the comment form inside the comment you are replying to.

 	See also: AJAX, HTML, XHTML
 	Related article: Using Javascript
 	External link: JavaScript (Wikipedia)

Back to the Top
Linux
Linux is an open source computer operating system, created by Linus Torvalds, similar in style to Unix. It is popular in web server and other high-performance computing environments, and has recently begun to gain popularity in workstation environments as well.

 	External links: Linux at Shortopedia

Back to the Top
Mac OS X
Mac OS X is an operating system specifically for modern Macintosh computers. The operating system was commercially released in 2001. It consists of two main parts: Darwin, an open source Unix-like environment which is based on the BSD source tree and the Mach microkernel, adapted and further developed by Apple Computer with involvement from independent developers; and a proprietary GUI named Aqua, developed by Apple.

 	Related articles: UNIX Shell Skills

Back to the Top
MariaDB
MariaDB is a fork of the MySQL relational database system developed by most of the original developers of MySQL. It works equally well with WordPress.
Menu
Menus are lists of links to pages and posts that appear on WordPress websites.

Back to the Top
Meta
Meta has several meanings, but generally means information about. In WordPress, meta usually refers to administrative type information. As described in Post Meta Data, meta refers to information associated with each post, such as the author's name and the date posted. Meta Rules define the general protocol to follow in using the Codex. Also, many WordPress based sites offer a Meta section, usually found in the sidebar, with links to login or register at that site. Finally, Meta is a MediaWiki namespace that refers to administrative functions within Codex.

 	External links: Wikipedia's Article on Meta

Back to the Top
Microformats
Microformats provide a way for programs to read certain information in web pages without making the pages look any different to humans. They add semantics to the generic HTML markup in order for these programs to understand the meaning of specific parts of a web page content which is better recognized by humans. For example, a web page displaying a user's profile could use microformats to make it easy for a program to extract the user's contact information so that it can be added to an address book in a single operation. In WordPress, some themes and plugins support some microformats.

 	Related: Themes and plugins providing microformats support
 	External links: Microformats.org

Back to the Top
MIME
MIME stands for Multipurpose Internet Mail Extension and is an Internet standard that extends the format of email to support:

 	Text in character sets other than ASCII
 	Non-text attachments
 	Message bodies with multiple parts
 	Header information in non-ASCII character sets

MIME's use, however, has grown beyond describing the content of email and now is often used to describe content type in general including for the web and as a storage for rich content in some commercial products.

 	External links: IANA Media Types Specification, Wikipedia

Back to the Top
Moblogging
Moblogging is the act of posting to one's blog via a mobile device, e.g. mobile phone, smartphone or tablet. It is pronounced as mōbə-logging or mōb-logging, or sometimes as mŏb-logging in reference to smart mobs.

 	Related articles: Moblog Clients, Post to your blog using email

Back to the Top
mod_rewrite
mod_rewrite is an extension module of the Apache web server software which allows for "rewriting" of URLs on-the-fly. Rewrite rules use regular expressions to parse the requested URL from the client, translate it into a different URL, and serve the content of this new URL under the original URL or pointing the client to make the new URL request.

WordPress uses mod_rewrite for its permalink structure, and also for multisite networks, which are both optional functionality.

 	Related articles: Using Permalinks, Create A Network

Back to the Top
Multisite
Multisite is a feature of WordPress 3.0 and later versions that allows multiple virtual sites to share a single WordPress installation. When the multisite feature is activated, the original WordPress site can be converted to support a network of sites.

 	Related article: Create A Network

Back to the Top
MySQL
MySQL is a popular open source SQL (Structured Query Language) database implementation, available for many platforms, including Windows, Unix/Linux and Mac OS X.

WordPress requires a MySQL database to store all blog information, including posts, comments, metadata, and other information.

WordPress also works with MySQL-compatible databases such as MariaDB and Percona Server.

 	Related articles: Database Description
 	External links: MySQL, MariaDB, Percona Server

Back to the Top
Navigation
Navigation is the term used to describe text on a page that, when selected, redirects you to a corresponding page elsewhere on the website. Navigation may sometimes be referred to as the menu, links and hyperlinks.

Back to the Top
Network
In the WordPress user interface, a network is a collection of separate sites created in a single WordPress installation by the multisite feature. The sites in a WordPress network are not interconnected like the things in other kinds of networks. They are very like the separate blogs at WordPress.com.

In WordPress code the network is known as the site and the sites are known as blogs.

 	Related articles: Create A Network

Back to the Top
News reader
A news aggregator or news (feed) reader is a computer program which tracks syndicated information feeds, via RSS, RDF, or Atom. Most news aggregators allow one to 'subscribe' to a feed, and automatically keep track of the articles one has read, similar to an email client tracking read emails.

Many blogs make their content available in feed form for the convenience of readers using news aggregators. WordPress can generate feeds in RSS and/or Atom formats.

 	External links: News aggregator at Wikipedia

Back to the Top
Nonce
Nonce is used for security purposes to protect against unexpected or duplicate requests that could cause undesired permanent or irreversible changes to the web site and particularly to its database. Specifically, a nonce is an one-time token generated by a web site to identify future requests to that web site. When a request is submitted, the web site verifies if a previously generated nonce expected for this particular kind of request was sent along and decides whether the request can be safely processed, or a notice of failure should be returned. This could prevent unwanted repeated, expired or malicious requests from being processed.

Nonce is usually included in a hidden HTML form field or as a part of an URL and therefore sent with a request by submitting a form field or visiting a link. If a request is not verified, the web site could generate a new nonce in its response and prompt the user to intentionally confirm the repetition of the request. In WordPress, the response message is "Are you sure you want to do this?" by default. 

 	Related articles: WordPress Nonces

Back to the Top
Open Source
Open source is simply programming code that can be read, viewed, modified, and distributed, by anyone who desires. WordPress is distributed under an open source GNU General Public License (GPL).

 	Related articles: GPL, License
 	External links: Open Source Initiative, Open Source at Wikipedia, Source Code at Wikipedia

Back to the Top
Options
Options are pieces of data that WordPress uses to store various preferences and configuration settings.

By using the wp_options table.

 	Related articles: Option Reference, Transients API, Options API

Back to the Top
Output Compression
Output Compression is the removal of white spaces, carriage returns, new lines and tabs from your HTML document. This reduces the file size of the HTML document without changing the functionality.

 	Related articles: Output Compression

Back to the Top
Page
A Page is often used to present "static" information about yourself or your site. A good example of a Page is information you would place on an About Page. A Page should not be confused with the time-oriented objects called posts. Pages are typically "timeless" in nature and live "outside" your blog.

The word "page" has long been used to describe any HTML document on the web. In WordPress, however, "Page" refers to a very specific feature first introduced in WordPress version 1.5.

 	Related articles: Pages, Write Page SubPanel

Back to the Top
Perl
Perl is an acronym for Practical Extraction and Report Language, but it's most commonly spelled as a proper name. It's a very popular and powerful scripting language used for web applications, although its use is being largely replaced by PHP in the mainstream. One of its strengths lies in its speedy and effective use of regular expressions. Its unofficial motto is, "There's More Than One Way To Do It," or "TMTOWTDI," owing to the extreme flexibility of the syntax.

WordPress does not use Perl, and it is therefore not required.

Back to the Top
Permalink
A permalink is a URL at which a resource or article will be permanently stored. Many pages driven by Content Management Systems contain excerpts of content which is frequently rotated, making linking to bits of information within them a game of chance. Permalinks allow users to bookmark full articles at a URL they know will never change, and will always present the same content.

Permalinks are optional in WordPress, but are highly recommended as they greatly increase the cleanliness of URL. WordPress uses the Apache module mod_rewrite to implement its permalink system.

 	Related articles: Using Permalinks
 	External links: URL at Wikipedia

Back to the Top
Permissions
Permissions are security settings restricting or allowing users to perform certain functions. In the case of files on Unix or Linux systems, there are three types of permissions: read, write, and execute. In the case of MySQL or MariaDB databases, there are many more: SELECT, INSERT, UPDATE, DELETE, etc. — although MySQL/MariaDB refer to them as privileges.

 	Related articles: Changing File Permissions

Back to the Top
PHP
PHP is a recursive acronym for PHP: Hypertext Preprocessor. It is a popular server-side scripting language designed specifically for integration with HTML, and is used (often in conjunction with MySQL or MariaDB) in Content Management Systems and other web applications. It is available on many platforms, including Windows, Unix/Linux and Mac OS X, and is open source software.

WordPress is written using PHP and requires it for operation.

 	External links: PHP Website, PHP for Designers — by WordPress lead developer Matthew Mullenweg, PHP at OnLAMP

Back to the Top
phpMyAdmin
phpMyAdmin is a popular, powerful web-based interface for administering MySQL or MariaDB databases. It is open source, written in PHP, and is among the better tools available for working with MySQL or MariaDB databases.

 	Related articles: phpMyAdmin
 	External links: phpMyAdmin web site

Back to the Top
Ping
Within the WordPress interface, "ping" is sometimes used to refer to Pingbacks and Trackbacks.

In general computer terms, "ping" is a common utility used in a TCP/IP environment to determine if a given IP Address exists or is reachable. Typically, Ping is used to diagnose a network connection problem. Many times you will be asked, "Can you ping that address?". That means, does the Ping utility return a success message trying to reach the "problem" IP Address?

 	External links: Ping at Wikipedia

Back to the Top
Pingback
Pingback lets you notify the author of an article if you link to his article (article on a blog, of course). If the links you include in an article you write on a blog lead to a blog which is pingback-enabled, then the author of that blog gets a notification in the form of a pingback that you linked to his article.

If you're feeling really geeky you may want to check out the Pingback technical specification or Otto's "How Pingbacks Work" explanation.

 	See also: Trackback
 	Related articles: Introduction to Blogging: Pingbacks

Back to the Top
Plugin
A Plugin is a group of PHP functions that can extend the functionality present in a standard WordPress weblog. These functions may all be defined in one php file, or may be spread among more than one file. Usually, a plugin is a PHP file that can be uploaded to the "wp-content/plugins" directory on your webserver, where you have installed WordPress. Once you have uploaded the plugin file, you should be able to "turn it on" or Enable it from the "Plugins" page in the administration interface of your weblog. The WordPress source code contains hooks that can be used by plugins.

 	See also: Hack, Hacking
 	Related articles: Plugins

Back to the Top
Port
Within the context of the WordPress community, a port is a bit of code that has been rewritten to be compatible with WordPress. For example, if someone wrote a plugin for MoveableType, WordPress users may want to find a port of that plugin for WordPress. Port can also be used as a verb: to rewrite a piece of software for a different platform/language.

 	External links: Porting at Wikipedia

Back to the Top
Post
Also known as “articles” and sometimes incorrectly referred to as “blogs”. In WordPress, “posts” are articles that you write to populate your blog.

Back to the Top
Post Slug
A few lowercase words separated by dashes, describing a post and usually derived from the post title to create a user-friendly (that is, readable and without confusing characters) permalink. Post slug substitutes the "%posttitle%" placeholder in a custom permalink structure. Post slug should not be changed and is especially useful if the post title tends to be long or changes frequently.

Back to the Top
Post Status
The status of a post, as set in the Administration Panel, user level), or Private (viewable only to WordPress users at Administrator level).

 	Related articles: Post Status

Back to the Top
Post Type
Post type refers to the various structured data that is maintained in the WordPress posts table. Native (or built-in) registered post types are post, page, attachment, revision, and nav-menu-item. Custom post types are also supported in WordPress and can be defined with register_post_type(). Custom post types allow users to easily create and manage such things as portfolios, projects, video libraries, podcasts, quotes, chats, and whatever a user or developer can imagine.

 	Related articles: Post Types

Back to the Top
Query
The process behind the scenes. See below. :-)

 	Related articles: Custom_Queries,_[[Class_Reference/WP_Query">WP Query, WP User Query
 	See also: query string, query variable

Back to the Top
Query String
A sequence of codes in a Uniform Resource Identifier (URI) that a web page uses to determine what dynamic data to display. The query string in a URI comes after an initial question mark, and may contain several parameters separated by ampersands. WordPress uses query strings to indicate criteria to search for specific posts or sets of posts in the database. The use of query strings is generally believed to impede the indexing of dynamic pages by search engines. For this reason, it is often desirable to use a method such as mod_rewrite to reduce exposure of query strings to search engines and other site visitors.

Back to the Top
Query Variable
A variable passed through the query string. For example, in the query string ?category_name=tech&feed=atom, there are two query variables: category_name with a value of "tech", and feed with a value of "atom".

Back to the Top
QuickTag
A Quicktag is a shortcut, or one-click button, that inserts HTML code into your posts. The  (emphasis) and  (stop emphasis) HTML tags are example of Quicktags. Some Quicktags, such as , insert HTML comment code that is used by plugins to replace text or perform certain actions.

Back to the Top
RDF
Resource Description Framework. A language used to describe the locations of resources on the web. WordPress can produce output in RDF format that describes the locations of posts. Like RSS, RDF is used for content syndication.

Back to the Top
Relative Path
A relative path is the location of a file in relation to the current working directory and does not begin with a slash (/). This is different from an absolute path which gives an exact location.

 	See also: Absolute Path
 	External links: Path_Computing at Wikipedia

Back to the Top
Relative URI
A relative URI (sometimes called a relative link) is a partial URI that is interpreted (resolved) relative to a base URI.

On the World Wide Web, relative URIs come in two forms:

A relative URI with an absolute path is interpreted relative to the domain root:

[code language="php"]
/images/icecream.jpg → http://domain.example/images/icecream.jpg
[/code]

A relative URI with a relative path is interpreted relative to the URL of the current document. E.g., on the web page http://domain.example/icecream/chocolate.html,

[code language="php"]
strawberry.html → http://domain.example/icecream/strawberry.html
[/code]

Wikipedia: URI Resolution

Back to the Top
Recordset
Recordset refers to the group of records or result returned from a database query.

 	See also MySQL, wpdb database class

Back to the Top
RSS
"Really Simple Syndication": a format for syndicating many types of content, including blog entries, torrent files, video clips on news-like sites; specifically frequently updated content on a Web site, and is also known as a type of "feed" or "aggregator". An RSS feed can contain a summary of content or the full text, and makes it easier for people to keep up to date with sites they like in an automated manner (much like e-mail).

The content of the feed can be read by using software called an RSS or Feed reader.

Feed readers display hyperlinks, and include other metadata (information about information) that helps people decide whether they want to read more, follow a link, or move on.

The original intent of RSS is to make information come to you (via the feed reader) instead of you going out to look for it (via the Web).

Programs called news aggregators permit users to view many feeds at once, providing 'push' content constantly. See :Category:Feeds for Codex resources about bringing RSS feeds into WordPress. See also RDF Site Summary.

Back to the Top
RTL
A written language is Right-to-left when its script flows from the right side of the page to the left.

 	Related articles: Right-to-Left Language Support

Back to the Top
Robots.txt
Web Robots are programs which traverse the Web automatically. They are also called Web Wanderers, Web Crawlers, and Spiders. Search Engines are the main Web Robots. Some Web Robots look for a file named robots.txt on your web server to see what and where they should look for content and files on your web server. Some Web Robots ignore this file.

 	Related articles: Search Engine Optimization for WordPress
 	External links: Google information about robots.txt, The Web Robots Page

Back to the Top
Role
A role gives users permission to perform a group of tasks. When a user logs in and is authenticated, the user's role determines which capabilities the user has, and each capability is permission to perform one or more types of task. All users with the same role normally have the same capabilities. For example, users who have the Author role usually have permission to edit their own posts, but not permission to edit other users' posts. WordPress comes with six roles and over fifty capabilities in its role-based access system. Plugins can modify the system.

 	Related article: Roles and Capabilities
 	External link: Role-based access control (Wikipedia)

Back to the Top
Screen
In WordPress a screen is a web page used for managing part of a weblog (site) or network. The term 'screen' is used to avoid confusion with 'page', which has a specific and different meaning in WordPress. For example, the web page used to manage posts is known as the Posts Screen.

 	Related article: Class_Reference/WP_Screen

Back to the Top
Shell
A shell is a program which interacts directly with an operating system such as MS-DOS, Unix/Linux, Mac OS X, or others — but it is most commonly associated with Unices. It is often referred to as a 'console' or 'command line', because it is controlled using typed commands rather than mouse or graphical interface input.

Most often, when interacting with a remote computer (as one would when configuring WordPress), an additional "faux" shell is involved called SSH.

Some popular shell programs are:

 	Bash (Bourne Again Shell)
 	Tcsh (an expanded C Shell)
 	Zsh

Back to the Top
Shortcode
A PHP code into the body of a page or other content item.

Back to the Top
Sidebar
A sidebar is a vertical column provided by a theme for displaying information other than the main content of the web page. Themes usually provide at least one sidebar at the left or right of the content. Sidebars usually contain widgets that an administrator of the site can customize.

In a theme, sidebars are generated by a template file, typically named sidebar.php.

 	See also: Footer area
 	Related articles: Sidebars, Templates, Customizing Your Sidebar, Stepping Into Templates, Template Hierarchy

Back to the Top
Site
In the WordPress user interface, a site can simply be the website created by WordPress, or it can be a virtual website created as part of a network by the multisite feature. A site in a network is virtual in the sense that it does not have its own directory on the server, although it has its own URL and it might have its own domain name.

In WordPress code the site is the website created by WordPress. If multisite is in use, then the site is the network website and each virtual website is known as a blog.

 	Related article: Create A Network

Back to the Top
Slug
A slug is a few words that describe a post or a page. Slugs are usually a URL friendly version of the post title (which has been automatically generated by WordPress), but a slug can be anything you like. Slugs are meant to be used with permalinks as they help describe what the content at the URL is.

Example post permalink: http://wordpress.org/development/2006/06/wordpress-203/

The slug for that post is "wordpress-203".

Slugs are also used for post types, categories, tags, etc. Like post and page slugs, this is usually for creating URL friendly versions of these items.

Back to the Top
Smileys
Smileys (also called Smilies or Emoticons) are stylized representations of a human face, usually displayed as yellow buttons with two dots for the eyes, and a half mouth. Smileys are often used in WordPress Plugins. By default, WordPress automatically converts text smileys to graphic images. When you type ;-) in your post you see
*** [TODO] Embed Image HERE !!! ***: icon_wink.gif|Wink Icon 
when you preview or publish your post.

Related article: Using Smilies

Back to the Top
Spam
Once upon a time, SPAM was an animal by-product that came in a can and was fodder for many Monty Python sketches, but since the world-wide adoption of the internet as an integral part of daily life, Spam has become synonymous with what is wrong with the internet. Spam, in general terms, is an email or other forms of unsolicited advertising. Spam is very easy to spread throughout the internet, and works on the principle that if you send out thousands, or hundreds of thousands of unsolicited advertisements, scams, or other questionable methods of making money, that you only need a very small percentage of people to be fooled and you will make lots of money.

Common spam these days comes from online gambling sites and those trying to sell drugs for "male enhancement." Lately, web logs, or blogs, as we call them, have been targeted by spammers to try to increase their site ratings in the search engines. Spammers use various methods to distribute their electronic junk mail, and employ bots, or computer programs to quickly and easily send email or comments to millions of addresses and IPs all over the world.

Spammers can be difficult to track down as they often hijack peoples' email and IP addresses. When this happens, it may appear a friend sent you the spam, but in fact, the spammer's bot grabbed your friend's email address and used it to hide the true source of the spam. WordPress developers and community members are constantly working on more and better ways to combat these annoying spammers as they clog the internet with their garbage. You can help by offering your talents, ideas, suggestions, or just by being vigilant and installing any of the currently-available spam combating tools.

 	External links: SPAM at Wikipedia

Back to the Top
SSH
SSH stands for Secure Shell. It is a communication protocol for connecting to remote computers over TCP/IP. Various authentication methods can be used which make SSH more secure than Telnet.

Back to the Top
SSL
SSL stands for Secure Sockets Layer and is the predecessor to Transport Layer Security. These are cryptographic protocols for secure communications across an unsecured network like the Internet.

 	External links: SSL at Wikipedia

Back to the Top
Stats
Stats are a record showing how many views and visitors a WordPress blog or website gets during a set period of time. Stats also show where in the world your viewers are.

Back to the Top
String
In computer science a string is any finite sequence of characters (i.e., letters, numerals, symbols and punctuation marks).

Typically, programmers must enclose strings in quotation marks for the data to be recognized as a string and not a number or variable name.

 	External links: String at Wikipedia

Back to the Top
Structure tags
These tags are used to customize WordPress permalinks. Structure tags are:

%year%, %day%, %hour%, %minute%, %second%, %post_id%, %postname%, %category% and %author%.

End permalink structure with either %post_id% or %postname%, so that each permalink points to an individual post.

 	Related articles: Permalinks

Back to the Top
Subversion
Subversion is an open-source version control software tool used by the WordPress Developers to maintain and track the changes and updates to the various WordPress versions.

 	Related articles: Using Subversion
 	External links: Subversion access at wordpress.org, Subversion book at red-bean.com

Back to the Top
SVC
SVC stands for Switched Virtual Circuit. An SVC is a virtual circuit that is temporary turned on during a session of data transfer.

 	External links: Virtual circuit at Wikipedia

Back to the Top
Syndication
See RSS: Really Simple Syndication

Back to the Top
Tag
A Tag is a keyword which describes all or part of a Post. Think of it like a Category, but smaller in scope. A Post may have several tags, many of which relate to it only peripherally. Like Categories, Tags are usually linked to a page which shows all Posts having the same Tag. Tags can be created on-the-fly by simply typing them into the Tag field. By default, tags can be assigned only to the Post and custom post types.

Tags can also be displayed in clouds which show large numbers of Tags in various sizes, colors, etc. This allows for a sort of total perspective on the blog, allowing people to see the sort of things your blog is about most.

Many people confuse Tags and Categories, but the difference is easy: Categories generally don't change often, while your Tags usually change with every Post and are closer to the topic of the Post.

Back to the Top
Tagline
A tagline is a catchy phrase that describes the character or the attributes of the blog in a brief, concise manner. Think of it as the slogan, or catchline for a weblog.

Back to the Top
Task Based Documentation
Task based, or task oriented documentation is writing that takes you through a process/task step-by-step; it is succinct, lacks jargon, is easily understood, and structured entirely around performing specific tasks.
In order to get to Z, you need to:
#Step x
#Step y
#Step z
Keep in mind that people who need to know how to perform a task usually need answers quick!

Back to the Top
Taxonomy
A taxonomy allows for the classification of things. In WordPress, there are two built-in taxonomies, categories and tags. These taxonomies help further classify posts and custom post types. Also, custom taxonomies can be defined.

 	See also: Category, Tag
 	External links: Taxonomy at Wikipedia, register_taxonomy()

Back to the Top
Telnet
Telnet is a communications protocol used to establish a connection to another computer. Telnet runs on top of TCP/IP and is typically used in conjuction with terminal emulation software to login to remote computers. Telnet is inherently insecure and has largely been replaced by SSH

 	External links: Telnet at Wikipedia

Back to the Top
Template
In WordPress a template is a file that defines an area of the web pages generated by a theme. For example, there is typically a template for the header area at the top of the web pages, a template for the content, a template for the sidebars, and so on. The templates are like building blocks that make up the complete web page.

 	Related articles: Templates, Stepping Into Templates, Template Hierarchy

Back to the Top
Template Tag
In a WordPress Theme, template tags are used in template files to generate specific programming instructions. They are used to display generated content and information on a WordPress site. Template tags are short programming words, also known as functions, that tap into the WordPress core for instructions. For example, the HTML title tag of a WordPress site may hold the bloginfo() template tag that requests the site title, site tagline, and other site information set by the template tag parameters. Using this in the title HTML tag allows the Theme to be used on multiple sites and the information displayed will change easily with each site.

Other template tags are more sophisticated, generating post content, queries, and site data.

 	Related articles: Stepping Into Template Tags, Anatomy of a Template Tag, How to Pass Tag Parameters, Include Tags, Conditional Tags, Function Reference, Templates

Term
In WordPress, a term is a classification, group or subset of a Taxonomy, where the latter can be a Category, Tag or Custom Taxonomy. By default, terms have a title, a slug and a description. Hierarchical taxonomies like categories can define a parent term.

 	Related articles: Taxonomies, the_terms()

Text editor
A text editor is a program which edits files in plain text format, as compared to binary format. Using a non-text based word processing program (e.g. using Microsoft Word to edit PHP scripts) can cause major problems in your code. This is because non-text based word processing programs insert extra formatting into text files, and can corrupt the files when they need to be interpreted by the interpreter. An editor like Notepad does not insert any extra formatting.

Edit WordPress Files with a text only editor.

Some examples of file formats which need to be edited as plain text:

 	HTML documents
 	PHP scripts
 	Perl scripts
 	Rich Text Format documents
 	JavaScript scripts

Some examples of text editor programs:

 	Atom (Cross-platform, Open Source, Free)
 	BBEdit (Classic Mac OS, Mac OS X)
 	Boxer Text Editor (Windows)
 	Brackets(Cross-platform, Open Source, Free)
 	Coda (Mac OS X)
 	EditPad Pro (Windows)
 	EditPlus (Windows)
 	Emacs (Cross-platform, Open Source, Free)
 	gedit (Cross-platform, Open Source, Free)
 	jEdit (Cross-platform, Open Source, Free)
 	Kate (Cross-platform, Open Source, Free)
 	Komodo Edit (Cross-platform, Open Source, Free)
 	Notepad++ (Windows, Open Source, Free)
 	phpDesigner (Windows)
 	PSPad (Windows, Free)
 	Smultron (Mac OS X)
 	SubEthaEdit (Mac OS X)
 	Sublime Text (Cross-platform)
 	TextEdit (comes with Mac OS X)
 	TextMate (Mac OS X)
 	TextPad (Windows)
 	UltraEdit (Windows)
 	vim (Cross-platform, Open Source, Free)

Some examples of non-plain text formats that require special software for editing:

 	Microsoft Word documents
 	Microsoft Excel spreadsheets
 	Images, such as JPEG, PNG, or GIF

Some examples of software which can edit text, but which are NOT regarded as basic text editors and NOT recommended for use on WordPress files:

 	Microsoft Word
 	Microsoft Excel
 	Adobe Photoshop
 	Adobe Illustrator
 	Adobe Dreamweaver

Back to the Top
Theme
A Theme is a collection of files that work together to produce a graphical front-end interface with an underlying unifying design for a site. A WordPress Theme modifies the way the site is displayed and designed, without modifying the underlying core programming of WordPress. While some associate a WordPress Theme with "skinning" your site with a design, a WordPress Theme contains programming code that influences the design, changing it with each generated page view based upon the programming with PHP, WordPress template tags, WordPress conditional tags, and CSS.

 	Related articles: Theme Development, Using Themes

Back to the Top
Toolbar
The Toolbar is an area of the screen just above that site that lists useful admininstration screen links such as add a new post or edit your profile. The Toolbar was added in Glossary#Admin_Bar">Admin Bar and in Toolbar. The toolbar can be turned on/off from the User Profile Screen.

 	Related articles: Toolbar
 	See also: Admin Bar, Your Profile Screen

Back to the Top
Trackback
Trackback helps you to notify another author that you wrote something related to what he had written on his blog, even if you don't have an explicit link to his article. This improves the chances of the other author sitting up and noticing that you gave him credit for something, or that you improved upon something he wrote, or something similar. With pingback and trackback, blogs are interconnected. Think of them as the equivalents of acknowledgements and references at the end of an academic paper, or a chapter in a textbook.

 	See also: Pingback
 	Related articles: Introduction to Blogging: Trackbacks

Back to the Top
Transient
A Transient is temporal data identified by a custom name, stored in the web server database or memory for fast access. This temporal nature and use of fast memory caching is their primary distinction from Options.

 	Related articles: Transients API, Options API

Back to the Top
Twenty Ten theme
Starting with Twenty Ten theme became the default (and fallback) theme. As described in 2010: A Theme Odyssey, the Twenty Ten theme serves as a good example theme that includes new theme-based features, and looks nice on a public site. Twenty Ten is a community-developed theme.

Up to Version 2.9.2, the default theme was the Kubrick theme and was housed in the wp-content/themes/default folder. The Twenty Ten theme is housed in the wp-content/themes/twentyten folder and was the only theme in the WordPress distribution.

 	See also: Default theme
 	Related articles: Child Themes

Back to the Top
Twenty Eleven theme
Starting with Glossary#Twenty_Eleven_theme">Twenty Eleven theme was the default (and fallback) theme. Twenty Eleven is a community-developed theme that emphasizes ,_random_theme_header_images,_customizable_layouts_and_colors,_HTML_5_improvements,_and_adherence_to_WordPress_coding_standards._It_was_replaced_as_the_default_in_[[Version_3.5">WordPress_Coding_Standards">WordPress coding standards. It was replaced as the default in [[Version 3.5 by the Twenty Twelve theme.

 	See also: Default theme
 	Related articles: Child Themes

Back to the Top
Twenty Twelve theme
Starting with WordPress_Widgets">Widgets, an optional display font, styling for [[Post Formats on both index and single views, and an optional no-sidebar page template.

 	See also: Default theme
 	Related articles: Child Themes

Back to the Top
Twenty Thirteen theme
Starting with Version 3.6, the Twenty Thirteen theme became the default (and fallback) theme.

 	See also: Default theme
 	Related articles: Child Themes

Back to the Top
Twenty Fourteen theme
Starting with Version 3.8, the Twenty Fourteen theme became the default (and fallback) theme.

 	See also: Default theme
 	Related articles: Child Themes

Back to the Top
Twenty Fifteen theme
Starting with Twenty Fifteen theme became the default (and fallback) theme.

It is clean, blog-focused, and designed for clarity. Twenty Fifteen's simple, straightforward typography is readable on a wide variety of screen sizes, and suitable for multiple languages. It was designed using a mobile-first approach, meaning content takes center-stage, regardless of whether the site is accessed by smartphone, tablet, laptop, or desktop computer.

 	See also: Default theme
 	Related articles: Child Themes

Back to the Top
Twenty Sixteen theme
Starting with Twenty Sixteen theme became the default (and fallback) theme.

Twenty Sixteen is a modernized take on an ever-popular WordPress layout — the horizontal masthead with an optional right sidebar that works perfectly for blogs and websites. It has custom color options with beautiful default color schemes, a harmonious fluid grid using a mobile-first approach, and impeccable polish in every detail. Twenty Sixteen will make your WordPress look beautiful everywhere.

 	See also: Default theme
 	Related articles: Child Themes

Back to the Top
Unicode
A widely supported and preferred character encoding system.

For a computer to display letters (or any text characters), it needs to enumerate them - create an index of characters it knows how to display. These indexes are known as character sets. This is invaluable for users hosting WordPress in a non-English language.

The most widely used collections of these character sets are the iso-8859 with iso-8859-1 and iso-8859-15 (which contains the euro sign and some characters used in Dutch, French, Czech and Slovak) being the most common; they are also known as Latin1 and Latin9. These character sets use 8 bits (a single byte) for each character, allowing for 255 different characters (256, counting null). However, when considering that Latin-based languages aren't the only ones in the world (think Japanese or Hebrew), 255 characters aren't nearly enough.

There is a wide index of characters known as Unicode. Unicode has so many characters that sometimes more than 16 bits (2 bytes!) are required to represent them. Furthermore, the first 127 characters of Unicode are the same as the first 127 of the most widely used character set - iso-8859-1. For this purpose, UTF, the Unicode Translation Format, was created. UTF uses different numbers of bits for characters, and allows for the entire range of Unicode to be used. What you should probably know is:

 	UTF-8 is an 8-bit-minimum type of UTF. There are also UTF-16 and UTF-32.
 	If your document is in a Latin-based encoding, you probably don't need to change anything about it for it to be UTF.
 	A single UTF document can be in various languages with no need to switch encodings halfway through.


 	External links: Joel Spolsky on Unicode

Back to the Top
Unix
Unix, or UNIX, is a computer operating system developed at AT&T's Bell Laboratories starting back in 1969. Initially designed with the objective of creating an OS written in a high level language rather than assembly, a majority of web servers currently run on different "flavors" of this high-performance OS, or on Linux, developed as a Unix-like operating system.

 	See also: UNIX Shell Skills, Mac OS X

Back to the Top
Unix Time
Unix Time, or a timestamp, is a method of tracking time by determining the approximate number of seconds from a particular event. That event is called an Epoch. Since this time format is only off by a few seconds each century, it is usually considered good enough for most applications.

Unix time is (currently) a ten digit number, and looks like this: 1229362315. WordPress often uses a Unix timestamp internally to track time. The human readable times and dates you see are converted from Unix Time or from a MySQL/MariaDB DATETIME field.

 	External Links: Unix Time at Wikipedia, DATETIME, MariaDB DATETIME

Back to the Top
URL
An address of a specific Web site or file on the Internet.

[code language="php"]
http://www.example.com/
http://www.example.com/reports/index.html
[/code]

UTC
UTC ("Universal Time, Coordinated") is the basis of international time standards from which time zones around the world are calculated. For most purposes it is the same as the older GMT standard.

 	External link: UTC (Wikipedia)

Back to the Top
Web server
A web server is a computer containing software for, and connected to infrastructure for, hosting, or serving, web sites written in HTML. The most common web server software on the internet is Apache, which is frequently used in conjunction with PHP, Perl, and other scripting languages.

It is possible to create one's own web server, hosted on any speed of internet connection, but many people choose to purchase packages from hosting providers, who have the capacity and facilities to provide adequate bandwidth, uptime, hardware, and maintenance for frequently-visited web sites.

 	Related articles: Hosting WordPress

Back to the Top
Widget
In WordPress a widget is a self-contained area of a web page that performs a specific function, or the code that generates such a self-contained area. For example, WordPress has a built-in widget that displays a list of pages in a weblog's sidebar, and it has another built-in widget that displays a list of recent comments in the Dashboard. Plugins and themes can provide additional widgets.

 	Related articles: WordPress Widgets, Widgets API, Dashboard Widgets API

Widget Area
Furthermore, a "Widget Area" is a pre-defined location, in the code of your WordPress Theme, that allows users to place Widgets into.

Back to the Top
XFN
The XHTML Friends Network. A decentralised project to have inter-blog links that represent relationships between bloggers. XFN links resemble "http://www.photomatt.net/" rel="friend met">Photo Matt.

Back to the Top
XHTML
XHTML, or Extensible HyperText Markup Language, is the successor to HTML as the W3C standard language with which all web pages are created. It is often used in conjunction with CSS and JavaScript.

WordPress strives to conform to the XHTML 1.0 Transitional standard.

 	External links: XHTML 1.0 Specification (Second Edition), XHTML 1.1 Specification

Back to the Top
XML
XML, or Extensible Markup Language, is written in Standard Generalized Markup Language (SGML) and essentially allows you to define your own markup language. XML is extremely useful in describing, sharing, and transmitting data across the Internet. Typically used in conjunction with HTML, XML defines data and HTML displays that data.

 	External links: Extensible Markup Language (XML) Resources at W3C org XML 4.0 FAQ, Overview of SGML Resources at W3C org

Back to the Top
XML-RPC
XML-RPC is Extensible Markup Language-Remote Procedure Call. A Remote Procedure Call (RPC) allows you to call (or request) another application and expect that application to honor the request (answer the call). So, XML-RPC allows a user (or developer) to send a request, formatted in XML, to an external application.

 	Related articles: XML-RPC Support
 	External links: Dave Winer's XML-RPC for Newbies, XML-RPC Home Page, Apache XML-RPC, XML-RPC for PHP Homepage, XML-RPC at Wikipedia

Back to the Top
More Resources
More glossaries with collection of blogging terms, acronyms and abbreviations.

 	Giant Blogging Terms Glossary
 	Blogging Terms at Wikipedia

Category:WordPress Help

Category:Troubleshooting

Category:Getting Started

Category:Advanced Topics

Category:UI Link 


Planning Session
dolgelukkig — Fri, 17 Mar 2017 14:42:35 +0000
If you want to create a good and solid website, you need a good and solid plan. It's hard and you probably want to keep playing with your new website, but it's time to take a break away from your computer and turn to pen and paper.

On a piece of paper, describe your site. Take five to twenty minutes to come up with a purpose for your site, or better yet, call it your Mission Statement.

Answer the following questions:

 	What am I going to do with this?
 	Who is going to read this?
 	What kinds of information will I be posting?
 	Why am I doing this?
 	Who am I doing this for?
 	How often am I going to be posting and adding information?

Now, compile this information into a paragraph so it looks like this:


This website will be dedicated to X, Y, and Z,

and cover the topics of A, B, and C. The audience will

be __________ ________________ _______. I will be adding

posts every _____________ about ________ _______ ______________.

I am doing this because _____________ _____________ __________________.


 
Using the Information
From this exercise, we've gathered a lot of information. We've uncovered information on how you might layout and design your site. If you know your audience is mostly made up of young people under the age of 25, you will probably want a fashionable look ranging from wild colors and crazy graphics to dark foreboding tones. If you are providing factual information about a serious subject, then you will probably want a more conservative look where the information is more important than a lot of pop and flash.

You may already have a design idea in mind, or perhaps you will be copying over from your previous site, but take a moment to use this information to reconsider your design, and to see how what you want will work with the WordPress options.

You have also uncovered the possible categories for your site. The topics and subjects you will be covering are listed in your purpose statement. Let's say your purpose statement said,

 	

 	

 	“The website will be dedicated to providing news and information on computers, web pages, and the internet and cover the topics of computer tips, web page design, and internet news.”





Your topics are your categories. Write your categories down below your purpose paragraph and notes about your web page design.

Now, what subcategories might be under these topics? Under Computer Tips, you might want to segregate them by Windows, Linux, and Mac. Or maybe Software and Hardware. You can have sub-sub-categories, but let's stop with subcategories for right now. Write these down.

Remember the question about why you are doing this? Is it because you have valuable and timely information or knowledge to share, because you want to talk about a subject that interests you, or maybe because you just think it will be fun to do.

Understanding the timeliness of the information you want to present on your site helps you organize the information on your website. Your website is organized by several different methods. If the date of when you posted the information is critical to the success of the page, then having links to your posts referenced by date is important. If the information itself is more important and timeless, then having your posts referenced by category is the best choice.

Have you noticed that you are starting to lay out your website? If you remember our earlier test drive of your new WordPress website, we examined the sidebar menu. This is the area where your past posts are organized. If you take another look, you will see the sidebar is laid out in a list, including Archives by date and Categories by category. It may even feature a calendar.

As you lay out your website on paper, consider whether you want both categories and dates, or just one of them in your sidebar. What information you have and how you want to help the user find the information is critical to your website design.
What Information Do You Want to Share
As you think about what information the user will need to know, you have to consider what information you are willing to share with them. That information may include how to contact you, what the purpose of the site is, who you are, and what your expertise is.

A WordPress feature called Pages makes the process of presenting this information easier. Pages, similar to posts, are most commonly used to present unchanging information such as About Us, Contact Us, Sign Up for Our Mailing List, and other static information. Before creating your individual Pages, you need to think about what information you would like the Page to hold. Write down the possible Page titles and describe the information you want to share on each Page.


Exploring your new website
dolgelukkig — Fri, 17 Mar 2017 15:36:54 +0000
I have done the 5 minute installation, now what?
You've just completed the 5 Minute Installation of WordPress or one-click install from your web host. So what is your next step?

Let's take a step-by-step tour through your WordPress site and see how the different functions work and how to make your new site your own. During the first part of this tutorial, please don't change anything within the program unless it is part of the tutorial. After following these steps, you'll soon be changing everything.
Log In


Begin by logging into the “administration area” or the back end of your website. Visit your site's login page by placing “wp-admin” after your domain name (e.g. http://example.com/wp-admin). Some themes provide a “login” link or form on the front end as well. Now log into WordPress using the username and password you created in the 5 minute install.
Start at the Top


After logging in you are on the main Administration Screen called the Dashboard.  This is where the organization of your site begins.

At the top of the screen is the area called the “toolbar.” Click on your site name, it's a link and it will take you to a view of your new WordPress site. Like it? Don't like it? Doesn't matter, just look at it. This is where you are going to be spending a lot of time!
Test Drive Your WordPress Site
Take time to look at the site before you get into the changing of things and figuring out how all of this works; it's important to see how the WordPress Twenty Seventeen theme is laid out and how it works. Consider this the test drive before you start adding on all the special features.



The layout you are looking at is defined by a WordPress Theme. It is the appearance of your website, styling the look of the site and the framing of the content. The WordPress Twenty Seventeen theme features a “header” at the top with the title and tagline for your site. Below this is your Menu, if you have one. Along the side you will see some titles and links. This is the Sidebar. The different items inside a Sidebar are called Widgets. The main middle section of the page is the content area.

Scroll down the page and notice the bar at the end of the page. This is called the “footer.” It says “Proudly powered by WordPress.”
Take a Quick Trip Around
For now you only have one post. It is residing within a page that is laid out as your home page or the front page. If you click on the title of the post, it will take you to the specific page for that post. The first page or home page of your site features the most recent posts on your site. Each post title will link to the actual page of the post. Some Theme designers design their single post pages to look different from the home page.

In the single post, pay attention to the layout and notice what is different about the design elements. Is the header different? Smaller, larger, or a different color? Is there a sidebar?

All of these changes are created from a few files called template files. You can find the template files inside the active theme on your website.
Test Drive the WordPress Administration Screens
Now that you have an idea of how your site looks and what the different layout sections are called, it's time to test drive the WordPress Administration. Familiarize yourself with the backend of your new website. In fact, the first page you see after logging in is called the Dashboard, a collection of information and data about the activities and actions on your WordPress site.



The Dashboard features a list of the most recent activity you've accomplished on your site and it helps to keep you up to date on new and interesting bits of information from the many WordPress resources.

On the left side of the screen is the main navigation menu detailing each of the administrative functions you can perform. Move your mouse down the list and the sub-menus will “fly out” for you to move your mouse to and click. Once you choose a “parent” navigation section, it will open up to reveal the options within that section.

The various menu items are as follows:

 	Dashboard
 	Posts
 	Media
 	Links
 	Pages
 	Comments
 	Appearance
 	Plugins
 	Users
 	Tools
 	Settings

Let's start with the Settings screen


Put in your Website title and Tagline if you didn't do this in the installing proces.  Check the date, the timezone and change if necessary. Also you use your own preferences for time formats.

Don't forget to save your setting.

After the general setting go to the Settings > Permalinks.

Permalinks are the permanent URLs to your individual pages and blog posts, as well as your category and tag archives. A permalink is the web address used to link to your content. The URL to each post should be permanent, and never change — hence the name permalink. The Settings Permalinks Screen allows you to choose your default permalink structure. You can choose from common settings or create custom URL structures. You must click the Save Changes button at the bottom of the screen for new settings to take effect.

By default, WordPress uses web URLs which have day and name in them; however, WordPress offers you the ability to create a custom URL structure for your permalinks and archives. This can improve the aesthetics, usability, and forward-compatibility of your links.


The User pages
Click on the Users tab. The screen will change and you will see the Screen called All Users that shows a list of all your users; from here you can add or change existing users and authors accounts. In the navigation menu, click on the Your Profile menu choice. This is where you will enter information about you, the author and administrator of the site. Fill in the information and click Update Profile when done.



Now, let's look at some other powerful features of the WordPress Admin.
Changing the Look

The Appearance, Themes Screen allows you to change the look of your site using different Themes. Themes are presentation styles that completely change the look of your site. Designed by developers and users, there are hundreds of themes available for you to choose from. In your Appearance Screen, you will see a list of currently installed themes, including the WordPress Twenty Seventeen theme. To quickly change the theme, simply click on the Activate button under one of the themes listed, then click on your site name in the top toolbar to see how it looks.


Wow, you have another look. It's that easy. Go back to Appearance > Theme and click the Activate button under the WordPress Twenty Seventeen theme to bring the design back to what you had. To see it again, click your site name in the toolbar, and there it is.
Adding functionality



Page
corwinstar — Thu, 15 Jun 2017 14:26:29 +0000
Goal:

Pre-requisites:
What is a Page
How to...?


Twenty Seventeen
chetan200891 — Mon, 12 Feb 2018 11:21:40 +0000
Twenty Seventeen is the new default theme for WordPress in 2017. Its business-oriented design highlights the new video headers, and has a front-page layout that can be created from multiple sections. The theme can be customized further using its custom color options, and adding a site logo, social menu, and widgets.


Quick Specs

 	The main column width is up to 525px wide with the two column layout, or up to 740px wide with the one column layout.
 	The sidebar column width is up to 326px.
 	The recommended Featured Image size is 2000px wide by 1200px high.
 	The recommended Header Video and Header Image sizes are 2000px wide by 1200px high.

Header Media
Twenty Seventeen supports both the Header Image [1] and the new Header Video. To modify either on your site, navigate to Customizer > Header Media.



For the Header Video, you have the option of uploading your own mp4 video, or linking to one hosted on YouTube. Smaller file sizes will help make sure your site is loaded quickly.

The Header Image can be used on its own to display a large photograph at the top of your site. It can also be used as a video fallback - if both a video and image are added, the image will be used as a placeholder to display while the video loads, and as a fallback on smaller screens where videos may be harder to serve over mobile networks.
Front Page
Twenty Seventeen allows you to build a striking front page comprised of content from different pages on your site. Each page’s featured image is highlighted, displayed at full screen size and with a fixed position. Twenty Seventeen has four different sections you can assign pages to.

To set this up, first navigate to Customizer > Static Front page, and set your site to use a static front page if you haven’t already.



Navigate to Customizer > Theme Options. Under each Front Page Section # Content header, select a page you’d like to display for that section.



If you haven’t created any pages yet, you can do that from the Customizer by clicking + Add New Page beneath one of the sections. This will allow you to create a new page from the Customizer, which you can later add content to.

For the best appearance, make sure each page includes a featured image, and some content.

You can also select your Blog Posts page, and the panel will display your three latest blog posts.



Once you’ve finished adding pages to the different sections, click Save & Publish.

If you want to change the number of the sections either you want to have more section or remove some, add this snippet to your theme's functions.php.

add_filter( 'twentyseventeen_front_page_sections', 'prefix_custom_front_page_sections' );
function prefix_custom_front_page_sections( $num_sections ) {
return 6;
}

By doing that, you will have 6 sections instead of the default 4.
Custom Colors
Twenty Seventeen includes three color options - the default light color scheme, a dark color scheme, and a Custom Colors scheme that can be adjusted to various hues using a slider.



To explore all the color options available, navigate to Customizer > Colors.
Language Support
Twenty Seventeen includes optimal font styles for many languages, thanks to feedback from the WordPress community. The theme uses Libre Franklin by default or https://github.com/impallari/Libre-Franklin and makes adjustments to the typography for the following alphabets:

 	Arabic
 	Chinese
 	Cyrillic
 	Devanagari
 	Greek
 	Gujarati
 	Hebrew
 	Japanese
 	Korean
 	Thai

Twenty Seventeen also removes its letter-spacing styles for all non-latin alphabets to improve legibility.
One and Two Column Layouts
On pages [2], Twenty Seventeen allows you to pick between a one and two column layout. This can be changed via Customizer > Theme Options. The theme defaults to the two-column layout, which displays the page title in one column, and the page content in the other.

Note: this feature only becomes available after setting a static front page.



When the one-column layout is selected, both the page title and content display in a wider single column, centered on the page.



Widgets
Twenty Seventeen includes a footer widget https://codex.wordpress.org/WordPress_Widgets area, where you can add widgets below the site’s content.

The blog index, archive, search, and single blog posts also include a sidebar widget area. For each, the content will display in one centred column until the sidebar widget is added. With the sidebar widget, the content will appear in one column, and the widgets in the other.
Pullquotes
Pullquotes can be used to direct your readers attention to a particular passage, or to add visual interest to your posts and pages. In Twenty Seventeen, you can pair a pullquote with an alignleft or alignright class to the blockquote element to highlight it further. Instructions on how to do this can be found here: https://codex.wordpress.org/Writing_Posts#Visual_Versus_Text_Editor An example would be:
This is my fabulous left-aligned pullquote.
When a two column layout is used (either by selecting via the Customizer for pages, or by adding a sidebar widget on posts), the pullquote aligned to the same side will display fully outside of the content area and below the second column. Note: this will only work when the pullquote appears in the content below where the second column ends.


Post Formats
Twenty Seventeen supports the following post formats:

 	Aside
 	Audio
 	Gallery
 	Image
 	Link
 	Quote
 	Video

Add Social Icons
Twenty Seventeen includes a Social Icons Menu, where you can add links to your social media profiles that will be displayed as logos in the footer. If you’re not familiar with this functionality, please check out the documentation from Twenty Fifteen https://codex.wordpress.org/Twenty_Fifteen#Add_Social_Icons.

The following services are supported by Twenty Seventeen’s Social Icons Menu:

 	Behance
 	Codepen
 	DeviantArt
 	Digg
 	Dribbble
 	Dropbox
 	Facebook
 	Flickr
 	Foursquare
 	GitHub
 	Google+
 	Instagram
 	LinkedIn
 	Meanpath
 	Medium
 	Pinterest
 	Pocket
 	Reddit
 	Skype
 	SlideShare
 	Snapchat
 	SoundCloud
 	Spotify
 	StumbleUpon
 	Tumblr
 	Twitch
 	Twitter
 	Vimeo
 	Vine
 	VK
 	WordPress
 	Yelp
 	YouTube

Support & Resources
Get community help with Twenty Seventeen in its forum.

Get tips for theming with Twenty Seventeen in this post from Make.wordpress.org by one of Twenty Seventeen's developers. You can also read the theme's changelog.

Tutorials:

 	How To Master Twenty Seventeen (Or Any WordPress Theme in 2017)
 	How to Customize the Free Twenty Seventeen WordPress Theme for Business
 	A Developer’s Introduction to the Twenty Seventeen Theme
 	How to Add Extra Twenty Seventeen Theme Front Page Sections



Overview of WordPress
atachibana — Sat, 24 Feb 2018 05:25:37 +0000

WordPress is a free and open source content management system (CMS) based on PHP and MySQL. It is the most widely-used CMS software in the world and it powers more than 29% of the top 10 million websites (https://w3techs.com/ as of Feb/2018), giving it an estimated 60% market share of all sites using a CMS.





WordPress started as just a blogging system in 2003, but has evolved to be used as full content management system and so much more through the thousands of plugins and widgets and themes.





WordPress is licensed under the General Public License (GPLv2 or later).





Refer this article for a list of the features that come as standard with WordPress.







History
atachibana — Sat, 24 Feb 2018 05:49:32 +0000
WordPress was born out of a desire for an elegant, well-architectured personal publishing system built on PHP and MySQL and licensed under the GPL. It is the official successor of b2/cafelog. WordPress is modern software, but its roots and development go back to 2001. It is a mature and stable product. We hope that by focusing on user experience and web standards we can create a tool different from anything else out there.
There are also various post launch versions with improvements for security, bug fixes and stability. Please review the full WordPress Release Archive for details or check out the version announcements!

2017 - Announcements:  4.8  4.9
Version 4.8 (Evans) (346 Contributors) brought an array of new widgets (image, video, audio and rich text). Adding links improved greatly setting boundaries around groupings of text to avoid mismatching. WordPress event streams became visible in the Admin Dashboard. Developer enhancements were introduced for added accessibility, API introduction to make the editor more portable to different areas via plugins.
Version 4.9 (Tipton) (443 Contributors) focused on user experience and introduced the ability to save design drafts for review and alteration prior to publishing. Design locking rolled out, protecting two multiple designers to override changes in progress. This was also the introduction point of code syntax checking and error reporting within the Admin experience. An official callout for contributors and testers went out for the Gutenberg project.
 
2016 - Announcements:  4.5  4.6  4.7
 Version 4.5 (Coleman) (298 Contributors) added inline links, added formatting shortcuts and responsive previews in Customizer to preview on mobile, tablet or desktop. Additionally, support was added for Custom Logos, smart image resizing for speed improvement and script loading improvements for dependent scripts from the header and footer.
Version 4.6 (Pepper) (272 Contributors) brought significant speed changes to Multisite with cached and comprehensive site queries to improve the network admin experience. Theme addition, activation and plugin updates were adapted to a one screen process. Local draft saving to browser was introduced. Native fonts were also made available to be used from the operating system for speed enhancement.
Version 4.7 (Vaughan) (482 Contributors) arrived along side a new theme with modern elements (including starter content) with video header support. New Customizer features allow editing CSS with live previewing. REST API endpoints allow for machine-readable external access for enhanced third party interaction. Page template functionality was opened up to all post types. Bulk actions additionally were branched out with custom option support. The Customizer continued extension to support auto saving of drafts. This was an exciting release for WordPress as the number of contributors significantly increased with this release.
 
2015 - Announcements:  4.2  4.3  4.4

Winner of CMS Critic Award's "Best CMS for Personal Websites."

 Version 4.2 (Powell) (283 Contributors) added emoji support, add extended character support and switched database encoding from utf8 to utf8mb4. Plugin updates became dynamic from one page without reloading. Two new oEmbed providers were added (Tumblr, Kickstarter). Theme switching became available through the Customizer. This version also included developer query improvements.
 Version 4.3 (Billie) (246 Contributors) added built-in site icons support and introduced formatting shortcuts in the visual editor. Live Menu previews became available from the Customizer. Password processes were improved for security as well as List Views in the Admin panel.
 Version 4.4 (Clifford) (471 Contributors) added responsive images, embeddable posts, and a new default theme, "Twenty Sixteen." oEmbed support was added for WordPress posts with rich previews and display as well as five new providers (Cloudup, Reddit Comments, ReverbNation, Speaker Deck, and VideoPress). Developer improvements included integration of the REST API structure, query improvements for comments, Term Metadata and two new Objects (Term and Network) for more predictable added interaction capability within code.
 
2014 - Announcements:  3.9  4.0  4.1
 Version 3.9 (Smith) (267 Contributors) improved the media experience and introduced live widget and header previews. The Visual Editor was improved for speed, accessibility and mobile use. Image and media improvements included adding the ability to upload images via drag and drop from desktop and image editing enhancement. Audio and video playlist support was added as well as Gallery previews from within the editor. Themes became browsable from the Appearance section.
 Version 4.0 (Benny) (275 Contributors) introduced a grid view for the media library and for installing plugins. Previews for embedded content such as Twitter and YouTube became available from within the editor while preparing content. Editor writing improvements included expanding the editor with content for an easier experience. The Plugin section was enhanced to show more detail and provide a better search experience.
Version 4.1 (Dinah) (283 Contributors) introduced a refreshed Distraction Free Writing mode, language installation from the Settings screen (to switch between 40 different languages with support from Google's Noto font family), and a beautiful new default theme, "Twenty Fifteen." Developer improvements included addition of advanced metadata query conditional logic.
 
2013 - Announcements:  3.6  3.7  3.8
 Version 3.6 (Oscar) introduced a new default theme called "Twenty Thirteen," built-in Audio and Video support, dynamic and scalable Revisions, improved Autosave and Post Locking. Audio and video improvements included native support for audio and video embeds, a built-in HTML5 media player, a new API for supporting metadata (such as ID3 tags) and enhancement to existing oEmbed providers Spotify, Rdio and SoundCloud.
 Version 3.7 (Basie) (211 Contributors) introduced automatic updates for maintenance and security updates, a stronger password meter and enhanced language support and auto installation of language files.
 Version 3.8 (Parker) (188 Contributors) introduced a new magazine style default theme called "Twenty Fourteen."  The Admin panel was completely overhauled with a fresh modern look and new vector icons. Color schemes were also made available to be applied to the Admin experience. The Widget section was also streamlined for easier use.
 
2012 - Announcements:  3.4  3.5
 Version 3.4 (Green) introduced the Theme Customizer and previewer, allowing to test and check theme revisions prior to applying them. The Media Library was extended to support using images to populate custom headers and to choose the height and width of the images. Image captioning saw improvements to support HTML. With this release, Twitter "Tweets" were made to format a nice display by dropping the URL into the editor. There were many developer improvements, including XML-RPC, a custom header API and performance improvements to WP_Query.
 Version 3.5 (Elvin) introduced the new media manager and the new default theme called "Twenty Twelve" with focus on mobile display. Focus was also placed on the flow for uploading photos and creating galleries.  The Admin Dashboard saw the coming of a Retina-ready display with high resolution graphics.
 
2011 - Announcements:  3.1  3.2  3.3

Winner of Infoworld's "Bossie award for Best Open Source Software."

 Version 3.1 (Reinhardt) (180+ Contributors) introduced Post Formats and the Admin Bar.  A redesigned linking workflow was added to more easily work with existing posts and pages.  The beginnings of a streamlined writing interface were introduced. The import/export system was overhauled and there were many query improvements to enable performing perform advanced taxonomy and custom fields queries.
 Version 3.2 (Gershwin) made WordPress faster and lighter, this version upgraded minimum requirements to PHP 5.2.4 and MySQL 5.0.15, and introduced a new fully HTML5 default theme called "Twenty Eleven." The Dashboard design was refreshed and the previously introduced Admin Bar saw additions. This release featured introduction of a Distraction Free Writing mode. The Comments Moderation screen was improved for approvals and replies. The update process was streamlined, making updates much faster with added stability.
 Version 3.3 (Sonny) made WordPress more friendly for beginners with welcome messages and feature pointers. Improvements included a new drag and drop uploader, improved co-editing support, navigation and toolbar improvements and better touch support for iPad and other tablets.
 
2010 - Announcements:  3.0

Winner of digitalsynergy's "Hall of Fame CMS category in the 2010 Open Source."

 Version 3.0 (Thelonious) (218 Contributors) was a major release, it introduced custom post types, made custom taxonomies simpler, added custom menu management, added new API's for custom headers and custom backgrounds, introduced a new default theme called "Twenty Ten" and merged former WordPress MU (allowing the management of multiple sites) to be part of WordPress Core, renamed to Multisite. Bulk plugin updates were further streamlined from the previous release. Theme developers saw introduction of new APIs allowing implementation of custom backgrounds, headers, shortlinks, menus, post types, and taxonomies without file editing. An initiative to add contextual help going forward saw its start.
 
2009 - Announcements:  2.8  2.9

Winner of Open Source CMS Awards's "Overall Best Open Source CMS."

 Version 2.8 (Baker) introduced a built-in theme installer and improvements to themes, widgets, taxonomies, and overall speed (including a new Widget API) (and drag and drop). There were significant speed enhancements relative to style and scripting. A new CodePress editor added syntax highlighting to the Dashboard based code editor. Screen Options were added to the Admin in order to customize user interaction with the items being used and the ability to filter out the others.
 Version 2.9 (Carmen) (140+ Contributors) was a development intensive release introducing image editing, a Trash/Undo feature, bulk plugin updating, and oEmbed support allowing integrated 3rd party provider content to seamlessly integrate with content. There were also significant batch updating compatibility improvements, comment framework enhancement, editor upgrades, user profile, registration and automation improvements, gallery items usage across multiple posts introduction and better hooks and filters for excerpts, smilies, HTTP requests, user profiles, author links, taxonomies, SSL support, tag clouds, query_posts and WP_Query.
 
2008 - Announcements:  2.5  2.6  2.7

Winner of Infoworld's "Best of open source software awards: Collaboration."

 Version 2.5 (Brecker) was released with a new administration UI design by Happy Cog, and introduced the dashboard widget system and the shortcode API.
 Version 2.6 (Tyner) built on 2.5 and introduced post revisions and Press This. A usability study was done on 2.5 over the summer, leading to the development of the Crazyhorse prototype, and the following release.
Version 2.7 (Coltrane) which redesigned the administration UI to improve usability and make the admin tool more customizable. Version 2.7 also introduced automatic upgrading, built-in plugin installation, sticky posts, comment threading/paging/replies and a new API, bulk management, and inline documentation.
 
2007 - Announcements:  2.1  2.2  2.3
Version 2.1 (Ella) introduced a new UI, autosave, spell check and other new features. Enhancements added ability to switch between content and code editor, setting pages as the front page, adding no-indexing to the entire site for search engine privacy, XML importing improvements and the addition of the private pages feature. MySQL queries saw an aggressive optimization and re-write. Other developer additions included new hooks and APIs, language improvements and psuedo-cron scheduling.
Version 2.2 (Getz) brought better Atom feed support and speed optimizations for plugins and filters. Widgets introduction laid the groundwork for moving additional features into design, which provided a base for plugin features extension. Protection was added on activating plugins, checking for errors prior to successful activation. phpMailer was added which also provided support for SMTP Mail. Database collation control and many code notation improvements were also part of this release.
Version 2.3 (Dexter) offered tagging, update notifications, pretty URLs and a new taxonomy system. Core update notifications were introduced allowing users to better keep track of when new release updates were available. The jQuery version was updated bringing speed increases. canonical URL fixes were added and a new $wpdb->prepare() syntax support rolled out allowing for safer MySQL queries.
 
2005 - Announcements:  1.5  2.0
Version 1.5 (Strayhorn) introduced a Theme system and featured the introduction of static pages, bring WordPress to be poised as a content management system. A new theme became available to showcase how the newly deployed Theme system could be extended and utilized. Hundreds of hooks were made available, allowing for integration of plugins to key parts of WordPress. The WordPress Plugin Repository was created allowing for a collaborative environment between Plugin Developers and users.
Version 2.0 (Duke) was introduced with persistent caching, a new user role system and a new backend UI. WYSIWYG editing brought a better experience producing content which also included inline image, video and file uploads. Post previewing allowed to review posts before being made live on sites. Plugin hooks were enhanced to allow for features extension by plugin developers. Theme functions were introduced to enhance themes with code, similar to plugins.
2004 - Announcement:  1.0  1.2
Version 1.0 (Davis) was the official 1.0 bringing browser installation, search engine permalinks, multiple category support, an intelligent upgrade process and import enhancement for moving from other systems to WordPress. Support was added to the Admin experience for editing posts and comments as well as the start of many other features to be improved on in the future.
Version 1.2 (Mingus) introduced plugins, hierarchically category support, OPML import and export as well as introductory language support. Features like automatic thumbnail creation, multiple update service pinging and password encryption also were highlights.
 
2003 - Announcement:  0.7 (initial)
Version 0.7  Matt Mullenweg  and Mike Little fork b2 and create WordPress. This initial release included a texturize engine, links manager, XHTML 1.1 compliant templates, a new administration interface, the ability to do manual excerpts and new templates.
 
2001
b2 cafelog launched by Michel Valdrighi.


Requirements
atachibana — Sat, 24 Feb 2018 06:02:33 +0000

To run WordPress we recommend your host supports:




    PHP version 7.2 or greater
    MySQL version 5.6 or greater OR MariaDB version 10.0 or greater
    HTTPS support






We recommend Apache or Nginx as the most robust and featureful server for running WordPress, but any server that supports PHP and MySQL will do.





Note: If you are in a legacy environment where you only have older PHP or MySQL versions, WordPress also works with PHP 5.2.4+ and MySQL 5.0+, but these versions have reached official End Of Life and as such may expose your site to security vulnerabilities.



Version 4.5
atachibana — Tue, 12 Jul 2016 22:19:18 +0000
On April 12, 2016, WordPress Version 4.5, named for jazz musician Coleman Hawkins, was released to the public. For more information on this enhancement and bug-fix release, read the WordPress Blog, and see the Changelog for 4.5.

For Version 4.5, the database version (db_version in wp_options) changed to 36686, and the Trac revision was 37181.

 	View Closed Tickets

Highlights
The Finer Points
Customizer Improvement
Device Previewer Buttons in the customizer controls footer shows how your site looks in mobile, tablet, and desktop contexts before making changes to its appearance. Theme installer previewer has the same function.

Customizer provides theme logo upload and adding feature. The latest WordPress official themes such as Twenty Sixteen utilize this feature.

Visual Editor Improvement
Inline Link Editing enables users to direct URL input without switching to modal dialog. Version 4.5 adds new shortcuts in Visual Editor.
*Use `your code` to transform my code
*Use --- to transform 



Comment Refinement
Refreshed Moderate Comment Screen has formatted comment content for display, navigation via a text link, updated message styles and so on. The comment form now enforce the maximum length of each field.


Optimization of Image Generation
Image sizes are generated more efficiently and remove unneeded meta, while still including color profiles in Imagick, for reduced sizes of up to 50% with near identical visual quality.

For Developers

 	Selective Refresh - A comprehensive framework for rendering parts of the customizer preview in real time. The same framework is used in Theme Install Preview.
 	Backbone and Underscore update - Backbone is upgraded from 1.1.2 to 1.2.3 and Underscore is upgraded from 1.6.0 to 1.8.3.
 	Embed templates - Embed templates were split into parts and can now be directly overridden by themes via the template hierarchy.

 	embed-{post-type}-{post_format}.php
 	embed-{post-type}.php
 	embed.php
 	wp-includes/theme-compat/embed.php


 	Term Edit Page changes - wp-admin/term.php was introduced.

What's New
Security
In addition to the new features, enhancements, and bug-fixes, WordPress 4.5 solves a few security problems:

 	SSRF Bypass using Octal & Hexedecimal IP addresses, reported by Yu Wang & Tong Shi from BAIDU XTeam
 	Reflected XSS on the network settings page, reported by Emanuel Bronshtein (@e3amn2l)
 	Script compression option CSRF, reported by Ronni Skansing

We thank them for disclosing the issues responsibly.
Posts

 	Inline Link Editing (#33301) – Within the visual editor, edit links inline for a smoother workflow. When the users type in the URL field, it uses jQuery UI Autocomplete to search for local posts and pages.
 	Additional Editor Shortcuts (#33300) – Includes a few new shortcuts, like `..` for code and --- for horizontal bar. In the future release, we may include bold or italic shortcuts.

Comments
Version 4.5 includes several bug fixes and enhancements in the Comments component.

 	Moderate Comment Screen Refresh (#34133) – Moderate Comment Screen is where you land when clicking one of the moderation actions from a comment notification email message.

 	Comment content is formatted for display, instead of one massive block of escaped text
 	Include navigation via a text link to the Edit Comment screen at the bottom of the comment
 	Updated message styles that match other screens
 	Only wrap the comment date in a link if the comment permalink exists to avoid confusion
 	Appended #wpbody-content to the comment email message links for accessibility




 	Max Lengths for Comment Form Fields (#10377) - The comment form will now enforce the maximum length of each field’s respective database column. The default length settings are as follows:

 	Comment: 65525 characters
 	Name : 245 characters
 	Email: 100 characters
 	Url: 200 characters




 	Comment Error Page Navigation (#4332) - A simple back link has been added to the bottom of the error message page

Appearance
Customizer includes many new features:

 	Responsive Preview of your site (#31195) - See how your site looks in mobile, tablet, and desktop contexts before making changes to its appearance. The device previewer is in the customizer controls footer, near the "Collapse" button.
 	Theme Logo Support (#33755) - Native support for a theme logo within the Customizer.
 	Selective Refresh - A comprehensive framework can render parts of the customizer preview such as site title and tagline in core themes in real time. No more entire preview screen reload happens.
 	Easy of use - Shift-click on nav menu items in preview to open corresponding control in Customizer pane.

The device preview buttons of customizer were brought to the theme-install previewer so that themes can be easily previewed on various device sizes before being installed. (#36017)
Install Process

 	Version 4.5 default to generating secret keys and salts locally instead of relying on the WordPress.org API. (#35290)

Under The Hood
General

 	Selective Refresh (#27355) – A comprehensive framework for rendering parts of the customizer preview in real time. Theme and plugin authors should test their widgets specifically for compatibility with selective refresh.
 	Backbone and Underscore updated to latest versions (#34350) – Backbone is upgraded from 1.1.2 to 1.2.3 and Underscore is upgraded from 1.6.0 to 1.8.3. See the this post for important changes.
 	Embed templates (#34561) – Embed templates were split into parts and can now be directly overridden by themes via the template hierarchy.
 	Script loader (#14853, #35873) – Introduces wp_add_inline_script() for including inline JavaScript just like wp_add_inline_style() works for CSS.
 	Changes to the Term Edit Page (#34988) - wp-admin/term.php was introduced. The links to edit a single term now look like example.com/wp-admin/term.php?tag_ID=123. (previously: example.com/wp-admin/edit-tags.php?action=edit&taxonomy=post_tag&tag_ID=127).
 	Allow rewrite rules to work in nested WordPress installations on IIS (#35558)
 	For Emoji, upgraded twemoji.js to version 2 (#36059) and added extra IE11 compatibility (#35977)

Images
Version 4.5 includes some performance enhancements for images.

 	Increased image compression for custom sizes
 	Improved resizing settings for ImageMagick
 	Introduction of wp_get_upload_dir() (#34359)

Also includes

 	Imagick support in HHVM (#35973)
 	Fixes for SSL with Responsive Images (#34945)

Embeds
After the introduction of the embeds feature in Version 4.4 there have been a few significant changes in Version 4.5 to make embeds more robust and easier to customize.

 	Embed Code Adjustments (#35804, #35894)
 	Discovery Improvements (#35979)
 	Embedding Static Front Pages (#34971)
 	Embed Template Changes (#35322, #35630, #34561)
 	Embeds in the Template Hierarchy (#34278) - Themes can now implement embed templates for specific post types and post formats within the confines of the template hierarchy. The embeds template cascade looks like this:
 	* embed-{post-type}-{post_format}.php – First, WordPress looks for a template for the specific post. For example, if its post type is product and it has the audio format, WordPress would look for embed-product-audio.php.
 	* embed-{post-type}.php – If the post type is car, WordPress would look for embed-car.php.
 	* embed.php – WordPress then falls back to embed.php.
 	* Finally, WordPress ultimately falls back to wp-includes/theme-compat/embed.php


 	Add oEmbed support for moments and timelines from Twitter (#36197)

Script Loader
Version 4.5 enhanced the script loader and script/style dependencies.

 	Individual stylesheets instead of wp-admin.min.css (#35229)
 	HTTP ETag header for load-scripts.php and load-styles.php (#28722)
 	wp_add_inline_script() (#14853)
 	Scripts/Styles with "alias" handles (#35643, #25247, #35229)
 	Support for scripts with dependencies in different groups (#35873)

Bug Fixes

 	Support Windows shares/DFS roots in wp_normalize_path() (#35996)
 	OPTIONS request to REST API does not return correct Accept header (#35975])

Multisite

 	New WP_Site class (#32450) – More object-oriented approach for managing sites in Multisite.

Classes
What's New

 	WP_Upgrader::create_lock()
 	WP_Upgrader::release_lock()


 	WP_Customize_Manager::get_nonces()
 	WP_Customize_Manager::get_previewable_devices()
 	WP_Customize_Manager::_render_custom_logo_partial()


 	WP_Customize_Nav_Menus::filter_nonces()
 	WP_Customize_Nav_Menus::customize_dynamic_partial_args()
 	WP_Customize_Nav_Menus::export_partial_rendered_nav_menu_instances()


 	WP_Customize_Widgets::get_selective_refreshable_widgets()
 	WP_Customize_Widgets::is_widget_selective_refreshable()
 	WP_Customize_Widgets::customize_dynamic_partial_args()
 	WP_Customize_Widgets::selective_refresh_init()
 	WP_Customize_Widgets::filter_wp_kses_allowed_data_attributes()
 	WP_Customize_Widgets::start_dynamic_sidebar()
 	WP_Customize_Widgets::end_dynamic_sidebar()
 	WP_Customize_Widgets::filter_sidebars_widgets_for_rendering_widget()
 	WP_Customize_Widgets::render_widget_partial()


 	WP_Image_Editor_Imagick::thumbnail_image()
 	WP_Image_Editor_Imagick::strip_meta()


 	WP_Metadata_Lazyloader


 	WP_Rewrite::remove_rewrite_tag()
 	WP_Rewrite::remove_permastruct()


 	WP_Site


 	WP::remove_query_var()


 	WP_Scripts::add_inline_script()
 	WP_Scripts::print_inline_script()


 	wpdb::close()


 	WP_Customize_Partial


 	WP_Customize_Selective_Refresh


 	WP_Customize_Site_Icon_Control::content_template()


 	WP_REST_Request::from_url()


 	WP_REST_Response::get_curies()


 	WP_REST_Server::get_compact_response_links()

Deprecated

 	WP_Query::is_comments_popup()


 	WP_Customize_Nav_Menus_Panel::wp_nav_menu_manage_columns()

Functions
What's New

 	wp_queue_comments_for_comment_meta_lazyload()
 	wp_get_comment_fields_max_lengths()
 	the_embed_site_title()
 	wp_get_raw_referer()
 	wp_get_upload_dir()
 	wp_add_inline_script()
 	has_custom_logo()
 	get_custom_logo()
 	the_custom_logo()
 	wp_metadata_lazyloader()
 	unregister_post_type()
 	get_post_types_by_support()
 	wp_queue_posts_for_term_meta_lazyload()
 	wp_add_trashed_suffix_to_post_name_for_trashed_posts()
 	wp_add_trashed_suffix_to_post_name_for_post()
 	rest_get_server()
 	_wp_post_revision_data()
 	remove_rewrite_tag()
 	remove_permastruct()
 	unregister_taxonomy()
 	get_embed_template()
 	_custom_logo_header_styles()
 	wp_authenticate_email_password()
 	_wp_get_current_user()

Deprecated

 	add_object_page()
 	add_utility_page()
 	get_comments_popup_template()
 	is_comments_popup()
 	comments_popup_script()
 	popuplinks()
 	_wp_upload_dir_baseurl()
 	get_currentuserinfo()

Actions & Filters
New Actions

 	{taxonomy}_term_edit_form_top
 	pre_uninstall_plugin
 	pre_network_site_new_created_user
 	network_site_new_form
 	network_user_new_form
 	clean_comment_cache
 	unregistered_post_type
 	unregistered_taxonomy

New Filters

 	press_this_save_post
 	customize_previewable_devices
 	customize_nav_menu_searched_items
 	image_strip_meta
 	network_allowed_themes
 	site_allowed_themes
 	pre_handle_404
 	comments_template_query_args
 	wp_get_comment_fields_max_lengths
 	pre_wp_update_comment_count_now
 	wp_unique_filename
 	get_custom_logo
 	rest_request_from_url
 	rest_response_link_curies

See also: other WordPress Versions.
In other languages
[codex_languages en="Version 4.5" ja_codex="Version 4.5"]