On 6/1/22 19:19, Mark Sapiro wrote:
On 1/6/22 4:25 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
In the last part of your suggestions you wrote:
"I suggest you do
pip install --upgrade hyperkitty mailman-hyperkitty
and ensure it installs hyperkitty 1.3.5 and mailman-hyperkitty 1.2.0"
But this is exactly what made me fall in this mess:
Sorry, I was confused. I thought the error message you were seeing was changed before HyperKitty 1.3.5 was released, but that isn't correct.
The problem is probably in Apache. See the last 2 posts in the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/W...
I'll try tomorrow, now I'm a bit slow-head after a hard day (and the collateral effects of the third vaccine).
It looks the right way (I have apache running in that server) to solve it. What intrigues me is the fact that I didn't change anything in the apache config or update apache itself.
Well, tomorrow will be antoher day.
Thanks for the point.