@stroupaloop wrote:

Hey Discourse community! This may be a quick fix, but I couldn't find anything that solved this problem.

I recently updated my Discourse server (docker > AWS setup > EC2, postgres, Redis, SES) and have been stuck in read only mode. I've tried ssh'ing into my server and running the following commands

sudo ./launcher enter app
discourse disable_readonly

which returns

WARN: Redis is in a readonly state. Performed a noop
The site is now fully operable.

OR entering the rails console

sudo ./launcher enter app
rails c
Discourse.disable_readonly_mode

which returns ...

WARN: Redis is in a readonly state. Performed a noop
=> true

but even after a rebuild I'm still unable to log into the Discourse server. Not super familiar with Redis, any help would be awesome!

Posts: 1

Participants: 1

Read full topic

@Minghui_Yu wrote:

Just installed Discourse a few days ago. It is amazing!

I have made some customization through admin control panel. However, I am stuck when I want to make further customization beyond what control panel offers.

Where can I edit template files? Do I have to write a plugin to customize the appearance of Discourse?

Thanks,

Posts: 6

Participants: 4

Read full topic

@Eric_Hoxworth wrote:

I have a production instance and testing instance, both at 1.3.0.beta7, and on both, as an admin, I cannot edit a category or create a new category. When the edit category or create category buttons are clicked, the transparent gray modal appears, but there is no dialog for edit or new.

The failing behaviour has been verified in different browsers. There are no javascript or network errors taking place. Nothing obvious shows up in discourse's syslog.

I've disabled plugins and recent changes for SSO with no change in behavior. We have, in the past used these features. Any clues/hints on troubleshooting to understand root cause?

Posts: 1

Participants: 1

Read full topic

@AlexAB wrote:

We are experiencing many Broken Images...Most are not loading at all!

Posts: 2

Participants: 2

Read full topic

@DeanMarkTaylor wrote:

I've had several users report receiving PM SPAM from LinkedIn.

These come in the form of emails sent to the special reply email addresses which are used by Discourse when notifications are sent out to users.
E.g. replies+nnnnnnnnnnnnnnnnn@reply.example.com

Somehow these email addresses are imported into LinkedIn (perhaps by contacts sync) and then used to invite you to LinkedIn.

The first line of the email is usually something similar to (but with a different name):

John Smith would like to connect on LinkedIn. How would you like to respond?

Or

I'd like to add you to my professional network on LinkedIn

---

In order to get ahead of these as I can see quite a number of my users have has messages in this form...

I've added a "filter" to the GMail account I use to handle mail for Discourse and set it to "Archive" / "Skip inbox" for those emails.

Pasted image657x540 35 KB

In my case I also added a label so I can track those emails if needs be later.

Hope this is helpful to someone to before it impacts their communities.

This might be helpful in the howto category - but I'll leave that to the Discourse team to review.

Posts: 3

Participants: 2

Read full topic

@benhamner wrote:

Do you do any form of user interviews at Discourse (e.g. to establish personas, to see how people use the current product, or to evaluate upcoming product features)?

If so, how do you do them and how helpful do you find them?

If not, why not?

Posts: 8

Participants: 6

Read full topic

@AlexAB wrote:

I'm missing something regarding inline animated gifs. Is there a size threshold over which the gif is made a thumbnail? If so, what's the size?

Posts: 3

Participants: 2

Read full topic

@Erik_Manger wrote:

Hi,

I have to keep editing categories and such on my Discourse forum because the permission sets do not save properly.

For instance, I'll give admin read / write / see and when I save / refresh, their permission set will either be different or non-existent.

Is this a glitch?

Posts: 1

Participants: 1

Read full topic

@AlexAB wrote:

For the sake of de-cluttering the main topic view and keeping it interesting, it would be cool if moderators could make the issue "resolved" and then the topic could go into an archive. The original poster could veto that decision if they don't think the issue has actually been resolved, which would restore the topic to the main feed, and original posters could mark the topic as Resolved themselves, as well.

