Your plugin vs. Jetpack

Just select post and page from the dropdown list.

Thank you! have a good evening

Now, I have a question regarding FB. Where my posts will be published? On my timeline? Or in the groups I am a member of? How do I set these options?
Thank you in advance.

Plugin will post to whatever profile, page or group you had in the “Facebook URL” field at the time of your last authorization.

Hi!

@nextscripts Polylang does not use custom fields to set the language but a taxonomy. It’s possible (I did not test) that the only thing to do is to add the ‘language’ taxonomy to nxs_filters::$taxonomies. It is currently not included because you include only public taxonomies, while the ‘language’ taxonomy has ‘public’ => false and ‘publicly_queryable’ => true

I see 3 possibilities to improve the compatibility between both plugins:
1. Add explicitly the ‘language’ taxonomy to your taxonomies for specific compatibility with Polylang
2. or increase the set of allowed taxonomies by using ‘publicly_queryable’ => true instead of ‘public’ => true
3. or ad a filter which would allow any developer to modify the list of taxonomies.

Hi again,

the author of my language plugin has just sent you a solution. Could you please incorporate it in your plugin so that I can connect my blog with the social sites? Thank you in advance.
I have a question regarding the custom fields in a post – please see the attached picture:

In the drop-down menu, there is no option for language selection. How should I proceed?
Thank you in advance!

Milada

Hi again,

can you please reply to both messages? I would love to finally launch my site.
Thank you very much in advance!

Milada

1. By making taxonomy not public, developer basically asks us not to use it. I am not sure the good solution will be us to include non-public taxonomies, but not the developer of your language plugin to make it “public”.

2. There is an “Enter New” link hidden on your screenshot under opened dropdown.

@nextscripts yes you are right. The language taxonomy is not public because I don’t want the language being displayed by themes (a lot of themes display custom taxonomies terms beside categories). I made it publicly queryable though. That’s because it can be used it queries.

That said, I understand your reticence to change from ‘public’ => true to ‘publicly_queryable’ => true. That’s why I proposed two other ways to make SNAP compatible with Polylang. Either you add the ‘language’ taxonomy and I have nothing to do. Or you can add a filter to allow all 3rd party plugins to modify the list of taxonomies. And I will hook to this filter to add the language.