@CharlesWil wrote:
This would be a useful plugin for some Followers Plugin
- Certain members you can follow
Posts: 1
Participants: 1
Followers Plugin
↧
↧
But ImageMagick is not installed
@limeblast wrote:
I'm not sure what's changed, but after upgrading to 1.2.0.beta6 over the weekend, I've logged into the admin of my site today and seen this:
The server is configured to create thumbnails of large images, but ImageMagick is not installed. Install ImageMagick using your favorite package manager or download the latest release.
I've never seen this before, and I'm surprised to see it at all, as I figured that things like this was handed by the docker image? Can you help? Thanks.
Posts: 2
Participants: 2
↧
SiteSetting numbers not properly validated
@rcfox wrote:
Entering a large value for some values in the admin settings can cause the settings dashboard to 500 upon reload. As an example, setting embed_post_limit to 999999999999999999999999999999999999999999999999999999999 will be successful, but breaks the settings page.
I was able to set it back to a non-broken value from the Rails repl, but I suspect most people won't know how to do that.
Posts: 8
Participants: 5
↧
Welcome Email has bad links for /staff and /my/preferences
@mrosas wrote:
Hiya Discourse folks,
The welcome email contains links towards the bottom to the following locations (actual URLs in parens)
- your user preferences (/my/preferences)
- trust level (https://meta.discourse.org/t/what-do-user-trust-levels-do/4924)
- civilized community behavior (https://discourse.looker.com/g=
uidelines)- staff members (/about)
Links #2 and #3 work ... but #1 and #4 are relative urls so they aren't working. I'm guessing there is a field in settings somewhere that needs to be filled in, but I can't find it.
Pointers most welcome.
Posts: 7
Participants: 4
↧
Internal server error while loading admin users page
@tyildir wrote:
This happens quite frequently. Only on random occasions do I get to access the admin users page. Below are the screenshots of the two console errors.
Posts: 14
Participants: 3
↧
↧
Internal server error while trying to delete empty categories
@tyildir wrote:
After deleting ALL OTHER subcategories, I was able to delete the four subcategories that gave me the following error when I tried to delete them:
Note that I was able to delete most of the empty subcategories with no problem. "Delete" button was there in each of the cases. In the four problematic cases, nothing seemed to happen when I clicked "Delete". Then I looked at the console and saw the above error.
Posts: 1
Participants: 1
↧
Initial locale setting now available
@riking wrote:
In a sentence: New Docker installs will now have the option to set the language at bootstrap time.
This has been a pain point for a while: the FAQ, Terms of Service, and Privacy policy would get set up with the wrong language. See this topic from July of last year:
Here's one of the support topics that came up: https://meta.discourse.org/t/setting-lang-ru-ru-utf-8-in-app-yml-does-not-work-when-bootstrapping-docker-container/22726
You can do this by setting the
DISCOURSE_DEFAULT_LOCALEenvironment variable inapp.yml. Note that this will make it impossible to change the locale from the web UI.Here's an example of an
app.ymlwith language settings set.params: db_default_text_search_config: "pg_catalog.french" ## Set db_shared_buffers to 1/3 of the memory you wish to allocate to postgres ## on 1GB install set to 128MB on a 4GB instance you may raise to 1GB #db_shared_buffers: "256MB" # ## Which Git revision should this container use? (default: tests-passed) # version: tests-passed env: LANG: fr_FR.UTF-8 DISCOURSE_DEFAULT_LOCALE: frThis will be available in latest right now, beta v1.2.0.beta7, stable v1.2.0.
Posts: 5
Participants: 2
↧
Pull request to simplify deployment and improve relative URL handling
@vadim wrote:
Hello, I've submitted a pull request a little while ago and was wondering if I could get some feedback on it? Thanks!
PR description, for convenience:
This set of changes does two things. They are mostly unrelated but they were essential for us in building our Discourse instance and, I believe, they are generally useful.
Better support for RAILS_RELATIVE_URL: we have fixed numerous places where it wasn't respected.
Running under a a relative URL (domain.com/forum/...) vs subdomain (forum.domain.com) is very useful from the SEO point of view, see, for instance, here.Better support for deployments with external Postgres, Redis and nginx.
The repo contains a Dockerfile which builds an image that includes only Discourse itself. This makes it easier to deploy, e.g., in AWS, using RDS (hosted Postgres) and ElastiCache (hosted Redis). The repo also contains a fig.yml, which helps you use fig to do local development using an equivalent setup (the Vagrant-based setup still works just fine). The fig setup is documented in docs/fig.md.
Posts: 6
Participants: 3
↧
Blueprint thin issue
@erule wrote:
Hello,
Discourse forum worked for quite a while and then some day it broke. I get 502 nginx error - bad gateway.
Below you can see errors from syslog. Please advice how to solve the problem with thin.Feb 9 20:22:48 ip-10-101-16-234 bluepilld[1224]: [discourse:thins:thin-1] Executing start command: bundle exec thin start -e production -t 0 --threaded --no-epoll --socket /var/www/discourse/tmp/sockets/thin.1.sock --pid /var/www/discourse/tmp/pids/thin1.pid --log /var/www/discourse/log/thin-1.log --daemonize Feb 9 20:22:52 ip-10-101-16-234 bluepilld[1224]: [discourse:thins:thin-1] Going from down => starting Feb 9 20:22:53 ip-10-101-16-234 bluepilld[1224]: [discourse:thins:thin-2] pid_file /var/www/discourse/tmp/pids/thin2.pid does not exist or cannot be read Feb 9 20:22:53 ip-10-101-16-234 bluepilld[1224]: [discourse:thins:thin-2] pid_file /var/www/discourse/tmp/pids/thin2.pid does not exist or cannot be read Feb 9 20:22:53 ip-10-101-16-234 bluepilld[1224]: [discourse:thins:thin-2] Failed to signal process with code 0: no implicit conversion from nil to integer Feb 9 20:22:53 ip-10-101-16-234 bluepilld[1224]: [discourse:thins:thin-2] pid_file /var/www/discourse/tmp/pids/thin2.pid does not exist or cannot be read Feb 9 20:22:53 ip-10-101-16-234 bluepilld[1224]: [discourse:thins:thin-2] pid_file /var/www/discourse/tmp/pids/thin2.pid does not exist or cannot be read Feb 9 20:22:53 ip-10-101-16-234 bluepilld[1224]: [discourse:thins:thin-2] Failed to signal process with code 0: no implicit conversion from nil to integer Feb 9 20:22:53 ip-10-101-16-234 bluepilld[1224]: [discourse:thins:thin-2] Going from starting => down Feb 9 20:22:54 ip-10-101-16-234 bluepilld[1224]: [discourse:thins:thin-2] pid_file /var/www/discourse/tmp/pids/thin2.pid does not exist or cannot be read Feb 9 20:22:54 ip-10-101-16-234 bluepilld[1224]: [discourse:thins:thin-2] pid_file /var/www/discourse/tmp/pids/thin2.pid does not exist or cannot be read Feb 9 20:22:54 ip-10-101-16-234 bluepilld[1224]: [discourse:thins:thin-2] Failed to signal process with code 0: no implicit conversion from nil to integer Feb 9 20:22:54 ip-10-101-16-234 bluepilld[1224]: [discourse:thins:thin-2] pid_file /var/www/discourse/tmp/pids/thin2.pid does not exist or cannot be read Feb 9 20:22:54 ip-10-101-16-234 bluepilld[1224]: [discourse:thins:thin-2] pid_file /var/www/discourse/tmp/pids/thin2.pid does not exist or cannot be read Feb 9 20:22:54 ip-10-101-16-234 bluepilld[1224]: [discourse:thins:thin-2] Failed to signal process with code 0: no implicit conversion from nil to integer Feb 9 20:22:54 ip-10-101-16-234 bluepilld[1224]: [discourse] pid journal file: /home/discourse/.bluepill/journals/.bluepill_pids_journal.thin-2 Feb 9 20:22:54 ip-10-101-16-234 bluepilld[1224]: [discourse] No previous process journal - Skipping cleanup Feb 9 20:22:54 ip-10-101-16-234 bluepilld[1224]: [discourse] pgid journal file: /home/discourse/.bluepill/journals/.bluepill_pgids_journal.thin-2 Feb 9 20:22:54 ip-10-101-16-234 bluepilld[1224]: [discourse] No previous process journal - Skipping cleanup Feb 9 20:22:54 ip-10-101-16-234 bluepilld[1224]: [discourse:thins:thin-2] Executing start command: bundle exec thin start -e production -t 0 --threaded --no-epoll --socket /var/www/discourse/tmp/sockets/thin.2.sock --pid /var/www/discourse/tmp/pids/thin2.pid --log /var/www/discourse/log/thin-2.log --daemonize
Posts: 4
Participants: 3
↧
↧
Low memory / ImageMagicK / White pages
@DeanMarkTaylor wrote:
I like many existing users I have been experiencing a combination of these issues:
- Low memory errors
- ImageMagicK message in admin panel.
![]()
- White pages / instability
This post / topic is a dump of available information before I restart the instance - so it might help track down the problem.
System
2GB Digital Ocean instance with 2GB Swap - single site running in Docker.
History
Earlier this week I restarted my Discourse instance using
./launcher restart appto resolve my then availability issues.Current version:
Discourse 1.2.0.beta6 - https://github.com/discourse/discourse version 8689c85b54efccbccfa216c800522e5ba1a79dd1Possible related reports
These are only noted here for there similarity and may not be the the same issue!
Digital Ocean graphs
Pingdom uptime graphs
![]()
Still collecting information and will continue to post in this thread.
Posts: 36
Participants: 4
↧
Ubuntu updates intefere with Docker and AUFS?
@codinghorror wrote:
This was going fine for me until the last moment, when I got the following super-useful error message:
Error response from daemon: Cannot destroy container 1cd705ffc49f5ce0622614316e3a742b8e6c8a77362528338db30a6f352477d2: Driver devicemapper failed to remove root filesystem 1cd705ffc49f5ce0622614316e3a742b8e6c8a77362528338db30a6f352477d2: Device is Busy FATA[0014] Error: failed to remove one or more containers Invalid cid file, deleting, please re-run
- How to recover?
- How to make this more reliable and easier for users/admins?
Posts: 10
Participants: 4
↧
Docker manager not installing?
@riking wrote:
I'm having the same problem. I just attempted to do a backup/restore to fix the problem, but after restoring, the /admin/upgrade page is still gone!
My backup was on version 1.2.0beta5, and when I restored (from beta6) it reports my current version as 1.2.0beta5 again. But the /admin/upgrade page is still gone. I tried what @sam said and although it completed "successfully" but I still don't have an /upgrade page and I'm still on beta5.
I originally ran into this problem while mucking about the container files, trying to setup multi-site. But my container files should be pristine now, I edited just what I needed to from the "sample" directory.
Posts: 3
Participants: 2
↧
URL parameter to force mobile theme?
@JSey wrote:
Hi all,
I'm not really sure where to dig for this one, so I'll just post it along: is there any parameter to force Discourse into displaying the mobile view? Like http://www.example.com?mobile=1?
Posts: 7
Participants: 4
↧
↧
Ban symbol next to suspended usernames
@AdamCapriola wrote:
I suspended a user today and one of my mods pointed out that it wasn't so obvious the user had been suspended. I was thinking that like how moderators get the shield next to their username, maybe suspended users should get the banned symbol? That way other members would realize the user is suspended and not currently active in conversation.
I could see an argument for not wanting to draw attention to suspended users though ... any thoughts?
Posts: 4
Participants: 4
↧
"New Topic" submission button in the form should use a verb instead
@JAW_dropping wrote:
This is a minor annoyance that I'd spotted when using Discourse for the first time but it's one of those things that add up as they're on the critical UX path.
I think verbs are pretty much the only way to go for buttons that actually perform an action. It seems to already be the case for most UI elements in Discourse but not that particular button.
"Submit" would work well but also "Create".
Thanks!
Posts: 4
Participants: 3
↧
When mention group, explode list in alphabetical order
@tobiaseigen wrote:
Fairly low priority item but something that I'd like to see happen nonetheless.
When you mention a discourse group and it "explodes" the list of people in that group, it appears to be listing them in order the user joined up. It would be easier to look at the resulting list if in alphabetical order, esp for longer lists.
Posts: 1
Participants: 1
↧
Privacy Policy, TOS
@godmoneytrust wrote:
I know how to edit the TOS and Privacy Policy and FAQ. But where do they show up in the system. I see the FAQ in the hamburger menu but I don't see the TOS or Privacy Policy anywhere else on the discourse forum.
Posts: 2
Participants: 2
↧
↧
Search sometimes tokenizes unique user names and some times does not
@peternlewis wrote:
As with Topic search doesn’t search for user names, regular search should include usernames.
For example, if I want to search for a topic on clipboards that a specific person posted in (say me for example), I want to be able to search the site for:
clipboard peternlewisyet this finds nothing generally. For example on my site I can find the post Paste Color Data with a search for:
paste color databut not with
paste color data peternlewisI'm getting complains from my users that they can't find posts or replies by specific people.
Posts: 17
Participants: 7
↧
Installing Discourse on Centos/WHM
@RupGautam wrote:
I've reinstalled ruby and all the gems. I cloned a clean copy of the files into the folder and still get the same error on:
bundle exec rspecThe rspec gems installed without error so the problem doesn't appear to be there.The complete error is below.
At this point I've exhausted all server side issues I can think of and have to believe there is an issue with the build files that is looking for fakeweb in some other location than where it is within the install. It doesn't matter if we specify the file directly, it still looks in the wrong location and can't find it.
/home/domain/public_html/support/spec/spec_helper.rb:12:in `require': cannot load such file -- fakeweb (LoadError) from /home/domain/public_html/support/spec/spec_helper.rb:12:in `<top (required)>' from /home/domain/public_html/support/spec/components/admin_user_index_query_spec.rb:1:in `require' from /home/domain/public_html/support/spec/components/admin_user_index_query_spec.rb:1:in `<top (required)>' from /home/domain/public_html/support/vendor/bundle/ruby/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/configuration.rb:1065:in `load' from /home/domain/public_html/support/vendor/bundle/ruby/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/configuration.rb:1065:in `block in load_spec_files' from /home/domain/public_html/support/vendor/bundle/ruby/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/configuration.rb:1065:in `each' from /home/domain/public_html/support/vendor/bundle/ruby/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/configuration.rb:1065:in `load_spec_files' from /home/domain/public_html/support/vendor/bundle/ruby/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/command_line.rb:18:in `run' from /home/domain/public_html/support/vendor/bundle/ruby/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/runner.rb:103:in `run' from /home/domain/public_html/support/vendor/bundle/ruby/2.0.0/gems/rspec-core-2.99.2/lib/rspec/core/runner.rb:17:in `block in autorun'Please suggest.
Thank you
Posts: 9
Participants: 4
↧
Welcome Topic Can't be Pinned
@mrosas wrote:
Hi --
My Welcome Topic is unpinned and I don't have any options to pin it in the admin dropdown.
![]()
Searching for similar problems here but not finding this exact problem. Pointers so very welcome ...
Thanks, Margaret
Posts: 7
Participants: 2
↧
More Pages to Explore .....
