Plugin Author
JK
(@justin_k)
Oh wow – I didn’t think anyone else was actually using that, sorry.
The change was because my original free/premium design of just overwriting the entire tag was really messy, and I’d planned to redo it up a bit in a future version – perhaps use HTML5 rather than xfbml and document.write().
I just submitted an update (2.5.3) that adds a new filter (renamed to reflect the fact that it ONLY applies to the text, not the whole entire tag) 🙂
Great! And what is the name of this new filter?
Plugin Author
JK
(@justin_k)
…Ummm, I don’t see why you don’t just open the file and look, but it’s wpfb_button_text… 😛
Ok but it seems this filter applies only to free version. How can I do with Premium version?
Plugin Author
JK
(@justin_k)
…Just do it in the options. There’s no need to use a filter with the premium version, never has been.
Please read what I wrote. I used this filter to change the button label according to language. So I need a programmatic way to change it.
Plugin Author
JK
(@justin_k)
Ohh, *according* to language – I thought you meant you were just setting it to the language of your site.
Why not just:
set_option($opt_jfbp_buttontext, “yourtext”)
in wp_head or something, based on the current language…? It’s equivalent to doing it in the options, but programmatic…
