For Version 5.5, the database version (db_version in wp_options) updated to 48748, and the Trac revision was 48786.

You can find the full list of tickets included in 5.5 on Trac.

The WordPress 5.5 Field Guide has pertinent, in-depth information on the major technical changes for this release.

Installation/Update Information

To download WordPress 5.5, update automatically from the Dashboard > Updates menu in your site’s admin area or visit the release archive.

For step-by-step instructions on installing and updating WordPress:

• Updating WordPress

If you’re new to WordPress, you’ll want to start by reading these:

• New To WordPress – Where to Start
• First Steps With WordPress or Upgrading WordPress Extended
• WordPress Lessons

Highlights #

Speed #

Posts and pages feel faster, thanks to lazy-loaded images.

Images give your story a lot of impact, but they can sometimes make your site seem slow.

In WordPress 5.5, images wait to load until they’re just about to scroll into view. The technical term is ‘lazy loading.’

On mobile, lazy loading can also keep browsers from loading files meant for other devices. That can save your readers money on data — and help preserve battery life.

Top ↑

Search #

Say hello to your new sitemap.

WordPress sites work well with search engines.

Now, by default, WordPress 5.5 includes an XML sitemap that helps search engines discover your most important pages from the very minute you go live.

So more people will find your site sooner, giving you more time to engage, retain and convert them to subscribers, customers or whatever fits your definition of success.

Top ↑

Security #

Auto-updates for Plugins and Themes

Now you can set plugins and themes to update automatically — or not! — in the WordPress admin. So you always know your site is running the latest code available.

You can also turn auto-updates on or off for each plugin or theme you have installed — all on the same screens you’ve always used.

Update by uploading ZIP files

If updating plugins and themes manually is your thing, now that’s easier too — just upload a ZIP file.

Top ↑

Highlights from the block editor #

Block patterns #

New block patterns make it simple and fun to create complex, beautiful layouts, using combinations of text and media that you can mix and match to fit your story.

You will also find block patterns in a wide variety of plugins and themes, with more added all the time. Pick any of them from a single place — just click and go!

Top ↑

Inline image editing #

Crop, rotate, and zoom your photos right from the image block. If you spend a lot of time on images, this could save you hours!

Top ↑

The New Block Directory #

Now it’s easier than ever to find the block you need. The new block directory is built right into the block editor, so you can install new block types to your site without ever leaving the editor.

Top ↑

And so much more. #

The highlights above are a tiny fraction of the new block editor features you’ve just installed. Open the block editor and enjoy!

Top ↑

Accessibility

Every release adds improvements to the accessible publishing experience, and that remains true for WordPress 5.5.

Now you can copy links in media screens and modal dialogs with a button, instead of trying to highlight a line of text.

You can also move meta boxes with the keyboard, and edit images in WordPress with your assistive device, as it can read you the instructions in the image editor.

Top ↑

For developers #

5.5 also brings a big box of changes just for developers.

Top ↑

Server-side registered blocks in the REST API #

The addition of block types endpoints means that JavaScript apps (like the block editor) can retrieve definitions for any blocks registered on the server.

Top ↑

Dashicons #

The Dashicons library has received its final update in 5.5. It adds 39 block editor icons along with 26 others.

Top ↑

Defining environments #

WordPress now has a standardized way to define a site’s environment type (staging, production, etc). Retrieve that type with wp_get_environment_type() and execute only the appropriate code.

Top ↑

Passing data to template files #

The template loading functions (get_header(), get_template_part(), etc.) have a new $args argument. So now you can pass an entire array’s worth of data to those templates.

Top ↑

More changes for developers #

• The PHPMailer library just got a major update, going from version 5.2.27 to 6.1.6.
• Now get more fine-grained control of redirect_guess_404_permalink().
• Sites that use PHP’s OPcache will see more reliable cache invalidation, thanks to the new wp_opcache_invalidate() function during updates (including to plugins and themes).
• Custom post types associated with the category taxonomy can now opt-in to supporting the default term.
• Default terms can now be specified for custom taxonomies in register_taxonomy().
• The REST API now officially supports specifying default metadata values through register_meta().
• You will find updated versions of these bundled libraries: SimplePie, Twemoji, Masonry, imagesLoaded, getID3, Moment.js, and clipboard.js.

Top ↑

Developer notes #

There’s a lot more for developers to love in WordPress 5.5. To discover more and learn how to make these changes shine on your sites, themes, plugins and more, check the WordPress 5.5 Field Guide.

Here is the complete list of all the developer notes published:

• Accessibility:
  • Accessibility improvements to widgets outputting lists of links in 5.5
• Auto-updates (Security):
  • Controlling Plugin and Theme auto-updates UI in WordPress 5.5
  • Controlling Plugin and Theme auto-update email notifications and Site Health infos in WP 5.5
  • Recommended usage of the Updates API to support the auto-updates UI for Plugins and Themes in WordPress 5.5
• Changes related to the Block Editor:
  • WordPress 5.5 Core Editor Accessibility Improvements
  • New editor preview options
  • Block API Updates in 5.5
  • Block Patterns in WordPress 5.5
  • Editing Images in the Block Editor
  • New Block Tools on WordPress 5.5
  • Various changes to WordPress React Components in WordPress 5.5
  • Proposed Block Directory guidelines
  • You can now add your own plugins to the Block Directory
• Customizer:
  • Themes: changes related to get_custom_logo() in WordPress 5.5
• Media:
  • Lazy-loading images in 5.5
• REST API:
  • REST API changes in WordPress 5.5
  • Register theme feature API
• Options, Meta APIs
  • Registering default values for meta data
• Sitemaps
  • New XML Sitemaps Functionality in WordPress 5.5
  • New esc_xml() function in WordPress 5.5
• Themes
  • Themes field guide: WordPress 5.5
• Other developer updates:
  • Miscellaneous Developer Focused Changes in WordPress 5.5
  • External Library updates in WordPress 5.5: call for testing
  • Passing arguments to template files in WordPress 5.5
  • Opcode Cache Invalidation in WordPress 5.5
  • Filtering archive page headings in WordPress 5.5
  • Introducing createInterpolateElement
  • New wp_get_environment_type() function in WordPress 5.5
  • WordPress 5.5: Better fine grained control of redirect_guess_404_permalink()
  • New CSS styles for buttons with disabled state in WP 5.5
  • Dashicons in WordPress 5.5 (the final update)
  • PHP related improvements & changes: WordPress 5.5 edition

Top ↑

The squad #

This release was led by Matt Mullenweg, with a great squad of supporting characters:

• Release Coordinator: Jake Spurlock (@whyisjake)
• Triage PM: David Baumvald (@davidbaumwald)
• Editor Tech: Ella Van Durpe (@ellatrix)
• Editor Design: Michael Arestad (@michael-arestad)
• Core Tech: Sergey Biryukov (@sergeybiryukov)
• Media Tech: Andrew Ozz (@azaozz)
• Accessibility: Jb Audras (@audrasjb)
• Docs Coordinator: Justin Ahinon (@justinahinon)
• Marketing/Comms Coordinator: Mary Baum (@marybaum)

Thank you to all who contributed to WordPress 5.5.

Top ↑

List of files revised #

