Dan

Brevo is the issue. We have the same problem on Gravity Forms with Brevo, they blame the form software.

We created a new TEXT INPUT at Brevo called LANDLINE so it should accept any text input, and it was still trying to validate the submissions as phone numbers. It’s ridiculous that their system can’t understand common phone formatting structures.

I can confirm I’m having the same issue. The plugin isn’t generating any Vimeo thumbnails. I’ve tried numerous videos with different settings applied.

The plugin still didn’t work with an older version, so I ended up purchasing a plugin called Gravity Forms Range Slider and it worked great.

Thank you so much for the fast reply. I will give that a shot.

I’ve had reports of an issue with a recent update this plugin made which has broken sliders that used conditional logic and calculations. I had created forms in 2019 with Gravity Forms and this Slider and they were working fine up until a recent update.

Is there a plan to resolve this, or an easy way to roll back to your previous plugin?

John from Astoundify (creators of Listify theme) found the file on their theme that is responsible for this.

The file named, class-wp-job-manager.submission.php (located in “../listify/inc/integrations/wp-job-manager/”) is where the code is located. For adding a placeholder, this is the code that managed to do the trick:

	public function phone( $fields ) {
		$fields['company']['phone'] = array(
			'label'       => __( 'Phone Number', 'listify' ),
			'type'        => 'text',
			'placeholder' => '###-###-####',
			'required'    => false,
			'priority'    => 2.5,
		);

		return $fields;
	}

• This reply was modified 4 years, 8 months ago by Dan.

OK, after further testing, I highly suspect the theme creators are wrong. I cloned my site, deactivated every plugin with exception to WP Job Manager. The issue persisted. I switched to a generic theme, and the phone number field disappeared (as you suggested it would).

I sent the theme creator an email suggesting that maybe they were incorrect in when they pushed the blame onto another plugin.

I realize this is now more of a theme (Listify) related issue, but if you could leave this thread open, I will drop the answer/solution in when I get it done… might be useful to others all the same!

• This reply was modified 4 years, 9 months ago by Dan.

WP Job Manager’s support told me that their plugin isn’t responsible for the placeholder fields..

“You can find them all in the github page you linked to:
https://github.com/Automattic/WP-Job-Manager/blob/master/includes/forms/class-wp-job-manager-form-submit-job.php

Phone number is not actually a default field on the job submission form. Are you using another plugin or a theme that might add its own fields? If so you may need to edit it within that theme/plugin, but yes, every text field can have a placeholder.”

Oddly enough, my theme creator said they don’t include a phone number by default and pointed to WP Job Manager’s Git hub page. I’ll keep plugging away and will return with the solution if I figure it out.

Thanks for the link to the plugin. I’m not looking to do this with a plugin. I’m capable of doing this in my theme’s function file. I am just seeking better documentation or at least a full list of variables available.

Thanks Mat, wow, very fast!! Enjoy your weekend too.

FYI, it was occurring in Chrome browser for me.

• This reply was modified 6 years, 7 months ago by Dan. Reason: Added environment

This still seems to be occurring. Is there any known fix?

Issue persists. Zip codes don’t want to save. Pricing by State won’t work in our situation. If you need to price shipping based on zip codes, this plugin (currently) will not help you out.

I commented about the person (or in this case, sure, a team), not the plugin it self. No where in my comment did I say the plugin is bad.

However, when a company has to solicit reviews for their plugin by paying people (potentially at scale), it certainly speaks volumes.

I apologize for thinking you’re a “guy” instead of a “team” – an oversight on my part.

Upon further testing, I cloned my site with the issue, moved it to another directory on the server and it began working. No idea why this is the case.

I started getting a similar error sometime this week, error I’m getting is seen below (private info replaced with _____)

Error : The XML document is not well formed
:: GetQuote ::DEBUG OUTPUT::
Arguments sent to UPSArray ( [username] => _____[password] => _____ [api_id] => _____ == [account_number] => _____ [negotiated_rates] => [residential] => 1 [singular_shipping] => 0 [insured_shipment] => 1 [DropoffType] => 01 [packaging] => 02 [currency] => USD [shipr_state] => [shipr_city] => _____ [shipr_ccode] => US [shipr_pcode] => _____ [shipf_state] => [shipf_city] => _____ [shipf_ccode] => US [shipf_pcode] => _____ [units] => LBS [weight] => [dest_ccode] => US [dest_pcode] => _____ [dest_state] => MS [cart_total] => 0 )

Response from UPS 0FailureHard10001The XML document is not well formed:: GetQuote ::End DEBUG OUTPUT::