Rodrigo

Ouch, my bad: I was using version 1.1 in my staging install. So I guess you already got the bug that allowed first user/admin to bem deactivated. Good!

Regarding other users being deactivated at random, I notice two cases in my production install. I’m checking regularly if there are new cases; if a new one appear, I’ll let you know.

PS: I just translated User Toolkit to pt_BR. Is there anything else needed to include pt_BR as a supported language in User Toolkit next release?

Ops, just found out it’s already there! I’ll send you the pt_BR translation by email.

Oh, I wasn’t aware.

Since I don’t use (nor intend to) these features, I’m gonna remove it via functions.php dequeue_style.

Thanks, @deryck!

Awesome! Thanks!

Haha, I guess so!

Good to know, @deryck. I just started allowing logged users on my site, so I’m looking for plugins for better manage them. Finding yours was a pleasing surprise, as well as discovered your attention and responsiveness here.

Thanks!

Awesome, @deryck! My use case is way simpler (just let some readers sign-in for posting a custom post type), but this granularity you suggested is good.

Since you seem open to more advanced features, maybe override WordPress built-in email notifications? I wrote above that default ones were enough, but on a second thought it would be nice if there were two messages instead of one — a first saying user’s submission was successful and will be reviewed soon by an admin, and a second when it’s approved.

It’s working now, @deryck. Thanks!

We noticed, reading logs, that Nginx Helper tries to purge a lot of things when a comment is posted. Maybe this is related with the delay?

(Is anyone reading this support forum?)

A added that snippet again, just in case. (I guess it can’t hurt even if it doesn’t work, right?)

Thanks, @zahardoc!

It’s a shame since the lack of <p> tag doesn’t affect WordPress’ front-end. Thanks for your reply, @zahardoc!

Thanks, @pfefferle!

@zahardoc are you based in Ukraine or France? Recently I got a wave of spamming bots subscribing to my newsletter from Ukrainian and French IPs to the point I had to block both countries. I just removed this restriction. Please try again.

I discovered that, by default, custom post type doesn’t “register” display authors. (“Register” probable isn’t the technical term, though.) I found a solution in editing functions.php as a workaround.

Please, check this document, specifically the arguments supports. Maybe SSP isn’t passing author when registering podcast post type?

It didn’t work, @zahardoc, as you can see in this post/podcast.

This issue with <p> tag predates this latest update. I was about to warn you guys but forgot to ??

@zahardoc, glad to see that this changing made its way to a release. Tested here and it’s working fine!

I noticed, however, a differente-but-related issue with <p> tags: they get vanished from SSP’s RSS unless I declared them using HTML editor. (I’m still using WordPress’ Classic Editor, btw.) If I just hit Enter (rich text editor) or double-Enter (HTML), which in WordPress automatically add <p> tags, they are ignored in SSP’s feed.

It’s a minor issue because there’s a workaround (write posts in HTML editor and write <p> tags), but I guess you’d like to know and, maybe, fix this in a upcoming update.