@codinghorror wrote:

We have a request from a customer that I've been expecting for a while:

We want to remove the beta and alpha categories, and all topics in those categories

Meaning, there are a whole lot of posts in those alpha and beta categories that represent the state of their software at a much older point in time, such that all the topics there are basically irrelevant, forever. (This is also video game software, where after 3 years a game is forgotten forever and never played again, so old beta/alphas of games are especially irrelevant in the world of software.)

The intent of the "archive" action on a topic is to prepare it for eventual archiving. Now that may mean deleting it. Or it could mean moving it to some kind of historical long term offline archives. At any rate, an archive is something that is

• not of practical current interest
• might be useful very rarely to someone digging through long term history for obscure reasons
• helpful to remove from the current active instance to make room for newer, more relevant current content

I believe archiving should be triggered either by:

• archiving out all topics with a state of archived
• archiving out all topics in a particular category

I'm not sure we can physically remove the posts and topics from the database without extreme trauma to our codebase, so perhaps the only alternatives are to

1. delete (all our deletes are soft deletes) every topic in the category
2. mark the category as archived, and have special handling for topics in archived categories

Then, produce an export file of the archived topics.

This also implies there is a way to selectively bring back a set of archived posts, or an archived category, which is probably way too hard.

I guess the simple thing to do, for now, is

• just mark every topic in the category (or all archived topics) as deleted for now.
• make sure we have an 'archived' category state (perhaps a date of archive) to look at later.

Any thoughts here?

Posts: 5

Participants: 4

Read full topic

@Umbrella wrote:

The badge system has been a big hit on our forums, but I've encountered a small issue. I'll admit, I'm not the most savvy and my permissions for the forums end forum-side as an administrator.

There are a couple of badges that I can "preview granted badges" perfectly well (and it shows a healthy list of users) but it doesn't award those badges. I also made sure I had update daily selected! My guess is that the query is snagging somewhere, but everything I've learned is from Discourse meta! I've tried to read up on other issues on Discourse meta, but none of them seem to solve my problem (or they do and I'm failing to interpret that they're the solution )

Posts: 4

Participants: 2

Read full topic

@Albert_Dao wrote:

What can I do to get my password on my forum reset without access to the email that I registered it with? I do have instances where I changed the registered email to an alternate one, but the password change prompt only wants to send to the originally registered email.

Posts: 3

Participants: 3

Read full topic

@JJames wrote:

Apologies for a possibly stupid question, but I upgraded my DO droplet and discourse is no longer listening on port 80 anymore.

root@droplet2:/var/discourse# docker ps
CONTAINER ID        IMAGE                        COMMAND             CREATED             STATUS              PORTS                                        NAMES
713e7cc60616        local_discourse/app:latest   "/sbin/boot"        4 minutes ago       Up 3 minutes        0.0.0.0:2222->22/tcp, 0.0.0.0:4578->80/tcp   app

I already tried upgrading and rebuilding the app. I also rebooted my box several times. What could be the problem?

I didn't change any configuration settings.

Thanks

Posts: 3

Participants: 2

Read full topic

@jd2066 wrote:

I was reading the meta.discourse.org about pages and noticed that the Privacy Policy has a link to the wrong Wikipedia article.
The link "Children's Online Privacy Protection Act" points to http://en.wikipedia.org/wiki/Children when it should point to http://en.wikipedia.org/wiki/Children%27s_Online_Privacy_Protection_Act instead.

Posts: 3

Participants: 2

Read full topic

@Mohit_Gupta wrote:

I have written a badge granting query for every time you receive a like but it seems that I cannot grant those badges because some of those badges have same badge id, user id and post id. Is their any solution for this problem?
Can i add any other parameter like time-stamp to distinguish them.

Posts: 3

Participants: 3

Read full topic

@wesochuck wrote:

Continuing the discussion from Link to /last post in topic no longer works after recent updates:

In documentation for our users, we frequently use URLs with /my to make it easier for users to jump to their preferences, profiles, etc. For example:

Instead of: https://meta.discourse.org/users/wesochuck/preferences

Is using /my in URLs considered a secret hidden feature (like /last) that might be depreciated in the future?

Posts: 5

Participants: 4

Read full topic

@marijn wrote:

I've set up what should be a vanilla Docker-based Discourse install (except that I've imported an existing database from another, non-Docker install). Things mostly work, but OAuth via github (as well as twitter) fails with a message=redirect_uri_mismatch error. Inspecting the actual packets that are being sent over, I see this in the url:

redirect_uri=http%3A%2F%2Flocalhost%3A6080%2Fauth%2Fgithub%2Fcallback

So that explains that error message. What can I do to make Discourse use its real url (discuss.codemirror.net in this case)?

Edit: Forgot to mention, the container isn't directly binding port 80/443, but being proxied through an nginx, since the host serves other sites as well.

Posts: 3

Participants: 3

Read full topic

@charleswalter wrote:

Our users are clamoring for signatures. It's the one thing that has become the most consistent issue brought up so far. We cannot just ignore our audience, so I wanted to see what could be done.

While I understand the drawback of them, if there were an option that they were off by default, and users had the option to turn them on, I don't see what the harm could be.

I hope that this is taken into consideration.

Posts: 37

Participants: 14

Read full topic

@marijn wrote:

