Problem when logging in to forum

Robert@HCC

I am having a strange problem when I try to use the " View Active Threads" feature at the bottm of the forum home -
If I login and and click the link for "View Active Threads" I get sent to another page with this error message :

Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. 
The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). 
It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, 
please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. 
This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom error page 
by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

This happens only when I log in - if I stay as "Guest", no probs - aside from having to sift through all of the links, instead of just the new ones.
Any fix for this problem? would be nice to login and only get the most recent posts - then be able to mark the threads as read [noparse]:)[/noparse]

Thanks,
Robert

SciTech02

I'm tried it too and I came up with the same message.· Maybe the site is having some technical difficulties right now?

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
There is always an answer.

There is always a way.
There is always a reason.··· -SciTech02.

SSteve

I get it too. It must be a server-side error. Looks like a job for IT Guy.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
OS-X: because making Unix user-friendly was easier than debugging Windows

Jim Ewald

The server-side error is caused by a time-out to the database while waiting for a list of unread topics. If you are like most forum members, you don't visit each thread in every forum, so they are left as "unread". The specific issue is that the database is attempting to return a list of ALL unread topics, going back to the beginning of the forum's lfe in 2004. That's a ton of threads. I don't think that it's useful and certainly not practical to go back that far. When you connect to the site and don't login, the system does a reasonable thing and shows threads that were active in the past couple of days.

So, the question I would like to pose is this; How far back do you want to go? Some sample queries suggest that going back a week will generate between 400 and 600 rows. That's still a lot to look at on one page. Let me know and I'll adjust the code to pare down the list to some reasonable number.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Jim

Parallax IT Dept.

John R.

As an additional thought, if you do set things for a week, somewhere there should be a "reminder" to users to "mark this forum read" or "Mark All Forums Read".

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
John R.

8 + 8 = 10

John R.

Speaking of this, is there any way we can fix the date on the top thread in the Archive? It will never show as read, at least not for 7 more years or so.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
John R.

8 + 8 = 10

Robert@HCC

IT Guy (Parallax) said...
The server-side error is caused by a time-out to the database while waiting for a list of unread topics. If you are like most forum members, you don't visit each thread in every forum, so they are left as "unread". The specific issue is that the database is attempting to return a list of ALL unread topics, going back to the beginning of the forum's lfe in 2004. That's a ton of threads. I don't think that it's useful and certainly not practical to go back that far. When you connect to the site and don't login, the system does a reasonable thing and shows threads that were active in the past couple of days.

So, the question I would like to pose is this; How far back do you want to go? Some sample queries suggest that going back a week will generate between 400 and 600 rows. That's still a lot to look at on one page. Let me know and I'll adjust the code to pare down the list to some reasonable number.

Wow no wonder it times out! 2004,lol!

For myself, a few days is fine for the particular day I log-in , a week probably a bit much. Then I can Mark all posts as read, and not need to sift through them.

John R. said...
As an additional thought, if you do set things for a week, somewhere there should be a "reminder" to users to "mark this forum read" or "Mark All Forums Read".

This feature is already available when you log in , if memory serves.




Thanks for the reply, IT Guy!
Alohas

John R.

The feature is available, but we might want a "reminder" for new users.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
John R.

8 + 8 = 10

Jim Ewald

Ideally, we should not need to mark threads as read as a fix to curtail the size of the active threads list. The system should, instead, take a reasonable course of action and not display all 22,000 threads.

One other note; the infamous 2013 archive message issue has been corrected.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Jim

Parallax IT Dept.

John R.

NEATO! on the "infamous 2013" date. It's the little things that make the world go round.

You made my day, and while that probably doesn't justify the effort, maybe it will give you at least a little smile!

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
John R.

8 + 8 = 10

Jim Ewald

That one has been a rock in my shoe for some time. As often happens when debugging things, I found the problem while tracking down the time-out issue. That probably wouldn't happen in a larger shop, but when there is only one of me, I can set the priorities. I'm glad that one is off the list. [noparse]:)[/noparse]

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Jim

Parallax IT Dept.