Matt Jaworski

Please contact us via the official channel: https://PeepSo.com/contact

Most likely you have been targeted by a script trying to break into your website.

I’d suggest forcing users to use emails to log in (instead of usernames) it makes harder for the attackers to guess.

Otherwise you can disable the email notifications for that feature or turn it off completely and use something like WordFence instead.

Please contact us via the official channel: https://PeepSo.com/contact

The widgets and sidebars work the same as everywhere else in WordPress. Maybe you configured your profile page to be sidebar-less? We can try advising you when you open a support ticket via our website,

Please contact us via the official channel: https://PeepSo.com/contact

This message shows when you filter the stream by “following” only, to warn the user they are not seeing everything.

It will disappear once the filter is changed. You can also hide it with CSS.

Unfortunately we do not provide tech support for multisite installs, or on this forum in general – we do it via support tickets on https://www.peepso.com/contact

This also sounds more like a generic WordPress question (cross-domain login in multisite environment). PeepSo is utilizing the WP framework for login and sessions, so nay solution that works for WP at large should work for PeepSo too. In my opinion it would be a job for a third party Multisite SSO plugin of sort.

That being said, yet again let me stress that – we do not develop, test or debug PeepSo in multisite environments. Whether it works or not, we do not provide any support to multisite installs. No matter if the problem seems to be multisite or not.

• This reply was modified 2 years, 4 months ago by Matt Jaworski.

As far as i know, WP does not support non-latin characters in usernames, and neither does PeepSo. In our tests, it’s impossible to type Chinese in registration (PeepSo and WordPress) or when editing the username in PeepSo UI.

Please send us a support ticket, as we’d like to know how Chinese characters made it into usernames despite being unsupported.

Hello, please contact us via the ticket system on https://PeepSo.com/contact ??

Hello, since you already opened a support ticket, we will continue there ??

Hello there! Please contact us via a support ticket through PeepSo.com/contact

In general all “integration” plugins require some sort of third party to work. The Mobile App was designed with MobiLoud in mind but also works with WPMobile.app – and you can use any other wrapper.

The PeepSo app in the app/play store is ours – it’s the PeepSo.com community. If you want your own app, it needs to be added to play/app store separately.

As we already replied in our community (in painstaking detail), piping emails through a third party service – be it MailGun, SMTP or any other – is a job for a third party plugin. That combined with the fact WordPress and PeepSo are both open source gives you all the flexibility you need.

The fact you felt compelled to repeat yourself in a low star review tells more about yourself than us.

All the best.

Yes, our community is now limited to active customers, so anyone with an active paid license (monthly or yearly).

And since we do not actively monitor the forum here (as outlined in the sticky post), the only way to get reasonably fast support without an active license is to send us a support ticket. Our support staff is happy to answer any questions, if they can.

We looked into the problem. It only occurs if the Brute Force protection is enabled and the same IP registers more than once in a very short window of time.

You can fix it by disabling the Brute Force protection in PeepSo Config > Accounts and Security.

On our end, we will disable the built in Brute Force protection by default on fresh installs to avoid any future confusion. And we will describe the option better, so when enabled manually it gives a good understanding to the admin how it works.

As for your review, it feels really unnecessary. It’s more of a bug report, and that’s also a stretch as this is a very specific and narrow edge case scenario. You could have reached out to our support and we’d have solved it the same.

Sorry to bring it up to moderators attention, but maybe we could get rid of this 1* as it’s really a chaotic bug report.

Hello,

please send us a support ticket with exact replication scenario and we will look into it. Not giving us access to the site might slow us down, but we might be able to help if the issue replicates for us.

We do not provide support via these forums.

Thanks

Please ensure that the site always loads with the same URL and with SSL, so: “https” (not http) and with or without leading “www.” – inconsistency in website URLs will be treated by browsers as separate URLs and cookies won’t work.

Maybe check your caching solution/plugin it might be to aggressive.

If that does not help, please contact us via our support system (via our website), as we can’t provide effective support through the forum.

• This reply was modified 3 years, 4 months ago by Matt Jaworski.
• This reply was modified 3 years, 4 months ago by Matt Jaworski.

Hello, thank you for this suggestion, it makes a lot of sense. We’ll try to ship this in 3.6.1.0 if there are no regressions.

$user = new WP_User($user_id):
$user->add_role('seller');
update_user_meta($user_id, 'dokan_enable_selling', 'yes');