Polylang compatibility

Hello there,

Apologies for the delay in response. We were closed for the holidays and we just got back.

To answer your question, the plugin does not have any polylang specific code or have been tested with Polylang. So we do not know if there would be any conflicts or not.

The plugin simply creates a custom post type called companies which will be listed in Job addition form. It does not have any other front-end content. So most likely it should work out of the box with polylang. However, if you run into issues please do let us know and we’ll resolve them in our updates.

Kindest Regards,
Ibrahim

Thanks for your feedback. By setting up a wpm-config.xml file the post get translatable. So that works. I do not know the names of the other taxonomies that are missing but by adding them that should work out well.

<wpml-config>
  <custom-types>
    <custom-type translate="1">company</custom-type>
  </custom-types>
  <taxonomies>
    <taxonomy translate="1">company_category</taxonomy>
  </taxonomies>
  <custom-fields>
    <custom-field action="copy">_featured</custom-field>
    <custom-field action="copy">_company_name</custom-field>
    <custom-field action="copy">_company_website</custom-field>
    <custom-field action="copy">_company_tagline</custom-field>
    <custom-field action="copy">_company_twitter</custom-field>
    <custom-field action="copy">_company_video</custom-field>
    <custom-field action="copy">_company_phone</custom-field>
    <custom-field action="copy">_company_since</custom-field>
    <custom-field action="copy">_company_location</custom-field>
  </custom-fields>
</wpml-config>

I will now check how I could add a feature to allow the customers to translate their company profiles via the front end. My base idea is to duplicate the profiles on creation with Polylang and then allow the customer to adjust the languages if he wants.

One question: What is the reason you added a custom value to the company name slug? A clean slug like: company/company-name would be far nicer.

Also an improvement for the future: If I get it right when you have not an approved company profile you cannot publish a job with Workscout for example. Selling job listings it would be great to be able to create the company and use it even though it not yet approved to create your job offer. Once the job offer is paid the profile and the listing are published and approved. Avoids extra admin interactions but still avoids spam profiles. From experience no spam bots wants to pay for a profile ;).

Thanks for the great plugin, I will further play around with it and maybe contribute in the future.

• This reply was modified 2 years, 10 months ago by lens2016.

Hello again,

Thank you for getting back and thank you for sharing with us the solution.

I also thank you for your suggestion about your improvement. I’ll pass this on to our tech support and see if we can include this feature in our upcoming release.

As regards your question, the reason for our slug name is that it could conflict with other plugins and could break.

You can use the register_post_type_company filter to override the slug.

Hope this helps. Let us know if you have any other questions or need further help.

Thanks,
Ibrahim