PDA

View Full Version : Unable to search forums HELP PLEASE



Doctor_Electron
03-15-2016, 01:01 AM
-----



vBulletin Message


vBulletin Message

Your submission could not be processed because you have logged in since the previous page was loaded.

Please push the back button and reload the previous window.


Lansing Heritage Forums
-----

Hello, I just hit this snag, never occured before. How to fix it? Following the instructions does not help.

BTW, I don't know if it is normal, but: After I log in, the forums page does not display "welcome" or my username until after I click on and open a forum selection. Not a new anomaly, but I have been curious about it.

I don't know how I could have logged in after having opened a page on the website. Could these two issues be related?

Thanks for any assistance, Rich P.

Challenger604
03-18-2016, 07:42 PM
-----



vBulletin Message


vBulletin Message

Your submission could not be processed because you have logged in since the previous page was loaded.

Please push the back button and reload the previous window.


Lansing Heritage Forums
-----

Hello, I just hit this snag, never occured before. How to fix it? Following the instructions does not help.

BTW, I don't know if it is normal, but: After I log in, the forums page does not display "welcome" or my username until after I click on and open a forum selection. Not a new anomaly, but I have been curious about it.

I don't know how I could have logged in after having opened a page on the website. Could these two issues be related?

Thanks for any assistance, Rich P.

Beside "welcome" on top, you click on your name and it will show all your active threads.
When you reply to a thread, you will not see it unless you click on your name...

Took me awhile to find out...
C

Doctor_Electron
03-20-2016, 10:25 PM
Beside "welcome" on top, you click on your name and it will show all your active threads.
When you reply to a thread, you will not see it unless you click on your name...

Took me awhile to find out...
C

Thanks for that info, didn't know that.

The original "problem" seems to have fixed itself.