Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8356361
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 9, 20262026-06-09T10:10:30+00:00 2026-06-09T10:10:30+00:00

I recently migrated a fairly large site (~6,000 posts) from Drupal to WordPress. As

  • 0

I recently migrated a fairly large site (~6,000 posts) from Drupal to WordPress. As part of the process, I migrated the Drupal-created url aliases to WordPress for SEO and link retention purposes.

An example of a url alias that Drupal created that worked great in Drupal:

  • /stories/will-this-be-another-la-niña-year

That url in WordPress returns a 404. However, this works:

  • /stories/will-this-be-another-la-nina-year

It seems then my best bet is to write a generic international character to english character set rewrite rule in htaccess, before the url is passed to WordPress.

Any idea how I might do this?
Thanks a lot for whatever help you can give.
Matt.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-09T10:10:32+00:00Added an answer on June 9, 2026 at 10:10 am

    It seems like there might be a better way to do this within wordpress, you may want to do a quick browser through the wordpress Trac tickets, there maybe some patch or temporary fix for the problem. But if you need to go to an htaccess/redirect method, you can either use a RewriteMap to sanitize and redirect-if-needed or explicitly redirect on non-ascii characters.

    A RewriteMap requires access to either server or vhost config to setup the map. It could be as simple as a list of /stories/will-this-be-another-la-niña-year URIs mapped to http://yourdomain.com/stories/will-this-be-another-la-nina-year (the all ascii URL, the http:// is significant because it tells mod_rewrite to redirect the browser). Or you can write a script to look for non-ascii characters and replace them with the appropriate ascii character.

    Text mapping:

    RewriteMap sanitize txt:/path/to/uri_mapping.txt
    

    Script mapping:

    RewriteMap sanitize prg:/path/to/sanitize_script.php
    

    Then in your htaccess file, you can invoke this mapping like this (these rules will need to be above the wordpress rules, since you want the URI sanitized before wordpress gets a hold of them.

    RewriteRule ^(.*)$ /${sanitize:$1|$1} [L]
    

    If you don’t have access to server/vhost config, you’ll have to enumerate the possibilities in your htaccess file, again putting these rules above the wordpress rules:

    # replace ñ
    RewriteRule ^(.*)ñ(.*)$ /$1n$2 [R=301,L]
    
    # replace ú
    RewriteRule ^(.*)ú(.*)$ /$1ú$2 [R=301,L]
    

    etc.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Fairly exotic it seems to me. We recently upgraded/migrated from Windows Server 2003 to
I recently migrated a django project from mysql to postgresql and in the process
I recently migrated a large AS3 site (lots of swfs, lots of flvs) to
I recently migrated a WordPress site to a new server and new domain name.
i recently migrated my whole DB from myisam to innodb. I am fairly new
We have recently migrated a large, high demand web application to Tomcat 5.5 from
I recently migrated a Wordpress network of two sites from a local MAMP server
I've recently migrated my wordpress.com blog to wordpress.org. When my posts include a [
I recently migrated my JSF app(using primefaces) from glassfish 3.1 to tomcat7 server. Previously
We have a 3.5 Gb SVN repository recently migrated from a 6 Gb one.

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.