kandrews

We are still trying to figuring out why it is failing. Since it is so random, it is hard to replicate the issue most of the time. The only way we know when it happens is when an order comes through without tax.

For now, the quick fix I added was to comment out the else condition and instead of replacing the select with the input, I have it replaced with text. This at least has stopped the orders with no tax and also put a hold on the the yelling from our client haha.

I have gone through each of the js files that the page is loading and don’t seem to see any conflicts that would overwrite the states variable in the checkout.js file. The condition states[country] looks to be failing for some, so the state select is being replaced with the input field.

This wouldn’t be an issue, but users are putting in the entire state name, but jigoshop only checks for the state code. So “Florida” =/= “FL” and that is why the tax doesn’t calculate since it is looking for “FL”.

Looks like you need to deactivate woocommerce before trying to use Jigoshop since the 2 seem to have matching methods.

Actually, this may not have solved the issue as we are still seeing no tax.

One thing I am seeing is that if a user who has data saved for the billing and shipping buys another product, data for the cart does not update.
So for instance, I am the admin and right now I am on the checkout screen.
All my data is carried over, but the tax is zero and there is no shipping method to select “Please enter your shipping destination and postal code to view shipping options and rates. There may be no methods available for your destination and you should contact us for assistance.”
The only way to get this to update is to change and item in the form.

And I don’t see any js errors in the debugger.

You were correct, as it was a clashing plugin.

For future reference it was the Respond.js plugin that seemed to be causing the issue with the state. Was tough to find this one since there were no items in the debugger.

Thanks.

For the multiple slashes, you would need to add stripslashes() around the echo of the textarea(s) on the admin form, then resave with the correct path.
Off hand, I’m not sure why you are only allowed to upload one attachment.

Sorry for the delay, busy schedule.

Just thinking off the top of my head, if you’ve added the columns in the database and corrected coded/queried them, it should work. I don’t know of anything from the WP 3.8 version that would stop from saving, especially if it saves without any mods.

On the query that is throwing the error, can you hard code the table name “YOUR_PREFIX_rsjp_job_postings” and see if that works?

The table is defined as $wpdb->prefix . ‘rsjp_job_postings’, so whatever your prefix is, make sure it matches to what is in the database.

I have an update in mind, but just haven’t had time start. Free time has been scarce since the last update. If there are any major errors that are brought to my attention, I will try to fix immediately.

Right now no, when I find time to update this, it use a lot more ajax.

This is a feature and should be working.
Check your server to make sure emails are sending from your site.

Yes, I would check to make sure that the attachment folder is writable.

This should be a css issue with your theme.

You need to resave your permalinks settings.

Right now the “Regarding Job” is hard coded. You can change this by editing line 347 in the /includes/form.php file.

The list populates with the job postings that you publish.

As of right now, it is coded to be required.