I had an old Discourse install whose 'backup' feature kept failing, so when migrating I manually dumped the database and imported it into a fresh install, followed by migrating the database. That worked great—I now have a mostly working new instance. But I suppose I missed some files, since a lot of users now have blank avatar images.

Unfortunately, the directory structure under uploads/default on the old install looks nothing like the structure on the new install, and I can't figure out which files to copy where. Any tips on how to move over the avatar files? Is there an equivalent to db migration for files?

Posts: 3

Participants: 2

Read full topic

@loopback0 wrote:

As above, when a user replies to a post with a poll in it, the poll shows in the reply-to expansion but with 0 votes.

The post:

The reply-to:

Pasted image895x499 55.6 KB

Posts: 1

Participants: 1

Read full topic

@lxsameer wrote:

Hi,
First of all well done on "Discourse".

I installed discourse with fa_IR as locale.

The question is, what full text search tool should I use with my instance.

Posts: 3

Participants: 2

Read full topic

@bedhed wrote:

fixed category positions is set to true

Screenshot from 2015-09-04 18:13:34.png729x63 10.5 KB

but I don't know where to go/clic to change the position of the categories.

This is mydomain/categories

Screenshot from 2015-09-04 18:14:16.png1187x563 77.4 KB

(also I cannot find Discourse software version anymore)

Posts: 5

Participants: 3

Read full topic

@tobiaseigen wrote:

On my site we are considering replacing our category structure with cross-cutting tags. To make this work, we need to be able to let users see and set the tags they are watching, as they can now with categories. This will also help admins to make sure people are getting everything they need to be getting.

So the suggestion is to add a section to the user preferences page that replicates the category notification settings, but for tags. Start typing a tag in "watching" and it autocompletes. Select the X next to a listed tag and it is removed.

Perhaps an MVP alternative to this would be to add simple UI to /tags to allow users to show tags filtered by their notification level.

Posts: 7

Participants: 5

Read full topic

@kingofseo wrote:

Hello,

I really like discourse and would like to install discourse on plesk 12 with ubuntu 14.04 would be happy to have a instruction.

Thanks

Posts: 2

Participants: 2

Read full topic

@wesochuck wrote:

Has anyone see this before?

Pasted image1174x115 9.39 KB

When I click on these topics a page opens that ONLY has the site header and nothing else:

Pasted image1128x263 21.3 KB

If I attempted to delete them using the post actions, I get the following backtrace in /logs:

/var/www/discourse/lib/post_destroyer.rb:73:in `block in perform_delete'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `block in transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/database_statements.rb:209:in `within_new_transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/transactions.rb:208:in `transaction'
/var/www/discourse/lib/post_destroyer.rb:72:in `perform_delete'
/var/www/discourse/lib/post_destroyer.rb:45:in `destroy'
/var/www/discourse/app/controllers/topics_controller.rb:276:in `destroy'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/base.rb:189:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:552:in `block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:502:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:502:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:86:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/notifications.rb:159:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/notifications.rb:159:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/base.rb:136:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.10/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.6/lib/mini_profiler/profiling_methods.rb:77:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal.rb:232:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:82:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:82:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/journey/router.rb:73:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/journey/router.rb:59:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/journey/router.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:692:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/builder.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/conditionalget.rb:35:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/head.rb:11:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:124:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/flash.rb:254:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.16/lib/message_bus/rack/middleware.rb:60:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/cookies.rb:562:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/connection_pool.rb:621:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:82:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/remote_ip.rb:76:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-1.0.0.3.pre/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/rack/logger.rb:22:in `call'
/var/www/discourse/config/initializers/quiet_logger.rb:10:in `call_with_quiet_assets'
/var/www/discourse/config/initializers/silence_logger.rb:26:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/methodoverride.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/runtime.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/sendfile.rb:112:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.6/lib/mini_profiler/profiler.rb:170:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:72:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/engine.rb:514:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/application.rb:144:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/builder.rb:138:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/urlmap.rb:65:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:576:in `process_client'
/var/www/discourse/lib/scheduler/defer.rb:85:in `process_client'
/var/www/discourse/lib/middleware/unicorn_oobgc.rb:95:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:670:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:525:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:140:in `start'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `load'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `<main>'

The only thing unique that I can think of is that these are in a category that is NOT visible by everyone AND these two users have not logged in for sometime.

Posts: 3

Participants: 2

Read full topic

@loopback0 wrote:

I have enough topics in new and unread that I get the new warning - but as of earlier the numbers aren't showing?

Is this intentional? Have tried a hard refresh.

Posts: 5

Participants: 3

Read full topic

@rc4 wrote:

Windows 10, Chrome 44:

Posts: 9

Participants: 5

Read full topic

@sjmscott wrote:

I am a high school teacher using Discourse to in the classroom. Is there any way to see all of a users posts without so many clicks?

For example, I currently click on a user name and I see all of the student posts. Each message gives a preview of the post. Ideally, I would be able to see all of the student posts without the preview. Is there any way to change this setting so there is no preview?

Posts: 2

Participants: 2

Read full topic

@Daquantics wrote:

I'm using Discourse for tech support, and accidentally added a second customer to a PM when I meant to add a coworker

No way to remove someone from a PM thread? I'm an admin, for what it's worth

We're running v1.4.0.beta8 +44

Posts: 3

Participants: 2

Read full topic