Wordpress multisite
2 likes1,145 views
This document discusses using WordPress Multisite as a development environment. Some key benefits include having a single database and location for plugins/themes, allowing for rapid deployment of new sites. To set it up, some code is added to wp-config.php and .htaccess to enable Multisite and handle subdomains/subdirectories. New sites can then be easily created and each functions independently while sharing plugins/themes network-wide. The process for exporting and importing sites to a live location is also outlined.
More Related Content
What's hot (20)
Viewers also liked (16)
Similar to Wordpress multisite (20)
More from Plasterdog Web Design (7)
Recently uploaded (20)
Wordpress multisite
- 1. Using WordPressMulti Site as aDevelopment EnvironmentJeff McNearplasterdog.comjeff@plasterdog.com@plasterdog847/849-7060
- 2. Development location requirements:Visible to the client
- 3. Hosted at a controlled location
- 4. Control over user permissions
- 5. Quick deployment & modification
- 6. Minimal impact on hosting resourcesIf Wordpress development sites are deployed individually, each site would require all the core files and a unique database.However there are only a couple of aspects that make each site unique:The theme being used
- 8. The actual content portion of the siteAll other aspects can easily be shared across a Multi Site deployment
- 9. As of WordPress 3.0:Wordpress MU capability is included in a standard install
- 10. Can be activated in four steps
- 11. Fast deployment of new sites
- 12. Single database
- 13. Single location for themes & plugins
- 14. Easily exported to “live” locationBefore getting started:Sub domain (sub.multisiteURL) – requires VPS or dedicated host
- 15. Sub directory (multisiteURL/sub) – scheme for local or shared hosting
- 16. Verify mod_Rewrite is active
- 17. Best with fresh install
- 18. Before activating multi-site associate the “root” site with desired URLMy first steps for any newly created WordPress site:Delete sample post
- 22. Verify site name & slogan
- 25. Leave default category aloneEdit wp-config.php file (under root of install)default:edited:
- 27. If you are in a VPS or dedicated hosting environment, you are given the option to select sites as sub-directories or sub-domains.If you are working locally or on a shared host, this selection has been made for you.
- 28. 3 further instructions:Create a new directory (blogs_dir) within the wp-content folder
- 29. Insert additional code into the wp-config.php file
- 30. Insert a piece of code into the (root) .htaccess file(code is dynamically generated based on install)
- 32. The purpose of the blogs_dir insertion is to provide a location for the media library structure. A folder for each site is dynamically created.
- 33. Network Administration controls:Theme upload & activation
- 34. Plugin upload
- 35. Updates
- 36. Site creation
- 37. Some aspects of user administrationEverything else is controlled on a site by site basis!
- 38. A single complaint: The navigation to the network admin panel is not immediately evident!
- 39. Themes are uploaded into the multisite “root” and must be “network enabled” before they can be applied to a site
- 40. Plugins are also uploaded into the “root” and can also be “network activated” but can be selectively activated on a site by site basis:
- 41. You now have a completely stable development environment for multiple individual wordpress sites. Any network enabled theme can be used.Any uploaded plugin can be accessed.
- 42. To create a new site:=> Sites => Add New => Create a New Site
- 43. name site => populate title => populate admin email(must be a pre-established user – should be “root” user)
- 44. Access site controls via “root”:=> Sites => All Sites => Select “Dashboard” for desired siteAccess controls directly: rootURL/sub/wp-admin
- 45. Each newly created site will then be editable like any other wordpress site, with a few exceptions:Only Network Enabled themes can be used
- 46. Only those plugins inserted via the Network admin can be used
- 47. …. and a couple of user management options … Standard user controls are available for every “sub” site:
- 48. Additional option in multisite: “Add existing user”
- 49. Once a user exists in the structure, that user can be associated with multiple sites – and with different permissions
- 50. Preparing a site for export:Verify that all components are fully updated
- 51. Make note of plugins used
- 52. Make note of widget configuration and contentsThen from the site’s admin:Tools
- 53. Export
- 54. All Content
- 55. Download export file to desired locationThe output of this export is an XML file that is generally small – but for a larger site this can create an issueThe php.ini file by default limits file upload size to 2mb – which wordpress further limits to 1.46mbIf you can’t edit the php.ini file on your server, you can export the data in pieces.While a date range division is offered, it isn’t reliable. It is better to segment by category.
- 56. Importing the site to the “live” location:Prepare fresh wordpress install
- 57. Upload and activate developed theme
- 58. Upload and activate pluginsThen:Tools
- 59. Import
- 60. Navigate to saved .xml file
- 62. Check “download and import attachments
- 63. The imported data will include:All pages, posts, and their contents
- 64. Page (and post) template assignments
- 66. Categories and their definitions
- 67. Created menus
- 68. Users attached to siteThe import will NOT include:Widget placement not defined by theme files
- 69. Site title & slogan
- 71. Text widgets inserted via widget panel
- 72. “Home” page settingBenefits of using multi-site for development:A single database
- 73. A single place for updates
- 75. Ability to apply certain plugins by default
- 77. Perfect location for site archives
- 78. Perfect location for testing updates, new plugins, etc.