SMF Development > Bug Reports
[4244]SMF 2.0 RC3 - Obfuscation of session variable name breaks integration
Orstio:
http://www.simplemachines.org/community/index.php?topic=373342.msg2562443#msg2562443
I don't see a way to retrieve or pass a value to $context['session_var']. This essentially breaks all interactions in regard to integration (no login, no logout, no posting, no voting in polls, etc. through integration.) This renders SSI.php pretty much useless for anything other than non-interactive display (recent topics, recent posts, etc.)
MultiformeIngegno:
[See this post for the procedure to reproduce it!]
As explained in the topic linked above, the behavior is the following:
In SSI pages located on different subdomain from the forum one, if you try to login with your right username and password from the ssi page login box, you are always redirected to the forum login with a "password wrong" error. Then after you have logged in from the forum, if you come back to the ssi page and you try to logout, you get a "session verification failed" error. I've noticed also that if you refresh the page the session number included in the logout link changes!!
Is there a temporary workaround? Maybe a code "downgrade" to RC2?
Please help me, my whole site is based on ssi.php!!
Thanks in advance,
Lorenzo
Orstio:
If I were you, I wouldn't hold my breath.
The bug is big enough that there is no quick fix. You're not going to get a small patch code to make it work.
So, the best that's going to happen is it will be fixed for 2.0 RC4. The worst case is it's never fixed.
MultiformeIngegno:
--- Quote from: Orstio on April 04, 2010, 08:52:05 AM ---If I were you, I wouldn't hold my breath.
The bug is big enough that there is no quick fix. You're not going to get a small patch code to make it work.
So, the best that's going to happen is it will be fixed for 2.0 RC4. The worst case is it's never fixed.
--- End quote ---
There's no way to replace the interested code with the RC2 one (that worked properly)?
Anyway.... this is a MAJOR BUG, that needs to be absolutely fixed for RC4!! I can't even see it on the bug tracker!
Orstio:
Most of the bugs posted here don't make it onto the bug tracker. Even the ones that do don't necessarily get fixed.
Keep in mind there are only three volunteer developers. They can't possibly keep up with it all in only their spare time.
Navigation
[0] Message Index
[#] Next page
Go to full version