@rlauriston wrote:

One of my users on foodtalkcentral.com is complaining about not getting alerts. Someone sends a message or posts a reply and there's no blue dot on the profile avatar.

Posts: 15

Participants: 5

Read full topic

@Callahan wrote:

Hello!
I'm a bit confused on what setting I might've changed to cause this. I set up sso last night which ended up working pretty nicely, props to that : ) I signed someone up and they said they weren't able to upload their avatar, I tried it myself and low and behold there's no option to upload avatar anymore. Allow uploaded user avatars is on and sso overrides avatar is off. Any idea?

Posts: 5

Participants: 3

Read full topic

@fearlessfrog wrote:

Discourse version: Lastest, as of v1.7.0.beta6 +1, tests-passed branch

Sidekiq retries (count - 6):

default
Jobs::UserEmail
{"type"=>"mailing_list", "user_id"=>43, "current_site_id"=>"default"}
Jobs::HandledExceptionWrapper: Wrapped ArgumentError: bad argument (expected URI object or URI string)

Logs (count 7):

/usr/local/lib/ruby/2.3.0/uri/common.rb:716:in `URI'
/var/www/discourse/lib/email/styles.rb:132:in `block in onebox_styles'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.6.8.1/lib/nokogiri/xml/node_set.rb:187:in `block in each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.6.8.1/lib/nokogiri/xml/node_set.rb:186:in `upto'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/nokogiri-1.6.8.1/lib/nokogiri/xml/node_set.rb:186:in `each'
/var/www/discourse/lib/email/styles.rb:130:in `onebox_styles'
/var/www/discourse/lib/email/styles.rb:101:in `format_notification'
/var/www/discourse/app/mailers/user_notifications.rb:433:in `block in apply_notification_styles'
/var/www/discourse/app/mailers/user_notifications.rb:431:in `tap'
/var/www/discourse/app/mailers/user_notifications.rb:431:in `apply_notification_styles'
/var/www/discourse/app/mailers/user_notifications.rb:93:in `mailing_list'
/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/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: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_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/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/actionmailer-4.2.7.1/lib/action_mailer/base.rb:596:in `block in process'
/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/actionmailer-4.2.7.1/lib/action_mailer/base.rb:593:in `process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionmailer-4.2.7.1/lib/action_mailer/base.rb:584:in `initialize'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionmailer-4.2.7.1/lib/action_mailer/message_delivery.rb:25:in `new'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionmailer-4.2.7.1/lib/action_mailer/message_delivery.rb:25:in `__getobj__'
/usr/local/lib/ruby/2.3.0/delegate.rb:80:in `method_missing'
/var/www/discourse/lib/email/sender.rb:30:in `send'
/var/www/discourse/app/jobs/regular/user_email.rb:41:in `execute'
/var/www/discourse/app/jobs/base.rb:154:in `block (2 levels) in perform'

Just started happening today, so thought I'd report it.

Plugins installed:

babble	1.1.0
discourse-cakeday	0.0.13
discourse-details	0.4
dice_roller	2
discourse-nginx-performance-report	0.1
Spoiler Alert!	0.3
docker_manager	0.1
lazyYT	1.0.1
poll	0.9
Steam Store Widget Onebox	0.2

Posts: 5

Participants: 3

Read full topic

@ItsGhost wrote:

When using the automated upgrade from /admin/upgrade I'm getting an error relating to "Javascript was terminated" whilst a rake task was executing. Sadly I can't find the actual log file and everything claims to have updated. This has happened a few times and I'm just wondering what on earth is going on.

Posts: 14

Participants: 5

Read full topic

@JMichaelTX wrote:

My apologies if this has been asked/answered, but I done extensive searching here and elsewhere, and cannot find an answer.

How Do I Keep/Show Notifications Online, but Do NOT Get EMail Notification?

Here is topic that had promise, but it was closed without a full understanding/description of the Notification feature:

If I am "Watching" a Topic, I want to:

• See online Notifications for all posts (except mine).
• NOT receive the corresponding email notification for these.

By "onine Notifications", I mean the views provided by:

• The "User Menu" (clicking on my avatar in top right, or pressing "p")
• The Notifications page: https://meta.discourse.org/users/<UserName>/notifications

IOW, I want to manage my Notifications, new posts, using the online tools, but I do NOT want to receive any email about them.

The exception to email notification, would be if I have checked any of the following in my Preferences:

Can anyone explain how to do this?

If it can not be done, please consider this a feature request.

Thanks.

Posts: 2

Participants: 2

Read full topic

@Silvanus wrote:

I did following:

• split messages from topic a to topic b
• split earlier messages
• now topic b has two sets of messages, first set written later than the next set

Any way to reorder without splitting again?

Posts: 1

Participants: 1

Read full topic

@JamesNorth wrote:

The awesome new change that @sam committed for the mobile scroll bar works great.

I have found though that if you are a right-hander using the interface, you can't see the text pertaining to the date or post number that you are trying to scroll to because your thumb/finger/hand covers it.

Perhaps those numbers could be underneath, or even floating somewhere else in that overlay?

IMG_2543.PNG1242x2208 131 KB

Posts: 7

Participants: 2

Read full topic

@dfabulich wrote:

Our forum has a lot of threads with a large number of posts. For example:

https://forum.choiceofgames.com/t/guns-of-infinity/2656/32265 33k posts
https://forum.choiceofgames.com/t/children-of-the-gods-update-post-8217/15482 9k posts
https://forum.choiceofgames.com/t/guenevere-wip/1996 8k posts

On threads that large, there's no way to use the vertical scroll bar to select an individual post by number. Moving the scroll bar even a single pixel moves the cursor by a large number of posts.

On desktop browsers, we can use the # shortcut key to select a particular post, which is kinda manageable but undiscoverable.

But now that the vertical scroll bar is used on mobile, there's now no way at all to select a particular post in a large thread on mobile. This is bad.

Posts: 3

Participants: 3

Read full topic

@mmuyskens wrote:

What's a good method to purge a dev install before going live - essentially, getting it ready for the final import. (aka killing all users, posts, pm's, etc.)

Posts: 1

Participants: 1

Read full topic

@meglio wrote:

The screenshot below should be self-explanatory:

Pasted image1329x1014 129 KB

Not sure if it is expected behavior or a bug, but to me look more like an UX issue.

Posts: 3

Participants: 2

Read full topic

@dirk.jahnke wrote:

In the skipped emails listing I find entries like:
[Sender] 501 : domain missing or malformed

It was right, the domain was really missing. But I was surprised, that in the user settings it says, that there are 0 mails that could not be delivered. It seems like "skipped mails" are not counted, which, from the user's perspective, I would not expect.

Posts: 1

Participants: 1

Read full topic

@dirk.jahnke wrote:

In the admin interface I got pointed to mail processing errors, which are in fact two entries of a "Job exception: 451 Error while writing spool file".

Do you have some more infos about this for me? With ~4000 mails sent yesterday, these 2 errors seem to be not that serious. Nevertheless, I ask myself for possible reasons. Out of disk space? At least locally that is unlikely. What else?

Thanks,
Dirk

This is the log entry:

Message

Job exception: 451 Error while writing spool file

Backtrace

/usr/local/lib/ruby/2.3.0/net/smtp.rb:965:in `check_response'
/usr/local/lib/ruby/2.3.0/net/smtp.rb:919:in `data'
/usr/local/lib/ruby/2.3.0/net/smtp.rb:664:in `block in send_message'
/usr/local/lib/ruby/2.3.0/net/smtp.rb:859:in `rcptto_list'
/usr/local/lib/ruby/2.3.0/net/smtp.rb:664:in `send_message'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/mail-2.6.4/lib/mail/network/delivery_methods/smtp.rb:114:in `block in deliver!'
/usr/local/lib/ruby/2.3.0/net/smtp.rb:522:in `start'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/mail-2.6.4/lib/mail/network/delivery_methods/smtp.rb:113:in `deliver!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/mail-2.6.4/lib/mail/message.rb:2149:in `do_delivery'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/mail-2.6.4/lib/mail/message.rb:237:in `block in deliver'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionmailer-4.2.7.1/lib/action_mailer/base.rb:543:in `block in deliver_mail'
/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/actionmailer-4.2.7.1/lib/action_mailer/base.rb:541:in `deliver_mail'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/mail-2.6.4/lib/mail/message.rb:237:in `deliver'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionmailer-4.2.7.1/lib/action_mailer/message_delivery.rb:85:in `deliver_now'
/var/www/discourse/lib/email/sender.rb:155:in `send'
/var/www/discourse/app/jobs/regular/user_email.rb:41:in `execute'
/var/www/discourse/app/jobs/base.rb:154:in `block (2 levels) in perform'

Env

hostname	forum-app
process_id	187
application_version	2a9331d061423f2b04d63ad7407f90fa6fd104cd
current_db	default
current_hostname	forum.fremo-net.eu
job	Jobs::UserEmail
problem_db	default
opts
type	user_posted
user_id	79
notification_id	52774
notification_type	posted
post_id	3322
current_site_id	default
notification_data_hash
topic_title	Reisende in "Fensterwagen" oder nicht?
original_post_id	3322
original_post_type	1
original_username	anonymized
display_username	anonymized
Solve  Protect Share

Posts: 1

Participants: 1

Read full topic

@code_4good wrote:

Hello Team,

I am new to discourse dev, actually i wanted to implement per topic permissions ( which is not supported yet) so I started hacking and was able to able to do it by manipulating the database directly. So i wanted to know if there can be any implications to this approach ? ( P.S I am using my customized repo which is based on the latest version as of now, so getting future updates will not be required)

Posts: 5

Participants: 3

Read full topic

@Mario120 wrote:

Which serwer from digitalocean should I choose for new forum (3000 users)?

Posts: 2

Participants: 2

Read full topic

@tobiaseigen wrote:

We're introducing a group of people in East Africa to our discourse as part of a learning exchange, and I have to say discourse has been holding up well! Even on slow 2g connections I am able to keep up on discourse and manage topics and users etc. I'm even doing an upgrade right now.

One area where we seem to have trouble, however, is with uploading pictures. Some participants have been trying to upload one or more pictures at a time and the composer then takes a long time to upload the files. Often no more than one or none of the pictures are uploaded successfully and the word "Uploading..." remains in the saved topic instead of the picture.

I'm not sure there's any easy solution to this and I know we are not the main clientele for discourse. But, at the least, it seems to me the error handling should be more robust. Instead of failing silently it should display an error with some advice on what to do in slow internet connection situations.

Another alternative that would be nice would be the ability on the upload interface to resize the file to be uploaded locally on the device before uploading.

Our biggest competition here is WhatsApp - everyone is on it and even uses it to set up ad hoc groups to coordinate activities. They understand the benefit of discourse for engaging with a larger network but are using WhatsApp for logistics and sharing pictures with each other instead of discourse because it "just works" while discourse is error prone on slow connections.

Update: everyone in our group uses android phones, btw, and I am talking here about tribulations with uploading pictures using android.

Posts: 2

Participants: 2

Read full topic

@precessor wrote:

How about an "apply Christmas hat" option for Admins!
Could affect each user's avatar in top-right of page only, or perhaps certain users by a list

Posts: 4

Participants: 3

Read full topic

@hellekin wrote:

Hi,

Typing u on the keyboard used to bring to the Unread page. But recently (a matter of weeks) u stopped going there and instead started going back (including to external sites!). It's not clear how the thing is mis-behaving, but it definitely breaks the workflow of u + j + o to fast-track movement across the board.

Posts: 4

Participants: 2

Read full topic

@pacharanero wrote:

(This is not really a bug with Discourse itself, it's just an oddity of the interaction between LastPass and Discourse. Hence if it's felt that this post should be in a different section of Meta, please feel free to tell me and I'll move it.)

Problem:
For some months now I've had an intermittent issue with logging into some of my Discourse instances using LastPass. On trying to log in via the normal GUI login dialog I would occasionally get an error/exception response ['BAD CSRF'], which didn't necessarily happen every time, and didn't happen with all users (I usually have several user accounts for each of my instances and can test with various accounts). The problem has persisted over several versions of Discourse and didn't seem to suddenly 'appear' after an update.

On logging into Discourse, with LastPass filling in my credentials and AutoLogin enabled, I would get this error persistently:

I think that this is being caused by the AutoLogin feature of LastPass - this feature fills in the login credentials in the login dialog, and automatically 'clicks' the Log In button. It's intended function is to make logging into sites more-or-less a 'one-click' operation.

I know next to nothing about CSRF except what I've just been googling about it - but possibly the absence of a delay between LastPass entering the credentials and clicking the 'Log In' button might be triggering the CSRF prevention mechanism in Rails? Somehow the CSRF prevention token is not getting sent to the server. Or maybe the absence of any delay makes Rails flag this as a possible automated login attempt (eg a login CSRF attack mediated via a malicious link). I dunno.

Selection_2996f.png1411x1294 83.5 KB

Solution: If the AutoLogin feature is disabled, LastPass will fill in the credentials but doesn't automatically 'click' the Log In button. You click it manually, and login proceeds as normal. To disable the feature, edit the site in your LastPass vault, and ensure that the AutoLogin flag is unchecked / unticked.

I thought I'd share this observation here in case anyone else in the community is having a similar problem, as there was nothing already that I could find on Meta (or anywhere else) relating to ['BAD CSRF']s on login using the GUI. (All I could find was ['BAD CSRF'] issues when using the API.)

Marcus

Posts: 1

Participants: 1

Read full topic

@RobMeade wrote:

Hi,

I am a moderator on one of the hosted sites and I am trying to get a wiki set up in place for collating useful posts from the community.

Having just stated to them all that they can also use in:wiki #category, where #category is the name of the specific category in question, I found that the wiki in question was not returned. This is due to it being in a sub-category.

My question is therefore, is it possible to add anything to this search query to search specifically within a sub-category, for example in:wiki #category +#sub-category or something similar?

I have seen someone else post on here back in March asking a very similar question, but it doesn't appear to have had a solution added, so I'm not sure whether perhaps this has been addressed or not, and despite looking through the How To Tutorials I wasn't able to find anything specific.

Any help would be gratefully received, as at the moment, the only solution I can think of is to move the wiki topic back up a level in the hierarchy to the #category, but I really don't want to have to do that.

Update

Ironically, whilst responding to one of the users I was trying to work this out for I stumbled across the answer!!

It would seem:

in:wiki #category:sub-category

works perfectly! Thank you and sorry for the inconvenience!

Posts: 2

Participants: 1

Read full topic

@RobMeade wrote:

Hi,

I have noticed that when you mark posts as solved, you can only do this on the comments to an original topic post, not on the first post itself.

I have seen situations where a user may posted a question, only to end up finding the answer themselves, but then updating the same initial topic post with the details of the answer (for everyone else's benefit) - there is no way currently to mark that original topic post as the solution - other than the standard [Solved] prefix.

I have actually just done the exact thing myself on a different topic, which is what reminded me of it.

Would this have any merit for a future feature?

Posts: 8

Participants: 4

Read full topic