Multi Vendor Marketplace Plugin | WCFM Marketplace › Forums › WCFM – Marketplace (WooCommerce Multivendor Marketplace) › No commission, no store site
- This topic has 6 replies, 2 voices, and was last updated 6 years, 3 months ago by
WCFM Forum.
- AuthorPosts
- December 6, 2018 at 8:35 pm #39260
JJ
GuestHi,
Short before I decided to develop a custom plugin for my purposes, I stumbled upon this and I have to say it completely floored me. The amount of features and options is stunning. Keep it up!
That said, it’s actually a bit too much for my purpose, although I might need it later. For now I would like to:
1) Switch the store sites off, just let vendors register and add products through your nice interface and list them in the default WooCommerce shop. Can this be implemented into the settings or do I have to filter your plugin?
2) Disable commisions, as I handle this differently with my vendors. Can I just set commision to 0% or will this cause any errors?I also realized your plugin is loading a jquery file from ajax.googleapis.com (jquery-ui.css smoothness theme) which I would need to get rid of for GDPR and site speed reasons. Don’t know if that’s on purpose or you just forgot to include it in your plugin?
All that aside, I need to say that all your marketing statements about the “best multivendor plugin” seem to be true so far 🙂
- December 7, 2018 at 5:43 am #39278
WCFM Forum
MemberHi,
Thanks for get in touch with us and really pleasure to have such appreciation 🙂
1) Switch the store sites off, just let vendors register and add products through your nice interface and list them in the default WooCommerce shop. Can this be implemented into the settings or do I have to filter your plugin?
– There is setting for disabling Store option at WCFM Admin Setting -> Marketplace -> https://ibb.co/vPtkxr82) Disable commisions, as I handle this differently with my vendors. Can I just set commision to 0% or will this cause any errors?
– No issues, just set Admin commission 100% or Vendor commission 0%I also realized your plugin is loading a jquery file from ajax.googleapis.com (jquery-ui.css smoothness theme) which I would need to get rid of for GDPR and site speed reasons. Don’t know if that’s on purpose or you just forgot to include it in your plugin?
– Is this anyhow violate GDPR if include any CSS from main plugin repository? Do you have guideline documentation for this? We can off course make this localize, that will be not a big deal.Please know me if you have any other suggestions.
Thank You
- December 7, 2018 at 9:27 am #39286
JJ
GuestThanks for your quick and helpful response!
Regarding 1, can the /stores/ URL be disabled or customized then as well?
Regarding GDPR: It does not directly violate it, but it creates the need to include it in your data security policy. The reason for that is, that visitor data (IP address is personal data) is getting to a third party (Google) by downloading the file. Same as for fonts, maps, etc. Examples are all over the internet, just google “gdpr google fonts” or similar. It’s nothing bad, but as your other users might not know or notice, it’s better to avoid it, also for the other reason mentioned (site speed).
Btw, do you have a preferred channel for bugreports or shall I just create a new post here? I think I found some other (minor) ones.
Have a nice day!
- December 7, 2018 at 10:39 am #39294
JJ
GuestOK, nevermind regarding 1).
I just found the views in your plugin, copied them to my child theme and can now happily adjust them to my needs. Very nice coding! I was looking for a custom post type slug to create custom templates for at first, but this way might even be better.Still finding minor bugs though besides the GDPR topic, so if you’re interested, let me know where to report to.
- December 8, 2018 at 5:21 am #39323
WCFM Forum
MemberHi,
Regarding 1, can the /stores/ URL be disabled or customized then as well?
– Yeah off course, there has a setting for this -> https://ibb.co/3hjhgzPRegarding GDPR: It does not directly violate it, but it creates the need to include it in your data security policy. The reason for that is, that visitor data (IP address is personal data) is getting to a third party (Google) by downloading the file. Same as for fonts, maps, etc. Examples are all over the internet, just google “gdpr google fonts” or similar. It’s nothing bad, but as your other users might not know or notice, it’s better to avoid it, also for the other reason mentioned (site speed).
– Umm .. in that case I think you will not able to use WordPress as WP core load those libraries from external source. WooCommerce also loads some resources.
Google Map and Analytics – you can not localize such scripts. Between, if you load any external Script or CSS they can not access customer’s IP or address anyway, so this will noway conflict with GDPR rule.Between, here is a help add for work with custom post type + WCFM -> https://drive.google.com/file/d/1ReqHNcRTXHcrQ-E4fx2TrKYq0OYhG7FX/view?usp=sharing
This will allow to create/manage custom post types under WCFM dashboard, you just have to set your CPT name and slug at it’s config file.Thank You
- December 8, 2018 at 1:14 pm #39350
JJ
GuestYes, running a website got a bit more complicated since GDPR became effective. But of course you can still run WordPress and most plugins/themes in Europe. It just requires some effort either way:
Either you self-host fonts, all CSS, libraries etc.
Or you adjust the privacy policy so that it mentions all external parties involved and the reasons for it.
Or, a mixture is also possible and that’s what most people do: Avoid external resources where possible and add a notice to the privacy policy where it’s not.My installation doesn’t load any external css or scripts besides your jquery css. Obviously I’d prefer to keep it like that, as it also makes my site load fast because the client doesn’t need to query several servers.
There are plugins that cannot be used in compliance with GDPR, as they store user data without permissions. But loading an external file doesn’t put you in that category obviously. Your users in GDPR countries would just need to add a statement. Or you include the file, which is what other developers go for, as it has some other benefits like inclusion in Cache and Optimization plugins, less DNS requests etc.
Now you know the GDRP issue, so you can decide how you handle (or ignore) it 😉
- December 9, 2018 at 5:56 am #39371
WCFM Forum
MemberThanks for all the details, we will take care of this.
Have a great weekend 🙂
- AuthorPosts
- The topic ‘No commission, no store site’ is closed to new replies.