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.

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

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`