Kane York wrote:
Repro:
Custom CSS:
@import "theme_variables"; body { background-color: $success; }
- Save this custom CSS, ensure that you see it.
- Change the
$successvariable and save the color scheme- All the UI except for the body background updates
Workaround
- Go to the custom CSS, add a space, and save
Posts: 1
Participants: 1
Bob McNeel wrote:
I can pin a topic but if there is more than one pinned, the order gets rearranged. I'd like to always keep the Welcome topic above other important announcements that I want to keep near the top for awhile.
Posts: 5
Participants: 2
William Gross wrote:
A few weeks ago I stopped receiving email notifications from community.enterpriseweblibrary.org even though I continue to have the "Receive an email every time a post is made on the forum" box checked. Other users have created several new topics recently and I haven't been notified. Furthermore, I've checked out the Mandrill account that Discourse should be using to send mail, and nothing has been sent through it in more than a week. Anyone know what could be happening here?
Posts: 1
Participants: 1
Volkan Unsal wrote:
I have been trying to make an API request through the Discourse gem, but it keeps returning
[error: 'invalid access']
I checked everything. My API key is correct and so is the username. I don't see anything in the logs.
Posts: 2
Participants: 2
Theron Boerner wrote:
If you use the autocomplete, it grays out the invite button. If you type in the full username, it works fine.
Posts: 3
Participants: 2
Ying Long wrote:
Or Tumblr no longer support open graph?
Onebox won't show url like this
http://deviantart.tumblr.com/I remember it was supported. Or I remembered it wrong?
Posts: 1
Participants: 1
Michael wrote:
lib/email/message_builder.rbuses the forum'sSiteSettingtitleas the email sender.def site_alias_email(source) "#{SiteSetting.title} <#{source}>" endWe have some customers using characters in the title that are not allowed per RFC2821/RFC2822, causing the email to be rejected by Mandrill.
Also, some users use 'Welcome to XYZ community' as a forum title, causing email digests to be sent out with the sender 'Welcome to XYZ community digest', where 'XYZ community digest' would make more sense.
How about making a separate site setting for the
titlewhen used as an email sender in conjunction withnotification_email?
Posts: 3
Participants: 2
Michael wrote:
When working on https://meta.discourse.org/t/title-being-used-in-digest/16943 we noticed that two other users on the same multisite host reported that email delivery was having issues. It turns out that they were able to see emails belonging to another forum in their Sidekiq "Retries" overview.
Posts: 5
Participants: 4
Tuan Anh Tran wrote:
Is it possible to setup a category's topic titles to be viewable by everyone but when clicking on it, permission require msg will show to those doesnt have permission?
I want this as a way to tease non-permitted users.
Posts: 3
Participants: 2
John Reid wrote:
Title says it all.
The last Discourse update managed to break the previous fix to the BlackBerry 10 browser problem caused by a bug with localstorage:
QuotaExceededError: DOM Exception 22: An attempt was made to add something to storage that exceeded the quota. application-e0d3659e604e1958f1c1c3d33ed50623.js:6Also, the last update reset the Lounge permissions to trust level 3 and removed the custom permissions that I set. I've put the permissions back but thought I'd bring it up here.
Posts: 4
Participants: 3
Tuan Anh Tran wrote:
Add download attachment as one of permission aside create/view and reply
Posts: 2
Participants: 2
Sander Datema wrote:
When pressing the three dots I'd like the extra buttons to appear right there instead of mixed with the rest of the icons.
![]()
Posts: 1
Participants: 1
John Reid wrote:
After you create a new category, the category should load.
BUT the page is redirected and the new category doesn't load. You just have a blank page instead.
Sadness ensues.
Haiku ends.
Posts: 1
Participants: 1
Lee_Ars wrote:
Since around the time I updated to 0.9.9.10, I've been seeing a warning in the admin dashboard that the upgrade check isn't being run and sidekiq might not be running. When I check
/sidekiq, everything appears normal:
![]()
There doesn't appear to be anything funky in
/logs, either (though I am getting LOTS of csrf spoof attacks):There are definitely sidekiq processes running, though. In fact, sidekiq is taking up 100% of one CPU core. I went ahead and bounced the server, and since reboot, it's still been sitting at 100%:
![]()
What can I do to wrangle sidekiq back down to normalcy?
Posts: 14
Participants: 4
bubill wrote:
Continuing the discussion from [How to Fix ]Cannot connect to the Docker daemon. Is 'docker -d' running on this host?:
Session 1:
root@AY1:/var/docker# service docker stop stop: Unknown instance: root@AY140222173108710dc0Z:/var/docker# docker -d 2014/06/29 01:33:22 WARNING: You are running linux kernel version 3.2.0-64-generic, which might be unstable running docker. Please upgrade your kernel to 3.8.0. 2014/06/29 01:33:22 docker daemon: 1.0.1 990021a; execdriver: native; graphdriver: [ce3a4985] +job serveapi(unix:///var/run/docker.sock) [ce3a4985] +job initserver() [ce3a4985.initserver()] Creating server 2014/06/29 01:33:22 Listening for HTTP on unix (/var/run/docker.sock) [ce3a4985] +job init_networkdriver() [ce3a4985.init_networkdriver()] creating new bridge for docker0 Could not find a free IP address range for interface 'docker0'. Please configure its address manually and run 'docker -b docker0' [ce3a4985] -job init_networkdriver() = ERR (1) Could not find a free IP address range for interface 'docker0'. Please configure its address manually and run 'docker -b docker0' [ce3a4985] -job initserver() = ERR (1) 2014/06/29 01:33:22 Could not find a free IP address range for interface 'docker0'. Please configure its address manually and run 'docker -b docker0' root@AY140222173108710dc0Z:/var/docker# service docker start docker start/running, process 18105 root@AY140222173108710dc0Z:/var/docker# service docker stop stop: Unknown instance: root@AY140222173108710dc0Z:/var/docker# docker -d 2014/06/29 01:34:04 WARNING: You are running linux kernel version 3.2.0-64-generic, which might be unstable running docker. Please upgrade your kernel to 3.8.0. 2014/06/29 01:34:04 docker daemon: 1.0.1 990021a; execdriver: native; graphdriver: [585cf499] +job serveapi(unix:///var/run/docker.sock) [585cf499] +job initserver() [585cf499.initserver()] Creating server 2014/06/29 01:34:04 Listening for HTTP on unix (/var/run/docker.sock) [585cf499] +job init_networkdriver() [585cf499.init_networkdriver()] creating new bridge for docker0 Could not find a free IP address range for interface 'docker0'. Please configure its address manually and run 'docker -b docker0' [585cf499] -job init_networkdriver() = ERR (1) Could not find a free IP address range for interface 'docker0'. Please configure its address manually and run 'docker -b docker0' [585cf499] -job initserver() = ERR (1) 2014/06/29 01:34:04 Could not find a free IP address range for interface 'docker0'. Please configure its address manually and run 'docker -b docker0' root@AY1:/var/docker#Session 2:
root@AY1:/var/docker# ./launcher bootstrap app 2014/06/29 01:35:42 Cannot connect to the Docker daemon. Is 'docker -d' running on this host? Cannot connect to the docker daemon - verify it is running and you have access root@AY1:/var/docker#
Posts: 5
Participants: 5
Theron Boerner wrote:
Say a user posts something like
I love this idea. I think it would be great to see.
I don't want that user to be punished by affecting his/her flag count but I want to be able to easily give the user an infraction saying please use the heart instead of responding. I've gotten stuff like this a few times on other forums from mods with similar things like "post in a different section for that".
Maybe just have a "minor" flag level for things like this?
Posts: 5
Participants: 3
Theron Boerner wrote:
I think we should be able to see this on our user profile. It's nice to see what more we have to do.
Posts: 2
Participants: 2
Volkan Unsal wrote:
I have tried to use the following commands to get to the console, but I am encountering a lot of errors when I run the command. Here is the input:
docker run -i -t local_discourse/app:latest bash cd /var/www/discourse/ RAILS_ENV=production bundle exec rails cAnd here is the shortened output:
root@d19b0a20422c:/var/www/discourse# RAILS_ENV=production bundle exec rails c Rails Error: Unable to access log file. Please ensure that /var/www/discourse/log/production.log exists and is chmod 0666. The log level has been raised to WARN and the output directed to STDERR until the problem is fixed. Error connecting to Redis on localhost:6379 (ECONNREFUSED) subscribe failed, reconnecting in 1 second. Call stack [ Error connecting to Redis on localhost:6379 (ECONNREFUSED) subscribe failed, reconnecting in 1 second. Call stack [ Error connecting to Redis on localhost:6379 (ECONNREFUSED) subscribe failed, reconnecting in 1 second. Call stack [ /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/connection_adapters/postgresql_adapter.rb:881:in `initialize': could not connect to server: No such file or directory (PG::Error) Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"? root@d19b0a20422c:/var/www/discourse#
Posts: 5
Participants: 4
Justin Gordon wrote:
I was showing a friend how to sign up for TalkSurf.com on his iPhone. He used a name, email, and password. Afterwards, he was not signed in and there was no mention that he had to confirm his email. He suggested we should display an alert.
Posts: 1
Participants: 1
bubill wrote:
My cloud provider aliyun.com can NOT support Docker .
here is error:：root@AY1:/var/docker# service docker stop stop: Unknown instance: root@AY140222173108710dc0Z:/var/docker# docker -d 2014/06/29 01:33:22 WARNING: You are running linux kernel version 3.2.0-64-generic, which might be unstable running docker. Please upgrade your kernel to 3.8.0. 2014/06/29 01:33:22 docker daemon: 1.0.1 990021a; execdriver: native; graphdriver: [ce3a4985] +job serveapi(unix:///var/run/docker.sock) [ce3a4985] +job initserver() [ce3a4985.initserver()] Creating server 2014/06/29 01:33:22 Listening for HTTP on unix (/var/run/docker.sock) [ce3a4985] +job init_networkdriver() [ce3a4985.init_networkdriver()] creating new bridge for docker0 Could not find a free IP address range for interface 'docker0'. Please configure its address manually and run 'docker -b docker0' [ce3a4985] -job init_networkdriver() = ERR (1) Could not find a free IP address range for interface 'docker0'. Please configure its address manually and run 'docker -b docker0' [ce3a4985] -job initserver() = ERR (1) 2014/06/29 01:33:22 Could not find a free IP address range for interface 'docker0'. Please configure its address manually and run 'docker -b docker0' root@AY140222173108710dc0Z:/var/docker# service docker start docker start/running, process 18105 root@AY140222173108710dc0Z:/var/docker# service docker stop stop: Unknown instance: root@AY140222173108710dc0Z:/var/docker# docker -d 2014/06/29 01:34:04 WARNING: You are running linux kernel version 3.2.0-64-generic, which might be unstable running docker. Please upgrade your kernel to 3.8.0. 2014/06/29 01:34:04 docker daemon: 1.0.1 990021a; execdriver: native; graphdriver: [585cf499] +job serveapi(unix:///var/run/docker.sock) [585cf499] +job initserver() [585cf499.initserver()] Creating server 2014/06/29 01:34:04 Listening for HTTP on unix (/var/run/docker.sock) [585cf499] +job init_networkdriver() [585cf499.init_networkdriver()] creating new bridge for docker0 Could not find a free IP address range for interface 'docker0'. Please configure its address manually and run 'docker -b docker0' [585cf499] -job init_networkdriver() = ERR (1) Could not find a free IP address range for interface 'docker0'. Please configure its address manually and run 'docker -b docker0' [585cf499] -job initserver() = ERR (1) 2014/06/29 01:34:04 Could not find a free IP address range for interface 'docker0'. Please configure its address manually and run 'docker -b docker0' root@AY1:/var/docker# ：[585cf499] -job init_networkdriver() = ERR (1) Could not find a free IP address range for interface 'docker0'. Please configure its address manually and run 'docker -b docker0'
Posts: 3
Participants: 2
