Closed Bug 551437 Opened 14 years ago Closed 11 years ago

Add Frisian to WPML for opentochoice

Categories

(Websites Graveyard :: opentochoice.org, defect, P1)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: stas, Unassigned)

References

Details

(Keywords: l12y)

Attachments

(1 file)

+++ This bug was initially created as a clone of Bug #547604 +++

Frisian is not supported by the WPML plug-in. We should support it. Javier, could you come up with some SQL magic to add it, please? The code is "fy-NL", the natie name is "Frysk". I don't think we need other languages' names in Frisian.
Sure Stas... working on it.
Assignee: nobody → javier.morales
Here is the script, please execute it on the stage database so we can test it. I tried it out on my local DB and it worked fine.
Assignee: javier.morales → nobody
create IT bug for running sql on stage, bug 551781
Depends on: 551781
CC'ing QA, since this is on stage now.

What's next?
I'm still being 302'd to /en/, with Frisian [fy] set as my primary language:

http://opentochoice.stage.mozilla.com/



GET / HTTP/1.1

Host: opentochoice.stage.mozilla.com

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6

Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8

Accept-Language: fy,en-us;q=0.5

<snip>

HTTP/1.1 302 Found

Date: Mon, 15 Mar 2010 20:25:44 GMT

Server: Apache/2.2.3 (Red Hat)

Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0, private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0, private

X-Powered-By: PHP/5.2.9

X-Pingback: http://opentochoice.stage.mozilla.com/xmlrpc.php

Pragma: no-cache

Location: http://opentochoice.stage.mozilla.com/en/
Comment 5 fixed in r64183
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
The redirection works, but http://opentochoice.stage.mozilla.com/fy/ is a 404?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Priority: -- → P1
Yes Stephen. We don't have content loaded in Frisian on stage.
Status: REOPENED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
Do we have that content on production?  Do we need to import production to stage?
No, the content cannot be created on production until we add the language to the database.
If you need a sample-content, just copy over an article from the Dutch articles.
I hope you get this working.
If you need a Frisian flag, you can find it here:
http://home.kpn.nl/~wbrch/mozilla/fy-NL.png.
Is this going to get from stage to live before the weekend?
Would be nice since I have some sparetime left.

Thanks in advance.
Alex, what we need to do in order to get the script executed on Live?
This SQL will be run today.  bug 554110 is the IT updates bug
Frisian has been enabled on production: https://opentochoice.org/wp-admin/edit.php. The flag is the Dutch one, but since it's only displayed in the wp-admin, I suggest we leave it as such. Wim, does it sound ok?
Don't know what happened. Yesterday evening I was able to find an empty language which appeard to be Frisian (Frysk), although the rest of the Wordpress layout was screwed up.
This morning I can't find Frisian at all, did you revert the SQL modification due to the layout problems?
If you need a proper flag, see comment #12.
Can someone please take a look at this, since fy-users are now redirected to a non-existing page.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Thanks Wim. I fixed this in r64618 and filed bug 554613 to get this to production.
Depends on: 554613
Product: Websites → Websites Graveyard
Status: REOPENED → RESOLVED
Closed: 14 years ago11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: