Forum Replies Created
-
Posts
-
Hello,
This is because the system is trying to create orders that have been deleted/trashed/some other weird status. If the order id’s don’t exist in the wp_posts table but are in the commissions table that is where the system is choking. I added code a long time ago that is supposed to fix the deletion of orders from killing the system.
You will have to clean up your commissions table with some SQL.
Instructions:
1. READ THE COMMENTS IN THE FILE
2. ONLY RUN THE FIRST COMMAND, DO NOT RUN BOTH.
3. IF FIRST COMMAND DOESN’T WORK, THEN USE THE SECOND COMMAND.This is the code:
https://gist.github.com/digitalchild/6c6ac086e1a08fd4e3befd7cc2b7e16f
DO NOT RUN THIS ON YOUR LIVE SITE WITHOUT TESTING IT ON A STAGING SERVER. YOU HAVE BEEN WARNED!!!!!!!!!
cheers,
Jamie.
Hello,
You’d have to create a completely new commission system. This would include a new payment gateway.
cheers,
Jamie.
Hello,
You need to have a paypal adaptive payments account setup and configured for wc vendors. Then you need to have all your vendors have paypal accounts. Then you need to set the commission on the commissions tab on the settings screen.
cheers,
Jamie.
Hello,
Ban your users that do that. If they are breaking the law, kick them off. If you require regulatory changes I’d recommend you’d find a custom developer to restrict this.
cheers,
Jamie.
Hello,
This fix is available in the next pro release due out once our testing is completed this week.
cheers,
Jamie.
Hi Dave,
All those features enable/disabled are done via options. You could in theory filter the options based on a user meta field. You’d need to look in the main pro class file in the includes dir and take a look at the filters in the dashboard to see how you can filter the menu based on user meta.
cheers,
Jamie.
Joe,
We have no code in the plugin that disconnects vendors on plugin deactivation. The only action that allows this is if vendors actually click the disconnect button on the dashboard.
cheers,
Jamie.
Hi @CANYASA
I spoke to a couple of other woocommerce extension devs and they are reporting the same warnings. I will also check to see if there is any open issues with woocommerce also.
cheers,
Jamie.
Hello,
Will test and add it to 1.4.4 if all is good. Running php 7.1.6 is nice and ‘fresh’ 🙂
The variation shipping issue has been fixed in the soon to be released 1.4.4. I may have forgotten to report that back, apologies!
cheers,
Jamie.
Hello,
Please send your translations to translate at wcvendors.com and I’ll look into this. Apologies for the delay there has been some interesting bugs in our main product that has taken a considerable amount of time to fix.
cheers,
Jamie.
Hello,
If you want to increase the price by 10% then who gets that fee ? If you the marketplace owner is getting that fee then that is essentially a commission. Otherwise your vendors are getting that extra 10% which doesn’t really make much sense. Why wouldn’t they just make their prices higher themselves?
Your filter will only change the prices for the field on the form, it won’t save the price increase. If you do save the price increase then you’ll need to do a bit more calculations.
For reference the following code will achieve what your filter does. Your filter is not needed.
https://gist.github.com/digitalchild/ee745bf7480e63d10b84b8eaf12d7ea7
This explains our form helper:
http://docs.wcvendors.com/knowledge-base/form-helper/
cheers,
Jamie.
Hello,
I’ve fixed the custom taxonomy saving issue in pro and the update will be available in 1.4.4. With the following definition you can add and save the custom taxonomy with no modifications necessary. If you need to select more than one option then add the multiple = multiple custom attribute and you’re good to go.
https://gist.github.com/digitalchild/67b9094442ac05fb04679982492e1b1e
Regarding checkboxes this is a limitation of php in that you need to know what ALL your fields are after post to be able to verify them. Currently your hook to save the checkbox separately is the correct way to do this. The only way I can see the solution for knowing fields is to create a registration system that the controller then references to grab fields and save them. I’ll put that into the what ifs bucket for now.
On a side note, why is puppy sex a taxonomy? There are only 2 options. Unless this shop is selling creations from the Island of Dr Moreau ?
cheers,
Jamie.
Hello,
Your reward? That warm fuzzy feeling of accomplishment and the knowledge that you understand the products you use very well. This will make it easier for you to run and maintain your business. This is what ALL our users should be doing 🙂
I’ve fixed the tax display issue now and that will be available in the 1.4.4 release out soon.
cheers,
Jamie.
Hello,
Replace this file in wc-vendors and test please.
https://github.com/wcvendors/wcvendors/blob/master/classes/class-vendors.php
It appears either shipping tax never worked or it was changed in WC3.0. This would be why both paypal ap and our stripe were calculating incorrectly but paypal standard did not. That took a of debugging to work it out but I believe that little change was all it took.
cheers,
Jamie.
Hello,
After several days, yes days! I’ve managed to recreate the issue! I can confirm that it is happening in at least the paypal gateway, but does not happen in BACS or our test gateway. Further testing required for stripe. Now I know where to look I can start debugging. I will let you know when I have further updates.
Thanks for your patience.
cheers,
Jamie.
Hi @scott,
Looking into this. Will report back. Your definition of the form is different to my examples. Will create a test install and see if I can replicate your issues.
cheers,
Jamie.
Hi Yasa,
You are getting support. Being transparent with our users and communicating with you what is wrong is part of that. It’s not just just a quick fix. There are a few bugs that I’m currently working on that will be included in the 1.4.4 release. I’m pretty sure I have fixed this variation shipping issue in the soon to be released version. I’ll double check in the morning and report back.
We do not provide release dates for our products as there are too many variables to control when we can release an update. To give you an example, 1.4.4 was about to be released when 3 shipping bugs were reported in quick succession. This has held up the release until they can be resolved. We don’t rush out releases unless it’s a critical break all bug that needs to be fixed.
cheers,
Jamie.
Hi @canyasa
Actually no it’s not. Pro support is for pro only. From your logic if there is a bug in woocommerce than any paid woocommerce extension should give you support for free woocommerce. Which is NOT the case. I can assure you we are working on fixing all currently reported bugs for the next release. Please be patient as we work through the issues.
cheers,
Jamie.
Hello,
Lead developer here. You found an issue and a fix, Yay! Welcome to the open source community. You also found this in our free offering which is NOT covered by your pro support. This is the same as if there was a bug in woocoomerce and it affected how pro worked, or a theme that affected how pro worked. Sometimes you have to wait for the upstream fix. Due to the sheer number of changes within WooCommerce 3.0 we have been unable to test every single possible use case and fix everything as we dont always know its broken till its reported. For the majority of people, who don’t use variations everything is working fine which is why sometimes bugs take a while to find and fix. There are quite a few other bugs across our products that were slightly higher up the priority list which is why this was on hold.
But thanks to @daman who has contributed to the free product which is how the community works, it’s all fixed!
cheers,
Jamie.
Hello,
Looks like the code is functioning when it shouldn’t for everyone else. There is a line in
includes/lib/class-wc-software-client.php line 198
It currently reads
if ( in_array( $_SERVER[ ‘REMOTE_ADDR’ ], $whitelist ) ){
change it to
if ( in_array( $_SERVER[ ‘SERVER_ADDR’ ], $whitelist ) ){
and see how you go.
If not cloudways is reporting your server host name in php some funky way. Please report back and let me know if that change fixed the issue.
cheers,
Jamie.
Hello,
That’s a woocommerce filter not us. The issue you have is that we had a large majority of users want vendor shipping split so that customers can see who charges what. By doing this it creates multiple shipping packages that have their own package name and available shipping method. This is why you get the repeated shipping title.
However, because our code does this, I feel partially responsible for it so here is the code you need.
http://docs.wcvendors.com/knowledge-base/remove-shipping-method-title/
cheers,
Jamie.
Hello,
This will remove the shipping title and make it blank.
https://gist.github.com/digitalchild/f0c7a077536643e1f477970888dc02ae
cheers,
Jamie.
Hello
The developers have contacted me and I am now working with them to resolve this.
cheers,
Jamie.
Hello,
A few things you need to know about bookings. You can only ever have one booking product in your cart. This is a limitation of bookings and has nothing to do with us.
The reason that our integration and none of our competitors allow vendors to create booking orders is it is a big security issue. To allow vendors to create their own booking orders would require that you give your vendors access to all customers of the marketplace. I dont know many marketplaces that would freely allow their vendors to see all the customer details even when they have no interactions with these customers. If you can think of a secure way to restrict vendors to the customer they need to create the order for, I’m all ears and eyes 🙂
Working on the emails and other reported issues.
cheers,
Jamie.
Hello,
Is this on the dev site? If so I will take a look in the morning. Currently 10pm where I am.
cheers,
Jamie.
Hello,
I have fixed the sold_by problem also. This was a bug I introduced when adding support for WC3.0. This has been fixed in the next release of free. Or you can use the version I modified on your dev site.
Problems listed:
1. shipping not calculating – fixed
2. fatal error – (broken commission class file, replaced) – fixed
3. Sold_by not showing correctly for variations – fixedcheers,
Jamie.
Hello,
It was actually your commision file that wasn’t playing nice, which I’ve fixed. I’m doing a test now to see what else I can find out before saying this is solved.
cheers,
Jamie.
Hello
The Oauth issue is usually another plugin (social logins) that is conflicting due to how they have declared it. Please try this replacement file.
https://gist.github.com/digitalchild/77079010da0f9a711916fd1fc5c9515b
cheers,
Jamie.
Hello,
That is because any version of pro before 1.4 is not compatible with WC3 at all. Please update to the latest version of Pro and try again.
cheers,
Jamie.
Hello,
Sorry for this, my search and replace broke commissions calculations, mental note. Triple check checkout before pushing release.
https://gist.github.com/digitalchild/0fba03355b9d93aae2dfaa83251cba7a
This will fix checkout.
cheers,
Jamie.
Hello,
Emails are part of the woo subsystem and we hook into these. Unless Woo has changed the actions for these emails to fire (which is possible lately) they should still be firing. When you mean latest update. Is that Woo Updates or 1.4.x updates or 1.4.2 update?
cheers,
Jamie.
Hello,
Whoops, forgot to give you the fix for coupons.
File: public/class-wcvendors-pro-order-controller.php
Line: 273 replace with
$coupon_amount = ( version_compare( WC_VERSION, ‘2.7’, ‘<' ) ) ? $the_coupon->coupon_amount : $the_coupon->get_amount();
cheers,
Jamie.
Hello,
Whoops, forgot to give you the fix for coupons.
File: public/class-wcvendors-pro-order-controller.php
Line: 273 replace with
$coupon_amount = ( version_compare( WC_VERSION, ‘2.7’, ‘<' ) ) ? $the_coupon->coupon_amount : $the_coupon->get_amount();
cheers,
Jamie.
Hello,
Until our next release (24 hrs or so) you can modify the source with the following fix.
File name and path
public/class-wcvendors-pro-order-controller.php
Line: 375
Replace with this :
$product_id = ( version_compare( WC_VERSION, ‘2.7’, ‘<' ) ) ? !empty( $item['variation_id'] ) ? $item['variation_id'] : $item['product_id'] : $item->get_product_id();
cheers,
Jamie.
Hello,
Until our next release (24 hrs or so) you can modify the source with the following fix.
File name and path
public/class-wcvendors-pro-order-controller.php
Line: 375
Replace with this :
$product_id = ( version_compare( WC_VERSION, ‘2.7’, ‘<' ) ) ? !empty( $item['variation_id'] ) ? $item['variation_id'] : $item['product_id'] : $item->get_product_id();
cheers,
Jamie.
Hello,
I am actively working on this. I can’t replicate this locally so I’m having to do remote debugging which is slowing things down.
cheers,
Jamie.
Hello,
The suggested code change makes no sense as to why it works when the code we have is effectively the same thing. Not only that he is declaring the post as global meaning he has full access to the object to only override it on the very next line with a local version and a db query. Which is completely unnecessary.
I would really like to know why Views isn’t using the product global and is using the underlying post instead.
cheers,
Jamie.
Hello,
This has been fixed. Let me know if you need the fixed class file asap and I’ll email over the replacement, until we push the next release (early next week).
cheers,
Jamie.
Hello,
My code change fixed your commissions, they have all been paid. This fix will be in the next version of WC Vendors so don’t worry about my changes being lost when you do your next update.
Regarding changes I wonder if that version of PHP you’re running which is relatively new has got a strict setting turned on to make these errors happen.
cheers,
Jamie.
Hello,
I’ve made a change to the commission class and was wondering if I can attempt to process. The change shouldn’t be required unless some kind of PHP strictness has been turned on.
Can we go ahead and try and process the commission?
cheers,
Jamie.
Hello,
So no plugin updates? No hosting updates? Have you contacted siteground to see if they have made any changes? Seeing as you have too many plugins to disable and start testing orders on the live site. Are you able to get a staging site setup that I can work on debugging this? With orders not working correctly and inconsistently it’s hard to know where to start with this. I would also need live access to your error logs so that I can start to debug this.
cheers,
Jamie.
Hello,
Has this always happened or only just started? What has changed since the last set of commissions were paid out?
The section of code that is having an issue hasn’t been modified since we launched.
Can I attempt to debug this payout issue on your site? I will need to add some debugging code to try and work out what is creating the error.
cheers,
jamie.
Hello,
We only provide code for you to store custom information with a product. If you need to display that information on the store front end then you need to then reference your meta keys and display them on the relevant part of the single product pages. As this is theme dependent we haven’t written any auto code to display these. The general thing is, open the relevant template file and see which actions are called where and then hook into that action to display the meta key you’re storing.
Here is a reference for the actions.
cheers,
Jamie.
