@wangerin wrote:

My discourse-forum is going to be shut down, as our org is soon being shutdown, but I’d like to keep a static version of the public porting of our forum.

How can I do that?

I tried to simply pull a copy using wget, but that didn’t get a usable result.

Thanx
/Henning

Posts: 3

Participants: 2

Read full topic

@ckshen wrote:

I don’t know if its me or not, but CSS not gzipped in v1.9.0.beta11 +11. I rebuilt twice. Same outcome. This is just an FYI because I recall your previous version had CSS gzipped.

From Webpagetest.com:

Use gzip compression for transferring compressable responses: 83/100
1,097.9 KB total in compressible text, target size = 905.3 KB - potential savings = 192.6 KB

FAILED - (238.9 KB, compressed = 49.9 KB - savings of 189.0 KB) - https://cdn.hungryonion.org/stylesheets/desktop_53db8b241fb591d95ca2def7e68b5778e6218d7b.css?__ws=www.hungryonion.org
FAILED - (4.9 KB, compressed = 1.3 KB - savings of 3.6 KB) - https://cdn.hungryonion.org/stylesheets/desktop_theme_4_559696c45721d3f1d25cc69be6a48a962905ddbb.css?__ws=www.hungryonion.org

Posts: 3

Participants: 2

Read full topic

@DaBeast_45 wrote:

When ever I try to undo a flag, the button disappears and it won’t undo.

Posts: 2

Participants: 2

Read full topic

@sianwhite wrote:

Is there a way to lock a category so only admins can post into it? I’d rather it didn’t look any different to the other categories, it would just be amazing if it could not appear in the dropdown selection for users to choose.

Not sure if this is possible, but thought I’d ask anyway!

Sian

Posts: 4

Participants: 3

Read full topic

@Trash wrote:

I just noticed that when a topic is closed, no notification is sent.

For example here (Cursor misalignment in the categories box (Firefox)) happened to see that the bug was fixed some days ago but I only saw this today, by looking at the list of suggested topics.

I think it’s a useful feature in forums frequented by many users and it helps to keep track of all the topics a user can have opened days or months before, if it is closed for a specific reason with a text added by one of the admins/mods (this does not trigger notifications for the topics set to be closed by @system).

Posts: 1

Participants: 1

Read full topic

@alehandrof wrote:

Is there a way to search for both public topics and PMs at once – and make that the default behavior for my site?

User case: I often know I’ve talked with someone about something but I can’t recall whether it was a message or a topic. To find it, I sometimes have to do two searches. And that’s charitably assuming that I use the correct keywords, which isn’t always the case

Posts: 1

Participants: 1

Read full topic

@alehandrof wrote:

This mockup shows a couple of desired features I think I’d like on the Messages list:

Discourse mockups.sketch 2017-09-29 14-04-51.jpg1844x526 124 KB

• Preview for first post
• Button to quickly archive messages

Also, not shown, I’d like the ability to delete messages when they’re selected.

These are the tweaks I’d like to see. What are yours?

Posts: 1

Participants: 1

Read full topic

@hellekin wrote:

Situation

• Running v1.9.0.beta10 +5
• Sending a private message to a group of two new users
• Addressed group has messaging permission
• Sender is admin

Error Message

NameError (undefined local variable or method `topic' for #<TopicCreator:0x007f33c34ad8c0>)
/var/www/discourse/lib/topic_creator.rb:254:in `rescue in find_or_create_user'

Backtrace

/var/www/discourse/lib/topic_creator.rb:254:in `rescue in find_or_create_user'
/var/www/discourse/lib/topic_creator.rb:240:in `find_or_create_user'
/var/www/discourse/lib/topic_creator.rb:211:in `block in add_emails'
/var/www/discourse/lib/topic_creator.rb:209:in `each'
/var/www/discourse/lib/topic_creator.rb:209:in `add_emails'
/var/www/discourse/lib/topic_creator.rb:174:in `process_private_message'
/var/www/discourse/lib/topic_creator.rb:47:in `create'
/var/www/discourse/lib/post_creator.rb:380:in `create_topic'
/var/www/discourse/lib/post_creator.rb:148:in `block in create'
/var/www/discourse/lib/post_creator.rb:299:in `block in transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `block in transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_record/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_record/transactions.rb:220:in `transaction'
/var/www/discourse/lib/post_creator.rb:297:in `transaction'
/var/www/discourse/lib/post_creator.rb:146:in `create'
/var/www/discourse/lib/new_post_manager.rb:183:in `perform_create_post'
/var/www/discourse/lib/new_post_manager.rb:143:in `perform'
/var/www/discourse/app/controllers/posts_controller.rb:151:in `create'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/abstract_controller/base.rb:198:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:778:in `_run_process_action_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/notifications.rb:164:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/notifications.rb:164:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/abstract_controller/base.rb:137:in `process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.9/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.5/lib/mini_profiler/profiling_methods.rb:102:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal.rb:237:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/routing/route_set.rb:43:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/journey/router.rb:43:in `block in serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/journey/router.rb:30:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/journey/router.rb:30:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/routing/route_set.rb:817:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/builder.rb:63:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/conditionalget.rb:38:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/head.rb:13:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:149:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/flash.rb:260:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rails_multisite-1.0.6/lib/rails_multisite/connection_management.rb:226:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.7/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.9/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.9/lib/rails/rack/logger.rb:22:in `call'
/var/www/discourse/config/initializers/100-quiet_logger.rb:17:in `call_with_quiet_assets'
/var/www/discourse/config/initializers/100-silence_logger.rb:29:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/methodoverride.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/runtime.rb:18:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/sendfile.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.5/lib/mini_profiler/profiler.rb:282:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.5/lib/message_bus/rack/middleware.rb:63:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:73:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.9/lib/rails/engine.rb:518:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.9/lib/rails/application.rb:165:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.9/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.9/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/urlmap.rb:66:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:606:in `process_client'
/var/www/discourse/lib/scheduler/defer.rb:85:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:702:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:549:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:142:in `start'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:22:in `load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:22:in `<main>'

Environment (anonymized)

hostname	ps-web
process_id	6560
application_version	a1ee61ec25d8de128faf46d765d1aeda9d880654
HTTP_HOST	ps.zoethical.com
REQUEST_URI	/posts
REQUEST_METHOD	POST
HTTP_USER_AGENT	Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0
HTTP_ACCEPT	application/json, text/javascript, */*; q=0.01
HTTP_REFERER	https://ps.zoethical.com/u/me/messages
HTTP_X_FORWARDED_FOR	62.A.B.C, 62.A.B.C
HTTP_X_REAL_IP	62.A.B.C
username	me

params	null
raw	Hello XX and XY, as you both accepted the invitation, I made a couple of modifications to y
title	Welcome Here
unlist_topic	false
category
is_warning	false
archetype	private_message
target_usernames	@foo
typing_duration_msecs	92000
composer_open_duration_msecs	734652
featured_link
nested_post	true

Posts: 4

Participants: 2

Read full topic

@pfaffman wrote:

I’m working on a site with two globally pinned topics. One is at the top of latest, but not the other.

The one that’s not showing on latest does appear at the top of its category page, just not on latest.

Is not that it’s un-pinned.

I’m stumped. It’s v1.7.0.beta10.

Posts: 4

Participants: 3

Read full topic

@appcomq wrote:

I have update to v1.9.0.beta11.

There is a new BUG, Attached .txt canot download.

Posts: 4

Participants: 3

Read full topic

@Eloi_Relange wrote:

Hi !
I may have missed it but the dashbaord do not include 2 KPI that seems important to monitor the health of the community :

• unique posters per day
• first poster per day (in addition to new user it will show the ability to convert new users to new posters)

As it’s my first post I will add a note for the team : Thanks and congrats disscourse rocks

Posts: 5

Participants: 3

Read full topic

@mikechristopher wrote:

Discourse 1.9.0.beta10
When changing the users title via the admin/users section it will save but revert back to what it was originally.

It still saves ok however via the users preferences page.

Anyone else able to repro this?

Posts: 4

Participants: 2

Read full topic

@uwe_keim wrote:

Since some days, the Start Upgrading button does not hide during upgrading:

image.png591x541 27 KB

I don’t know how it looked before that change, but probably there was a cancel button or the like.

Posts: 3

Participants: 2

Read full topic

@Berto wrote:

Hey everyone, my forum emailed me about an update. I’m on 1.9.0.beta10. I entered /var/discourse and tried to run a git pull but it says I’m up to date… yet I’m not!

I’m currently (and always) on the master branch, and when I do git log, the most recent thing I have is commit ee9a607677106603ace3e90f3c5bd9ca84a11ef7 from Fri Sep 15 08:27:27 2017 +0800 (Upgrade to Ruby 2.4.2).

Is my repository busted? Github having issues?

Thanks!

Posts: 4

Participants: 3

Read full topic

@dfabulich wrote:

As a new “feature” of iOS 11, Safari web views no longer share cookies with the main Safari app.

As a result, when you upgrade to iOS 11, you’re logged out of all of your associated forums in the Discourse iOS app. When you attempt to login with Google or Facebook, your authentication credentials aren’t there; you have to sign in to Facebook with a password, re-enter your second factor code, and “remember this browser” in the future.

The intended workaround for this is for iOS apps to use SFAuthenticationSession for logging in to third party services.

The Discourse iOS app should use SFAuthenticationSession to sign in to Discourse forums.

Posts: 3

Participants: 2

Read full topic

@tophee wrote:

During the last two weeks or so, I tried a little Facebook promotion aimed at getting people to follow the link to my discourse forum. According to facebook, 48 people clicked the link. However, discourse tells me on the admin dashboard under “Top Traffic Sources (Last 30 Days)” that I have received a total of 7 clicks from facebook (3 from www.facebook.com, and 2 each from lm.facebook.com and l.facebook.com). Who is right?

I also checked google analytics which saw a total of 19 referrals from facebook during the past 30 days and 8 since the camaign started.

Posts: 2

Participants: 2

Read full topic

@LucyA wrote:

Beginner here, go easy.

So in one of my categories there still appears to be a background image, even though in edit->images->category background image is blank. This image was an old one, previously uploaded but then deleted.

I have cleared my browser cache and tried incognito mode.

I found the image name using the developer tools, but I am unable to find its source in any of the CSS, code or anywhere in discourse.

Any help would be appreciated.

Posts: 1

Participants: 1

Read full topic

@michaeltcoelho wrote:

Hi there,

i’m new here and i’d like to run a high availability environment on Digital Ocean to Discourse. I’m thinking about a Load Balancer upfront with 2 instances running Discourse with docker images behind, probably using a hosted PostgreSQL and a hosted mail provider. How can i generate a configured image of the web only Discourse hosted on docker hub for my instances?

Thanks in advance.

Posts: 1

Participants: 1

Read full topic

@Michaelakatrina wrote:

Hello - I am not code savvy, nor my co-workers. I’ve gotten the error posted below. I don’t know what any of this means - but being that it’s dealing with the backup of the site I am concerned. Does this mean that the site backup isn’t working? Or is it just a random error that really doesn’t matter? Thank you in advance.

If you are a programmer who is good with this, we need help with this sort of stuff - will pay, of course.

`uninitialized constant BackupRestore::Backuper::Discouse /var/www/discourse/lib/backup_restore/backuper.rb:263:in `notify_user' /var/www/discourse/lib/backup_restore/backuper.rb:56:in `run' /var/www/d`

uninitialized constant BackupRestore::Backuper::Discouse
/var/www/discourse/lib/backup_restore/backuper.rb:263:in `notify_user'
/var/www/discourse/lib/backup_restore/backuper.rb:56:in `run'
/var/www/discourse/lib/backup_restore/backup_restore.rb:163:in `block in start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:160:in `fork'
/var/www/discourse/lib/backup_restore/backup_restore.rb:160:in `start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:15:in `backup!'
/var/www/discourse/app/jobs/regular/create_backup.rb:8:in `execute'
/var/www/discourse/app/jobs/base.rb:154:in `block (2 levels) in perform'

Posts: 1

Participants: 1

Read full topic

@Mathieu wrote:

Hello there,

I saw this post which says that if I want to get all posts from a single topic, I need to:

1. Get the topic to get all posts ID ;
2. Make a second request to get all posts with the ?posts_id[] param.

I really well understand this is a good practice to break up all posts in multiple requests, but when you have 30-40 posts to request, it makes non-sens to use two API requests to get all the data I need.

I do not think so, but is there a way to add a param on the API to say that I want x posts by requests? 20 is maybe a good value, but why not give the availability for users to set 30 or 40 (or 938 maybe…).

Cheers,
Mathieu

Posts: 1

Participants: 1

Read full topic