Topic-icon Redirects with cache enabled

Active Subscriptions:

None
14 years 7 months ago #14708 by keenmouse
I seem to be experiencing the same problem described here and here . I've disabled the cache for now, but I'd really like to solve the problem and turn it back on.

I'm using both JReviews and JomSocial, which were mentioned in previous instances. I know you're busy, and it sounds like the problem is likely not with JFBC itself, but would you be interested in delving deeper to figure it out? I'm not a PHP developer and I'm really not sure where to look. Disabling JReviews or JomSocial is not an option for me.

The problem behaves quite consistently on my site. A user who is not logged in will visit page 'A' within the site. Page 'A' throws a 404 error because the user is not logged in. The Joomla Redirect component catches the error and redirects to page 'B', an error page which informs him that he must be logged in to view content, and provides a link to page 'C', the login page. He clicks the link for page 'C' and then the Login with Facebook button, and although JFBC is configured to redirect to the site's front page on Facebook login, the user is returned to page 'C', the error page, which tells him that he is still not logged in, even though he is.

There are a couple of possible solutions I can think of, but I have to wait until they become available. One is that you mentioned you were considering adding some new redirect features to JFBC (when I mentioned possibly adding tag parameters to override the main redirect configuration setting). Maybe your changes would work around the issue somehow. The other possibility is using the NoNumber ReReplacer plugin to remove or override the duplicate code that seems to be at the root of the issue, but the extension is not yet available for Joomla 1.6/1.7.

If you're interested in taking a look, I'll PM you my site details so you can turn on the cache and play with it.
The topic has been locked.
Support Specialist
14 years 7 months ago #14710 by alzander
Definitely PM us the site info (and URLs we can use to recreate the problem). We're never too busy to look into issues for our customers. While this issue is rare, if there's a magic bullet we can diagnose on your site, we gladly will just so that we can implement it in future versions.

We'll let you know what we find.

Thanks for the great description on how to reproduce!
Alex
The topic has been locked.