Quantcast
Channel: Discourse Meta - Latest topics
Viewing all 60309 articles
Browse latest View live

Failed bootstrap: rake aborted (wrong number of arguments)

0
0

@tophee wrote:

When rebuilding my app, bootstrapping fails like this:

2017-12-19 09:36:33.578 UTC [48] LOG:  database system is shut down


FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 569 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle install --deployment --verbose --without test --without development --retry 3 --jobs 4'", "su discourse -c 'bundle exec rake db:migrate'", "su discourse -c 'bundle exec rake assets:precompile'"]}
40524c0dfb47d3a58c4b841f5dd20a252f4530659897e23ea6be2c702ff088b1
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

Further up, I find

Bundled gems are installed into `./vendor/bundle`

I, [2017-12-19T09:36:12.734165 #14]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate'
rake aborted!
ArgumentError: wrong number of arguments (given 1, expected 2..3)

I uninstalled any suspicious plugins. Here is what I have left:

          - git clone https://github.com/discourse/docker_manager.git
          - git clone https://github.com/discourse/discourse-spoiler-alert.git
          - git clone https://github.com/discourse/discourse-solved.git
          - git clone https://github.com/discourse/discourse-data-explorer.git
          - git clone https://github.com/discourse/discourse-canned-replies.git
          - git clone https://github.com/discourse/discourse-translator.git
          - git clone https://github.com/discourse/discourse-admin-statistics-digest.git
          - git clone https://github.com/discourse/discourse-feature-voting.git
          - git clone https://github.com/discourse/discourse-staff-notes.git
          - git clone https://github.com/berlindiamonds/discourse-sync-base.git
          - git clone https://github.com/berlindiamonds/discourse-sync-to-dropbox.git
          - git clone https://github.com/discourse/discourse-assign.git
          - git clone https://github.com/discourse/discourse-bbcode.git

How can I troubleshoot this?

Posts: 2

Participants: 1

Read full topic


Forum is down (Error: invalid CSS)

0
0

@Maciej_Orlowski wrote:

Hi guys,

Our forum’s been down since yesterday. All we get when we log in / sign up is this Error:

The thing is, right now I’m not able to get into my admin to change the code and since Discourse is hosting our site, I’m not able to change anything. Tried reading some similar topics about entering the safe-mode, but it doesn’t work - my site doesn’t want to connect this way.

What should I do?

Posts: 3

Participants: 3

Read full topic

Backup failed — whats to check?

0
0

@Dmitry_Krasnoperov wrote:

The backup has failed.

Here’s the log:

[2017-12-19 10:59:34] [STARTED]
[2017-12-19 10:59:34] 'dmitre' has started the backup!
[2017-12-19 10:59:34] Marking backup as running...
[2017-12-19 10:59:34] Making sure '/var/www/discourse/tmp/backups/default/2017-12-19-105934' exists...
[2017-12-19 10:59:34] Making sure '/var/www/discourse/public/backups/default' exists...
[2017-12-19 10:59:34] Pausing sidekiq...
[2017-12-19 10:59:34] Waiting for sidekiq to finish running jobs...
[2017-12-19 10:59:34] Dumping the public schema of the database...

[2017-12-19 11:01:08] Finalizing backup...
[2017-12-19 11:01:08] Creating archive: da-stereo-2017-12-19-105934-v20171214040346.tar.gz
[2017-12-19 11:01:08] Making sure archive does not already exist...
[2017-12-19 11:01:08] Creating empty archive...
[2017-12-19 11:01:08] Archiving data dump...
[2017-12-19 11:01:09] Archiving uploads...
[2017-12-19 11:02:37] Removing tmp '/var/www/discourse/tmp/backups/default/2017-12-19-105934' directory...
[2017-12-19 11:02:37] Gzipping archive, this may take a while...
[2017-12-19 11:11:29] EXCEPTION: Failed to gzip archive.

gzip: /var/www/discourse/public/backups/default/da-stereo-2017-12-19-105934-v20171214040346.tar.gz: No space left on device

[2017-12-19 11:11:29] /var/www/discourse/lib/discourse.rb:27:in `execute_command'
/var/www/discourse/lib/backup_restore/backuper.rb:244:in `create_archive'
/var/www/discourse/lib/backup_restore/backuper.rb:42: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/controllers/admin/backups_controller.rb:31:in `create'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/basic_implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/base.rb:186:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/rendering.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:131:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/rescue.rb:20:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/notifications.rb:166:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/notifications.rb:166:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/params_wrapper.rb:252:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/railties/controller_runtime.rb:22:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/base.rb:124:in `process'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionview-5.1.4/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-0.10.7/lib/mini_profiler/profiling_methods.rb:102:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal.rb:189:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal.rb:253:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/route_set.rb:49:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/route_set.rb:31:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/mapper.rb:16:in `block in <class:Constraints>'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/mapper.rb:46:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/journey/router.rb:50:in `block in serve'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/journey/router.rb:33:in `each'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/journey/router.rb:33:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/route_set.rb:834:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-protection-2.0.0/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/builder.rb:63:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/conditional_get.rb:38:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/head.rb:12:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:149:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/session/abstract/id.rb:232:in `context'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/session/abstract/id.rb:226:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/cookies.rb:613:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/callbacks.rb:26:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:97:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/callbacks.rb:24:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/debug_exceptions.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/logster-1.2.9/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/rack/logger.rb:36:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/rack/logger.rb:26:in `call'
/var/www/discourse/config/initializers/100-quiet_logger.rb:16:in `call'
/var/www/discourse/config/initializers/100-silence_logger.rb:29:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/remote_ip.rb:79:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/request_id.rb:25:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/method_override.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/runtime.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/executor.rb:12:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/sendfile.rb:111:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-0.10.7/lib/mini_profiler/profiler.rb:282:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/message_bus-2.1.1/lib/message_bus/rack/middleware.rb:63:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:138:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/engine.rb:522:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/railtie.rb:185:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/railtie.rb:185:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/urlmap.rb:68:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/urlmap.rb:53:in `each'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/urlmap.rb:53:in `call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.3.1/lib/unicorn/http_server.rb:606:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.3.1/lib/unicorn/http_server.rb:702:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.3.1/lib/unicorn/http_server.rb:549:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.3.1/lib/unicorn/http_server.rb:563:in `maintain_worker_count'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.3.1/lib/unicorn/http_server.rb:293:in `join'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.3.1/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.4.0/bin/unicorn:23:in `load'
/var/www/discourse/vendor/bundle/ruby/2.4.0/bin/unicorn:23:in `<main>'
[2017-12-19 11:11:29] Notifying 'dmitre' of the end of the backup...

I’m on DO server.

Posts: 3

Participants: 3

Read full topic

504 Gateway time out

Launcher fails after latest commits

0
0

@Tzanko_Matev wrote:

When running ./launcher bootstrap app I get the following error message:

I, [2017-12-19T12:38:25.878582 #15]  INFO -- : > cd /var/www/discourse && git fetch origin tests-passed
From https://github.com/discourse/discourse
 * branch            tests-passed -> FETCH_HEAD
I, [2017-12-19T12:38:28.270063 #15]  INFO -- :
I, [2017-12-19T12:38:28.270201 #15]  INFO -- : > cd /var/www/discourse && git checkout tests-passed
error: Your local changes to the following files would be overwritten by checkout:
        app/assets/javascripts/locales/sr.js.erb
Please, commit your changes or stash them before you can switch branches.
Aborting
I, [2017-12-19T12:38:28.406612 #15]  INFO -- :


FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && git checkout tests-passed failed with return #<Process::Status: pid 69 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"code", "cmd"=>["git reset --hard", "git clean -f", "git remote set-branches --add origin master", "git pull", "git fetch origin $version", "git checkout $version", "mkdir -p tmp/pids", "mkdir -p tmp/sockets", "touch tmp/.gitkeep", "mkdir -p                    /shared/log/rails", "bash -c \"touch -a           /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr}.log\"", "bash -c \"ln    -s           /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr}.log $home/log\"", "bash -c \"mkdir -p           /shared/{uploads,backups}\"", "bash -c \"ln    -s           /shared/{uploads,backups} $home/public\"", "chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups"]}
715e5e87c5c947c310a17451f0c16479a4f12a05232ab068b892ef7bb5717198
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

I suspect that the error was introduced by this commit: FEATURE: Serbian translation (#5443) · discourse/discourse@0df1c85 · GitHub

Posts: 4

Participants: 2

Read full topic

Payment option plugin

0
0

@Gagan_Khokhar wrote:

I using discourse as my main website, and I would like to get payment options for my users while signup, for my services

Posts: 2

Participants: 2

Read full topic

Different counting methods for Likes Take II

0
0

@RonjaS wrote:

Hey there,

our users complain about a problem with disappearing likes.
I tried to grab the problem, but failed. So first of all (before I actually can say, what the bug is) it would be nice, to have some more information about the likes.

Here was discussed, what the difference in the like-counter for badges an the user_stats is.
Now is my question: what ist the difference between the numbers likes submitted/received in

a) the user profile
b) the user list
c) the admin-view of the user profile

I suspect in c) likes in PMs/private categories are missing, but a) & b) should be similar (they aren’t always!)?

Maybe I’ll make a seperate post for the bug, when I can say anything else about it than “likes disappearing”…

Thanks :heart:

Posts: 1

Participants: 1

Read full topic

Ability to set a topic reminder for someone else?

0
0

@tobiaseigen wrote:

I just came across a situation where I wanted to be able to set a topic reminder for another moderator and was unable to do so. I realize this is likely to be be abused by delegation happy admins but I still think it might be worth considering. A group of us share moderator/membership management duties and it would be helpful to assign a message to someone else and set a topic reminder at the same time.

Posts: 4

Participants: 3

Read full topic


Minor CSS Change Proposal

0
0

@Patrick_David wrote:

Hi all! Happy Holidays!

I’ve got users on my instance (discuss.pixls.us) that have what I think is a reasonable request: the spacing between list elements could be increased a bit.

At the moment, list items don’t have any extra spacing to offset each item:

  • I am the very model of a modern Major-General,
    I’ve information vegetable, animal, and mineral,
    I know the kings of England, and I quote the fights historical,
    From Marathon to Waterloo, in order categorical;
  • I’m very well acquainted too with matters mathematical,
    I understand equations, both the simple and quadratical,
    About binomial theorem I’m teeming with a lot o’ news—
    With many cheerful facts about the square of the hypotenuse.

The line height is the same as the list element spacing, making it hard sometimes to read lists effectively. This doesn’t pertain to list items that are rendered loose, which look a bit better:

  • I am the very model of a modern Major-General,
    I’ve information vegetable, animal, and mineral,
    I know the kings of England, and I quote the fights historical,
    From Marathon to Waterloo, in order categorical;

  • I’m very well acquainted too with matters mathematical,
    I understand equations, both the simple and quadratical,
    About binomial theorem I’m teeming with a lot o’ news—
    With many cheerful facts about the square of the hypotenuse.

Though I think the loose rendering is a bit much personally, it is certainly more readable than the tight rendering.

So I took a quick look and adding some slight margin spacing between <li> elements makes things look a bit better (this is with .cooked li { margin-bottom: 0.2em; }):

image

This plays nicely with loose lists as the vertical margin will collapse (basically doesn’t change anything on loose lists).

Any thoughts on possibly defaulting this style:

.cooked li {
    margin-bottom: 0.2em;
}

Posts: 8

Participants: 6

Read full topic

Want to show ad in the right side of 2nd post in topic pages

After recent release our text editing options not working - Disabled

0
0

@wasghar wrote:

After recent releases, we are experiencing that our text editor optons are disabled and while writing post, we cannot use those. No text editing, no file upload, no emoje. Please can you help.

Cheers,
Muahmmad

Posts: 4

Participants: 2

Read full topic

Opening all links on a new page

0
0

@McBlu wrote:

I would like to open all links within the forum in a new page. Is that possible?

Posts: 7

Participants: 3

Read full topic

Timing topics max amount

0
0

@jordan1909 wrote:

Theoretically, is there a limit to the number of topics that may be timed at any one time?

I am currently trying to create a plugin that when an admin or moderator replies to a topic it automatically sets a timer to remind them to check the status by doing a post (same way the current timer implementation does but automagically). My only concern is say we end up at 150 timed topics, will this cause an issue?

Posts: 2

Participants: 2

Read full topic

About administration for begginer , Clean Cloud

0
0

@Tumi wrote:

Hello

Some questions. I got clean server just ubuntu. Now after installation i dont know:

  • should i install any “software” like iptables (firewall) or somethink else? Or docker over this ?
  • should i know/learn hot to configure somethink more on server?
  • should i connecting via ssh as non admin ? how to do it ? just create an new user only ?

for example - after install a docker - "If you would like to use Docker as a non-root user, you should now consider
adding your user to the “docker” group with something like:

sudo usermod -aG docker" Should i do it ?

Posts: 5

Participants: 3

Read full topic

Tooltip undefined


Recover deleted editor text for New Topic?

0
0

@tophee wrote:

I don’t have much hope, but: is there a way to recover previously saved copies of the text in the (mobile) editor? Or is only the respective latest version saved?

I’m referring to the situation where the user starts composing a new topic but accidentally deletes the text (select all -> type any character) before pressing “create topic”.

Posts: 17

Participants: 3

Read full topic

Autolinks to new but unknown categories gives a 404

Plugin howto self-announcement

0
0

@supermathie wrote:

One of our customer’s sites gave me an idea earlier that was well-received by the team so I’d like to hear what the community thinks of it.

Do you think it’d be pretty cool if plugins automatically injected a “how to use me” page into a meta topic when enabled? Kind of like what these people are doing:

It’d be very useful if plugins could ‘announce’ themselves like this with a short post like that :arrow_double_up: in the forum’s default Meta category (is there one? oh, wait, there isn’t. that’s another discussion).

possible ideas:

  • hidden by default on existing sites (that have existed for a certain $duration)
  • a note to @staff explaining these announcements (especially on existing sites) that can be moved into a public place

This would let forum users know about extra :cool: features that may not be present on other sites and ease the burden on site leaders explaining how these features work.

Posts: 2

Participants: 2

Read full topic

Amend "flag to re-open" to topic-is-closed posts

0
0

@tophee wrote:

Continuing the discussion from Contributor Interviews – Felix "fefrei"

This is a great idea, but it’s not quite as easily implemented as it may seem. Searching for closed in Customize -> Text Content yields quite a number of text elements.

To start with, it’s not immediately clear which ones of these need to be customized to achieve the desired outcome. But even if one goes ahead and edits all of those that look like they should be edited, it’s quite a pile of work. And when you realize that maybe one of them should not have been changed, you need to figure out which one that was.

So, if there is widespread support for adding “flag to re-open” to those text elements, maybe that could become the default. In any case, it would be great if a new text element containing “Flag to re-open” could be added and that variable would then be inserted in all relevant text elements. That way, changing or deleting that part, only requires editing one copy, instead of more than a dozen.

Posts: 1

Participants: 1

Read full topic

Any way to disable gzip of backup?

0
0

@nixie wrote:

My discourse instance is hosted at DigitalOcean on a droplet with 60GB SSD.

Out of 60 GB, 34 GB is already consumed, so free space left is 25GB.

My backup settings

  1. Keeps just latest 1 backup
  2. And sends the same to Amazon S3

What is the exact issue I’m facing

  1. Backup starts.
  2. It creates the archive. The archive size = 14 GB. Free space left = 11GB.
  3. It then starts to do create a gzip of the archive.
    (once gzip is successfully done, the archive will be deleted, and only the gzipped version will stay)
  4. Unfortunately, the gzip process fails, because of low free space.
  5. Because of this the backup is NOT sent to Amazon S3.

I have 2 questions

  1. Is it possible to disable gzip of backup?
  2. If gzip of backup fails - can it be made to send the archive to Amazon S3? That way, at least something is being sent to the cloud.

Posts: 4

Participants: 2

Read full topic

Viewing all 60309 articles
Browse latest View live




Latest Images