Jump to content

Loosing a character in automatic page name: bug?


Xonox
 Share

Recommended Posts

Hi,

The sites I develop using ProcessWire are, lots of times, in portuguese where we use accented characters. The problem is that when we add a page with a title like:

Cães, Canhões e Fátima

The page name I get is:

c-es-canhoes-e-fatima

When it should be:

caes-canhoes-e-fatima

As you can see, we're loosing the "a" with the respective SEO penalty. Usually, my clients can't be bothered to make the change manually, wich I think is fair on their part.

As far as I can tell,"ã" is the only character that has that problem.

Is this a bug? Is there anything I can do not to loose that "a" in the URL?

Thanks!

Link to comment
Share on other sites

BEAUTIFUL!!!!

Thanks guys! Each time I have a question I end up liking ProcessWire more and more! Everything can be reached just around the corner.

I think that "ã = a" should be default. It's strange everything working BUT that one.

By the way, it's: Admin > Modules > Core > InputfieldPageName

Thanks again for the quick response.

  • Like 5
Link to comment
Share on other sites

 I think that "ã = a" should be default.

We can propose that on Github. Done.

... and thanks for noting where the module is (and what its correct name). I know that we have this, but everytime I need it, forget how it is named and where to find it.

  • Like 2
Link to comment
Share on other sites

Ah, so you have this ~ with o and u, but not with a?

 

And in portuguese, there is no o and u with that ~?

In portuguese there's o with ~ but not u. However, o with ~ is working fine, no need to add it.

... and in my tests, u with ~ is also working.

Link to comment
Share on other sites

Interesting! You are right, the õ is already in. In PW 2.7 stable too!

But I cannot find one with the u ??

You're right. My test was not done well. I can't even insert an u with ~ through my keyboard because it doesn't exist in the portuguese language. I was inserting the page title field and watching the page name field for the result. You're absolutely right.

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By SwimToWin
      I love nice urls - but I also recognize that they are not always needed nor desired due to the additional steps in page creation.
      Suggested solution:
      Page ID Page ID is a per-template auto-incrementing number. No. series might be added on a per-template basis (to be configured by webmaster). Page url Replace the full page url with an ID (as an optional configuration). Page url might then change to something like: www.example.com/page/1234 Editing (Page Tree is much less important in this scenario.) Like Drupal's Node IDs (nid).
      Why this change? Name may reveal confidential info. Name may not matter on certain templates. Page creation is no longer a two-step process; much like adding a row in MySQL.
      Benefit: This change will make it easier to use ProcessWire for other purposes than websites ("Oh - so ProcessWire is also a finance system!").
    • By sebr
      Hi
      In my search page, I used a selector like this :
      $searchQuery = $sanitizer->entities($input->get('q')); $searchQuery = $sanitizer->selectorValue($searchQuery); $selector = 'title|subtitle|summary|html_body_noimg~=' . $searchQuery; $matches = $pages->find($selector); I don't have the same results if $searchQuery contains accent or not.
      For example,
      with « bâtiment » I have no result with « batiment » I have onea result : « Les bâtiments et les smart-city » Normally I should have the same results? How can I do that ?
      Thanks for your help
    • By Sten
      Hello,

      I still did not solve my problem about Hebrew letters. In fact, it is ok for Russian for example to have a transliteration of characters (one to one) but in languages like Hebrew, Arabic, it is better to slugify with phonetic like here :
      use EasySlugger\Utf8Slugger; $slug = Utf8Slugger::slugify('日本語'); // slug = ri-ben-yu $slug = Utf8Slugger::slugify('العَرَبِيةُ‎‎'); // slug = alrbyt $slug = Utf8Slugger::slugify('עברית'); // slug = bryt So I am planning to insert https://github.com/javiereguiluz/EasySlugger
      Should I create a module or just add a hook ?
       
      I am a PW newbie.
      Thanks for your help
       
    • By Marco Angeli
      sorry, very basic question here:
      how to edit the name of each single page that appears in my navigation?
      It seems I can only change the url....
×
×
  • Create New...