readme.html
wp-activate.php
wp-admin/about.php
wp-admin/admin-ajax.php
wp-admin/admin-header.php
wp-admin/admin.php
wp-admin/async-upload.php
wp-admin/comment.php
wp-admin/credits.php
wp-admin/css/about-rtl.css
wp-admin/css/about-rtl.min.css
wp-admin/css/about.css
wp-admin/css/about.min.css
wp-admin/css/admin-menu-rtl.css
wp-admin/css/admin-menu-rtl.min.css
wp-admin/css/admin-menu.css
wp-admin/css/admin-menu.min.css
wp-admin/css/color-picker-rtl.css
wp-admin/css/color-picker-rtl.min.css
wp-admin/css/color-picker.css
wp-admin/css/color-picker.min.css
wp-admin/css/colors/_admin.scss
wp-admin/css/colors/_mixins.scss
wp-admin/css/colors/_variables.scss
wp-admin/css/colors/blue/colors-rtl.css
wp-admin/css/colors/blue/colors-rtl.min.css
wp-admin/css/colors/blue/colors.css
wp-admin/css/colors/blue/colors.min.css
wp-admin/css/colors/coffee/colors-rtl.css
wp-admin/css/colors/coffee/colors-rtl.min.css
wp-admin/css/colors/coffee/colors.css
wp-admin/css/colors/coffee/colors.min.css
wp-admin/css/colors/coffee/colors.scss
wp-admin/css/colors/ectoplasm/colors-rtl.css
wp-admin/css/colors/ectoplasm/colors-rtl.min.css
wp-admin/css/colors/ectoplasm/colors.css
wp-admin/css/colors/ectoplasm/colors.min.css
wp-admin/css/colors/light/colors-rtl.css
wp-admin/css/colors/light/colors-rtl.min.css
wp-admin/css/colors/light/colors.css
wp-admin/css/colors/light/colors.min.css
wp-admin/css/colors/midnight/colors-rtl.css
wp-admin/css/colors/midnight/colors-rtl.min.css
wp-admin/css/colors/midnight/colors.css
wp-admin/css/colors/midnight/colors.min.css
wp-admin/css/colors/ocean/colors-rtl.css
wp-admin/css/colors/ocean/colors-rtl.min.css
wp-admin/css/colors/ocean/colors.css
wp-admin/css/colors/ocean/colors.min.css
wp-admin/css/colors/ocean/colors.scss
wp-admin/css/colors/sunrise/colors-rtl.css
wp-admin/css/colors/sunrise/colors-rtl.min.css
wp-admin/css/colors/sunrise/colors.css
wp-admin/css/colors/sunrise/colors.min.css
wp-admin/css/common-rtl.css
wp-admin/css/common-rtl.min.css
wp-admin/css/common.css
wp-admin/css/common.min.css
wp-admin/css/customize-controls-rtl.css
wp-admin/css/customize-controls-rtl.min.css
wp-admin/css/customize-controls.css
wp-admin/css/customize-controls.min.css
wp-admin/css/customize-nav-menus-rtl.css
wp-admin/css/customize-nav-menus-rtl.min.css
wp-admin/css/customize-nav-menus.css
wp-admin/css/customize-nav-menus.min.css
wp-admin/css/dashboard-rtl.css
wp-admin/css/dashboard-rtl.min.css
wp-admin/css/dashboard.css
wp-admin/css/dashboard.min.css
wp-admin/css/deprecated-media-rtl.css
wp-admin/css/deprecated-media-rtl.min.css
wp-admin/css/deprecated-media.min.css
wp-admin/css/edit-rtl.css
wp-admin/css/edit-rtl.min.css
wp-admin/css/edit.css
wp-admin/css/edit.min.css
wp-admin/css/forms-rtl.css
wp-admin/css/forms-rtl.min.css
wp-admin/css/forms.css
wp-admin/css/forms.min.css
wp-admin/css/ie-rtl.css
wp-admin/css/ie-rtl.min.css
wp-admin/css/ie.css
wp-admin/css/ie.min.css
wp-admin/css/install-rtl.css
wp-admin/css/install-rtl.min.css
wp-admin/css/install.css
wp-admin/css/install.min.css
wp-admin/css/list-tables-rtl.css
wp-admin/css/list-tables-rtl.min.css
wp-admin/css/list-tables.css
wp-admin/css/list-tables.min.css
wp-admin/css/login-rtl.css
wp-admin/css/login-rtl.min.css
wp-admin/css/login.css
wp-admin/css/login.min.css
wp-admin/css/media-rtl.css
wp-admin/css/media-rtl.min.css
wp-admin/css/media.css
wp-admin/css/media.min.css
wp-admin/css/nav-menus-rtl.css
wp-admin/css/nav-menus-rtl.min.css
wp-admin/css/nav-menus.css
wp-admin/css/nav-menus.min.css
wp-admin/css/revisions-rtl.css
wp-admin/css/revisions-rtl.min.css
wp-admin/css/revisions.css
wp-admin/css/revisions.min.css
wp-admin/css/site-health-rtl.css
wp-admin/css/site-health-rtl.min.css
wp-admin/css/site-health.css
wp-admin/css/site-health.min.css
wp-admin/css/themes-rtl.css
wp-admin/css/themes-rtl.min.css
wp-admin/css/themes.css
wp-admin/css/themes.min.css
wp-admin/css/widgets-rtl.css
wp-admin/css/widgets-rtl.min.css
wp-admin/css/widgets.css
wp-admin/css/widgets.min.css
wp-admin/customize.php
wp-admin/edit-comments.php
wp-admin/edit-form-advanced.php
wp-admin/edit-form-blocks.php
wp-admin/edit-form-comment.php
wp-admin/edit-link-form.php
wp-admin/edit-tag-form.php
wp-admin/edit-tags.php
wp-admin/edit.php
wp-admin/erase-personal-data.php
wp-admin/export-personal-data.php
wp-admin/export.php
wp-admin/freedoms.php
wp-admin/import.php
wp-admin/includes/admin-filters.php
wp-admin/includes/ajax-actions.php
wp-admin/includes/bookmark.php
wp-admin/includes/class-core-upgrader.php
wp-admin/includes/class-custom-background.php
wp-admin/includes/class-custom-image-header.php
wp-admin/includes/class-ftp.php
wp-admin/includes/class-language-pack-upgrader.php
wp-admin/includes/class-plugin-installer-skin.php
wp-admin/includes/class-plugin-upgrader-skin.php
wp-admin/includes/class-plugin-upgrader.php
wp-admin/includes/class-theme-installer-skin.php
wp-admin/includes/class-theme-upgrader-skin.php
wp-admin/includes/class-theme-upgrader.php
wp-admin/includes/class-walker-category-checklist.php
wp-admin/includes/class-walker-nav-menu-checklist.php
wp-admin/includes/class-walker-nav-menu-edit.php
wp-admin/includes/class-wp-ajax-upgrader-skin.php
wp-admin/includes/class-wp-automatic-updater.php
wp-admin/includes/class-wp-comments-list-table.php
wp-admin/includes/class-wp-community-events.php
wp-admin/includes/class-wp-debug-data.php
wp-admin/includes/class-wp-filesystem-base.php
wp-admin/includes/class-wp-filesystem-direct.php
wp-admin/includes/class-wp-filesystem-ftpext.php
wp-admin/includes/class-wp-filesystem-ftpsockets.php
wp-admin/includes/class-wp-filesystem-ssh2.php
wp-admin/includes/class-wp-importer.php
wp-admin/includes/class-wp-links-list-table.php
wp-admin/includes/class-wp-list-table.php
wp-admin/includes/class-wp-media-list-table.php
wp-admin/includes/class-wp-ms-sites-list-table.php
wp-admin/includes/class-wp-ms-themes-list-table.php
wp-admin/includes/class-wp-ms-users-list-table.php
wp-admin/includes/class-wp-plugin-install-list-table.php
wp-admin/includes/class-wp-plugins-list-table.php
wp-admin/includes/class-wp-posts-list-table.php
wp-admin/includes/class-wp-privacy-policy-content.php
wp-admin/includes/class-wp-privacy-requests-table.php
wp-admin/includes/class-wp-screen.php
wp-admin/includes/class-wp-site-health-auto-updates.php
wp-admin/includes/class-wp-site-health.php
wp-admin/includes/class-wp-terms-list-table.php
wp-admin/includes/class-wp-theme-install-list-table.php
wp-admin/includes/class-wp-themes-list-table.php
wp-admin/includes/class-wp-upgrader-skin.php
wp-admin/includes/class-wp-upgrader.php
wp-admin/includes/class-wp-users-list-table.php
wp-admin/includes/comment.php
wp-admin/includes/dashboard.php
wp-admin/includes/deprecated.php
wp-admin/includes/export.php
wp-admin/includes/file.php
wp-admin/includes/image-edit.php
wp-admin/includes/image.php
wp-admin/includes/list-table.php
wp-admin/includes/media.php
wp-admin/includes/menu.php
wp-admin/includes/meta-boxes.php
wp-admin/includes/misc.php
wp-admin/includes/ms.php
wp-admin/includes/nav-menu.php
wp-admin/includes/network.php
wp-admin/includes/options.php
wp-admin/includes/plugin-install.php
wp-admin/includes/plugin.php
wp-admin/includes/post.php
wp-admin/includes/privacy-tools.php
wp-admin/includes/revision.php
wp-admin/includes/schema.php
wp-admin/includes/screen.php
wp-admin/includes/taxonomy.php
wp-admin/includes/template.php
wp-admin/includes/theme-install.php
wp-admin/includes/theme.php
wp-admin/includes/translation-install.php
wp-admin/includes/update-core.php
wp-admin/includes/update.php
wp-admin/includes/upgrade.php
wp-admin/includes/user.php
wp-admin/includes/widgets.php
wp-admin/index.php
wp-admin/install-helper.php
wp-admin/install.php
wp-admin/js/code-editor.js
wp-admin/js/color-picker.js
wp-admin/js/color-picker.min.js
wp-admin/js/comment.js
wp-admin/js/comment.min.js
wp-admin/js/common.js
wp-admin/js/common.min.js
wp-admin/js/custom-background.js
wp-admin/js/customize-controls.js
wp-admin/js/customize-controls.min.js
wp-admin/js/customize-nav-menus.js
wp-admin/js/customize-nav-menus.min.js
wp-admin/js/customize-widgets.js
wp-admin/js/customize-widgets.min.js
wp-admin/js/dashboard.js
wp-admin/js/edit-comments.js
wp-admin/js/edit-comments.min.js
wp-admin/js/editor-expand.js
wp-admin/js/editor.js
wp-admin/js/image-edit.js
wp-admin/js/image-edit.min.js
wp-admin/js/inline-edit-post.js
wp-admin/js/inline-edit-post.min.js
wp-admin/js/inline-edit-tax.js
wp-admin/js/inline-edit-tax.min.js
wp-admin/js/media-gallery.js
wp-admin/js/media.js
wp-admin/js/media.min.js
wp-admin/js/nav-menu.js
wp-admin/js/nav-menu.min.js
wp-admin/js/password-strength-meter.js
wp-admin/js/password-strength-meter.min.js
wp-admin/js/plugin-install.js
wp-admin/js/plugin-install.min.js
wp-admin/js/post.js
wp-admin/js/post.min.js
wp-admin/js/postbox.js
wp-admin/js/postbox.min.js
wp-admin/js/privacy-tools.js
wp-admin/js/privacy-tools.min.js
wp-admin/js/set-post-thumbnail.js
wp-admin/js/set-post-thumbnail.min.js
wp-admin/js/site-health.js
wp-admin/js/site-health.min.js
wp-admin/js/tags-box.js
wp-admin/js/tags-box.min.js
wp-admin/js/tags-suggest.js
wp-admin/js/tags-suggest.min.js
wp-admin/js/tags.js
wp-admin/js/tags.min.js
wp-admin/js/theme-plugin-editor.js
wp-admin/js/theme-plugin-editor.min.js
wp-admin/js/theme.js
wp-admin/js/theme.min.js
wp-admin/js/updates.js
wp-admin/js/updates.min.js
wp-admin/js/user-profile.js
wp-admin/js/user-profile.min.js
wp-admin/js/widgets.js
wp-admin/js/widgets.min.js
wp-admin/js/widgets/custom-html-widgets.js
wp-admin/js/widgets/media-widgets.js
wp-admin/js/word-count.js
wp-admin/link-manager.php
wp-admin/link-parse-opml.php
wp-admin/link.php
wp-admin/load-scripts.php
wp-admin/load-styles.php
wp-admin/maint/repair.php
wp-admin/media-upload.php
wp-admin/media.php
wp-admin/menu-header.php
wp-admin/menu.php
wp-admin/ms-delete-site.php
wp-admin/my-sites.php
wp-admin/nav-menus.php
wp-admin/network.php
wp-admin/network/edit.php
wp-admin/network/plugin-install.php
wp-admin/network/settings.php
wp-admin/network/site-info.php
wp-admin/network/site-new.php
wp-admin/network/site-settings.php
wp-admin/network/site-themes.php
wp-admin/network/site-users.php
wp-admin/network/sites.php
wp-admin/network/theme-install.php
wp-admin/network/themes.php
wp-admin/network/update.php
wp-admin/network/upgrade.php
wp-admin/network/user-new.php
wp-admin/network/users.php
wp-admin/options-discussion.php
wp-admin/options-general.php
wp-admin/options-media.php
wp-admin/options-permalink.php
wp-admin/options-reading.php
wp-admin/options-writing.php
wp-admin/options.php
wp-admin/plugin-editor.php
wp-admin/plugin-install.php
wp-admin/plugins.php
wp-admin/post-new.php
wp-admin/post.php
wp-admin/privacy.php
wp-admin/revision.php
wp-admin/setup-config.php
wp-admin/site-health-info.php
wp-admin/site-health.php
wp-admin/term.php
wp-admin/theme-editor.php
wp-admin/theme-install.php
wp-admin/themes.php
wp-admin/update-core.php
wp-admin/update.php
wp-admin/upgrade.php
wp-admin/upload.php
wp-admin/user-edit.php
wp-admin/user-new.php
wp-admin/users.php
wp-comments-post.php
wp-content/plugins/akismet/_inc/akismet.css
wp-content/plugins/akismet/_inc/akismet.js
wp-content/plugins/akismet/akismet.php
wp-content/plugins/akismet/class.akismet-admin.php
wp-content/plugins/akismet/readme.txt
wp-content/plugins/akismet/views/notice.php
wp-content/themes/twentynineteen/classes/class-twentynineteen-svg-icons.php
wp-content/themes/twentynineteen/inc/customizer.php
wp-content/themes/twentynineteen/inc/icon-functions.php
wp-content/themes/twentynineteen/inc/template-functions.php
wp-content/themes/twentynineteen/inc/template-tags.php
wp-content/themes/twentynineteen/package-lock.json
wp-content/themes/twentynineteen/package.json
wp-content/themes/twentynineteen/readme.txt
wp-content/themes/twentynineteen/sass/blocks/_blocks.scss
wp-content/themes/twentynineteen/sass/mixins/_mixins-master.scss
wp-content/themes/twentynineteen/sass/navigation/_menu-main-navigation.scss
wp-content/themes/twentynineteen/sass/site/secondary/_widgets.scss
wp-content/themes/twentynineteen/style-editor.css
wp-content/themes/twentynineteen/style-editor.scss
wp-content/themes/twentynineteen/style-rtl.css
wp-content/themes/twentynineteen/style.css
wp-content/themes/twentynineteen/style.scss
wp-content/themes/twentyseventeen/assets/images/svg-icons.svg
wp-content/themes/twentyseventeen/functions.php
wp-content/themes/twentyseventeen/header.php
wp-content/themes/twentyseventeen/inc/custom-header.php
wp-content/themes/twentyseventeen/inc/customizer.php
wp-content/themes/twentyseventeen/inc/icon-functions.php
wp-content/themes/twentyseventeen/inc/template-tags.php
wp-content/themes/twentyseventeen/readme.txt
wp-content/themes/twentyseventeen/style.css
wp-content/themes/twentyseventeen/template-parts/page/content-front-page.php
wp-content/themes/twentytwenty/assets/css/editor-style-block-rtl.css
wp-content/themes/twentytwenty/assets/css/editor-style-block.css
wp-content/themes/twentytwenty/assets/js/customize-controls.js
wp-content/themes/twentytwenty/assets/js/index.js
wp-content/themes/twentytwenty/classes/class-twentytwenty-customize.php
wp-content/themes/twentytwenty/classes/class-twentytwenty-non-latin-languages.php
wp-content/themes/twentytwenty/classes/class-twentytwenty-svg-icons.php
wp-content/themes/twentytwenty/comments.php
wp-content/themes/twentytwenty/functions.php
wp-content/themes/twentytwenty/inc/starter-content.php
wp-content/themes/twentytwenty/inc/template-tags.php
wp-content/themes/twentytwenty/index.php
wp-content/themes/twentytwenty/package-lock.json
wp-content/themes/twentytwenty/package.json
wp-content/themes/twentytwenty/readme.txt
wp-content/themes/twentytwenty/style-rtl.css
wp-content/themes/twentytwenty/style.css
wp-content/themes/twentytwenty/template-parts/content-cover.php
wp-content/themes/twentytwenty/template-parts/content.php
wp-content/themes/twentytwenty/template-parts/entry-header.php
wp-content/themes/twentytwenty/template-parts/featured-image.php
wp-includes/ID3/getid3.lib.php
wp-includes/ID3/getid3.php
wp-includes/ID3/module.audio-video.asf.php
wp-includes/ID3/module.audio-video.flv.php
wp-includes/ID3/module.audio-video.matroska.php
wp-includes/ID3/module.audio-video.quicktime.php
wp-includes/ID3/module.audio-video.riff.php
wp-includes/ID3/module.audio.ac3.php
wp-includes/ID3/module.audio.dts.php
wp-includes/ID3/module.audio.flac.php
wp-includes/ID3/module.audio.mp3.php
wp-includes/ID3/module.audio.ogg.php
wp-includes/ID3/module.tag.apetag.php
wp-includes/ID3/module.tag.id3v1.php
wp-includes/ID3/module.tag.id3v2.php
wp-includes/ID3/module.tag.lyrics3.php
wp-includes/IXR/class-IXR-client.php
wp-includes/IXR/class-IXR-clientmulticall.php
wp-includes/IXR/class-IXR-message.php
wp-includes/IXR/class-IXR-server.php
wp-includes/Requests/SSL.php
wp-includes/SimplePie/Author.php
wp-includes/SimplePie/Cache.php
wp-includes/SimplePie/Cache/Base.php
wp-includes/SimplePie/Cache/DB.php
wp-includes/SimplePie/Cache/File.php
wp-includes/SimplePie/Cache/Memcache.php
wp-includes/SimplePie/Cache/MySQL.php
wp-includes/SimplePie/Caption.php
wp-includes/SimplePie/Category.php
wp-includes/SimplePie/Content/Type/Sniffer.php
wp-includes/SimplePie/Copyright.php
wp-includes/SimplePie/Core.php
wp-includes/SimplePie/Credit.php
wp-includes/SimplePie/Decode/HTML/Entities.php
wp-includes/SimplePie/Enclosure.php
wp-includes/SimplePie/Exception.php
wp-includes/SimplePie/File.php
wp-includes/SimplePie/HTTP/Parser.php
wp-includes/SimplePie/IRI.php
wp-includes/SimplePie/Item.php
wp-includes/SimplePie/Locator.php
wp-includes/SimplePie/Misc.php
wp-includes/SimplePie/Net/IPv6.php
wp-includes/SimplePie/Parse/Date.php
wp-includes/SimplePie/Parser.php
wp-includes/SimplePie/Rating.php
wp-includes/SimplePie/Registry.php
wp-includes/SimplePie/Restriction.php
wp-includes/SimplePie/Sanitize.php
wp-includes/SimplePie/Source.php
wp-includes/SimplePie/XML/Declaration/Parser.php
wp-includes/SimplePie/gzdecode.php
wp-includes/Text/Diff/Engine/shell.php
wp-includes/admin-bar.php
wp-includes/assets/script-loader-packages.php
wp-includes/atomlib.php
wp-includes/author-template.php
wp-includes/blocks.php
wp-includes/blocks/archives.php
wp-includes/blocks/block.php
wp-includes/blocks/calendar.php
wp-includes/blocks/categories.php
wp-includes/blocks/latest-comments.php
wp-includes/blocks/latest-posts.php
wp-includes/blocks/rss.php
wp-includes/blocks/search.php
wp-includes/blocks/shortcode.php
wp-includes/blocks/shortcode/block.json
wp-includes/blocks/social-link.php
wp-includes/blocks/social-link/block.json
wp-includes/blocks/tag-cloud.php
wp-includes/bookmark-template.php
wp-includes/bookmark.php
wp-includes/cache.php
wp-includes/canonical.php
wp-includes/capabilities.php
wp-includes/category-template.php
wp-includes/category.php
wp-includes/certificates/ca-bundle.crt
wp-includes/class-http.php
wp-includes/class-phpmailer.php
wp-includes/class-pop3.php
wp-includes/class-requests.php
wp-includes/class-simplepie.php
wp-includes/class-smtp.php
wp-includes/class-snoopy.php
wp-includes/class-walker-category.php
wp-includes/class-walker-comment.php
wp-includes/class-walker-page.php
wp-includes/class-wp-admin-bar.php
wp-includes/class-wp-ajax-response.php
wp-includes/class-wp-block-type-registry.php
wp-includes/class-wp-block-type.php
wp-includes/class-wp-comment-query.php
wp-includes/class-wp-comment.php
wp-includes/class-wp-customize-control.php
wp-includes/class-wp-customize-manager.php
wp-includes/class-wp-customize-nav-menus.php
wp-includes/class-wp-customize-panel.php
wp-includes/class-wp-customize-setting.php
wp-includes/class-wp-customize-widgets.php
wp-includes/class-wp-date-query.php
wp-includes/class-wp-dependency.php
wp-includes/class-wp-editor.php
wp-includes/class-wp-embed.php
wp-includes/class-wp-error.php
wp-includes/class-wp-fatal-error-handler.php
wp-includes/class-wp-http-cookie.php
wp-includes/class-wp-http-curl.php
wp-includes/class-wp-http-encoding.php
wp-includes/class-wp-http-ixr-client.php
wp-includes/class-wp-http-proxy.php
wp-includes/class-wp-http-requests-hooks.php
wp-includes/class-wp-http-streams.php
wp-includes/class-wp-image-editor-gd.php
wp-includes/class-wp-image-editor-imagick.php
wp-includes/class-wp-image-editor.php
wp-includes/class-wp-list-util.php
wp-includes/class-wp-locale.php
wp-includes/class-wp-matchesmapregex.php
wp-includes/class-wp-meta-query.php
wp-includes/class-wp-network-query.php
wp-includes/class-wp-object-cache.php
wp-includes/class-wp-oembed-controller.php
wp-includes/class-wp-oembed.php
wp-includes/class-wp-paused-extensions-storage.php
wp-includes/class-wp-post-type.php
wp-includes/class-wp-query.php
wp-includes/class-wp-recovery-mode-email-service.php
wp-includes/class-wp-recovery-mode-key-service.php
wp-includes/class-wp-recovery-mode.php
wp-includes/class-wp-rewrite.php
wp-includes/class-wp-role.php
wp-includes/class-wp-roles.php
wp-includes/class-wp-site-query.php
wp-includes/class-wp-tax-query.php
wp-includes/class-wp-taxonomy.php
wp-includes/class-wp-term-query.php
wp-includes/class-wp-text-diff-renderer-table.php
wp-includes/class-wp-theme.php
wp-includes/class-wp-user-query.php
wp-includes/class-wp-user-request.php
wp-includes/class-wp-user.php
wp-includes/class-wp-walker.php
wp-includes/class-wp-widget.php
wp-includes/class-wp-xmlrpc-server.php
wp-includes/class-wp.php
wp-includes/class.wp-dependencies.php
wp-includes/class.wp-scripts.php
wp-includes/class.wp-styles.php
wp-includes/comment-template.php
wp-includes/comment.php
wp-includes/compat.php
wp-includes/cron.php
wp-includes/css/admin-bar-rtl.css
wp-includes/css/admin-bar-rtl.min.css
wp-includes/css/admin-bar.css
wp-includes/css/admin-bar.min.css
wp-includes/css/buttons-rtl.css
wp-includes/css/buttons-rtl.min.css
wp-includes/css/buttons.css
wp-includes/css/buttons.min.css
wp-includes/css/dashicons.css
wp-includes/css/dashicons.min.css
wp-includes/css/dist/block-directory/style-rtl.css
wp-includes/css/dist/block-directory/style-rtl.min.css
wp-includes/css/dist/block-directory/style.css
wp-includes/css/dist/block-directory/style.min.css
wp-includes/css/dist/block-editor/style-rtl.css
wp-includes/css/dist/block-editor/style-rtl.min.css
wp-includes/css/dist/block-editor/style.css
wp-includes/css/dist/block-editor/style.min.css
wp-includes/css/dist/block-library/editor-rtl.css
wp-includes/css/dist/block-library/editor-rtl.min.css
wp-includes/css/dist/block-library/editor.css
wp-includes/css/dist/block-library/editor.min.css
wp-includes/css/dist/block-library/style-rtl.css
wp-includes/css/dist/block-library/style-rtl.min.css
wp-includes/css/dist/block-library/style.css
wp-includes/css/dist/block-library/style.min.css
wp-includes/css/dist/block-library/theme-rtl.css
wp-includes/css/dist/block-library/theme-rtl.min.css
wp-includes/css/dist/block-library/theme.css
wp-includes/css/dist/block-library/theme.min.css
wp-includes/css/dist/components/style-rtl.css
wp-includes/css/dist/components/style-rtl.min.css
wp-includes/css/dist/components/style.css
wp-includes/css/dist/components/style.min.css
wp-includes/css/dist/edit-post/style-rtl.css
wp-includes/css/dist/edit-post/style-rtl.min.css
wp-includes/css/dist/edit-post/style.css
wp-includes/css/dist/edit-post/style.min.css
wp-includes/css/dist/editor/editor-styles-rtl.css
wp-includes/css/dist/editor/editor-styles-rtl.min.css
wp-includes/css/dist/editor/editor-styles.css
wp-includes/css/dist/editor/editor-styles.min.css
wp-includes/css/dist/editor/style-rtl.css
wp-includes/css/dist/editor/style-rtl.min.css
wp-includes/css/dist/editor/style.css
wp-includes/css/dist/editor/style.min.css
wp-includes/css/dist/format-library/style-rtl.css
wp-includes/css/dist/format-library/style-rtl.min.css
wp-includes/css/dist/format-library/style.css
wp-includes/css/dist/format-library/style.min.css
wp-includes/css/dist/list-reusable-blocks/style-rtl.css
wp-includes/css/dist/list-reusable-blocks/style-rtl.min.css
wp-includes/css/dist/list-reusable-blocks/style.css
wp-includes/css/dist/list-reusable-blocks/style.min.css
wp-includes/css/dist/nux/style-rtl.css
wp-includes/css/dist/nux/style-rtl.min.css
wp-includes/css/dist/nux/style.css
wp-includes/css/dist/nux/style.min.css
wp-includes/css/editor-rtl.css
wp-includes/css/editor-rtl.min.css
wp-includes/css/editor.css
wp-includes/css/editor.min.css
wp-includes/css/jquery-ui-dialog-rtl.css
wp-includes/css/jquery-ui-dialog-rtl.min.css
wp-includes/css/jquery-ui-dialog.css
wp-includes/css/jquery-ui-dialog.min.css
wp-includes/css/media-views-rtl.css
wp-includes/css/media-views-rtl.min.css
wp-includes/css/media-views.css
wp-includes/css/media-views.min.css
wp-includes/css/wp-auth-check-rtl.min.css
wp-includes/css/wp-auth-check.min.css
wp-includes/customize/class-wp-customize-code-editor-control.php
wp-includes/customize/class-wp-customize-custom-css-setting.php
wp-includes/customize/class-wp-customize-date-time-control.php
wp-includes/customize/class-wp-customize-image-control.php
wp-includes/customize/class-wp-customize-media-control.php
wp-includes/customize/class-wp-customize-nav-menu-item-setting.php
wp-includes/customize/class-wp-customize-nav-menu-setting.php
wp-includes/customize/class-wp-customize-partial.php
wp-includes/customize/class-wp-customize-selective-refresh.php
wp-includes/customize/class-wp-customize-theme-control.php
wp-includes/customize/class-wp-customize-themes-section.php
wp-includes/default-constants.php
wp-includes/default-filters.php
wp-includes/deprecated.php
wp-includes/embed.php
wp-includes/error-protection.php
wp-includes/feed-rss2-comments.php
wp-includes/feed.php
wp-includes/fonts/dashicons.eot
wp-includes/fonts/dashicons.svg
wp-includes/fonts/dashicons.ttf
wp-includes/fonts/dashicons.woff2
wp-includes/formatting.php
wp-includes/functions.php
wp-includes/functions.wp-scripts.php
wp-includes/functions.wp-styles.php
wp-includes/general-template.php
wp-includes/http.php
wp-includes/js/admin-bar.js
wp-includes/js/admin-bar.min.js
wp-includes/js/clipboard.js
wp-includes/js/clipboard.min.js
wp-includes/js/comment-reply.js
wp-includes/js/comment-reply.min.js
wp-includes/js/customize-base.js
wp-includes/js/customize-loader.js
wp-includes/js/customize-models.js
wp-includes/js/customize-preview-nav-menus.js
wp-includes/js/customize-preview-widgets.js
wp-includes/js/customize-preview.js
wp-includes/js/customize-selective-refresh.js
wp-includes/js/dist/a11y.js
wp-includes/js/dist/a11y.min.js
wp-includes/js/dist/annotations.js
wp-includes/js/dist/annotations.min.js
wp-includes/js/dist/api-fetch.js
wp-includes/js/dist/api-fetch.min.js
wp-includes/js/dist/autop.js
wp-includes/js/dist/autop.min.js
wp-includes/js/dist/blob.js
wp-includes/js/dist/blob.min.js
wp-includes/js/dist/block-directory.js
wp-includes/js/dist/block-directory.min.js
wp-includes/js/dist/block-editor.js
wp-includes/js/dist/block-editor.min.js
wp-includes/js/dist/block-library.js
wp-includes/js/dist/block-library.min.js
wp-includes/js/dist/block-serialization-default-parser.js
wp-includes/js/dist/block-serialization-default-parser.min.js
wp-includes/js/dist/blocks.js
wp-includes/js/dist/blocks.min.js
wp-includes/js/dist/components.js
wp-includes/js/dist/components.min.js
wp-includes/js/dist/compose.js
wp-includes/js/dist/compose.min.js
wp-includes/js/dist/core-data.js
wp-includes/js/dist/core-data.min.js
wp-includes/js/dist/data-controls.js
wp-includes/js/dist/data-controls.min.js
wp-includes/js/dist/data.js
wp-includes/js/dist/data.min.js
wp-includes/js/dist/date.js
wp-includes/js/dist/date.min.js
wp-includes/js/dist/deprecated.js
wp-includes/js/dist/deprecated.min.js
wp-includes/js/dist/dom-ready.js
wp-includes/js/dist/dom-ready.min.js
wp-includes/js/dist/dom.js
wp-includes/js/dist/dom.min.js
wp-includes/js/dist/edit-post.js
wp-includes/js/dist/edit-post.min.js
wp-includes/js/dist/editor.js
wp-includes/js/dist/editor.min.js
wp-includes/js/dist/element.js
wp-includes/js/dist/element.min.js
wp-includes/js/dist/escape-html.js
wp-includes/js/dist/escape-html.min.js
wp-includes/js/dist/format-library.js
wp-includes/js/dist/format-library.min.js
wp-includes/js/dist/hooks.js
wp-includes/js/dist/hooks.min.js
wp-includes/js/dist/html-entities.js
wp-includes/js/dist/html-entities.min.js
wp-includes/js/dist/i18n.js
wp-includes/js/dist/i18n.min.js
wp-includes/js/dist/is-shallow-equal.js
wp-includes/js/dist/is-shallow-equal.min.js
wp-includes/js/dist/keyboard-shortcuts.js
wp-includes/js/dist/keyboard-shortcuts.min.js
wp-includes/js/dist/keycodes.js
wp-includes/js/dist/keycodes.min.js
wp-includes/js/dist/list-reusable-blocks.js
wp-includes/js/dist/list-reusable-blocks.min.js
wp-includes/js/dist/media-utils.js
wp-includes/js/dist/media-utils.min.js
wp-includes/js/dist/notices.js
wp-includes/js/dist/notices.min.js
wp-includes/js/dist/nux.js
wp-includes/js/dist/nux.min.js
wp-includes/js/dist/plugins.js
wp-includes/js/dist/plugins.min.js
wp-includes/js/dist/primitives.js
wp-includes/js/dist/primitives.min.js
wp-includes/js/dist/priority-queue.js
wp-includes/js/dist/priority-queue.min.js
wp-includes/js/dist/redux-routine.js
wp-includes/js/dist/redux-routine.min.js
wp-includes/js/dist/rich-text.js
wp-includes/js/dist/rich-text.min.js
wp-includes/js/dist/server-side-render.js
wp-includes/js/dist/server-side-render.min.js
wp-includes/js/dist/shortcode.js
wp-includes/js/dist/shortcode.min.js
wp-includes/js/dist/token-list.js
wp-includes/js/dist/token-list.min.js
wp-includes/js/dist/url.js
wp-includes/js/dist/url.min.js
wp-includes/js/dist/vendor/lodash.js
wp-includes/js/dist/vendor/lodash.min.js
wp-includes/js/dist/vendor/moment.js
wp-includes/js/dist/vendor/moment.min.js
wp-includes/js/dist/vendor/wp-polyfill.js
wp-includes/js/dist/vendor/wp-polyfill.min.js
wp-includes/js/dist/viewport.js
wp-includes/js/dist/viewport.min.js
wp-includes/js/dist/warning.js
wp-includes/js/dist/warning.min.js
wp-includes/js/dist/wordcount.js
wp-includes/js/dist/wordcount.min.js
wp-includes/js/heartbeat.js
wp-includes/js/imagesloaded.min.js
wp-includes/js/masonry.min.js
wp-includes/js/mce-view.js
wp-includes/js/media-editor.js
wp-includes/js/media-editor.min.js
wp-includes/js/media-models.js
wp-includes/js/media-views.js
wp-includes/js/media-views.min.js
wp-includes/js/plupload/handlers.js
wp-includes/js/plupload/handlers.min.js
wp-includes/js/plupload/wp-plupload.js
wp-includes/js/plupload/wp-plupload.min.js
wp-includes/js/thickbox/thickbox.css
wp-includes/js/tinymce/plugins/compat3x/css/dialog.css
wp-includes/js/tinymce/plugins/compat3x/plugin.js
wp-includes/js/tinymce/plugins/lists/plugin.js
wp-includes/js/tinymce/plugins/lists/plugin.min.js
wp-includes/js/tinymce/plugins/media/plugin.js
wp-includes/js/tinymce/plugins/media/plugin.min.js
wp-includes/js/tinymce/plugins/paste/plugin.js
wp-includes/js/tinymce/plugins/paste/plugin.min.js
wp-includes/js/tinymce/plugins/wptextpattern/plugin.js
wp-includes/js/tinymce/skins/lightgray/content.inline.min.css
wp-includes/js/tinymce/skins/lightgray/content.min.css
wp-includes/js/tinymce/skins/lightgray/skin.min.css
wp-includes/js/tinymce/themes/inlite/theme.js
wp-includes/js/tinymce/themes/inlite/theme.min.js
wp-includes/js/tinymce/themes/modern/theme.js
wp-includes/js/tinymce/themes/modern/theme.min.js
wp-includes/js/tinymce/tinymce.min.js
wp-includes/js/tinymce/wp-tinymce.js
wp-includes/js/twemoji.js
wp-includes/js/twemoji.min.js
wp-includes/js/wp-ajax-response.js
wp-includes/js/wp-ajax-response.min.js
wp-includes/js/wp-api.js
wp-includes/js/wp-auth-check.js
wp-includes/js/wp-auth-check.min.js
wp-includes/js/wp-backbone.js
wp-includes/js/wp-custom-header.js
wp-includes/js/wp-emoji-loader.js
wp-includes/js/wp-emoji-loader.min.js
wp-includes/js/wp-emoji-release.min.js
wp-includes/js/wp-lists.js
wp-includes/js/wp-pointer.js
wp-includes/js/wp-pointer.min.js
wp-includes/js/wp-util.js
wp-includes/kses.php
wp-includes/l10n.php
wp-includes/link-template.php
wp-includes/load.php
wp-includes/media-template.php
wp-includes/media.php
wp-includes/meta.php
wp-includes/ms-blogs.php
wp-includes/ms-default-constants.php
wp-includes/ms-default-filters.php
wp-includes/ms-deprecated.php
wp-includes/ms-functions.php
wp-includes/ms-load.php
wp-includes/ms-network.php
wp-includes/ms-settings.php
wp-includes/ms-site.php
wp-includes/nav-menu-template.php
wp-includes/nav-menu.php
wp-includes/option.php
wp-includes/pluggable.php
wp-includes/plugin.php
wp-includes/pomo/mo.php
wp-includes/pomo/po.php
wp-includes/pomo/streams.php
wp-includes/pomo/translations.php
wp-includes/post-formats.php
wp-includes/post-template.php
wp-includes/post-thumbnail-template.php
wp-includes/post.php
wp-includes/query.php
wp-includes/rest-api.php
wp-includes/rest-api/class-wp-rest-request.php
wp-includes/rest-api/class-wp-rest-server.php
wp-includes/rest-api/endpoints/class-wp-rest-attachments-controller.php
wp-includes/rest-api/endpoints/class-wp-rest-autosaves-controller.php
wp-includes/rest-api/endpoints/class-wp-rest-block-renderer-controller.php
wp-includes/rest-api/endpoints/class-wp-rest-blocks-controller.php
wp-includes/rest-api/endpoints/class-wp-rest-comments-controller.php
wp-includes/rest-api/endpoints/class-wp-rest-controller.php
wp-includes/rest-api/endpoints/class-wp-rest-post-types-controller.php
wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php
wp-includes/rest-api/endpoints/class-wp-rest-revisions-controller.php
wp-includes/rest-api/endpoints/class-wp-rest-settings-controller.php
wp-includes/rest-api/endpoints/class-wp-rest-terms-controller.php
wp-includes/rest-api/endpoints/class-wp-rest-themes-controller.php
wp-includes/rest-api/endpoints/class-wp-rest-users-controller.php
wp-includes/rest-api/fields/class-wp-rest-meta-fields.php
wp-includes/rest-api/search/class-wp-rest-post-search-handler.php
wp-includes/revision.php
wp-includes/rewrite.php
wp-includes/rss.php
wp-includes/script-loader.php
wp-includes/shortcodes.php
wp-includes/sodium_compat/src/Core/Ed25519.php
wp-includes/sodium_compat/src/Core32/Ed25519.php
wp-includes/taxonomy.php
wp-includes/template-loader.php
wp-includes/template.php
wp-includes/theme-compat/comments.php
wp-includes/theme-compat/footer.php
wp-includes/theme-compat/header.php
wp-includes/theme.php
wp-includes/update.php
wp-includes/user.php
wp-includes/version.php
wp-includes/widgets.php
wp-includes/widgets/class-wp-nav-menu-widget.php
wp-includes/widgets/class-wp-widget-archives.php
wp-includes/widgets/class-wp-widget-calendar.php
wp-includes/widgets/class-wp-widget-categories.php
wp-includes/widgets/class-wp-widget-links.php
wp-includes/widgets/class-wp-widget-media-image.php
wp-includes/widgets/class-wp-widget-meta.php
wp-includes/widgets/class-wp-widget-pages.php
wp-includes/widgets/class-wp-widget-recent-comments.php
wp-includes/widgets/class-wp-widget-recent-posts.php
wp-includes/widgets/class-wp-widget-rss.php
wp-includes/widgets/class-wp-widget-search.php
wp-includes/widgets/class-wp-widget-tag-cloud.php
wp-includes/wp-db.php
wp-login.php
wp-mail.php
wp-settings.php
wp-signup.php
xmlrpc.php

