ecottles

Hello,

My previous report of the errors is not accurate. The following is accurate.

When customer registration on the My Account page is enabled, the user is automatically logged in. The errors reported occur because add_action( ‘wp_login’, $plugin_public, ‘maybe_create_and_migrate_wishlist_data’, 10, 2 ); does not fire. If the user logs out and logs back in the action fires and the errors cease.

So, to reproduce the issue enable registration on MY Account page ( CHECK:: Allow customers to create an account on the “My account” page ). All 3 other “Account creation” options must be UNCHECKED. Register as new user. After automatic login attempt to add a product to wish list.

Under this scenario, you need to hook into do_action( ‘woocommerce_created_customer’, $customer_id, $new_customer_data, $password_generated ); to overcome this issue.

Good Day

It’s evident that actions speak louder than words, and currently, your actions are lacking. We need concrete resolutions, not just sales pitches. With each unaddressed issue, trust in your product and brand diminishes. Your lack of commitment to action is disappointing and undermines confidence in your ability to deliver on your promises.

Hello,

WordPress Version 6.4.3….PHP Version 7.4.30…Wishlist Version 2.0.10 Woocommerce Version 8.5.2

I installed version 2.0.10 of the plugin, and it has never been installed on my development platform before this version.

The error occurred after attempting to add a product to the wish list from the shop page for the first time. Please note, at this point, I only set the wish list page, inserted the referenced wishlist page shortcode into said page and turned on the sidebar in the plugin admin. The error presented itself in the popup that would normally confirm that the product was successfully added to the list. In this instance, the product was not added and instead the error was displayed in the pop up.

I then proceeded to this support thread and read Unable to add to wishlist (2) where the issue was reported and fixed in the current version, a few weeks ago. I then proceeded to deactivate then reactivate the plugin, whereby the product was successfully added to the list without error.

Also, while evaluating the plugin there are two classes within addonify-wishlist-icon.min.css?ver=2.0.10 named .settings::before and .x::before. The .x::before places a content tag in the very popular Flatsome theme slider(flickity slider). https://prnt.sc/xYV7Mad0WtEq

The .settings::before places a content tag in the very popular Dokan Multi vendor dashboard menu. https://prnt.sc/lqMVGxxgTh7G

Not a big deal, as the tag can easily be hidden. However, as is, the tag might give the impression that the plugin is problematic to users trying it out for the first time.

Please note that the mentioned anomalies are what I have noticed so far.

Good Day

• This reply was modified 9 months, 1 week ago by ecottles.

All of the 500 plus reviews received here are for Dokan>NON pro version.

The NON pro version works well as the review ratings show, and the support is VERY GOOD. However, there are no reviews ratings for the Pro version. There is no way to gauge the support of the Pro version.

Dokan Pro is created in SECRET. From my experience, Dokan Pro support is a firewall, because of poorly written code. That is why you have problems getting support.

I think WordPress needs to include the ability to rate commercial versions of the plugins listed in the directory. Too many people are being taken advantage of.

Good Luck!

Hello,

The non-minified versions are not on Github In version v3.7.21 & the current version v3.7.22. Access to the non-minified versions has been denied by Dokan

The minified files are specifically located in the assets/js directory. Previous versions to v3.7.21 have always included both minified and non-minified versions. Non minified versions are now being denied.

While some level of minification might be acceptable for performance optimization, advanced obfuscation techniques that deliberately obscure the code’s purpose or logic are not allowed. The Plugin Directory guidelines state that code should be “human-readable” and “well-documented” to foster transparency and promote a safer environment for WordPress users.

Link: https://github.com/weDevsOfficial/dokan/tree/develop/assets/js

Thank you for you time resolving this issue.

Larry J Cottle

Describe the bug
As of Dokan Lite version v3.7.21, the JavaScript source files are missing from the plugin.

Expected behavior
The source files have always been included in previous versions.

Steps to reproduce the issue:
Inspect the plugin’s contents and check for the presence of JavaScript source files.

Additional Information:
I contacted Dokan Lite support to inquire about the missing JavaScript source files, and they confirmed that these files are no longer available with the plugin. However, I believe this decision is surprising and concerning given that Dokan exists as an open-source solution for WooCommerce, which inherently involves including JavaScript files.

