From: thinktankworkspaces@gmail.com
To: 9front@9front.org
Subject: [9front] [werc] comments activation
Date: Mon, 17 Jan 2022 00:35:33 -0800 [thread overview]
Message-ID: <F2ADB80F4C68A214DAC1A8DAC80F2B52@gmail.com> (raw)
I feel like I'm getting further with the comments. Still the same error
I don't believe I should need to create comments directory but I did manualy anyways
I still run into the following problems.
Auth: success
umask: '/usr/bin/umask' does not exist
mkdir: can't create sites/cirno/_werc/comments/1642408320: 'sites/cirno/_werc/comments/1642408320' access permission denied
ERROR XXX: Could not create comment: mkdir 22877: error
cirno/ - Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15 - POST - md_handler sites/cirno/index.md - lib/default_master.tpl
Mon Jan 17 00:32:00 PST 2022 :: cirno :: POST / HTTP/1.1 :: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15 :: 200 :: http://cirno/
tee: cannot open /tmp/fltr_cache/923e12ff215b0e44105268bcdd2950bffec9fc41/22890: '/tmp/fltr_cache' does not exist
mv: can't stat /tmp/fltr_cache/923e12ff215b0e44105268bcdd2950bffec9fc41/22890: '/tmp/fltr_cache' does not exist
Auth: success
Mon Jan 17 00:32:00 PST 2022 :: cirno :: GET /pub/style/style.css HTTP/1.1 :: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15 :: 200 :: http://cirno/
next reply other threads:[~2022-01-17 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 8:35 thinktankworkspaces [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-17 8:35 thinktankworkspaces
2022-01-17 8:34 thinktankworkspaces
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F2ADB80F4C68A214DAC1A8DAC80F2B52@gmail.com \
--to=thinktankworkspaces@gmail.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).