altometa
Forum Replies Created
-
Hi,
I upgraded the plugin to latest version. Everything is good now. Problems been resolved!
Thanks
[Update]
I was able to fix it by adding __DIR__ to include_once so yeah, it’s confirmed it’s my VPS setting. It doesn’t default the directory to file’s current directory.
Not all servers have the same setup so I guess it’s safer if you use __DIR__ on require or include. You have several non-standard include and include_once code that doesn’t use __DIR__. Please fix it on next update.
By the way, I love your plugin and I trust it to clean stuff on my database. Thanks…
I deleted and reinstalled as you suggested. It’s still the same thing.
I see the class existing in the code, but it seems like it’s not being included.
My VPS wasn’t setup to use chdir(__DIR__) so I think if you use require_once(‘acdb.php’) or include(‘acdb.php’), it will not find it because it doesn’t default to current directory. You have to use require_once(__DIR__ . ‘acdb.php) or include(__DIR__ . ‘acdb.php’); instead.
Hi, I am also seeing these errors.
Deprecated: Creation of dynamic property Marketking_New_Vendor_Requires_Approval_Email::$user_login is deprecated in /wp-content/plugins/marketking-multivendor-marketplace-for-woocommerce/public/emails/class-marketking-new-vendor-requires-approval-email.php on line 49
Deprecated: Creation of dynamic property Marketking_New_Vendor_Requires_Approval_Email::$user_email is deprecated in /wp-content/plugins/marketking-multivendor-marketplace-for-woocommerce/public/emails/class-marketking-new-vendor-requires-approval-email.php on line 50
Thank you. Looks like a conflict with the plugin, the Stripe plugin made by Automattic doesn’t show this error. It must be related to MarketKing’s Stripe Split pay built-in function. I’ll try to disable it and see what happens. Anyway, I’ll also reach out to them.
Nope, Captcha doesn’t work. I already tried that with Cloudflare Turnslide. They just bypass the token because they don’t register on the form.
The reason why I suspect it’s MarketKing’s issue is because the bots were able to set part of the marketking generated usermeta – marketking_account_approved to “yes” even though I set MarketKing’s setting to review application. WooCommerce doesn’t create that usermeta.
Anyway, I was able to reinforce the endpoint via a plugin that I created. I added some checks on the registration endpoint including setting a honeypot trap. It seemed to stop the bot registrations. Guess it’s good now.
You may close this ticket. Thank you…
- This reply was modified 9 months, 1 week ago by altometa.
I already use Cloudflare on the form. They are not even using the form. They are submitting it via some kind of endpoint. But I already disabled WooCommerce registration as well as WordPress registration. So it means they are getting through MarketKing’s endpoint.
The link filter for the you may also like feature doesn’t work. I tried filtering some pages from my website, one of them is this https://www.altometa.com/rl_gallery/digital-art-portfolio-images/ and it’s still showing up in the you may also like post although I already configured it not to show up in your site’s dashboard. Can you please fix this?
Thanks,
AltometaTry disabling the Social Icons (ie. Facebook, Twitter) support of the plugin by switching it off. See if it works…
More likely, it’s an incompatibility issue with your theme.
- This reply was modified 8 years, 1 month ago by altometa.