-
-
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
Unable to do a fresh install #1608
Comments
Hum, this means no config entry was created when you added a new user. Could you tell us which version are you using? Did you got an error when adding a new user? |
I have just been using the v2 branch, so whatever the most updated version of it was when I posted the message. When using git clone and then composer install, I run into these errors:
On the other hand, when using:
Everything seemingly gets installed, but when I do a server:run after wallabag:install, I get a html page with no css or js rendering. What exactly is the recommended method of installing? |
Looks like a duplicate of #1613 |
It totally is now. Using fBSD 10.2 as well. Will close the issue |
Now that you can enable a user without email confirmation, the original issue posted here still exists. |
Which one ? The fatal error related to |
getLanguage and getTaggingRules and twig throwing exceptions because it can't find taggingRules as well. |
I've tested again and everything is fine.
Don't forget to define Also, don't forget to run the server in prod env at the end (if you are using the
|
So using those commands to install, I don't get the tagging rules error, but still get the getLanguage error (using bot en and en_US.UTF-8 as my locale) when logging in as a newly registered user at https://domain.com/login_check
Also using those commands, it seems like wallabag isn't able to pick up my pocket_consumer_key from app/config/paramaters either...
|
Also adding a new article leads to the same "get taggingRules" error as before
|
Actually I've no idea on how it happen 😞 Could you please detail each step your are doing? Which command, which action on the browser, etc .. |
First command:
Fill out the information, seems to install with no problem.
After this, in the browser make a new user. When you log in the first time everything is fine. logging out and logging back in as the new user causes #1608 (comment) Adding a new article causes: #1608 (comment)
For parameters I only added the pocket id at the end
|
Everything looks normal.. Did you get any errors during the first command?
Could you try by just setting |
Same issues when using just en. No errors when filling out the install with locale: en_US.UTF-8 |
I'm going out of idea. |
|
Even though it isn't the problem since you manage to connect, shouldn't |
Here is the list of the FreeBSD php-related packages from issue #1613 that you don't have :
Can you try installing some of them if by any luck it changes something ? |
@tcitworld: Thank you man! I wonder which of those dependencies fixed it, but I can now add articles.
Is the only error I still see. I've tried with pocket_consumer_key: 'key' in app/config/paramaters.yml with both single quotes and without any quotes but I still get that error. |
You need to go on /settings with your admin account and define the key in the Import section. |
@j0k3r Thank you bro! Wallabag is awesome and you guys are awesomer. |
❤️ |
Get a room. |
Don't be jealous, please. |
Hey @j0k3r, Trying to update wallabag but I get the same issue as before (Fatal error: Call to a member function getTaggingRules() on null in /usr/local/www/apache24/wallabag/src/Wallabag/CoreBundle/Helper/RuleBasedTagger.php on line 103) Using this "2.x-dev" version fixed it last time. Currently tried installing with 2.1.x-dev and 2.0.7 but neither seemed to work. I checked the dependencies this time and all of them seem to be there (but updated). Any idea? |
I guess config is missing here. |
Could you told us when you got this error? What is the url? It's mostly to trace the error. |
Not really an update, just reinstalled it on the same host. https://wallabag.domain.tld/new-entry rm -rf wallabag Also reset my schema when doing the install I've tried 2.0.7 as the version, 2.1.x doesn't work since Node.js doesn't support FreeBSD 64bit during composer install |
What's your About node it seems you just need |
parameters:
database_driver: pdo_mysql
database_host: 10.1.1.15
database_port: 3306
database_name: wallabag
database_user: wallabag
database_password: PASSWORDHERE
database_path: '%kernel.root_dir%/../data/db/wallabag.sqlite'
database_table_prefix: wallabag_
mailer_transport: smtp
mailer_host: 127.0.0.1
mailer_user: null
mailer_password: null
locale: en
secret: SECRETHERE
twofactor_auth: false
twofactor_sender: no-reply@wallabag.org
fosuser_confirmation: false
from_email: no-reply@wallabag.org I will try 2.1.x-dev after installing node and get back to you |
Installing node won't fix your problem :) Could you remove the path to sqlite to : And again:
|
removing the path in database_path didn't help either. |
What did you put as answer to each question for |
Ah sorry.
|
And now if you connect with the user |
Hm. No. Only when I create a new user (using registration) and then add something as the new user. |
Ha interesting. |
Should be fixed in the 2.1. |
When doing a fresh install using composer:
I am able to create a new user, but logging in as the new user causes /login_check to give me a internal service error:
Going to the root url brings me to the quickstart page so that isn't a 'breaking' issue. However whenever adding new links or importing from pocket, I get the following error:
Furthermore, trying to get to the config page of a new user leads to this:
None of these issues occur when using the user created during the installation phase (admin user).
Thanks.
The text was updated successfully, but these errors were encountered: