Bug 975 - http://blog.mageia.org/et is not exist. Please foward it to english page
Summary: http://blog.mageia.org/et is not exist. Please foward it to english page
Status: RESOLVED FIXED
Alias: None
Product: Websites
Classification: Unclassified
Component: blog.mageia.org (show other bugs)
Version: trunk
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Romain d'Alverny
QA Contact:
URL: http://blog.mageia.org/et
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-25 12:55 CEST by Ojangu
Modified: 2011-06-13 12:33 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Ojangu 2011-04-25 12:55:38 CEST
http://blog.mageia.org/et is not exist. 

Please foward it to english page on http://www.mageia.org/et/ page.
Comment 1 Ahmad Samir 2011-04-25 17:04:40 CEST
Well, the point is "Estonian" doesn't exist in the header in the blog http://blog.mageia.org , so why would a non-existinghttp://blog.mageia.org/et redirect anywhere?
Comment 2 Marek Laane 2011-04-25 17:08:19 CEST
But there is "Ajaveeb" (=Blog) on http://www.mageia.org/et/ which directs to non-existing http://blog.mageia.org/et - and if clicked, of course, "404 Not found" happens...

CC: (none) => bald

Comment 3 Ahmad Samir 2011-04-25 17:59:18 CEST
I see what you mean now. Sorry for the noise :)
Comment 4 Romain d'Alverny 2011-04-26 09:33:59 CEST
That's more the global navigation links to be fixed.

Status: NEW => ASSIGNED
CC: (none) => rdalverny
Assignee: mageia-webteam => rdalverny

Damien Lallement 2011-06-10 10:24:16 CEST

CC: (none) => mageia

Comment 5 Damien Lallement 2011-06-10 18:45:08 CEST
Bug fixed.
Now only redirect on /{$locale}/ for existing blogs.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED

Comment 6 Marek Laane 2011-06-10 23:56:03 CEST
well, http://blog.mageia.org/et still gives 404...
Comment 7 Marek Laane 2011-06-13 12:28:45 CEST
Now it seems to work!
Comment 8 Romain d'Alverny 2011-06-13 12:33:26 CEST
The /et blog still doesn't exist (no one to manage it, but that's open). It's just the update that got pushed into production this morning.

Note You need to log in before you can comment on or make changes to this bug.