Neziah

Hi

Thanks for your quick reply. I haven’t been able to generate the issue myself so unfortunately I could not provide additional information. This issue was just reported to me on two occasions.

Yes, I believe this “The access to that page has been restricted by the administrator of this website.” As it’s a Siteground with a padlock that is shown and the user can not access the login form.

I’ve checked the activity log and there was one blocked IP I removed. I will let you know if the issue continues.

I got the same problem following…

Hi @nazmulhassann20

I saw this issue was address in the latest Dokan lite release. I hope this will be fixed/applied for all supported payment gateway as well.

Fix: Deduct PayPal gateway fee from vendor’s earning #830

However, there is now a secondary bug/issue which is causing Vendors to lose money with Dokan.

When “PayPal Identity Token” feature is enabled in PayPal Standard as shown below:

Link to Image: https://ibb.co/YjqJVq5

The “Payment gateway processing fee” of 0.71 is deducted/subtracted twice. Which again results in providing the wrong “Earning From Order” of $11.97 . The correct amount should be $12.68.

Now Dokan is deducting/subtracting to much PayPal Fees from the Vendors earnings which is causing them to lose money. See image below:

Link to Image: https://ibb.co/180rrGf

Additionally, in the image below you can see many transitions are doubled or executed twice.

Link to Image: https://ibb.co/gPBqsq5

This is because even if “IPN Email Notifications” feature is disabled/off, Dokan is still firing/executing it. Which cause both the IPN and PDT to execute hence the double fees deduction and other transactions. This bug/error did not happen in previous versions of Dokan.

Note: If “IPN Email Notifications” only is enabled and “PayPal Identity Token” is disabled/not used, this bug/issue does not occur in PayPal Standard.

This need to be fixed ASAP as it will affect many. I’ve already submitted this to support to which I’ve once again not received a reply.

Thanks.

• This reply was modified 4 years, 6 months ago by Neziah.

Thanks @nazmulhassann20 for your response and confirming that this issue exits in Dokan.

Note: This should be fixed for all supported payment gateways (all have fees) and not only PayPal.

I have one question for you, are you using PayPal Standard?

I’m using WooCommerce PayPal checkout.

I’ve tested PayPal Standard, Dokan do not display/show PayPal Fees and Payout Amount in the Vendor Order page when using PayPal Standard. I would suggest Dokan show this information for transparency and correct Vendor Earnings calculations.

Will this information be added to PayPal standard?

Thanks

Thanks @nazmulhassann20 for your response.

Our support team already replied to your ticket

I can confirm to this date I have not received any response/reply to my ticket related to this issue from your support team. If someone informed you of this or this originated from you. Sadly it’s not true, which brings into question the validity of the remainder of your statement. See image below:

Link to image: https://ibb.co/26J41CD

In fact I have 5 other bug opened tickets with no response and other bugs discovered which I have not yet submitted. As this bug is top priority.

Hopefully, this issue can get can get resolved quickly.

Thanks

Hi

Here are the logs I recently experience this error with 6.2.2 it seems to occur on Sunday’s

[Sun Nov 06 05:11:06.757471 2016] [proxy_fcgi:error] [pid 27423:tid 139654686832384] [client 207.46.13.68:13194] AH01071: Got error ‘PHP message: PHP Warning: session_start(): open(/home/user/tmp/sess_q82esrkghgj68d4hkmrdnhlf72, O_RDWR) failed: No space left on device (28) in /home/user/public_html/wp-content/plugins/pro/pro-files/lib/Pro/Helper/Session.php on line 29\n’
[Sun Nov 06 05:11:06.818867 2016] [proxy_fcgi:error] [pid 27423:tid 139654686832384] [client 207.46.13.68:13194] AH01071: Got error ‘PHP message: PHP Fatal error: Uncaught exception ‘wfWAFStorageFileException’ with message ‘Unable to save temporary file for atomic writing.’ in /home/user/public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:13\nStack trace:\n#0 /home/user/public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(497): wfWAFStorageFile::atomicFilePutContents(‘/home/user…’, ‘<?php exit(‘Acc…’)\n#1 [internal function]: wfWAFStorageFile->saveConfig()\n#2 {main}\n thrown in /home/user/public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php on line 13\nPHP message: PHP Warning: Unknown: open(/home/user/tmp/sess_q82esrkghgj68d4hkmrdnhlf72, O_RDWR) failed: No space left on device (28) in Unknown on line 0\nPHP message: PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/home/user/tmp) in Unknown on line 0\n’

Hi

I updated the file as suggest however there is no change.

Also note the search feature does not work.

As requested here is the link.

https://www.caribonix.com/careers/

It would be great if you could integrate with gravity forms or provide this option as it already has all the forms functionality built.

I’m aware that a similar path is used what I would like to know is why is the standard path not used?

I have the same problem any update on when this will be fixed?

Thanks guys the php version works great.

However there is still the issue of submitting the actual request form on the password reset page as the form post to the following

/wp-login.php?action=lostpassword

which generates 404

Has anyone tested submitting the form?

Can we also solve this via a filter?

Anyone of you guys care to explain how this is done? Thanks.

Any update?

I would also like to get in touch with you to discus how we can help support development of this plugin. As we would like to use it on a Multisite production environment

let me know how I can get in touch with you.

Thanks Patrick