-
Welcome to the Chevereto User Community!
Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.
Please keep in mind:
- This community is user-driven. Always be polite and respectful to others.
- Support development by purchasing a Chevereto license, which also gives you priority support.
- Go further by joining the Community Subscription for even faster response times and to help sustain this space
-
Chevereto Support CLST
Support response
- Extra Support is delivered within 24-hours.
- Pro Subscription ticket response time is within 7 days on Software Support, Bug Tracking and RFC.
- Bug Tracking requires an active Chevereto self-hosted subscription.
- Community Help is user driven. Be polite with other users and do not expect official support.
Support checklist
- Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
- Confirm that the server meets the System Requirements
- Check for any available Hotfix - your issue could be already reported/fixed
- Read documentation - It will be required to Debug and understand Errors for a faster support response
Facebook login
- Thread starter weblinkpost
- Start date
TigerDragon
Chevereto Member
@weblinkpost hi you work /connect/facebook/ you Facebook work!!
weblinkpost
Chevereto Member
Tried everything... no error logs being generated... When trying to use Facebook Login I am getting authorization screen and when pressed OK I am getting the same Something went wrong message....
That you can't find those doesn't means it wasn't generated. Don't worry, in 4.0.0 you will be able to name your own error log file so there won't be any challenge left to properly debug your installation.
In any case, you should read here: https://chevereto.com/community/threads/login-providers-v4-0-0-beta-11.14510/#post-72496
weblinkpost
Chevereto Member
I tried this solution, but it did not work. It still gives the same error.
I'm afraid that you will have to wait for the patches, we can't help you further without knowing what's the actual error.
I hope that with the next update you will be able to get the debug info and open a bug tracking issue for this matter.
I hope that with the next update you will be able to get the debug info and open a bug tracking issue for this matter.