Top ↑

Updated packages #

@babel/polyfill: 7.10.1
@wordpress/a11y: 2.11.0
@wordpress/annotations: 1.20.4
@wordpress/api-fetch: 3.18.0
@wordpress/autop: 2.9.0
@wordpress/blob: 2.9.0
@wordpress/block-directory: 1.13.6
@wordpress/block-editor: 4.3.6
@wordpress/block-library: 2.22.6
@wordpress/block-serialization-default-parser: 3.7.0
@wordpress/blocks: 6.20.3
@wordpress/components: 10.0.5
@wordpress/compose: 3.19.3
@wordpress/core-data: 2.20.3
@wordpress/data: 4.22.3
@wordpress/data-controls: 1.16.3
@wordpress/date: 3.10.0
@wordpress/deprecated: 2.9.0
@wordpress/dom: 2.13.1
@wordpress/dom-ready: 2.10.0
@wordpress/edit-post: 3.21.6
@wordpress/editor: 9.20.6
@wordpress/element: 2.16.0
@wordpress/escape-html: 1.9.0
@wordpress/format-library: 1.22.6
@wordpress/hooks: 2.9.0
@wordpress/html-entities: 2.8.0
@wordpress/i18n: 3.14.0
@wordpress/icons: 2.4.0
@wordpress/is-shallow-equal: 2.1.0
@wordpress/keyboard-shortcuts: 1.9.3
@wordpress/keycodes: 2.14.0
@wordpress/list-reusable-blocks: 1.21.5
@wordpress/media-utils: 1.15.0
@wordpress/notices: 2.8.3
@wordpress/nux: 3.20.5
@wordpress/plugins: 2.20.3
@wordpress/primitives: 1.7.0
@wordpress/priority-queue: 1.7.0
@wordpress/redux-routine: 3.10.0
@wordpress/rich-text: 3.20.4
@wordpress/server-side-render: 1.16.5
@wordpress/shortcode: 2.9.0
@wordpress/token-list: 1.11.0
@wordpress/url: 2.17.0
@wordpress/viewport: 2.21.3
@wordpress/warning: 1.2.0
@wordpress/wordcount: 2.10.0
clipboard: 2.0.6
imagesloaded: 4.1.4
lodash: 4.17.19
masonry-layout: 4.2.2
moment: 2.27.0
twemoji: 13.0.0

The post Version 5.5 first appeared on CODIBU.

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 Instances.

Top ↑

Basic Instructions #

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

1. Download and unzip the WordPress package if you haven’t already.
2. 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.
3. (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.
4. 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.
5. 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.

Top ↑

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.

Top ↑

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.

1. 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” (Refer this article).

2. 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:

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

  * Authentication Unique Keys and Salts.

SET PASSWORD FOR 'wordpressusername'@'hostname' = OLD_PASSWORD('password');

The post How to install WordPress first appeared on CODIBU.

The Your Profile Screen is accessible from both the main navigation menu under Users and by clicking on your name link at the top of the WordPress screen. Here you can specify your name and how it will be displayed on your site, your e-mail address (for administrative purposes), other personal information, and personal options.

Top ↑

Your Profile and Personal Options #

The only pieces of information WordPress requires you to include in your Profile are your e-mail address and a nickname. It should be noted that WordPress requires your email address only for your blog’s administration purposes. The email address is never sent to any other site (not even to the people at WordPress headquarters), and it is never displayed on your site (unless you put it there manually). Only the other registered users of your blog have access to the e-mail address you provide. Also, remember that each user’s email address must be unique.

Note: it is possible for a theme to display your e-mail address (and the e-mail addresses of your other registered users) on your site, since the the_author_meta('user_email') template tag can be used for such purposes. This would be a poorly conceived theme, however, if it didn’t inform you of that before you downloaded it. None of the themes included with WordPress display any e-mail address anywhere on the public side of your site by default.

All of the other personal information asked for here is optional, and, again, it is never sent to any other site or person. It may be displayed on your site, however, depending on the theme you use, so you should test things out with your particular theme if you’re at all paranoid (and a bit of paranoia regarding your personal information is healthy). See the_author and related template tags for information on how to display this information on your site (and, consequently, how to ensure the theme you use does/does not display any of this information). Typically, themes only display the information you enter in the Display name publicly as field, however the Authors username is also often included in the URL (for Author Archives) and in the CSS classes for per-author targeted stylings.

Personal Options :

• Visual Editor – Checking this box Disables the visual editor when writing, and uses the plain HTML editor.
• Syntax Highlighting – Checking this box Disable syntax highlighting when editing code.
• Admin Color Scheme – Check this radio button next to the color scheme desired for the Administration Screens. The left two colors are menu background colors and the right two are roll-over colors.

• Keyboard Shortcuts – Checking this box Enables keyboard shortcuts for comment moderation. Keyboard shortcuts are designed to allow you to rapidly navigate and perform actions on comments. The Keyboard Shortcuts article describes the various shortcuts in detail.
• Toolbar – Check the box to display the Toolbar when you are viewing your site.
• Language – You can select the language you wish to use while using the Administration Screen without affecting the language site visitors see.

Name :

• Username – You cannot edit your Username because it is used as your Username during the login process. Even an Administrator cannot change your Username. Usually, no one else ever needs to see your Username.
• First name – Enter your first name in this text box.
• Last name – Enter your last name in this text box.
• Nickname – Enter the nickname as it is a required for every user. It may be the same as your User Name or it can be different. If you don’t supply a Nickname, then the User Name will be placed in this field.
• Display name publicly as – Select, from the drop-down, how your name is cited on your blog. This defaults to your first and last name. You can choose from several of the above pieces of information: Nickname, Login name, First Name, Last Name, “First Last“, or “Last First“. If you prefer “Last, First“, insert a comma after your last name in the Last Name text box above and choose the last option from this dropdown.

Contact Info :

• E-mail – All users are required to list an e-mail address in their respective Profiles. The E-mail address must be unique for each user. Your blog will use this address to notify you of new comments to your posts and for other administrative purposes. To reiterate what was said above, only other registered users of your blog will have access to this e-mail address. It is never sent anywhere.
• Website – Enter your website address.

About Yourself :

• Biographical Info – Enter a short description or profile of yourself here. This optional information can be displayed by your theme if so configured by the theme author. See the_author_meta('description') template tag.
• Profile Picture – Your picture in Gravatar is shown here. To change it, access to the https://en.gravatar.com/. See also Using Gravatars.

Account Management :

• Generate Password – You can click this button to generate a new password for the account. This will show you a new field with the generated password. If you choose to change this password, a checkbox will appear to confirm that you want to use a weak password. You can check this box to confirm that you want to use your own password instead of a secure one.
• Strength Indicator This indicates if the password you entered is Very Weak, Weak, Medium, or Strong (displayed in green). The stronger the password the more secure your login. Hint: The password should be at least seven characters long. To make it stronger, use upper and lower case letters, numbers and symbols like !”?$%^&).
• Log Out Everywhere Else – You can click this button to log out of other devices, such as your phone or a public computer.

