margarita - boomCodes

Somehow it seems to be working again. I’ll keep watching. But yes, there was probably another factor involved.

Thank you for your feedback!

In our use case, we only need subscribers to access the frontend and their network status – without assigning them to a subsite – was enough for them to log in.

But it’s still confusing to me: I can define what is the default registration role, but the user doesn’t really get it after activation. Or a user has registered to a specific site, but after activation the user is still not part of the site.

Btw… I just found how to hook on the user activation and automatically assign them to a subsite… so basically I’m fine with this solution.

• This reply was modified 1 year ago by margarita - boomCodes.
• This reply was modified 1 year ago by margarita - boomCodes.

OK, understandable!
Thanks for the quick response.

I’m sorry for the confusing and thanks for the link. I forgot about that. I’ll make there suggestions.

Thank you!

Unfortunately last week the problem suddenly came back with the 2.0.49. We’ve updated now to the new version 2.0.50 und it seems to work. But we will keep observing.

That’s interesting.. I’ve updated the plugin (from 2.0.48 to 2.0.49) and now it works. The bug was on both local and production environments. Maybe there were corrupted or missing files?

The log file showed nothing really helpful. Just the
“PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes)” with some wp-includes filename path. Unfortunately (or fortunately) I cannot reproduce the error anymore.

Thanks for the fast reply!

@magazine3 Thank you ??

@magazine3 I have the same issue.

Also I’ve tried to rollback to the 6.57 version to test from which version the problem appears, but it seems that it doesn’t exist anymore in the plugin repository.

I have the same issue. Some weeks ago the migration worked fine, but with the latest updates it doesn’t backup the plugin folder. When I backup from the backend, it works fine.

Oh, I didn’t realise there is a new version.
OK, now there are no errors.
Thanks for you quick response!

I tried it with a normal taxonomy using the Simple Taxonomy plugin and it works.
So it seems that the cpt-onomies have really a different taxonomy structure.

do you think you could embed it somehow?

OK. I got the following

Postie Shortcodes (begin)
sticky shortcode
taxonomy shortcode
taxonomy: added ‘type’=’video’
Postie Shortcodes (end)
Post postie_post filter

I’m using cpt-onomies to built up my taxonomies. Do you think it works differently?

I made a debug with the following method:
https://codex.www.ads-software.com/Debugging_in_WordPress

I didn’t find any “taxonomy shortcode” on the debug.log, I only found some postie logs and a PHP deprecated function:
[19-Sep-2015 14:17:06 UTC] Postie: Post time: 2015-09-19 15:17:06
[19-Sep-2015 14:17:06 UTC] Postie: Successful IMAP-SSL connection on port 993
[19-Sep-2015 14:17:06 UTC] Postie: # of waiting messages: 0

[19-Sep-2015 14:18:48 UTC] PHP Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /../wp-content/plugins/postie/postie-functions.php on line 611

is it with quotation marks or without?