Forum Replies Created
Author | Posts |
---|---|
August 17, 2015 at 3:18 am in reply to:
Pick Up In Store 67413 | |
Joonas | I also would like to see this feature, please make this happen 🙂 |
August 12, 2015 at 8:58 pm in reply to:
Products don't display correctly 66779 | |
Joonas | Hey Towhid, It still won’t show more than one on the first line, but the rest will show correctly. Also, there is no next-button on the page either for some reason. There is more than 7 products, but doesn’t show the rest of the products. |
January 14, 2015 at 1:44 am in reply to:
Orders get duplicated in earnings 34084 | |
Joonas | Ok, You will need to have an access to your database, and then run following SQL-query (how this is exactly done, depends on your database): ALTER TABLE dokan_orders |
December 10, 2014 at 12:41 pm in reply to:
Translation of .js Files? 32080 | |
Joonas | I had the same issue and I just edited the from-validate.js file. I’d like to know if there’s a more clever way. |
December 8, 2014 at 2:20 am in reply to:
Orders get duplicated in earnings 31974 | |
Joonas | A follow-up on this. I added a unique constraint in my MySQL database for dokan_orders: ALTER TABLE dokan_orders This fixed my problem, since multiple rows with same order_id and seller_id are no longer allowed. I think Dokan should, in it’s own code, either add this kind of constraint to dokan_orders or use seller_id – order_id combination as primary key. |
November 30, 2014 at 12:48 am in reply to:
Orders get duplicated in earnings 31399 | |
Joonas | In the file /includes/wc-functions.php I see that row 1140 has changed in v1.2, from
to
Can you confirm if this fixes the error? |
November 29, 2014 at 10:38 pm in reply to:
Orders get duplicated in earnings 31393 | |
Joonas | Actually, shouldn’t order_id – seller_id combination be the primary key of dokan_orders? |
November 29, 2014 at 8:49 pm in reply to:
Orders get duplicated in earnings 31390 | |
Joonas | Now I deleted all the duplicate rows in database, and now earning reports are correct. The question is, what could be causing these duplicate rows, and do the keep coming up in future? |
November 29, 2014 at 8:41 pm in reply to:
Orders get duplicated in earnings 31389 | |
Joonas | I don’t see how this could be plugin conflict, but I disabled other plugins anyway, no help. Could I just get a clear answer (yes or no): is there an error in the database data when there are multiple rows with same order-id, seller-id combination, in the table dokan-orders? |
November 27, 2014 at 3:18 pm in reply to:
Orders get duplicated in earnings 31295 | |
Joonas | Thank you Nayem! |
November 27, 2014 at 2:49 pm in reply to:
Orders get duplicated in earnings 31293 | |
Joonas | I’d like to have it confirmed that in database table dokan_orders, by design if there should or shouldn’t be multiple rows that contain the same order_id seller_id combination. Can you check this from the dev team? |
November 27, 2014 at 2:14 pm in reply to:
Orders get duplicated in earnings 31287 | |
Joonas | When I go to database and see the table wp_dokan_orders, I can see same order_id – seller_id combination in multiple rows. So the seller earns from same order multiple times, but I get the money only once. Shouldn’t be a constraint that the same order_id – seller_id combination may exist only once?
|
October 3, 2014 at 10:13 pm in reply to:
Seller can't remove products from seller dashboard 27958 | |
Joonas | I couldn’t find any update. Can you provide the code snippet I need to change to fix this bug, if update isn’t going to be released yet? |
September 9, 2014 at 1:23 am in reply to:
Signup and Settings 26495 | |
Joonas | “Even though the information is filled in you must sign in as them go under their profile and hit save for it to work properly.” I have a similiar issue – some information sent via the registration form isn’t saved. This happened after I updated Dokan to 1.0.6 and WordPress to 4.0. |
September 9, 2014 at 12:18 am in reply to:
Customer migration to seller 26494 | |
Joonas | I agree with Mike – this was possible through backend already before 1.0.6. |