Update Profile #

Remember to click this button to save the changes you have made to your Profile and Personal Options. After clicking this button you should see a splash message at the top of the screen saying User Updated. If you don’t see that message, then your changes are not saved!

The post Users Your Profile Screen first appeared on CODIBU.

In contrast, pages are for non-chronological content: pages like “About” or “Contact” would be common examples. Pages live outside of the normal blog chronology, and are often used to present timeless information about yourself or your site — information that is always relevant. You can use Pages to organize and manage the structure of your website content.

In addition to the common “About” and “Contact” pages, other examples include “Copyright”, “Disclosure”, “Legal Information”, “Reprint Permissions”, “Company Information” or “Accessibility Statement”.

In general, pages are very similar to posts in that they both have titles and content. WordPress Theme template files maintain a consistent look throughout your site. Pages, though, have several key distinctions that make them different from posts.

What Pages Are

• Pages are for content that isn’t specifically time-dependent, or which isn’t “blog content”.
• Pages can be organized into pages and subpages.
• Pages can use different page templates, including template files, Template Tags and other PHP code.
• More sophisticated themes may provide a wider range of adjustments or display options for individual pages.
• It’s quite possible to make a website using WordPress which only contains pages.

What Pages Are Not

• Pages are not posts, so they don’t appear in the time-structured views within a blog section of a website.
• Pages by default do not allow taxonomy (categories, tags and any custom taxonomies) associations. You can enhance it via plugins.
• The organizational structure for Pages comes from hierarchical interrelationship, not from a system of categorization. (e.g. Tags or Categories.)
• Pages are not files. They are stored in your database, just like posts.
• Although you can put Template Tags and PHP code into a Page Template file, you cannot put these into the Page or Post content without using a WordPress Plugin. But be careful: integrating PHP code directly into page or post content may introduce a security problem, or an unexpected error on your website.
• Pages are not included in your site’s “feeds”. (e.g. RSS or Atom.)
• Pages and Posts can be interpreted differently by site visitors and by search engines. Commonly, search engines place more relevance to time-dependent site content – posts – because a newer post on a topic may be more relevant than a static page.
• A specific page (or a specific post) can be set as a static front page. Websites which are set up in this way usually have a secondary page defined on which the latest blog posts are displayed.

