"This topic will automatically close in 3 months."


Searching for topics in advanced mode or for specific issues requires that you have already reached a certain point of understanding of SketchUp’s terminology. Most of the time , new users don’t have a clue what to search for. There is a whole (new) generation that doesn’t take effort in learning even the basic principles. They want answers, and they want them quick. They don’t bother searching. Perhaps a tagging system could automatically link topic’s to page’s with solutions. If they have 'clicked ’ on these links and got the answer the (automated) reply would be " Hey, I’ve clicked on these links and it solved my issues ! "The topic would get solved automatically. If the OP still hasn’t found what it was looking for, he could remove the automated message and the topic would be still editable. Searching for solved topic’s should be on top of the search-results
Cultures are based upon what our predecessors already have built and accomplished. Don’t throw away the building blocks!


Thanks Dan I will give it a go when I can get back to it.


When typing a new post you already get search results that matches what you are writing. I think the forum system already does a lot to help people here.


I think that’s fair enough. We have a satisfactory mix here.

[quote=“eneroth3, post:30, topic:40562, full:true”]
When typing a new post you already get search results that matches what you are writing. I think the forum system already does a lot to help people here.
[/quote]I totally agree with @eneroth3 , even if users can’t find search button ‘for some reason’, that feature corners them! :sweat_smile:


Or enter my user name and attempt order and then taken to advanced search and have to take time now to fill out another form. Who designs should be forced to use for awhile.
In my pass role as level three staff engineer I would not approve any application that waste so much of staffs time. Don’t point me toward someones help write up, I find they are mostly non-intutive and also waste time.


Or I get emails that do not have any meaningful title so I just skip


forcing users to new threads often with same issues only because a thread feels old (3 month… really?) is surely no good idea especially with most people not getting bothered by this.

Reminds me at the old forum and Google groups repeatedly being closed and nuked with all the valuable knowledge mainly created by volunteers went down the drain:

but hey, was only ol’ stuff :unamused:


Almost very program I’ve worked on the question usually comes up how one captures knowledge base. This is almost like intellectual property and should be worth $$ to Trimble, Google, etc. but may there here are some leagl reasons it does not get done or does it?
I can not think of a real technical reason for not except for leader ship commitment ?


And here is another type of topic (feature request) that should not ever be automatically closed. Only manually closed if the feature is actually added to the application.

Topic automatically closing.... system new message

Restating these thoughts from the “Auto close wiki” thread.

Users with high privileges (sages, etc.,) should be able to switch off auto-close if they are creating a perpetual discussion or help thread (and do not intend that there ever be a post marked as a solution.)


Auto Close should only apply to solved threads.


Apparently, the Close feature does NOT affect the ability to edit existing posts in any closed thread:

Jeff Attwood (co-founder) in Discourse support: Best practices for archiving topics, says:

Close only prevents new replies.
Archive freezes a topic in carbonite so nothing about it can ever change. Ever.


This is not happening. Ie, the counter is not resetting when new posts are adding to long running threads.

For example, this thread has only a month of life left in it, despite all it’s activity.


Would it be possible to close the topics after a set period of inactivity? I think that would be better than an artificial time limit with a counter starting at the thread’s creation. The inactivity setting could even be shorter than the three months life now allowed for a thread.



I read @Jody’s post as informing us that he can set things up to base the closing on <xx> days after the last activity, not that he has set things up that way - and asking us if this might be a good middle ground.

Thus I’m not surprised that this is not yet observable behavior.

And BTW: Jody, I think that’s a good middle ground. Not perfect, but far better than closing 3 months after initial creation of a thread.


I’m curious when Jody started on the high doses of estrogen.


Oops! I made assumption based on my cultural connotations on his name without noticing his avatar picture! Post corrected.


This is correct. I’ll go through and set them all to be based on last activity promptly.



On the assumption (quite possibly premature) that you have done this, it appears not to have been applied to topics which the previous “Close 3 Months After Initial Post” has been applied. Had it been, then this topic would be showing that it will close in 3 months (since the last activity is today) instead of the 1 month that it is showing.

IMHO, the correct action - if possible is to change all topics that have the old (since topic creation) criteria to the new (since last activity).

“This topic will automatically close in 3 months.” cont

This topic was automatically closed after 91 days. New replies are no longer allowed.



I can both see the a text saying the topic is closed and see an enabled Reply button. Is this a sage thing or is it the same to everyone?

Also I’m still wondering what this feature is good for. There have been several examples of posts that never gets irrelevant. Are there any examples of these undesired “zombie” post replies?