David Sirius
Forum Replies Created
-
Posts
-
Hi Kiran,
Thank you for looking into this. I’m currently running the site on my localhost but I’ll upload the website today so you can have a look (this was overdue anyway).
You can replicate the error by creating 40 custom fields (Im using type checkbox) in GD -> Place Settings -> Custom fields that you all make eligible for the advanced search via each setting of the custom field. When getting to c 30 you should start getting the same error message and these custom fields will even disappear but reappear when you refresh.
Now most of your custom fields will appear in the advanced search tab (still GD -> Place Settings), however you will notice some are missing, ie those you got the error message for.
I presume the easiest way for you to check this and track each custom field would be to just give numerical names to the custom fields of 1-40.
I believe the error may stem from the advanced search tab that can only handle a limited number of custom fields.
I will provide you with logins to my site later today.
Thanks,
DavidShortcodes are a general feature of WP, so would have expected there to be a solution how to use them in files (outside the WP pages). I did quite some research and typically the php shortcode I posted should work to call shortcodes but not for geodir. I dont think its practical to limit usage of the shortcodes to pages only created in the wordpress dashboard itself. Anyone serious in using the geodir plugin will build its own complementing pages from scratch. Anyway, I understand I wont get support on this here.
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,
DavidYes 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.
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.
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
DavidFantastic, works perfectly! Didnt think it would be easily solvable via CSS.
Thank you so much!!
Hi Kor,
The link I posted is an example geodir page (not my page!) to demonstrate how I want it to work, while my page has the issue as per screenshot in original post (i.e. hr line is static).
I want a grey divider line like in this screenshot (attached marked in red border), but naturally only when the listview ist active. So when the listview is not active ie. a grid view is selected 2-5 then the hr line needs to dissappear like in your screenshot from the example page otherwise the results are not aligned next to each other because the hr line breaks each result item (as you can see from my first screenshot).
Thank you for looking into this!
Cheers,
DavidChanging the code:
Couldnt I just copy the file into my supreme directory folder and amend it there? I’m not planning to update the supreme directory theme as I have customised it extensively.Translation:
As per above, the translation doesnt allow to eliminate the space between “Places” and “:” see again screenshot attached..You can translate “Search” and “For :” separately, for example “Search” and “for:”, so the result becomes Search Events for: ‘party’ ‘Amsterdam’
OK. There was a also missunderstanding on my behalf then, I didnt know that “For :” is indeed an existing source text in POedit and thus translatable. I translated “For :” to “for:” but that didnt change eliminate the space. I presume its because I already translated “Search” “Places” to “Results” “for” and changing “For :” to “for:” would only change accordingly where “For :” is originally placed in the code but not layered on top via a language file.
If you translate “Places” that will be translate “Places” on other pages too, so you should only translate it with something similar like “Businesses” or “Listings” etc
Understood. The better solution would be then to not translate it via POedit but change the words in the code, i.e. find the PHP code that outputs “Search Places :” and replace it with “Results for:”. In which file would I find the code?
I think we are missunderstanding, I’ll explain what I did in more detail:
1. I downloaded and installed POedit (see https://wpgeodirectory.com/docs/translate-core/)
2. I followed steps 1.-7. to create a new language file (German)
3. I made various translations on the search page which all worked fine
4. The original supreme theme has a header on the search page showing “Search Places :” see also in the demo https://wpgeo.directory/supreme-directory/?geodir_search=1&stype=gd_place&s=+&snear=&sgeo_lat=&sgeo_lon=
5. I tried to rename this via the translation tool POedit by changing “Search” to “Results” and “Place” to ” for”. However the colong is not shown in POedit (source text) so it the space and colon must come from a template filePlease dont be confused by the fact that I said I created a German file and now I’m making English to English translations, this is just to demonstrate the problem (German prahses wouldnt help solving this). Eventually Results for will be something in German.
I adjusted my translation for “for” to ” for :” and that did indeed changed For to lowercase for. But the problem with the space before the colon remains. In the screenshot you see two colons because I entered it exactly as you provided,but even if I remove the colon (‘ for ‘) or colon and space (‘ for’) the space remains.
I’m confused. The “Results For” you see in my screenshot is already my translation by entering “Results” for “Places” and “for” for “Places”. So there is no actual string from the code of “For” that can be translated. Or maybe I missunderestand your solution.
The regular supreme directory theme.
Hi Guust,
Unfortunately, the website is currently only on localhost. I hope there is still a solution?
Many thanks,
David
