Renaming search page title

This topic contains 20 replies, has 4 voices, and was last updated by  David Sirius 6 years, 3 months ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
  • Author
    Posts
  • #411730

    David Sirius
    Expired Member
    Post count: 163

    Hi Alex

    I’m not deleting any strings.

    I just want to get rid of that typo space that is produced by the geodir code.

    The very general text format in any western language for a colon is ‘text:’ not ‘text :’ so it would be fantastic to correct it and given that it’s not a translation problem, it is indeed a bug/typo in the code.

    Thanks
    David

    #411736

    Alex Rollin
    Moderator
    Post count: 27815

    Hello!

    I am sorry for the misunderstanding.

    What I meant was, that is not a bug. You can change the string as Stiofan pointed out. I attach a screenshot for clarification.

    Thank you for your understanding

    #411751

    David Sirius
    Expired Member
    Post count: 163

    No worries Alex.

    Understanding you joined the topic later, please see my reply to Stiofan before (#411660). I already tried replacing ‘For :’ to ‘for:’. It doesnt change anything for this typo space, because “for” doesnt appear when you search by post code/near me, it only appears when searching by name.

    The way the geodir plugin (oddly) works is that when you search by name of the place, the headline on the search page will be ‘Results Places For :” so you can translate that to ‘for:’ (see screenshot 1 from demo). When you search by zip code the headline on the search page will be “Results Places :” (see screenshot 2 from demo), so there is just different output by the plugin depending on whether you search by name or zipcode/near me. Both have the typo space, but only once can be correct with translation.

    Try it yourself on the demo: https://wpgeo.directory/supreme-directory/?geodir_search=1&stype=gd_place&s=tasty&snear=&sgeo_lat=&sgeo_lon=
    1. Search for tasty –> no typo space in headline (screenshot 1)
    2. now search for zip code or near me –> typo space in headline (screenshot 2)

    That why Stiofan’s suggestion works only when searching for a name because the plugin code has “For :” in it. But when searching for zip code or near me, there is no “For :” in the output and so translating doesnt make sense.

    #411777

    Alex Rollin
    Moderator
    Post count: 27815

    Looks like there is a colon string, too, preceeded by a space.

    See attached

    #411792

    David Sirius
    Expired Member
    Post count: 163

    Yes that would make sense and was my thought yesterday as well after discovering the different outputs, but I couldnt find it. I will have another thorough look in a bit, I must have overseen it.

    #411799

    David Sirius
    Expired Member
    Post count: 163

    Thank you Alex. I got it to work now.

    For anyone attempting the same:

    For zip code search:
    I basically replaced the ‘ :’ with a space ‘ ‘ and added to the colon to the second word, i.e. translated ‘Places’ to “Germanword:”

    For name search:
    I translated ‘For :” in a space ‘ ‘ and given that ‘Places’ is already renamend to a word with colon for the zip code search, thats the only change needed.

    Cheers,
    David

Viewing 6 posts - 16 through 21 (of 21 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket