brownbagmarketing

Well… what can I say but dev is dev…

In setting up the dev site to provide example links, it all appears to be working in dev now… sigh.

Leaving this open because I have it feeling it is not resolved. And any insight anybody might have as to why this is occurring in my local would be very welcome.

Still not resolved. Multiple attempts to reach you. I understand it’s annoying, it’s also annoying to my client.

If you could maybe share what the fix is, I’d be happy to implement?

https://www.floridacitrus.org/grower?s=past+events

This is not resolved. We are using pro.

Hi Kawashar,
The problem is still there.

We are not using a caching plugin on the site.

The Hosting platform has some sort of adaptive cache, but not really anything configurable in the hosting tools that I’ve seen.

Thanks

Right now I have no solution.

The select looks to be correctly formed and rendered.

Your error message snippet that you posted originally seems to indicate the question is being submitted as an Array.

Where did that code snippet come from?

Can you verify that the post does contain “question_15066172002” as an array?

Have you reached out to Greenhouse to see if something different needs to happen for the submittal to the API?

I can’t troubleshoot what happens in your backend, I can only see what happens client side.

The select seems to be formed correctly.

The code snippet you posted in your original question seems to have the multi-select input values in an array.

I went back to look at your example this morning and it’s no longer available.

Hmmm…
Do you have a link to the page I could take a look at?

Looks like your multi-select is an array.

[question_15066172002] => Array
        (
            [0] => 68473102002
            [1] => 68473103002
        )

Is it rendering a select box or a list of radio buttons?

If it’s a select box, can you inspect the code and to see if it’s properly adding the “multiple” attribute to the select box?

We too are having the same issues with our Elementor site.

I found that if I renamed the wp-content/nitropack folder to wp-content/nitropack_bak and went to my site, the pages giving us issues look correct and the “nitropack” folder reconstitutes itself.

So looking into the old nitropack_bak folder I noticed config.json and .htaccess files that did not appear in the reconstituted folder.

So… I copied them into the new wp-content/nitropack folder and my problems came back.

Removed config.json file and the problem went away.

Maybe support can chime in here and give us some insite to this?

I deleted the plugin from dev and reinstalled it and the admin are is working again.
This does not make me comfortable.

The URL token is the name of your job board on green house.
The API call to GreenHouse uses it like so:
https://boards-api.greenhouse.io/v1/boards/{URL token}/jobs

If you go to Plugins and select “settings” for the Greenhouse Jobs plugin, it will tell you where to go to get the URL token and Greenhouse API key.

The instructions under “installation” must be outdated.

Just use the shortcode [greenhouse] once you get the URL token and enter it in the Greenhouse Job board settings.

Glad you got it worked out.

FYI, the token is only used for POST to the Greenhouse API, like an application submittal. The jobs are publicly available via the API so no need for a token to GET the jobs.

It looks like you’re not returning any jobs. Can you set a breakpoint on line 698 in greenhouse-job-board-public.js and tell us if you have any jobs in json.jobs?

Or do you have a link to your dev site?

Try [greenhouse] for your shortcode.

You would need to use the “location” value from the greenhouse api.

This should filter for jobs in London and Shanghai:
[greenhouse location_filter=”London|Shanghai”]