-
Notifications
You must be signed in to change notification settings - Fork 438
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Activation link is not written to stdout #138
Labels
Milestone
Comments
4 tasks
You're right, this is a regression but I won't fix it for now. The extension module is not well written and needs an overhaul in general. |
posativ
added a commit
that referenced
this issue
Nov 25, 2014
ix5
added
bug
needs-contributor
Someone needs to implement this. Help wanted!
server
(Python) server code
labels
Feb 10, 2022
pkvach
added a commit
to pkvach/isso
that referenced
this issue
Apr 23, 2024
3 tasks
pkvach
added a commit
to pkvach/isso
that referenced
this issue
Apr 23, 2024
pkvach
added a commit
to pkvach/isso
that referenced
this issue
Apr 23, 2024
pkvach
added a commit
to pkvach/isso
that referenced
this issue
Apr 24, 2024
ix5
pushed a commit
to ix5/isso
that referenced
this issue
Apr 29, 2024
mgc8
pushed a commit
to mgc8/isso
that referenced
this issue
Apr 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
The docs say
I have my server configured with
general.notify = stdout
andmoderation.enabled = true
. Comments are properly held back from the view until they're activated, but I could find no links in the logs.I inspected the Stdout class and could find no hint of the activation link been written to stdout as well. For SMTP,
uwsgi.spool
is called with a formatted message body, but for Stdout, just the json data is written.I think logging the activation link to stdout is not nearly as practical as sending via SMTP, but then the docs would have to be changed accordingly.
The text was updated successfully, but these errors were encountered: