@RobMeade wrote:

Hi,

I act as a moderator on a hosted Discourse solution (https://community.gamedev.tv) and over the last few days have noticed an issue with posts not being set as read.

I am not an admin, so am not able to access any settings, equally I am not sure when updates take place, I guess these are done server-wide, but wondered if there had been a recent update which may have caused this behaviour?

Regarding the posts, I can scroll to the bottom of a topic, the styling of the last post is highlighted and fades out. If I return to the main summary/home page of the forum the count has not changed. Additionally, some posts are being marked with a grey icon for the count instead of the blue.

The only way I have found to force this to change is to scroll to the bottom of the topic, and change the tracking options to "Normal", but this is a very manual process and wasn't necessary previously.

Any thoughts/suggestions would be welcome.

Kind regards - Rob

Posts: 21

Participants: 4

Read full topic

@bek wrote:

Hey there!

I want to remove a post completely. For example can I delete post shown below? I don't want to see this deleted post shown in red, even if they're only visible to staff. (If you wondered why I want to remove it, because I have obsession.)

Capture.PNG761x197 8.8 KB

I think discourse is a very pleasant forum software. But sometimes it makes me laugh. I can do a lot of thing as an admin, but I can't delete post completely... What a contradiction!

Posts: 3

Participants: 2

Read full topic

@Karin3 wrote:

My 5-person, geographically-diverse writers group is looking for a new venue, as the mini-Ning platform where we've spent the past 7 years is being discontinued. There is a lot that we like about Discourse, but some members want to get more comfortable with it before we make the switch, particularly with the experience of "conversing." Changing the interface we use to interact feels like trying to speak a new language.

We've been testing in the Sandbox, but whenever we start to get going we run into the daily post limit. Would it be possible to lift that limit? Or do you have any other ideas about how we could delve a little more into Discourse before take the plunge of starting our new hanging out place in a Discourse world?

Posts: 12

Participants: 6

Read full topic

@Karin3 wrote:

One thing I love about Discourse on the desktop computer is that I can see not only the topic I'm responding to, but scroll through it and even search and check other topics while composing a reply. On iOS (both on iPhone and iPad on Safari and Chrome) my experience is that while composing replies I can't see the topic--not even the post I'm replying to. I see that an iOS app will be part of the 1.7 release. In that new app will users be able to view the topic they are replying to while composing a reply?

Posts: 5

Participants: 2

Read full topic

@deltaskelta wrote:

I installed discourse as per the instructions here: https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md

I thought that I saw something about it being served from nginx and I definitely got an error page one time that was a 500 error from nginx, so I went in to my server to tweak the nginx configs and I couldn't find it anywhere.

So how is this happening. Did I see the nginx error from my top level domain? What is serving the app?

Sorry I don't know much about ruby apps

Posts: 5

Participants: 3

Read full topic

@RGJ wrote:

Seems like you forgot to cherry pick this commit from backup_restore.rb into 1.6.2 / 1.6.3 so the constant is missing...

Resulting in:

Completed 500 Internal Server Error in 58ms (ActiveRecord: 34.9ms)
NameError (uninitialized constant BackupRestore::OLD_DUMP_FILE)
/var/www/discourse/lib/backup_restore/restorer.rb:118:in `initialize_state'

Posts: 2

Participants: 2

Read full topic

@deltaskelta wrote:

I have a t2.micro EC2 instance. 1CPU 1GB ram and 2GB swapped on.

My rebuild is running 1+ hours, I know it is a minimal machine but the time seems a bit excessive. Would this be an expected rebuild time on a small machine?

Posts: 5

Participants: 2

Read full topic

@tonninseteli wrote:

Some of my users are complaining about the new Android 7.0 emoji mostly because we have made some... customizations to some of them so the customized 6.0.1 emoji are no longer uniform with 7.0.

I know there must be bigger things in life, surely, however this is currently the only issue I have on my plate and would like to at least look into it.

I could probably include 6.0.1 emoji from an older version of discourse, what would be the most reasonable way to get around to it?

Posts: 2

Participants: 1

Read full topic

@T_Disco wrote:

It displays correctly as & on the individual category page.

I noticed this after upgrading from v1.7.0.beta3 +47 to v1.7.0.beta5 +1.

Posts: 3

Participants: 2

Read full topic

@T_Disco wrote:

The top of the category logo no longer aligns with the top of the category description and is too close to the category name.

Would adding margin-top: 15px; to .category-logo resolve this?

I noticed this after upgrading from v1.7.0.beta3 +47 to v1.7.0.beta5 +1.

Posts: 3

Participants: 2

Read full topic

@AndrzejS wrote:

dic_lang.jpg1134x208 45.6 KB

Posts: 1

Participants: 1

Read full topic

@irondev wrote:

Hey everyone,

we're looking to create a theme similar to https://talk.turtlerockstudios.com/

We would like have a header with buttons like that plus a background image and a nice border around the forums.
We don't want the dark theme, I can give more details about the specific styles later.

We can pay $150 for the design.

Thanks for the offers!

Posts: 4

Participants: 3

Read full topic

@ChrisBeach wrote:

One thing my fellow mods and I have noticed:

Often (if not always), the red dot shows above the menu icon to indicate moderator action is required, but opening the menu shows no pending items in "Flags", and no "Needs Approval" option visible.

With a subsequent click on the menu button, the "Needs Approval" option is now available and action can be taken.

Am on Discourse 1.7.0.beta5, and have seen this issue today. Will take a screenshot next time I encounter it.

Settings:

Pasted image1004x910 102 KB

Posts: 1

Participants: 1

Read full topic

@deltaskelta wrote:

I have a minimal EC2 instance running the app and I did a rebuild which I accidentally disconnected from and after that it is nearly impossible to connect to with ssh.

If I restart, it seems to restart the process and it is maxing out my swap. when I try to connect to ssh then I have to wait a few minutes for it to connect and I am lucky if I can get top to work or get any commands off. I have tried doing sudo pkill ruby but it seems to just spawn another process. I have also tried navigating to /var/discourse and running ./launcher stop app and that just hangs and never goes anywhere.

IDK where to go from here really, how would you recommend stopping it so I can recover my instance without destroying it?

Posts: 1

Participants: 1

Read full topic

@dylanh7241 wrote:

So many features, but no color really shocked me How can I allow colored text?

Posts: 6

Participants: 3

Read full topic

@rhotimee wrote:

I am trying to migrate from DigitalOcean to Ovh. i have discourse installed already on Ovh. But, when i try to restore my backup, it displays - The restore failed. Please check the logs.

[    2016-09-23 13:01:33] 'rotimi' has started the restore!
    [2016-09-23 13:01:33] Marking restore as running...
    [2016-09-23 13:01:33] Making sure /var/www/discourse/tmp/restores/default/2016-09-23-130133 exists...
    [2016-09-23 13:01:33] Copying archive to tmp directory...
    [2016-09-23 13:01:33] Unzipping archive, this may take a while...
    [2016-09-23 13:01:33] EXCEPTION: Failed to unzip archive.

    gzip: /var/www/discourse/tmp/restores/default/2016-09-23-130133/jaratalk-2016-09-23-111225-v20160919054014.tar.gz: invalid compressed data--format violated

    [2016-09-23 13:01:33] /var/www/discourse/lib/backup_restore/utils.rb:10:in `execute_command'
    /var/www/discourse/lib/backup_restore/restorer.rb:178:in `block in unzip_archive'
    /usr/local/lib/ruby/2.3.0/fileutils.rb:128:in `chdir'
    /usr/local/lib/ruby/2.3.0/fileutils.rb:128:in `cd'
    /var/www/discourse/lib/backup_restore/restorer.rb:177:in `unzip_archive'
    /var/www/discourse/lib/backup_restore/restorer.rb:38:in `run'
    /var/www/discourse/lib/backup_restore/backup_restore.rb:164:in `block in start!'
    /var/www/discourse/lib/backup_restore/backup_restore.rb:161:in `fork'
    /var/www/discourse/lib/backup_restore/backup_restore.rb:161:in `start!'
    /var/www/discourse/lib/backup_restore/backup_restore.rb:20:in `restore!'
    /var/www/discourse/app/controllers/admin/backups_controller.rb:81:in `restore'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/base.rb:198:in `process_action'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rendering.rb:10:in `process_action'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:117:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/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.7.1/lib/active_support/callbacks.rb:505:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:778:in `_run_process_action_callbacks'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:81:in `run_callbacks'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/callbacks.rb:19:in `process_action'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rescue.rb:29:in `process_action'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/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.7.1/lib/active_support/notifications.rb:164:in `block in instrument'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications.rb:164:in `instrument'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/base.rb:137:in `process'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/rendering.rb:30:in `process'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/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.7.1/lib/action_controller/metal.rb:196:in `dispatch'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal.rb:237:in `block in action'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/route_set.rb:43:in `serve'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/mapper.rb:49:in `serve'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:43:in `block in serve'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:30:in `each'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:30:in `serve'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/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.3.1/lib/omniauth/strategy.rb:186:in `call!'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/builder.rb:63:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/conditionalget.rb:38:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/head.rb:13:in `call'
    /var/www/discourse/lib/middleware/anonymous_cache.rb:129:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/flash.rb:260:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:225:in `context'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:220:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/cookies.rb:560:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/query_cache.rb:36:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:81:in `run_callbacks'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.5/lib/logster/middleware/reporter.rb:31:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/rack/logger.rb:38:in `call_app'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/rack/logger.rb:22:in `call'
    /var/www/discourse/config/initializers/100-quiet_logger.rb:13:in `call_with_quiet_assets'
    /var/www/discourse/config/initializers/100-silence_logger.rb:26:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/request_id.rb:21:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/methodoverride.rb:22:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/runtime.rb:18:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/sendfile.rb:113:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/mini_profiler/profiler.rb:278:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus/rack/middleware.rb:62: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.7.1/lib/rails/engine.rb:518:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/application.rb:165:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/railtie.rb:194:in `public_send'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/railtie.rb:194:in `method_missing'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/urlmap.rb:66:in `block in call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `each'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `call'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/lib/unicorn/http_server.rb:562: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.1.0/lib/unicorn/http_server.rb:658:in `worker_loop'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/lib/unicorn/http_server.rb:508:in `spawn_missing_workers'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/lib/unicorn/http_server.rb:132:in `start'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/bin/unicorn:126:in `<top (required)>'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:23:in `load'
    /var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:23:in `<main>'
    [2016-09-23 13:01:33] Trying to rollback...
    [2016-09-23 13:01:33] There was no need to rollback
    [2016-09-23 13:01:33] Notifying 'rotimi' of the end of the restore...
    [2016-09-23 13:01:34] Cleaning stuff up...
    [2016-09-23 13:01:34] Removing tmp '/var/www/discourse/tmp/restores/default/2016-09-23-130133' directory...
    [2016-09-23 13:01:34] Unpausing sidekiq...
    [2016-09-23 13:01:34] Marking restore as finished...
    [2016-09-23 13:01:34] Finished!

i don't understand what is happening. Please help

Posts: 6

Participants: 2

Read full topic

@rebel wrote:

point to your discourse install?

I followed the simple docker guide made my site

discourse.mysite.com

Is it possible to change it to
www.mysite.com ?

Thanks everyone!

Posts: 2

Participants: 2

Read full topic

@DanielMarquard wrote:

I recently wrote a PHP script that receives data from a Discourse webhook every time a new topic or reply is posted. I thought I'd share the foundation for the code so that other developers can quickly get started working with the event data sent by their Discourse webhooks.

If you have any questions or improvements for this code, let me know!

<?php

// Immediately verify the authenticity of the request.
if (array_key_exists('HTTP_X_DISCOURSE_EVENT_SIGNATURE', $_SERVER)) {
    $discourse_payload_raw = file_get_contents('php://input');
    $discourse_payload_sha256 = substr($_SERVER['HTTP_X_DISCOURSE_EVENT_SIGNATURE'], 7);

    // For security, configure the webhook with a secret in Discourse and set it below.
    $discourse_payload_secret = '';

    // Verify that the request was sent from an authorized webhook.
    if (hash_hmac('sha256', $discourse_payload_raw, $discourse_payload_secret) == $discourse_payload_sha256) {
        echo 'received';
    }
    else {
        die('authentication failed');
    }
}
else {
    die('access denied');
}

// Prepare the payload for use in the PHP script.
$discourse_json = json_decode($discourse_payload_raw);

// Below here, do whatever you want with the JSON.
print_r($discourse_json);

?>

Posts: 1

Participants: 1

Read full topic

@bek wrote:

Hi,

I'm investigating my sql dump because it took 15mb with only 3 post. I figure out that there is a table which is named "scheduler_stats" and it have about 40k lines of data. I just want to learn is it safe to clean this table with some sql query like "delete from scheduler_stats where id < 500;" ? Or may be there is a feature which is come with discourse by default for cleaning that table?

Also I found that it is possible to completely remove posts which is already "deleted" by :

DELETE FROM posts WHERE deleted_at IS NOT NULL;
DELETE FROM topics WHERE deleted_at IS NOT NULL;

But I don't sure about if this is safe or not..
Does anyone have any idea?

Posts: 13

Participants: 6

Read full topic

@cappslock wrote:

Found this out while writing a request to change the tags on a topic.

Basically, this doesn't work:

PUT /t/123.json?api_username=...&api_key=...

{
  tags: ['a']
}

The server responds with:

403
{
  "errors": [
    "You are not permitted to view the requested resource."
  ],
  "error_type": "invalid_access"
}

However, if you put the topic slug on the URL, everything works fine (i.e. PUT /t/why-arent-there-better-animals/123.json?api_username=...&api_key=...)

Posts: 2

Participants: 2

Read full topic