pbearne / Bullhorn2WP

fixed version of the Bullhorn2WP plugin
5 stars 11 forks source link

Missing Resume Upload Button and a Few Other Items #16

Open VR51 opened 7 years ago

VR51 commented 7 years ago

Hi, I've not long installed the plugin. Noticed a couple of items you will want to look into and I have a general question.

1) The resume upload button is missing from the individual job listing page. The form fields display but the browse for file button does not show.

2) I notice there is a Skills taxonomy. It appeared with the latest plugin update. There is no shortcode for it yet.

3) The shortcode columns attribute has a little bug. When the [bullhorn] shortcode is used several times with the same page and the columns attribute is set with a different value for each shortcode, the value in the last encountered shortcode is applied to all [bullhorn] shortcodes within the page e.g. I'm unable to list 2 columns then 3 columns within the same page.

4) Can we add more fields to the application form and will those fields send data back to Bullhorn?

Thank you for this plugin. It looks to be exactly what I'm looking for.

pbearne commented 7 years ago

The missing button sounds like a css problem can you check source to see if is there

What sort of shortcode do you want for the skills I was thinking that it could be used as a category archive

I will have to look at have more than one shortcode on a page

Yes we have/are adding actions/filters to allow extra form fields. The question has always been where do we save the extra data

We just added a call to add a note to the candidate so you can use this filter to add content to the note

wp_bullhorn_note_content

you can add to the form with these filters wp_bullhorn_shortcode_elements_to_show set the requeired elements wp_bullhorn_shortcode_elements_to_require

and handle custom inputs with this action wp_bullhorn_render_cv_form_default_input

You will have to read the code to understand how to use these as I haven't create any doc's for them yet

If you need custom coding do reach out and we will be happy to work with to get this working as you need

Paul

paul@bearne.ca

pbearne commented 7 years ago

you will need to get the latest version for all the filters

VR51 commented 7 years ago

Thank you for your quick reply.

The upload button is not present in the source code. There are hidden form elements for the position, post and CV form IDs, and the page referrer but there is no upload button. You can see what I mean here.

I was thinking the skills shortcode would be a category archive too. Maybe with option to display counts.

Thank you for adding these hooks. I can see that wp_bullhorn_shortcode_elements_to_show and wp_bullhorn_render_cv_form_default_input are for the shortcode (so are in shortcode.php). Do they also affect the general form placed at the bottom of individual job listings? I assume wp_bullhorn_render_cv_form_default_input does?

pbearne commented 7 years ago

wp_bullhorn_render_cv_form_default_input may not yet be in use for the bottom of the job page it is a recent addition and the code is in flux

pbearne commented 7 years ago

Fix regrestion pull new version

VR51 commented 7 years ago

It's there now. Thank you. The invalid token error occurred on first attempt but reconnecting to Bullhorn in the site admin solved that. Will let you know if that happens again.

I found the extra admin settings options, too, for the resume upload button and message (note) field. Looks great.

VR51 commented 7 years ago

Some extra info for you.

I have now added WP Job Manager into the mix. Initially, no matter how hard I tried (or the server tried) I could not sync with Bullhorn from the WP Job Board > Bullhorn admin page. I was always met with the invalid token error. However, the Bullhorn2WP synced properly with WP Job Manager disabled.

With WP Job Manager installed and activated,

All the above failed to enable synchronisation with Bullhorn.

What did work was,

It seams that the access token is not being added to the database when WP Job Manager is used.

I will keep monitoring this.

Thanks again, Paul.

pbearne commented 7 years ago

The URL you need to give to bullhorn support for the API white list changes when you use WP job manager as we move the settings page into the Job Manage settings

You need to get Bullhorn support to ADD the new URL to the white list

Does that make sense?

Paul

Paul Bearne Freelance Senior Full-Stack WordPress Developer Cell: +1 647 780 7594 Home Office: +1 416 792 8894 *E-mail: *paul@bearne.com pbearne@gmail.com @pbearne http://twitter.com/pbearne or +pbearne https://plus.google.com/u/0/100456877588970933323

On 28 June 2017 at 08:48, Lee notifications@github.com wrote:

Some extra info for you.

I have now added WP Job Manager into the mix. Initially, no matter how hard I tried (or the server tried) I could not sync with Bullhorn from the WP Job Board > Bullhorn admin page. I was always met with the invalid token error. However, the Bullhorn2WP synced properly with WP Job Manager disabled.

With WP Job Manager installed and activated,

  • I tried reconnecting to Bullhorn
  • I tried uninstalling then reinstalling Bullhorn2WP then syncing with Bullhorn through WP Job Manager.
  • I tried disabling WP Job Manager then refreshing the access token from the Bullhorn2WP settings alone.
  • I asked a Bullhorn Support Analyst to whitelist the wp-admin/edit.php?post_type=job_listing&page=job-manager-settings#settings-bullhorn but was told this is not needed because Bullhorn whitelists the entire domain (though Bullhorn support has given me conflicting info here).
  • I cleared the database of data stored in table 'bullhorn_api_access' and tried to connect afresh to Bullhorn via WP Job Manager. This table remained empty after this attempt to reconnect.

All the above failed to enable synchronisation with Bullhorn.

What did work was,

  • Disabling WP Job Manager
  • Reconnecting with Bullhorn via Bullhorn2WP after the table 'bullhorn_api_access' had been emptied.
  • Re-enabling WP Job Manager
  • Clicking 'Sync Now' in WP Job Manager > Bullhorn.

It seams that the access token is not being added to the database when WP Job Manager is used.

I will keep monitoring this.

Thanks again, Paul.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/pbearne/Bullhorn2WP/issues/16#issuecomment-311649605, or mute the thread https://github.com/notifications/unsubscribe-auth/AAC0vuMEtUSTG98xdCbrxC_Fou04Iqmrks5sIkuGgaJpZM4OEP6k .

VR51 commented 7 years ago

I requested that Bullhorn whitelist the new URL before I posted the above. Bullhorn said they did not need to whitelist the new URL because they only need to whitelist the domain.

To be completely honest, Bullhorn has provided consistently contradictory information whenever I have spoken with them. I will speak with them again.

pbearne commented 7 years ago

Yes they are like that

You will need to explain you have moved the end point

Paul

Paul Bearne Freelance Senior Full-Stack WordPress Developer Cell: +1 647 780 7594 Home Office: +1 416 792 8894 *E-mail: *paul@bearne.com pbearne@gmail.com @pbearne http://twitter.com/pbearne or +pbearne https://plus.google.com/u/0/100456877588970933323

On 28 June 2017 at 18:41, Lee notifications@github.com wrote:

I requested that Bullhorn whitelist the new URL before I posted the above. Bullhorn said they did not need to whitelist the new URL because they only need to whitelist the domain.

To be completely honest, Bullhorn has provided consistently contradictory information whenever I have spoken with them. I will speak with them again.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pbearne/Bullhorn2WP/issues/16#issuecomment-311812427, or mute the thread https://github.com/notifications/unsubscribe-auth/AAC0vs57AslI7_LlWCXiq9i10VqmnAMaks5sItapgaJpZM4OEP6k .

VR51 commented 7 years ago

Thanks Paul. I will do that.

As a note, I am able to synchronise job details with Bullhorn using the token generated earlier today (using Bullhorn2WP to get the token then WP Job Manager for the extra features) but only some test job applications will sync with Bullhorn. Thought I'd mention this in case you find it useful.

I have mentioned your plugin to Bullhorn, too, as requested in the Install Instructions :-)

pbearne commented 7 years ago

Job should upload as added / sync on their own

Check you have latest code few more fixes added

Paul

Paul Bearne Freelance Senior Full-Stack WordPress Developer Cell: +1 647 780 7594 Home Office: +1 416 792 8894 *E-mail: *paul@bearne.com pbearne@gmail.com @pbearne http://twitter.com/pbearne or +pbearne https://plus.google.com/u/0/100456877588970933323

On 28 June 2017 at 19:46, Lee notifications@github.com wrote:

Thanks Paul. I will do that.

As a note, I am able to synchronise job details with Bullhorn using the token generated earlier today (using Bullhorn2WP to get the token then WP Job Manager for the extra features) but cannot sync job applications. I understand the reason for this but thought I'd mention it in case you find it useful.

I have mentioned your plugin to Bullhorn, too, as requested in the Install Instructions :-)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pbearne/Bullhorn2WP/issues/16#issuecomment-311822854, or mute the thread https://github.com/notifications/unsubscribe-auth/AAC0vlnMbHAnRU7F1hsWKTE8SuL-LbRoks5sIuXwgaJpZM4OEP6k .

VR51 commented 7 years ago

Hi Paul, I apologise for my late response. Had all sorts of fun speaking with Bullhorn support.

To briefly explain where are. We are using WP Job Board with Bullhorn2WP. We need to have the root URL whitelisted by Bullhorn but they now tell us the URL is too long (insert any image of me backing my head against my desk).

The URL is now:

http://dev.example.com/wp-admin/edit.php?post_type=job_listing&page=job-manager-settings#settings-bullhorn

The previous URL was:

http://dev.example.com/wp-admin/options-general.php?page=bullhorn

That last URL was short enough for Bullhorn to whitelist. I'm wondering whether we can shorten the longer URL or can we move the Bullhorn settings page from WP Job Board back to Settings > Bullhorn ? What do you suggest/think?

pbearne commented 7 years ago

What a pain !!!!! Do we know to we know the max length?

We will/can change this but we will need to change the code.

My plan is to more it to domain.com/api/bullhorn/auth and do the save at this location then do a redirect to the settings page

This is going to take a few days to fix as we are in the mid of a bit of rewrite so if you can bear with us for a bit that will help

Paul

VR51 commented 7 years ago

I asked for the maximum URL length but Bullhorn said they didn't know, just offered that the previous URL was 65 characters long so to try and keep it to that length or less.

I appreciate the work you put into the plugin. A few days I can wait easily. Thank you, Paul.

VR51 commented 7 years ago

Hi Paul! Is there an update on this? We sent you a donation a few moments ago to show our appreciation for your help. Do let us know what we can do to help you.

pbearne commented 7 years ago

We almost have a new version that is working

With much shorter URL (sitedomain.com/matator/api/auth)

As soon as it is ready (this week) you will get a copy

Paul

Paul Bearne Freelance Senior Full-Stack WordPress Developer Cell: +1 647 780 7594 Home Office: +1 416 792 8894 *E-mail: *paul@bearne.com pbearne@gmail.com @pbearne http://twitter.com/pbearne or +pbearne https://plus.google.com/u/0/100456877588970933323

On 30 July 2017 at 20:41, Lee notifications@github.com wrote:

Hi Paul! Is there an update on this? We sent you a donation a few moments ago to show our appreciation for your help. Do let us know what we can do to help you.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pbearne/Bullhorn2WP/issues/16#issuecomment-318941787, or mute the thread https://github.com/notifications/unsubscribe-auth/AAC0vptMNEiOPMGO6D-p2T3LCLadfofTks5sTSLSgaJpZM4OEP6k .

VR51 commented 7 years ago

Thank you, Paul.