Creating Pages #

To create a new Page, log in to your WordPress installation with sufficient admin privileges to create new pages. Select the Pages > Add New option to begin writing a new Page.

Organizing Your Pages #

Just as you can have subcategories within your Categories, you can also have subpages within your Pages, creating a hierarchy of pages.

For example, a WordPress site for a travel agent may feature an individual Page for each continent and country to which the agency can make travel arrangements. Under the Page titled “Africa” would be subpages for Cameroon, Lesotho, Swaziland and Togo. Another parent Page “South America” would feature subpages of Argentina, Brazil and Chile.

The structure of the pages on the site would then look like this.

• Africa
  • Cameroon
  • Lesotho
  • Swaziland
  • Togo
• South America
  • Argentina
  • Brazil
  • Chile

To create a subpage #

1. Go to Administration > Pages > Add New screen.
2. In the right menu, click the “Page Parent” drop-down menu. The drop-down menu contains a list of all the Pages already created for your site.
3. Select the appropriate parent Page from the drop-down menu to make the current Page a child Page.
4. Add content to the subpage.
5. Click Publish when ready.

When your Pages are listed, the Child Page will be nested under the Parent Page. The Permalinks of your Pages will also reflect this Page hierarchy.

In the above example, the Permalink for the Cameroon Page would be:

http://example.com/africa/cameroon/

Top ↑

Changing the URL of Your Pages #

To change the URL part (also referred to as “slug”) containing the name of your Page, use the “Edit” button under the Page title on the Edit screen of the particular Page, accessible from Pages tab of WordPress Administration Screen.

Top↑

Creating a List of Pages #

WordPress is able to automatically generate a list of pages on your site within the sidebar or footer, for example, using a Template Tag called wp_list_pages(). See the wp_list_pages page for information on how to customize how WordPress displays the list of pages on your site.

There are also WordPress Plugins that will help you display a list of Pages within in Posts and in other areas of your WordPress Theme.

Top ↑

Page Templates #

Individual Pages can be set to use a specific custom Page Template (a WordPress Theme PHP template file, e.g., my-custom-page.php) you create within your Theme. See Custom Page Templates for instructions on how to create a custom template file for a Page. This new Page Template will then override the default page.php Page Template included with your Theme.

Top ↑

The Dynamic Nature of WordPress Pages #

A web page can be static or dynamic. Static pages, such as a regular HTML page that you might create with Dreamweaver, are those which have been created once and do not have to be regenerated every time a person visits the page. In contrast, dynamic pages, such as those you create with WordPress, do need to be regenerated every time they are viewed; code for what to generate on the page has been specified by the author, but not the actual page itself. These use extensive PHP code which is evaluated each time the page is visited, and the content is thus generated upon each new visit.

Almost everything in WordPress is generated dynamically, including Pages. Everything published in WordPress (Posts, Pages, Comments, Blogrolls, Categories, etc…) is stored in the MySQL database. When the site is accessed, the database information is used by your WordPress Templates from your current Theme to generate the web page being requested.

An example of a static page might be an HTML document (without any PHP code). The problem with purely static pages is that they are difficult to maintain. Changes you make to your WordPress settings, Themes and Templates will not be propagated to pages coded only in HTML. The Page feature of WordPress was developed to alleviate this problem. By using Pages, you no longer have to update your static pages every time you change the style of your site. If written properly, your dynamic Pages will update along with the rest of your blog.

Despite the dynamic nature of Pages, many people refer to them as being static. They are actually called “pseudo-static” web pages. In other words, a Page contains static information but is generated dynamically. Thus, either “static,” “dynamic,” or “pseudo-static” may be validly used to describe the nature of the WordPress Page feature.

The post Pages first appeared on CODIBU.

How to use the Block Directory #

1. Type a keyword in the search field of the Inserter, like “team” or “staff”.

In the background, the system first searches the current site and if it doesn’t find a block, it also searches in the Block Directory, a special corner of the WordPress plugin repository, where single block plugins are available. If it finds blocks, they will be displayed in the inserter, including a preview section.

2. Decide which block to use and click the button “Add Block.”

In the background the single-block plugin is installed and activated, and the user can continue creating the team page.

3. If the first choice not work out, you can go back to the search and select a different one that also will be installed.

EXAMPLES OF TESTED SINGLE BLOCK PLUGINS:

• Apple Maps by 10up,
• an Event block by Automattic,
• simple User Profile Block by Ham.works,
• GuidePost by Nick Hamze (sorta brilliant).

Top ↑

How to uninstall the block #

Installed block is the plugin. You can uninstall it from Plugins Screen.

Demonstration on how the Block Directory works

In this video shows you how the Block Directory works. It’s starts at 3:00 time stamp. Start it at the beginning if you are new to the block editor and need a refresher.

On Learn.WordPress.org contributors started creating workshop videos for self-study and scheduled discussion groups online. Check it out.

Resource Links:

• Introduction to the Block Directory (Video)
• Series: Introduction to Publishing with the Block Editor
• Single Block Plugins available through the Block Directory
• Proposed Block Directory guidelines

The post Block Directory first appeared on CODIBU.

The main WordPress Editor document has information about how to add blocks.

Common Blocks

• Paragraph
• Image
• Heading
• Gallery
• List
• Quote
• Audio
• Cover
• File
• Video

Formatting

• Code
• Classic
• Custom HTML
• Preformatted
• Pullquote
• Table
• Verse

Layout Elements

• 
  WidgetsPage Break
• Spacer
• Buttons (new 5.4)
• Button (deprecated)
• Columns
• Group
• Media & Text
• More
• Separator

• Widgets
  EmbedsShortcode
• Archives
• Calendar (new in 5.3)
• Categories
• Latest Comments
• Latest Posts
• RSS (new in 5.3)
• Search (new in 5.3)
• Social Icons (new in 5.4)
• Tag Cloud (new in 5.3)

• Embed
• Twitter
• YouTube
• Facebook
• Instagram
• WordPress
• SoundCloud
• Spotify
• Flickr
• Vimeo
• Animoto
• CloudUp
• Crowdsignal
• Dailymotion
• Imgur
• Issuu
• Kickstarter
• Meetup.com
• Mixcloud
• Reddit
• ReverbNation
• Screencast
• Scribd
• Slideshare
• SmugMug
• Speaker Deck
• TikTok (new in 5.4)
• TED
• Tumblr
• VideoPress
• WordPress.tv
• Amazon Kindle

The post Blocks first appeared on CODIBU.

Widgets were originally designed to provide a simple and easy-to-use way of giving design and structure control of the WordPress Theme to the user, which is now available on properly “widgetized” WordPress Themes to include the header, footer, and elsewhere in the WordPress design and structure.
Widgets require no code experience or expertise. They can be added, removed, and rearranged on the Theme Customizer or Appearance > Widgets in the WordPress Administration Screens.

Some WordPress Widgets offer customization and options such as forms to fill out, includes or excludes of data and information, optional images, and other customization features.

The Appearance Widgets Screen explains how to use the various Widgets that come delivered with WordPress.

Plugins that come bundled with widgets can be found in the WordPress Plugin Directory.

Installing Widgets #

WordPress comes pre-packaged with a variety of Widgets. If those are insufficient for your needs you can install new ones by searching the WordPress Plugin Directory which is accessible from the WordPress Administration Plugins > Add New Screen.

Top ↑

Displaying Widgets #

Existing Widgets in Existing Widget Areas #

Before you can add a Widget you must verify that the Theme you’re using supports Widgets (more specifically: Widget Area). You can do so by simply navigating to the Appearance menu and looking for a sub menu titled “Widgets”.

If your Theme supports Theme Customizer then you can use the following Steps. In Theme Customizer, the live preview of changes is available.

1. Go to Appearance > Customize in the WordPress Administration Screens.
2. Click the Widget menu in the Theme Customizer to access to the Widget Customize Screen.
3. Click the down arrow of Widget Area to list the already registered Widgets.
4. Click Add a Widget button at the bottom of sidebar. It shows the list of available widgets.
5. Click a widget you want to add. The widgets should be added in the sidebar.
6. Preview your site and you should see the content from your new Widget.
7. To arrange the Widgets within the Sidebar, drag and drop the widgets in the order you want or click Reorder link and click up arrow and down allow of each widget and click Done after the arrange operation.
8. To customize the Widget features, click the down arrow in the right to expand the Widget’s interface.
9. To remove the widget, click Remove from Widget’s interface in above step.

If your Theme does not support Theme Customizer then you can use the following conventional steps:

1. Go to Appearance > Widgets in the WordPress Administration Screens.
2. Choose a Widget and either drag it to the sidebar where you wish it to appear, or click the widget, (select a destination sidebar if your theme has more than one) and click the Add Widget button. There might be more than one sidebar option, so begin with the first one. Once in place, WordPress automatically updates the Theme.
3. Preview the site. You should find that the “default” sidebar elements are now gone and only the new addition is visible.
4. Return to the Widgets Screen to continue adding Widgets.
5. To arrange the Widgets within the sidebar or Widget area, click and drag it into place.
6. To customize the Widget features, click the down arrow in the upper right corner to expand the Widget’s interface.
7. To save the Widget’s customization, click Save.
8. To remove the Widget, click Delete.

If you want to remove the widget but save its setting for possible future use, just drag it into the Inactive Widgets area. You can add them back anytime from there. This is especially helpful when you switch to a theme with fewer or different widget areas.

When changing themes, there is often some variation in the number and setup of widget areas/sidebars and sometimes these conflicts make the transition a bit less smooth. If you changed themes and seem to be missing widgets, scroll down on the screen to the Inactive Widgets area, where all of your widgets and their settings will have been saved.

Enabling Accessibility Mode, via Screen Options, allows you to use Add and Edit buttons instead of using drag and drop.

Top ↑

Widget Areas #

While widget areas typically occur in webpage sidebars, a theme can place widget areas anywhere on a page. For example, besides the usual sidebar locations, the Twenty Seventeen theme has a widget area in the footer of every page.

If you would like to place a Widget somewhere on your Theme that does not have a pre-defined Widget Area, you will need some programming knowledge and should follow the instructions on the Widgets API section found here.

Top↑

Using Text Widgets #

The Text Widget is one of the most commonly used WordPress Widgets that comes with every WordPress installation. It allows users to add text, video, images, custom lists, and more to their WordPress sites.

To use the WordPress Text Widget:

1. Go to Appearance > Customize in the WordPress Administration Screens and click the Widget menu in the Theme Customizer. Or Go to Appearance > Widgets in the WordPress Administration Screens.
2. Open the sidebar to which you wish to add the Text Widget.
3. Find the Text Widget in the list of Widgets.
4. Click and drag the Widget to the spot you wish it to appear.

To open and edit the Text Widget:

1. Click the down arrow to the right of the Text Widget title.
2. Set the Text Widget Title (optional).
3. Add the text or HTML code to the box or edit what is currently there.
4. Choose the option to Automatically add paragraphs to wrap each block of text in an HTML paragraph tag (recommended for text).
5. Click Save to save the Text Widget.
6. Click Close to close the Text Widget.
7. Switch tabs in your browser and preview the results and make changes if necessary.

The Text Widget can hold a variety of HTML, XHTML, and multimedia links and players such as video and object embeds.

Top↑

Adding Code to the Text Widget #

Basic HTML, embeds, and JavaScript are added easily to the WordPress Text Widget. Most embed codes from social sharing sites for multimedia will work in a WordPress Text Widget. However, active code and programming languages such as PHP will not work as the Widget will strip out code it cannot display.

To add active code to the Text Widget, use one of the many WordPress Plugins from the WordPress Plugin Directory that override WordPress restrictions on using PHP in posts. Check that they will work on Widgets as some will not.

Top↑

Using RSS Widgets #

The RSS Widget allows you to integrate an external feed source for content into a Widget area of your site, such as your Twitter account, Facebook posts, Google+ posts, or other blogs.

The RSS Widget displays the most recently published content from any source with an active feed. This is an ideal way of integrating outside content into your site.

By default, WordPress RSS Widget displays the post title or the first 100 or so characters of a Tweet or long untitled post. These are either in the form of a link or features a link to the original source depending upon the feed’s design and structure.

1. Enter the RSS feed URL in the first box, copied from the source page for the content you wish to include in your sidebar or other widgetized space.
2. Give the feed a title: This is optional and gives you the chance to showcase the source of the content.
3. How many items would you like to display?: By default, 10 are show, but you can choose from 1-20 posts.
4. Display item content?: This allows you to show an excerpt of the content not just the title.
5. Display item author if available?: If you wish to give credit to the original author of the content, check this to display the author.
6. Display item date?: If available, the date of the original content will be shown.

You may add multiple RSS Widgets for incoming feeds to your WordPress sidebar and other widgetized areas of your site.

Top ↑

Resources #

• Widgetizing Themes
• Widgets API
• WordPress Tips on Exploring the WordPress Text Widget
• WordPress Widgets Announcement (historical reference)

The post WordPress Widgets first appeared on CODIBU.

By default, WordPress adds all the published pages to the menu automatically. However, customization of menu is possible, such as adding a link to a category or to external site, changing the order of the menu link, or creating a sub-menu.

The Appearance Menu Screen is accessible via Dashboard > Appearance > Menus.

Screen Options #

The Screen Options allow you to choose which modules are displayed, or not displayed, in the underlying Screen. Clicking on the Screen Options tab shows a list of the possible modules and options with a check-box next to each. Check the box for each module or option you want displayed, or uncheck the box to not display that module. Click the Screen Options tab again to close the Screen Options.

Certain modules, like Posts are hidden by default.

Top ↑

Creating Menu #

1. Go to the WordPress Dashboard.
2. From the ‘Appearance’ menu on the left-hand side of the Dashboard, select the ‘Menus’ option to bring up the Menu Editor.
3. Select Create a new menu at the top of the page
4. Enter a name for your new menu in the Menu Name box
5. Click the Create Menu button.

Top ↑

Adding Items to a Menu #

You can add different item types into your menu, such as Pages, Categories, or even Custom Links. These are split between panes left of the menu you’re currently editing. An example on how to add link to a page:

1. Locate the pane entitled Pages.
2. Within this pane, select the View All link to bring up a list of all the currently published Pages on your site.
3. Select the Pages that you want to add by clicking the checkbox next to each Page’s title.
4. Click the Add to Menu button located at the bottom of this pane to add your selection(s) to the menu that you created in the previous step.
5. Click the Save Menu button once you’ve added all the menu items you want.

Your custom menu has now been saved.

Note: The Screen Options allow you to choose which items you can use to add to a menu. Certain items, like Tags are hidden by default.

Top ↑

Deleting a Menu Item #

1. Locate the menu item that you want to remove in the menu editor window
2. Click on the arrow icon in the top right-hand corner of the menu item to expand it.
3. Click on the Remove item. The menu item will be immediately removed.
4. Click the Save Menu button to save your changes.

Top↑

Creating Multi-level Menus #

When planning the structure of your menu, it helps to think of each menu item as a heading in a formal report document. In a formal report, main section headings (Level 1 headings) are the nearest to the left of the page; sub-section headings (Level 2 headings) are indented slightly further to the right; any other subordinate headings (Level 3, 4, etc) within the same section are indented even further to the right.

The WordPress menu editor allows you to create multi-level menus using a simple ‘drag and drop’ interface. Drag menu items up or down to change their order of appearance in the menu. Drag menu items left or right in order to create sub-levels within your menu.

To make one menu item a subordinate of another, you need to position the ‘child’ underneath its ‘parent’ and then drag it slightly to the right.

1. Position the mouse over the ‘child’ menu item.
2. Whilst holding the left mouse button, drag it to the right.
3. Release the mouse button.
4. Repeat these steps for each sub-menu item.
5. Click the Save Menu button in the Menu Editor to save your changes.

Top ↑

Adding Your Menu to Your Site #

If your current theme supports custom menus, you will be able to add your new menu to one of the Theme Locations.

1. Scroll to the bottom of the menu editor window.
2. In the section titled Theme locations, click the check box for the location where you want your menu to appear.
3. Click Save menu once you’ve made your selection.

If your current theme does not support custom menus, you will need to add your new menu via the Custom Menu widget in the Appearance Widgets Screen.

Rearranging, Configuring Menu Items #

Once an item is added to a menu, those menu items can be rearranged. Placing the mouse cursor over the menu item title, when the mouse cursor changes to 4-arrows, hold the left-mouse button down, drag the module to where you want to place it, then release the mouse button (this is called drag-and-drop). Remember you can drag a menu item slightly to the right of the menu item above it to create a hierarchy (parent/child) relationship in the menu.

Each Menu Item has a configuration arrow on the right side of the Menu Item title, that when clicked opens the configuration box. Click the arrow a second time closed the configuration box. If you don’t see Link Target, CSS Classes, Link Relationship (XFN), and Description, then under Screen Options make sure those boxes are checked to expose them here.

Then configuration choices are:

Navigation Label

The label for this particular menu item

Title Attribute

The attribute used when displaying the label

Link Target

Select “Same window or tab” or “New window or tab” from the pulldown.

CSS Classes

Optional CSS Classes for this menu item

Link Relationship (XFN)

Allows for the generation of XFN attributes automatically so you can show how you are related to the authors/owners of site to which you are linking. See Link Relationship for details.

Description

Description for this link. The description will be displayed in the menu if the current theme supports it.

Original

A link to the original source of the menu item (e.g. a link to view the post or page).

Remove

Remove this menu item from the menu.

Cancel

Cancel the configuration of the menu item and

The post Appearance Menus Screen first appeared on CODIBU.

From the Dashboard Screen, you can quickly access your site’s content and get glimpses into other areas of the WordPress community.

The Dashboard screen presents information in blocks called widgets. By default, WordPress delivers five widgets on this page: At a Glance, Activity, Quick Draft, WordPress Events and News, and Welcome.

Top ↑

Default Dashboard Widgets #

The following dashboard widgets are included by default with WordPress:

At a Glance #

The At a Glance widget provides a summary of the number of posts, pages, and comments on your site. Each of these content types are displayed in the form of a link and, when clicked upon, direct you to the specific area to manage that content.

A statement at the bottom of this widget tells you what WordPress version you’re running on, as well as the current theme that you have activated on your site.

Top ↑

Activity #

This widget shows the upcoming scheduled posts, recently published posts, and the most recent comments on your posts–and allows you to moderate them.

A list of the most recent comments on your blog is detailed in this widget. Each comment that is listed has a link to the related post title–clicking this link allows you to edit the post. Hovering the mouse over each comment activates a menu of choices: to approve (or unapprove) the comment, edit the comment, reply to the comment, mark the comment as spam, or delete the comment.

Top ↑

QuickDraft #

The QuickDraft widget allows you to quickly and easily write a new draft. Enter a post title, upload/insert media, enter the post content, add tags, and click the Publish button or click the Save Draft button. It’s that easy!

Top ↑

WordPress Events and News #

This Dashboard widget lists upcoming local events and the latest news from the official WordPress blog.

Here you can find out an upcoming event near you, or, what WordPress developers have been up to recently, and you can also keep up with the latest WordPress related news. In addition to software developments–such as version announcements and security notices–news about the WordPress community in general is periodically posted.

