'You need to login' suddenly prevents users from reading articles

[klp29]

Hi!

Yesterday, I installed Fireboard at www.bryllup.dk.

We've beeing using SMF for at long time. Now we use both.

After that, users cannot read content - they get an "you need to be logged in" message, even though their logged in.

When turning SEFadvance off, the problem is not there.

Can someone please help med?

[klp29]

Help - anyone?

[Saka]

I don't understand the problem. Please send exact URL. Your description doesn't say anything, that's why I haven't replied.
If you can't post sensitive info here then contact me on mail.

[klp29]

Oh, I'm sorry - I'll try describe it better her, then

Site is www.bryllup.dk - what ever article you try to open, it says that you have to login, to read it. Even if you ARE logged in, you still get the same message.

Tak for instance this article: http://www.bryllup.dk/artikler-for-brudepar/k%e6rlighed-og-samliv/gifter-du-dig-til-penge-eller-g%e6ld?.html

I noticed the problem after installing Fireboard BUT the reason why I post the question here, is that it works when I turn sefadvance off.

Was that a better descrition?

[Saka]

Please check your SEF Advance settings. URL replacements and Encode exceptions in particular. Remove them or revert to original settings and try again.

[klp29]

1. I uploaded latest 5.5 version inkl. htaccess file
2. I checked that the settings are the same as original
3. It doesn't work on content (allmost every article cannot open)
4. It does work for the rest of our site (like mtree and other links)
5. The same setup is perfectly working for our other sites - it's only a problem on www.bryllup.dk

Please help 

[Saka]

Please use the .htaccess file that comes with SEF Advance and revert to original settings and try again.
If you can't find out what's wrong send a mail with the access info.

[ginajack]

Emir

I am experiencing the exact same problem after uploading the 5.5 Upgrade.  The EXACT same "you need to login" to read any article issue.

I replaced the htaccess file, No Good.  Uninstalled and reinstalled the component and found the same problem.  When I delete the component completely - everything works fine.

I then reverted back to the 5.4.4 version (replaced the htaccess file with corresponding zip version)  and unfortunately, have the same problems. 

Items in the sitemap show "not authorized to view this resource"  Thus Google shows 23 unknown URLs and I now think these may have existed  since the 11/27 upgrade.

I think I need you go take a look - I am not a programmer and absent your specific (simple) instructions, I will be lost in the woods.

[klp29]

Ok - Saka is normally very fast at fixing things, so I hope we can soon have our sites running smoothly again.

[ginajack]

Emir,

Since my last post and email, I went back to the site, refreshed, and everything is now fine - albeit with the older version of the component 5.4  Cache cleared apparantely.

Waiting for your advice on the 5.5.2

[Saka]

klp29: do you use latest version (5.5.2)?
gina: activate debug and see what it returns. Make sure you have default settings too.

[ginajack]

Emir,

Really weird but I just reinstalled the 5.5.2 version - initiated it to debug - kept default and everything was clear/clean.  Installed the backup settings and we are still good. All articles post fine.

Not sure what the problem was/is. 

I also notice that now there is 5.5.3 version available?

[Saka]

The problem could have been cached URLs, so you should always turn off cache and clear it when upgrading. 5.5.3 fixes a little bug in alias handling.

[klp29]

After upgrading from 5.5 to 5.5.3, it works for me.

It would be nice to have a newmails or notice when you have new upgrades

[Saka]

After upgrading from 5.5 to 5.5.3, it works for me.

It would be nice to have a newmails or notice when you have new upgrades

I would have to create a new mailing list for that because not all customers appreciate constant emailing.

You can always check for new version on "About" page of your SEF Advance installation or on this site though.