jsConnect login issue: redirects OK, but the user is not logged in on forums
TaylorTay
New
I cannot figure out this issue that I am having using the latest repos for both Vanilla and jsConnect. If it matters, I am trying to integrate with the latest stable release of Kohana.
The following occurs
- Log into main site
- Navigate to forum
- Forum sidebar has a link with the following text (Taylor is the display name of the user on the main site):
Taylor
>
Sign In with Main Site
- Clicking link goes to http://mainsite.com/vanilla/entry/jsconnect?client_id={my_client_id}&Target=/ (I have double checked that the client id and secret matches)
- Redirects back to the forum's main page and user is not logged in
No errors are being thrown and the "entry" page loads quickly. If code of the auth page is needed, I will put it up. Any help would be greatly appreciated!
Best Answer
-
peregrine
MVP
if you read the readme, which you should always do.
you will see that 2.2.11.2 is not for use in self-hosted versions.
@linc Can you guys put a note somewhere that is really easy to see and find, obviously it is not working. Not something anyone seems to notice. Still.
@TaylorTay
2.1 is the recommended version. do you see the message at the top of the forum here.I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
5
Answers
maybe if you listed the version numbers of vanilla and the version of jsconnect. someone could help you.
latest version means very little.
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
Pulled yesterday: Vanilla 2.2.11.2 and jsConnect 1.4.1
why 2.2.11.2?
why not 2.1?
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
Pulling from https://github.com/vanilla/vanilla gives at the bottom of the dashboard "Version 2.2.11.2". Is this not recommended?
if you read the readme, which you should always do.
you will see that 2.2.11.2 is not for use in self-hosted versions.
@linc Can you guys put a note somewhere that is really easy to see and find, obviously it is not working. Not something anyone seems to notice. Still.
@TaylorTay
2.1 is the recommended version. do you see the message at the top of the forum here.
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
Thank you for your help. Which readme does it state this in? I read the one on github on the master branch and it doesn't mention this (ctrl+f for 2.2.11.2 gives only a commit as well).
I understand 2.1 is the stable version, but normally grabbing from the master branch, at least in my experience, is also a stable version. I will try it with 2.1; thanks again!
It's not explicit. which it should be.
https://github.com/vanilla/vanilla/blob/master/README.md#version-control-strategy
it should be reworded.
Use 2.1 and odd numbered versions only for self-hosted solutions.
2.2.x and 2.4.x and 2.6.x and 2.8.x are for internal hosted solutions - do not use this if you are self-hosting.
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
filed on github
Unclear readme.
https://github.com/vanilla/vanilla/issues/1909
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.