Top ↑

Welcome #

The Welcome widget shows links for some of the most common tasks when setting up a new site.

Top ↑

Screen Options #

The Screen Options panel allows you to choose which widgets are displayed or not displayed.

When you click on the Screen Options tab, the resulting panel shows the various Dashboard widgets, with a checkbox next to each widget. Check the box to display a specific widget, or uncheck the box to hide that widget.

Click the Screen Options tab again to close the Screen Options panel.

Top ↑

Expanding, Collapsing, and Rearranging Widgets #

Each widget can be expanded or contracted by clicking on the widget title bar.

Widgets can be moved by hovering the mouse cursor over the widget title bar. When the mouse cursor changes to four arrows, hold the left mouse button down, drag the widget to where you want to place it, and then release the mouse button (this cursor motion is called drag and drop).

Top ↑

Adding new Dashboard Widgets #

Plugin or theme developers can make new Dashboard widgets available through the plugin (or functions.php) code. For more information, see the Dashboard Widgets API.

The post Dashboard Screen first appeared on CODIBU.

Permalink Types #

There are three basic types of WordPress permalinks:

Default: “Ugly” #

The default looks like

http://example.com/?p=N

where N is the Post ID number. It works on all server environments, but it doesn’t look as nice as some of the other options.

Top ↑

mod_rewrite: “Pretty Permalinks” #

Using mod_rewrite or lighttpd you can produce much nicer permalinks (see Pretty Permalinks). There are many different formats, but the most common, and most versatile looks like

http://example.com/2012/post-name/

or

http://example.com/2012/12/30/post-name

Pretty permalinks are available under:

• Apache web server with the mod_rewrite module
• Nginx using try-files, e.g. according to this tutorial
• Hiawatha web server with UrlToolkit support enabled.
• Lighttpd using a 404 handler or mod_rewrite
• Caddy using rewrite, e.g. according to this tutorial

Top ↑

PATHINFO: “Almost Pretty” #

PATHINFO permalinks look very much like mod_rewrite permalinks but for one exception: they have /index.php inserted before them, like so:

http://example.com/index.php/yyyy/mm/dd/post-name/

Otherwise, they are the same as the “pretty” mod_rewrite permalinks, and are similarly flexible. Anything that mod_rewritepermalinks can do, PATHINFO permalinks can do, with the help of that /index.php part.

Top ↑

Choosing your permalink structure #

In the Settings → Permalinks Screen, you can choose one of the more common permalink structures or enter your own in the “Custom structure” field using the structure tags.

Please note: You do not put your site url in the permalinks fields. You only use one of the structure tags, or a combination of tags.

To activate PATHINFO permalinks, start your permalink structure with index.php/.

Top ↑

Structure Tags #

You can use these tags to customize your “Pretty” or “Almost Pretty” permalinks. A few hints:

• You do not put your site url in the permalinks fields. You only use one of the structure tags, or a combination of tags.
• Make sure to end your structure with either %post_id% or %postname% (e.g. /%year%/%monthnum%/%day%/%postname%/) so that each permalink points to an individual post.

%year%
The year of the post, four digits, for example 2018

%monthnum%
Month of the year, for example 05

%day%
Day of the month, for example 28

%hour%
Hour of the day, for example 15

%minute%
Minute of the hour, for example 43

%second%
Second of the minute, for example 33

%post_id%
The unique ID # of the post, for example 423

%postname%
A sanitized version of the title of the post (post slug field on Edit Post/Page panel). So “This Is A Great Post!” becomes this-is-a-great-post in the URI.

%category%
A sanitized version of the category name (category slug field on New/Edit Category panel). Nested sub-categories appear as nested directories in the URI.

%author%
A sanitized version of the author name.

Top ↑

Category base and Tag base #

The Category base and Tag base are prefixes used in URLs for category and tag archives, which look like this:

 example.net/wp/category_base/category_name
 example.net/wp/tag_base/tag_name

The default values for these are category and tag. You can change them, but you can’t remove them from the URLs altogether.

Custom permalinks work on most systems without any problems, but there are still some conditions where problems occur.

Top ↑

Using %category% with multiple categories on a post #

When you assign multiple categories to a post, only one can show up in the permalink. The categories are ordered alphabetically. In each group of sub-categories the order will also be alphabetical. (see Manage Categories). The post will still be accessible through all the categories as normal.

Try the WP Category Permalink plugin if you want to choose which category shows up in the permalink.

Top ↑

Using “Pretty” permalinks #

Requirements:

• Apache web server with the mod_rewrite module installed
• In WordPress’s home directory,
  • The FollowSymLinks option enabled
  • FileInfo directives allowed (e.g. AllowOverride FileInfo or AllowOverride All)
  • An .htaccess file (if this file is missing, WordPress will try to create it when you activate “pretty” permalinks)
  • If you want WordPress to update the .htaccess file automatically, WordPress will need write access to the file.

• For nginx, a web server aimed at high concurrency, high performance and low memory usage, add the following location block within the server block:

location / {
            try_files $uri $uri/ /index.php?$args;
}

• For Hiawatha, a web server with a strong focus on security, use the following UrlToolkit rule:

UrlToolkit {
    ToolkitID = wordpress
    RequestURI exists Return
    Match .*?(.*) Rewrite /index.php?$1
    Match .* Rewrite /index.php
}

• Mac Users running WordPress locally must edit their httpd.conf file editing the AllowOverride line to read AllowOverride All in theDirectory “/Library/WebServer/Documents” host instructions. For Mac OS X 10.5.x and up this file is located in/private/etc/apache2/users/[your-username].conf, otherwise it is located at /etc/httpd/httpd.conf.

When you create or update a “pretty” permalink structure, WordPress will generate rewrite rules and attempt to insert them into the proper .htaccess file. If it can’t, it will say something like You should update your .htaccess now and print out the rules for you to copy and paste into the file (put them at the end).

You’ll probably need to do this only once, because WordPress does the rewriting internally. If you ever move your WordPress home directory (Site address), you’ll need to repeat this step.

WordPress will play nice with an existing .htaccess and will not delete any existing RewriteRules or other directives. If you have other mod_rewrite rules, put yours before WordPress’s.

Top ↑

Where’s my .htaccess file? #

WordPress’s index.php and .htaccess files should be together in the directory indicated by the Site address (URL) setting on your General Options page. Since the name of the file begins with a dot, the file may not be visible through an FTP client unless you change the preferences of the FTP tool to show all files, including the hidden files. Some hosts (e.g. Godaddy) may not show or allow you to edit .htaccess if you install WordPress through the Godaddy Hosting Connection installation.

Top ↑

Creating and editing .htaccess #

If you do not already have a .htaccess file, create one. If you have shell or ssh access to the server, a simple touch .htaccesscommand will create the file. If you are using FTP to transfer files, create a file on your local computer, call it 1.htaccess, upload it to the root of your WordPress folder, and then rename it to .htaccess.

You can edit the .htaccess file by FTP, shell, or (possibly) your host’s .

The following permalink rewrite code should be included in your .htaccess file:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

If your .htaccess file contains errors that bring down your site (“Internal Server Error (500)”), you will need to use FTP or your host’s control panel to delete the rogue .htaccess file.

Top ↑

Automatically updating .htaccess #

If WordPress can’t update your .htaccess file automatically, it will tell you something like If your .htaccess file were writable, we could do this automatically, but it isn’t… near the bottom of the Settings → Permalinks Screen.

If you want to let WordPress do this, you’ll need to give WordPress write access to the .htaccess file. The exact permissions necessary depend on your server setup. Try adding write permissions for the owner, then group, then world, testing after each change; once WordPress has edited the file successfully, don’t add any further write permissions.

After applying the permalinks, you should change the permissions to something stronger like 660 or 644 to prevent others on the server from potentially having access to it.

Top ↑

Fixing Permalink Problems #

Top ↑

Fixing .htaccess Generation Issues #

If your installation of WordPress does not generate a .htaccess file or if it does not write the new rules onto your existing .htaccess file then there are a couple reasons that could be causing this. Work step by step and continue to the next step only if the previous step does not work.

1. Change File Permissions: You must chmod the .htaccess file to 666 to edit it with the WordPress template editor, but this is not recommended, since if you do that, any user of your blog, who can edit templates will be able to edit it. You can change the permissions to 660 to make it server-writable, which again will have the same limitation.
2. Server Blockage: Your host might have blocked the SERVER_SOFTWARE variable and this will cause WordPress’ .htaccess generation to fail. If you are sure that your server is running Apache, you can force WordPress to believe that your server is running Apache by changing your wp-includes/vars.php file. Follow the steps below to implement these changes.
   • Open the wp-includes/vars.php file using the built in file editor in your WordPress Admin panel. To navigate to this panel, login to WordPress, click on “Manage”, then on “Files”, scroll to the bottom and type in wp-includes/vars.php into the text box under the “Other Files” title. Look for
     $is_apache = strstr($_SERVER[‘SERVER_SOFTWARE’], ‘Apache’) ? 1 : 0;
     and replace it with
     // $is_apache = strstr($_SERVER[‘SERVER_SOFTWARE’], ‘Apache’) ? 1 : 0;
   • Add a new line under
     // $is_apache = strstr($_SERVER[‘SERVER_SOFTWARE’], ‘Apache’) ? 1 : 0;
     and type in
     $is_apache = 1;
3. Users of XAMPP (Windows): Some versions of XAMPP do not enable mod_rewrite by default (though it is compiled in Apache). To enable it — and thus enable WordPress to write the .htaccess file needed to create pretty permalinks — you must open apache/conf/httpd.conf and uncomment the line LoadModule rewrite_module modules/mod_rewrite.so(i.e., delete the hash/pound sign at the front of the line).
4. Users of WAMP (Windows): Some versions of WAMP (all versions?) do not enable mod_rewrite or permit following SymLinks by default. To enable the required functionality navigate to the apache/conf/httpd.conf file, open with a text editor and uncomment the line LoadModule rewrite_module modules/mod_rewrite.so (i.e., delete the hash/pound sign at the front of the line). Then further down in the same file there is a section that starts with the line “Options FollowSymlinks”. Change the second line in that section from “AllowOverride none” to AllowOverride all. Save edited httpd.conf and restart all WAMP modules. Your permalinks should now work.

Top ↑

Tips and Tricks #

Top ↑

Avoiding interpretation as an archive link #

Note that even though one might never make more than one posting a day, and thus wishes to use e.g., %year%%monthnum%%day%, links so generated will however be interpreted as the archive of all posts for that day. One needs at least %year%%monthnum%%day%%hour% to target an individual post.

Top ↑

Check for permalink structure #

A way to check if the blog has a permalink structure is:

<?php if ( get_option('permalink_structure') ) { echo 'permalinks enabled'; } ?>

Top ↑

See Also #

• User:Lazyking/Using Permalinks (Saetta Web Server)
• Linking Posts Pages and Categories for how to link from one article to another

The post Using Permalinks first appeared on CODIBU.