As a concerned user, I want to highlight that the absence of JavaScript source files in the Dokan Lite plugin may be a violation of WordPress terms for listing plugins in the Directory. According to Section 4 of the WordPress guidelines, developers are required to provide public, maintained access to their source code and any build tools, either by including the source code in the deployed plugin or by providing a link to the development location in the readme.

I hope that this is merely an oversight or misunderstanding and not an intentional deviation from WordPress guidelines. I kindly request the development team to review this matter and address it accordingly. Access to the JavaScript source files is essential for transparency, security, and the continued success of Dokan Lite as a trusted plugin in the WordPress community.

Thank you for your attention to this matter. I look forward to a resolution that aligns with WordPress guidelines and maintains the integrity of the Dokan Lite plugin.

Larry J Cottle

You said: We provide exclusively the build file, which is the compiled version of the original source file written in JavaScript.

Really? That profound!

You said: The source file contains the unaltered JavaScript code we authored, while the build file represents a minified and optimized version of that code, intended for loading in the user’s browser.

Thanks for the education!

You said: As a result, you won’t be able to access the actual source file.

Then how am I to customize the source file to suit my needs as you have promised in your marketing? Dokan has always provided the source file along with the minified version for performance. The source for some reason has been removed in the latest version. When are you going to include the source?

You Said: Our primary concern is optimizing the site speed for our valued clients, which is why we have included the minified version of the JS file.

That great! So where are the source files?

Good Day!

So, when will this issue be fixed. The plugin is useless without it working.

Thank You!

Revoke Access To Download & Grant Access To Download Not Working in dashboard.

click Revoke access removes the file from view only. Upon page refresh it re-appears.

Checked in wp_woocommerce_downloadable_product_permissions the entry for the file remains in database

Woo v3.8.1

Dokan-lite vCurrent

works fine in back-end wp-admin

Resolved

No, as of today they are not willing to fix it. Nazmul claims a security issue. I am currently waiting for a response about what that means. The only issue I can see is if the product has been previously purchased, the customers record in MY ACCOUNT orders will no longer be linked to that product for which they purchased because the product has a new URL….Can you imagine having 100 sellers editing the title of there product? (And then the customer is viewing the product in your GREEN EV Certificate BAR, and then notices the url represents a different product? Not good for business. That is for sure. There are ways to solve this very easily. Dokan currently has no options or tutorials to understand the importance and apply, in a practical business, to “contain” url consistency. However we need to work in cooperation with the developer. Hopefully they will work with us.

LJC

OK,

Listen up, In Woocommerce product editor……Create a product……..After creation…… Change the title…….Then save the product after the title change……You will notice that the permalink reflects the new title…….!!!!!!!!!

Dokan does not do this….!!!!!!!!!! The old permalink remains after changing the title in dokan seller dashboard product creator, editor, or what ever you want to call it…….!!!!!!!!!!!!! Because you all have not included the code to update the permalink when the title has been changed……!!!!!!!!!!!!!!!!!!!!!!!!.

Are you going to fix this? Do you want me to provide you with the code to do so?

Please respond,

LJC

hello

Just tried to purchase 3 Licenses. I received the following message after filling out and submitting first name, last name, user name, user password. “Things don’t appear to be working at the moment. Please try again later.” (Google Chrome Browser). URL = https://www.paypal.com/webapps/shoppingcart/error?flowlogging_id=5866ee191321d&code=GENERIC_ERROR&mfid=1509990164645_5866ee191321d….. I then attempted to log in thinking that my account may have been created anyway even though I had not made a purchase. I was able to log in. I selected purchase history from the menu. The line item is as follows; #7821 November 6, 2017 $65.00 Pending — Complete Purchase……. I then selected complete purchase….I checked the box agreeing to terms…..I then submit and received the following error; “Things don’t appear to be working at the moment. Please try again later.” URL=https://www.paypal.com/webapps/shoppingcart/error?flowlogging_id=5866ee191321d&code=GENERIC_ERROR&mfid=1509990164645_5866ee191321d.

Thanks,

LJC

Hello,

Thank You for fast response. 2 questions!

1. Do you perform customization as mentioned above? cost?

2. I am using extension Searching by Author. Is there a Woof shortcode argument to filter by author specific name?

Thanks,

LJC

Your solution solved my issue.

Nice work. Great plugin.

LJC