That way the Resolved Posts could still be available in search results, but wouldn't have this forum presenting topics it doesn't need to present to people.

OR - perhaps near the topic name, there could be a "resolved" icon or text so it would still be visible and not archived necessarily, but you can see right away that it is resolved and you don't need to go into the thread to see if someone needs help. Perhaps this is an admin only feature and/or the original poster.


Although, I think there's shades of grey at times. Some questions aren't ever resolved; they always benefit from further suggestions, because there's often more than one awesome solution, and more may be added with time. So having 3 categories of resolution, with the writer of the initial topic having voting power on an imposed resolution status, might be useful. Unresolved, Resolved-ish or Discussion-level, and Resolved would let potential helpers in the forum know how much attention to pay to each topic. Symbols could be used to quickly identify posts.

? for "Needs Help"
~ for ongoing "Welcomes Suggestions and Thoughts", which might be discussions or partially resolved questions.
- for Resolved

Posts: 3

Participants: 3

Read full topic

@nahtnam wrote:

Hey!

I was wondering what the cheapest option is to host Discourse. I have seen a lot of sites that say 6gb of ram for $5-10 per month (http://vpsdime.com/) but they never end up having the correct version of kernel.

The only "cheap" option I have found is Digital ocean with $10 per month.

EDIT: It looks like OpenVZ doenst support Docker.

Posts: 4

Participants: 2

Read full topic

@BCHK wrote:

I, and some of my members, have seen a "read only mode" pop up after we've accepted the notifications on our browser notice.

Should this notification come on after I accept the notifications? Seems very strange. This is the first I've heard of read-only mode (I don't follow all the discussions here).

After a while the message seemed to go away - not sure why. I didn't notice any changes in my abilities on the forum.

Posts: 7

Participants: 3

Read full topic

@MarcoZehe wrote:

Continuing the discussion from Accessibility software and discourse:

When I advertised the great changes made to Discourse in accessibility over the past few days on Twitter last night, a friend came back with this PageSpeed results page. Some of these sound pretty serious, especially the first one.

Are you aware of these problems?

Thanks!
Marco

Posts: 4

Participants: 2

Read full topic

@dreeves wrote:

Here's an example of an existing poll that seems to have broken:

And to test it here:

• Polls work for me...
• Polls broken for me as well!

0voters

Show results

Posts: 27

Participants: 9

Read full topic

@Howen wrote:

Hello guys,

since I have upgraded to version 1.3.0.beta7, I have this error message at the bottom of each topic :

Missing Key: topic.read_more_MF

What can I do to avoid this problem ?

Posts: 1

Participants: 1

Read full topic

@Pesegato wrote:

I post something. Then I edit it. Then I change my mind and want to revert the edit: I think there should be an easy way to do this.

Posts: 3

Participants: 3

Read full topic

@BCHK wrote:

Tried to add a censored word via my ipad today and came across the issue (with about 20 words in our list) that you can'd get / see the check box to approve the updated list, after you've made a change/addition.

Posts: 1

Participants: 1

Read full topic

@downey wrote:

Sorry but I'm on the go and the nature of this problem didn't allow me to do any screenshot.

After selecting 1+ posts with the wrench in a looong topic, I can't then move the post to a new topic, because the blue dialog box is at the very top of the page. When I scroll up, I can't use the dialog because more posts keep loading. As a result I'm constantly "chasing" the dialog.

Posts: 1

Participants: 1

Read full topic

@Del_Boy_Trotter wrote:

How can I change the link on the header logo? I want that to go to our main site so it's consistent with our main site?

The site in question is http://sonatribe.com and our discourse is at http://discourse.sonatribe.com

Posts: 6

Participants: 4

Read full topic

@raul_pareja wrote:

Hi all,

