-
-
Notifications
You must be signed in to change notification settings - Fork 756
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
Freshly registered user doesn't have Config associated #2312
Comments
You can switch the confirmation by email to https://github.com/wallabag/wallabag/blob/master/app/config/parameters.yml.dist#L37 Once this is done, run |
Thanks, but how can I do this? I guess this is related to the way the Wallabag Docker is built. |
Hum yep, you can login into the docker image and do the change. Locate the container using |
That's what I've tried many times, doesn't work.
Any idea? |
Ow :( |
If we get a step higher from this issue, I think it depends what's the purpose of the Docker image. If we assume its purpose is to ease self-hosting, then, I guess this activation mechanism through email should be disabled by default. I'm far from being a Docker expert, but if I clone this repository, can I generate a Dockerfile by myself? |
@romu70 try |
Thanks @xsteadfastx , I was able to change the settings, but when I run
And Wallabag still tries to send an email to activate the account. |
My bad. Try this instead: php bin/console cache:clear -e=prod |
that with email in the docker image... honestly i never used that with my little wallabag setup. i wonder how difficult it is... or what the requirements are to get that working. something like a ssmtp? |
@xsteadfastx sendmail should be ok |
@j0k3r isnt sendmail a little overload? im just asking. ssmtp is just a little tool to send mails to a relay email server. |
should be ok too :) |
Done the trick with the @j0k3r command, output:
But now, when I open a new wallabag page, I get an empty page. Favicon is good, but nothing on the page, even when showing the source code of the page. Any idea? I tried to restart the container with / # cat /var/www/wallabag/app/config/parameters.yml.dist This file is a "template" of what your parameters.yml file should look like parameters:
|
Could you look into |
Yep. Here is what I did:
Here is the log file:
This helps? |
So :)
I think the problem is that you edited |
You win :-D but... clearing the cache still brings an empty page after a refresh. So, I still had to restart the container. Now it works, but I captured the log before the restart:
Hope this helps. |
Ok permissions problem. It's because you cleared the cache using the root user and the www user now can't write to the cache directory which is now owned by root. You don't need to restart the container everytime you got a blank page :) For that could you |
Ok. I'm closing the issue. I now need to seriously think about my own setup. Un grand merci à toi !! |
haha 🍻 |
Oups, I get an Error 500 when I click on "Archive": http://localhost:4000/archive/list (standard port redirected to 4000 for my testings). |
Could you share the content of |
Here it is:
"starred", "Archive" and "All entries", all lead to the error 500. |
Did you get that error with a recently created user with the email confirmation set to false? |
Yep. |
All right, there might be a bug. |
Created a new account, tried to add a new article -> 500.
|
Weird. What database are you using? SELECT * FROM wallabag_config |
MariaDB from the official Docker image. My setup is made of 3 containers:
I run the Wallabag image with this command line:
As far as I see the database is correctly populated. I do confirm the wallabag_config table only contains data for the default user. For the previous testing we discussed some moments ago, I created 2 user accounts and there is no line in this table for them. |
S**t. |
I do confirm that if I duplicate the default line and change the ID and user_id fields values, no more error 500. |
Just tried on my side using Docker too and the config is well created. Before creating the user.
And right after
Let's remote debugging 😑 var_dump($config->getId(), $config->getUser()->getId());
die(); And paste here the results. |
Just tried on my own PC (this afternoon this was on my Pro one), same containers setup, same issue. Nothing in the config table. Definitely miss something here:
|
Oups sorry forget to tell how to see the dump. |
Right after? Where? On the screen? In a file? In the DB? Sorry I'm a web dev dummy. |
Could you join on Gitter? https://gitter.im/wallabag/wallabag :) |
@j0k3r When I was trying to import accounts into framabag, the config wasn't created either while creating them from CLI so I couldn't import any articles into these accounts. See https://github.com/wallabag/wallabag/compare/framabag-v2 for what I had to do. |
It'll be fixed in 2.1.0. |
Issue details
Just playing with the Docker image from the hub, and it's way better than some months ago, great job! Within few minutes I was able to get a working Wallabag!!
But (damned "but"), when I want to create a user account, Wallabag tries to send an email and because I didn't do in this area on my computer, it can't. And so, I'm stucked with a unusable user account.
Any way to workaround or to fix this?
Environment
Steps to reproduce/test case
The text was updated successfully, but these errors were encountered: