Forum Replies Created
Great, thanks. I can confirm that target, class and id attributes can now be set.
Thanks Kiran. Is that change going to be made to the core?
I can confirm that it is now possible to include links in the Field Description. Many thanks to Alex and the devs!
Sorry to be a pain, but the way it has been implemented strips out the target attribute. Being able to include target, and also class and id attributes would be very useful because:
1. target would allow you to open a page giving further instructions in a new window. If the instructions open in the same window, and the user has spent a while editing their inputs, they might get a shock and think their work has been lost.
2. class and id would allow further styling to be done easily, or to be able to hook on JS functions. This would allow the instructions to open in a pop-up over the page or an icon to be added, for example.
Fantastic, that’s looking good to me now.
Thank you Kiran.
I looked at the other available filters in the codex (says it’s for v1 only?) and couldn’t see one that would meet the other needs unfortunately.
On further experimentation I can address #1 and #4 by using the gd_post_meta shortcode instead so that leaves me with:
2. Only show the primary category, not all categories
3. Show the parent categories (this is a hierarchical structure)
Thanks Guust but CSS can’t fix this.
I don’t want all the options to be lowercase, I want the casing of the options to be maintained exactly as I entered it.
The initial capital letter is being forced on the server side by GeoDirectory, not by CSS, so by the time it is shown on the page there is no way to know if the initial letter was originally upper case or lower case.
That’s great news, thanks!
My reply seems to have disappeared… if I try to post it again it says it is a duplicate. Maybe it has gone for moderation?
OK, thank you.
It seems like a long and not intuitive way around to achieve it but it does work.
But I don’t like it from a maintainability point of view, so I would like to request from the devs that Field Description simply allows HTML – what is the right way to request that?
A couple of other questions, if you don’t mind…
As this isn’t a real translation I have left the language as en_US and put the resulting PO and MO files into \wp-content\languages\plugins. Will these get overwritten by a language pack update (mentioned in the docs)?
If the original Field Description string changes, will it stop picking up the translation?
I am setting up GD as a replacement for a 16-year old software directory that was completely custom-coded. I’ll have more support requests over the next weeks and expect that some customization will indeed be required.
Just working through it one piece at a time at the moment.