korneelwever

Actually I found that that was to far down. The problem already occurs when the get_job_listing_types(); is called https://github.com/Automattic/WP-Job-Manager/blob/master/includes/class-wp-job-manager-ajax.php#L88

Found in https://github.com/Automattic/WP-Job-Manager/blob/master/wp-job-manager-functions.php#L257

But that has a beautiful ‘function_exists’ around it, so I could overrule it in my theme. And solve my problem. I’ll contact the Polylang author about it too, maybe he knows of a permanent solution.

Further logic explanation:
Polylang inserts itself in every query to pull up language related content. So missing the right language defaults to returning the listing types of the default language.
And obviously that would have no listings in the second language.

Again, thanks for your help. This topic can be closed.

Thanks!
I don’t know how I missed that! Will try and respond (probably tomorrow).

Cheers,

Ah, didn;t get notifications on that one, wasn’t sure where to get attention ??

First suggestion fixed it: rocketload was set to automatic, I’ve switched it off.

Yeah, I went with framework first, that didn’t work. Then I went with an exact copy of the pot file name. So clearly that didn’t work either, for reasons I understand now (the text domain is different and I didn’t declare it).

Your last note helped, I forgot to declare the text domain in the plugin!

Thanks, it looks like it’s working!

So for any people finding this via the Google:
I made a dummy plugin with just a readme.txt, a functions.php and the framework.pot file.
I named it ‘framework’ and declared the text domain as such in functions.php:

function my_plugin_load_plugin_textdomain() {
    load_plugin_textdomain( 'framework', FALSE, basename( dirname( __FILE__ ) ) . '/' );
}
add_action( 'plugins_loaded', 'my_plugin_load_plugin_textdomain' );

Then I could use Loco Translate to add a translation which I added to the ‘global’ upon creation.
I’m not 100% sure if loading the text domain this way is the absolute correct way of doing it, but that’s what I found and this works.
Note: if your translations don’t show up, clear your server and browser cache!

Hey Tim,

Thanks. I’ve created a plugin with just ‘framework’ and saved it’s translation in the global directory. I’ve named the plugin runway-framework and just copied the pot file. Loco sees it and I can translate, but it doesn’t show. So I think I need to do the second step you mentioned. Now, the parent theme has an existing translation, do you suggest to move that, or everything? Is there a quick way to do this?
Thanks for your time, it’s very kind to provide free support ??

Yep, running the plugin, https protocol rewriting is switched on.
Not using Falcon Cache.

Hey,

Got it, i accidentally skipped uninstall, went-> deactivate->remove. Looked ad your code and saw the version check and uninstall option.
Used uninstall then it worked. Thanks!

Got it, will try tomorrow. Thanks!

Hey, thanks,
I’m running into problems and keep being sent back and forth between old versions. So, since we had only a couple of events I decided to remove the plugin and install the latest version. However, I still get the message.

I have no problem with sql-ing to remove any traces and have a clean start, just let me know what to do.

Cheers,

nvm. my bad.

Since the last update the homepage seems to be unable to determine the language. I get all items mixed together. Setting the default language does not help either.
Once the language is set via the URL it works fine.