News/2013 Archive

Recent updates
* **Current News**

2013 updates
* Saturday 27th of April  (talk)
* Friday 18th of January  (talk)

**This is an Archive of the news from 2013. Please do not edit it.**

## April 27, 2013: Wiki migration and user merge

On May 1, the PvXwiki will be migrated to Curse's new **Gamepedia platform**.

### What is the Gamepedia platform?

The "Gamepedia platform" has been designed by Curse's Wiki Platform Team to assist in the management of Curse's wiki network. It allows unified login across the entire Curse network through the netbar at the top of each page. All users are then logged in through the central user database. It also incorporates the Curse footer. These two items help to standardize the look and feel of our wikis with our other properties.

Aside from these front-end items, the Gamepedia platform allows the wiki team easy access to implement MediaWiki extensions as requested by our communities, as well as other basic configuration settings. It also allows our Wiki Platform Team to upgrade MediaWiki software on all the wikis at one time, rather than having to do each one separately. This is a major time saving step. Prior to the development of this platform, it would take up a significant amount of time to upgrade all of our wikis. This kind of mass management is the driving idea behind its development.

### How does this affect me?

The most direct affect the migration will have on individual users of PvXwiki will be visible the first time they try to login to the "new and improved" wiki. We have set up a User Merge process that will compare your user information with the main Curse user database and either merge your wiki account with an existing Curse account, or will create a new Curse user account that will then be valid on all Curse.com websites.

### The User Merge process

After the migration has been completed, users will be asked to login normally. The system will compare the wiki's user database, and the Curse.com user database.

* If your wiki username and e-mail address match exactly to an existing Curse.com account the two will be merged, and you can continue to edit normally.
* If your e-mail address matches a record in the Curse.com database, but the username is different, the system will use the Curse.com username for the wiki. You will also be granted a one time display name credit to choose a display name that will then appear throughout the wiki (default signatures/recent changes/userpage).
* If your e-mail address does not match any existing account in the Curse.com database, you will be asked for a username. If the username does not match an existing username in the Curse.com database, a new account will be generated.
* If your Username matches, but not the e-mail address on the wiki account, the system renames user on wiki <username001> - you can link to existing Curse account or create a new Curse account. This also grants a display name credit.
* If neither e-mail address or username exist in the Curse.com database, a new curse account is created automatically.

### What do I do if I have problems merging my accounts?

If you run into problems merging your account, please email wiki@curse.com as soon as possible and someone will assist you.

## January 18, 2013: Closing Time

Activity on the wiki has died down considerably since the release of GW2. We have more vandal and troll edits than we do legitimate edits, and no one seems to be interested in keeping the wiki up-to-date with whatever metagame is left in Guild Wars. I am the only active admin remaining, but I am seeing less and less reason to monitor the wiki daily. With these things in mind, I am proposing a lock on anonymous editing and account creation similar to Guildwiki's.

Please discuss this proposal on our Community Portal. By next Monday, I will be implementing the lock if there are no significant objections. —*The preceding unsigned comment was added by* Toraen (talk • contribs) 22:00, 18 January 2013‎ (UTC).

Update: The lock is now in effect. -- Toraen confer 23:20, 21 January 2013 (UTC)