Please I need some help because of the 6to5 gem now renamed as babel, I am aware of the issue already closed here Cannot upgrade from Docker Manager (missing gem) but those changes has not been ported to older versions in git (at least in tags v1.2.0.*)

The thing is I am trying to update from 1.1.3 to the latest one 1.3.0.beta7, so makes sense that next command crashes because misses some database changes done before in the 1.2.0.x versions

    RUBY_GC_MALLOC_LIMIT=90000000 RAILS_ENV=production bundle exec rake db:migrate --trace
    ** Invoke db:migrate (first_time)
    ** Invoke environment (first_time)
    ** Execute environment
    ** Invoke db:load_config (first_time)
    ** Execute db:load_config
    ** Invoke set_locale (first_time)
    ** Execute set_locale
    ** Execute db:migrate
    == 20150325190959 CreateQueuedPosts: migrating ================================
    -- create_table(:queued_posts, {:force=>true})
    rake aborted!
    StandardError: An error has occurred, this and all later migrations canceled:

    PG::UndefinedObject: ERROR:  type "json" does not exist
    LINE 1: ...ger NOT NULL, "raw" text NOT NULL, "post_options" json NOT N...
                                                                 ^
    : CREATE TABLE "queued_posts" ("id" serial primary key, "queue" character varying(255) NOT NULL, "state" integer NOT NULL, "user_id" integer NOT NULL, "raw" text NOT NULL, "post_options" json NOT NULL, "topic_id" integer, "approved_by_id" integer, "approved_at" timestamp, "rejected_by_id" integer, "rejected_at" timestamp, "created_at" timestamp, "updated_at" timestamp) /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.3/lib/patches/db/pg.rb:90:in `exec'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.3/lib/patches/db/pg.rb:90:in `async_exec'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/postgresql/database_statements.rb:128:in `block in execute'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract_adapter.rb:378:in `block in log'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract_adapter.rb:372:in `log'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/postgresql/database_statements.rb:127:in `execute'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/schema_statements.rb:205:in `create_table'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:656:in `block in method_missing'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:628:in `block in say_with_time'
    /home/kingadmin/.rvm/rubies/ruby-2.0.0-p576/lib/ruby/2.0.0/benchmark.rb:281:in `measure'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:628:in `say_with_time'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:648:in `method_missing'
    /fjord/discourse/db/migrate/20150325190959_create_queued_posts.rb:3:in `change'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:602:in `exec_migration'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:586:in `block (2 levels) in migrate'
    /home/kingadmin/.rvm/rubies/ruby-2.0.0-p576/lib/ruby/2.0.0/benchmark.rb:281:in `measure'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:585:in `block in migrate'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/connection_pool.rb:294:in `with_connection'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:584:in `migrate'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:759:in `migrate'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:998:in `block in execute_migration_in_transaction'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:1044:in `block in ddl_transaction'
    /fjord/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'
    /fjord/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'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `transaction'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/transactions.rb:208:in `transaction'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:1044:in `ddl_transaction'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:997:in `execute_migration_in_transaction'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:959:in `block in migrate'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:955:in `each'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:955:in `migrate'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:814:in `up'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:792:in `migrate'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/railties/databases.rake:34:in `block (2 levels) in <top (required)>'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/task.rb:240:in `call'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/task.rb:240:in `block in execute'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/task.rb:235:in `each'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/task.rb:235:in `execute'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/task.rb:179:in `block in invoke_with_call_chain'
    /home/kingadmin/.rvm/rubies/ruby-2.0.0-p576/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/task.rb:172:in `invoke_with_call_chain'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/task.rb:165:in `invoke'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:150:in `invoke_task'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:106:in `block (2 levels) in top_level'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:106:in `each'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:106:in `block in top_level'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:115:in `run_with_threads'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:100:in `top_level'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:78:in `block in run'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:176:in `standard_exception_handling'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:75:in `run'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/bin/rake:33:in `<top (required)>'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/bin/rake:23:in `load'
    /fjord/discourse/vendor/bundle/ruby/2.0.0/bin/rake:23:in `<main>'
    Tasks: TOP => db:migrate

But the, if I **try to update from v 1.1.3 to 1.2.0**, then bundle complains of the missing 6to5 gem

    $ bundle install --without test --deployment
    Fetching gem metadata from https://rubygems.org/.......
    Fetching version metadata from https://rubygems.org/...
    Fetching dependency metadata from https://rubygems.org/..
    Could not find 6to5-source-3.3.7 in any of the sources

I tried to do a dirty workaround, I did the next:

• Delete the Gemfile.lock

• Edit the Gemfile line 110 like this (comment gem 6to5 and add babel
  instead)

  110 #gem '6to5'
  111 gem 'babel'

• Edit the .bundle/config setting BUNDLE_FROZEN: '0' in order to do
  not complain of the version control Gemfile.lock needed

• Launch 'bundle install', in order to have a brand new Gemfile.lock,
  and again bundle install --without test --deployment without any
  prompting error

But then again when trying to update the database the 6to5 dependency appears again:

RUBY_GC_MALLOC_LIMIT=90000000 RAILS_ENV=production bundle exec rake db:migrate --trace
rake aborted!
LoadError: cannot load such file -- 6to5
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:274:in `require'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:274:in `block in require'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:240:in `load_dependency'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:274:in `require'
/fjord/discourse/lib/es6_module_transpiler/tilt/es6_module_transpiler_template.rb:2:in `<top (required)>'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:274:in `require'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:274:in `block in require'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:240:in `load_dependency'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:274:in `require'
/fjord/discourse/lib/es6_module_transpiler/tilt.rb:2:in `<top (required)>'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:274:in `require'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:274:in `block in require'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:240:in `load_dependency'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:274:in `require'
/fjord/discourse/lib/es6_module_transpiler/rails.rb:2:in `<top (required)>'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:274:in `require'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:274:in `block in require'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:240:in `load_dependency'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:274:in `require'
/fjord/discourse/config/application.rb:32:in `<class:Application>'
/fjord/discourse/config/application.rb:19:in `<module:Discourse>'
/fjord/discourse/config/application.rb:18:in `<top (required)>'
/fjord/discourse/Rakefile:5:in `require'
/fjord/discourse/Rakefile:5:in `<top (required)>'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/rake_module.rb:28:in `load'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/rake_module.rb:28:in `load_rakefile'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:689:in `raw_load_rakefile'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:94:in `block in load_rakefile'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:176:in `standard_exception_handling'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:93:in `load_rakefile'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:77:in `block in run'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:176:in `standard_exception_handling'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:75:in `run'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/bin/rake:33:in `<top (required)>'
/fjord/discourse/vendor/bundle/ruby/2.0.0/bin/rake:23:in `load'
/fjord/discourse/vendor/bundle/ruby/2.0.0/bin/rake:23:in `<main>'

So as a summary error shows this: "rake aborted! LoadError: cannot load such file -- 6to5"

I read in the closed topic Cannot upgrade from Docker Manager (missing gem) that the needed changes to substitute 6to5 gem to babel were done already in git ( I am not on Docker) , but maybe not in the older versions?

Please will appreciate really a lot any hint to work around this, so the aim is to do the necessary upgrades to reach latest production version

Many thanks in advance!

Posts: 4

Participants: 3

Read full topic

@henick wrote:

Hi, I seem to have messed up my locales while issuing a silly sed command in a loop and am trying to re-checkout just the locales files from git.

I was able to 'git rm locales* -rf' to delete my borked local copies however when trying to check them back out from the remote side the wild card does not work.

Is there an easy way to pull just the locales from git without having to do them all individually?

Not really urgent, site still runs fine with locales switched off in control panel. Any advice would be appreciated.

Thanks,
Ray

Posts: 1

Participants: 1

Read full topic