Closed
Bug 971433
Opened 11 years ago
Closed 10 years ago
Migrate Mozilla Côte d'Ivoire to WordPress Multisite
Categories
(Participation Infrastructure :: MCWS, task)
Participation Infrastructure
MCWS
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: Logan, Unassigned)
References
()
Details
(Whiteboard: [blocked: WPMS])
This is a bug that will track the migration of Mozilla Côte d'Ivoire to our new WordPress Multisite installation. We are doing this to ensure security and consistency across all Community IT-hosted websites.
The cooperation of the maintainer of this WordPress site will be crucial in getting this done. I have requested information from the person who appears to be most involved, but please let us know if there is someone else who controls it.
As part of this process, we will need to know what plugins are necessary, as we will have to reinstall them as part of the transition. Some may be incompatible, so flexibility will be required in some cases.
As for first steps, can we first get an OK from the current maintainer of the WordPress site for the eventual transfer to our WordPress Multisite installation?
Reporter | ||
Updated•11 years ago
|
Flags: needinfo?(yorogoule)
Comment 1•10 years ago
|
||
Moving over to new Community IT components.
Component: Server Operations: Community IT → Community IT: Hosting
Product: mozilla.org → Infrastructure & Operations
Updated•10 years ago
|
Whiteboard: [blocked: WPMS]
Comment 2•10 years ago
|
||
Yes you can transfert our site in WordPress Multisite installation , but make a backup please [:Logan]
Flags: needinfo?(yorogoule)
Reporter | ||
Comment 3•10 years ago
|
||
WordPress Multisite is no longer a solution we are considering. We are looking at other ways to move our WordPress sites on shared hosting and VPSes. Closing this accordingly.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Comment 4•6 years ago
|
||
Bulk move of bugs
Component: Community IT: Hosting → MCWS
Product: Infrastructure & Operations → Participation Infrastructure
You need to log in
before you can comment on or make changes to this bug.
Description
•