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

Userlist not working

$
0
0

@Lutz wrote:

If you open the hamburger-menu, and select "Users", the list shows up and everything ist is working.
If you change the period to "all" (in german: "Gesamt"), the loading animation is spinning for ever.

v1.7.0.beta11 +105
URL: https://www.[myforum].com/users?period=all

Logs:

NoMethodError (undefined method `time_read' for nil:NilClass)
/var/www/discourse/app/serializers/directory_item_serializer.rb:14:in `time_read'



/var/www/discourse/app/serializers/directory_item_serializer.rb:14:in `time_read'
(eval):4:in `_fast_attributes'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:467:in `rescue in attributes'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:455:in `attributes'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:479:in `_serializable_hash'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:361:in `serializable_hash'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/active_model_serializers-0.8.3/lib/active_model/array_serializer.rb:89:in `block in _serializable_array'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/active_model_serializers-0.8.3/lib/active_model/array_serializer.rb:79:in `map'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/active_model_serializers-0.8.3/lib/active_model/array_serializer.rb:79:in `_serializable_array'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/active_model_serializers-0.8.3/lib/active_model/array_serializer.rb:73:in `serializable_array'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/active_model_serializers-0.8.3/lib/active_model/array_serializer.rb:53:in `as_json'
/var/www/discourse/app/controllers/application_controller.rb:294:in `serialize_data'
/var/www/discourse/app/controllers/directory_items_controller.rb:66:in `index'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/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/action_controller/metal/rendering.rb:10: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:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:92: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/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/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/actionpack-4.2.7.1/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/railties/controller_runtime.rb:18: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/rack-mini-profiler-0.10.1/lib/mini_profiler/profiling_methods.rb:102:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal.rb:237:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/route_set.rb:43:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:43:in `block in serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:30:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:30:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/route_set.rb:817:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/builder.rb:63:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/conditionalget.rb:25:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/head.rb:13:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:138:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/flash.rb:260:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/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_call_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/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.5/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/rack/logger.rb:22:in `call'
/var/www/discourse/config/initializers/100-quiet_logger.rb:13:in `call_with_quiet_assets'
/var/www/discourse/config/initializers/100-silence_logger.rb:26:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/methodoverride.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/runtime.rb:18:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/sendfile.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/mini_profiler/profiler.rb:278:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus/rack/middleware.rb:62:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:73:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/engine.rb:518:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/application.rb:165:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/urlmap.rb:66:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:562:in `process_client'
/var/www/discourse/lib/scheduler/defer.rb:85:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:658:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:508:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:132:in `start'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:22:in `load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:22:in `<main>'

hostname	dragon-app
process_id	675
application_version	1b92d44fb2ecf08948337871da9a3eaa40255cbc
HTTP_HOST	www.[myforum].com
REQUEST_URI	/directory_items?period=all&order=likes_received&_=1483726748445
REQUEST_METHOD	GET
HTTP_USER_AGENT	Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36
HTTP_ACCEPT	application/json, text/javascript, */*; q=0.01
HTTP_REFERER	https://www.[myforum].com/users?period=all
HTTP_X_FORWARDED_FOR	178.202.82.52, 178.202.82.52
HTTP_X_REAL_IP	178.202.82.52
username	[me]
params
period	all
order	likes_received
_	1483726748445

Posts: 9

Participants: 4

Read full topic


Moderators should not be able to access customizations

$
0
0

@barreeeiroo wrote:

Hi there :wave:

I've discovered a security problem in Discourse related to moderators:
There are some restricted zones for moderators in Admin Panel, and only admins can reach them, BUT if you have the full URL you can enter them:

In this community I'm a moderator, but as you can see I can edit anything if I have the URL

Please, fix the issue


EDIT: It seems that the issue only affects to customize section, and only to some tabs

Posts: 3

Participants: 2

Read full topic

Discourse 1.7 Released!

$
0
0

@codinghorror wrote:

Originally published at: http://blog.discourse.org/2017/01/discourse-1-7-released/

Today, after four months of work, we’re proud to release Discourse 1.7. Discourse 1.2 – Feb 2015 Discourse 1.3 – June 2015 Discourse 1.4 – September 2015 Discourse 1.5 – April 2016 Discourse 1.6 – August 2016 Official iOS and Android Apps Thanks to Sam Saffron, we released an Official Android Discourse app and an…

Posts: 1

Participants: 1

Read full topic

Onebox reverting to textual links in post

$
0
0

@RobMeade wrote:

Hi,

This one is possibly a bit unusual...

I am in the processing of creating a fairly lengthy post which includes links to images / videos / sketchfab from a variety of posts during 2016. I am pasting in the URLs from the actual images already posted rather than adding them all over again.

Unfortunately, a few minutes ago, the tab within Chrome became unresponsive. I am not certain whether I have hit a limit for the size of a post, perhaps a limit on the size that can be saved asynchronously? (saved as text file the content is 16kb which just seems a tad coincidental).

Anyway... whilst I still have the content if I open a new browser window / tab for the post, all of the links (and there are a LOT of them) have changed back in the preview window from being the relevant images / videos / sketchfab oneboxes, to just text for the links.

One of the team here previously mentioned to me that sometimes the content gets cached and by adding ?v=1 etc to the end of the URL it will force it to load it correctly - I have tried this on a couple of the links and it made no difference. I am now somewhat stuck.

The post is not yet finished and will be significantly longer by the time it is, but the re-working of all of these links, assuming I can re-work them, is going to be painful (especially if whatever caused the issue happens again).

Any ideas / thoughts?

No new entries to this post using URLs Onebox the images / video / sketchfab item in the preview either.

Update:
I've just noticed that, having been creating this post for over 4 hours, it's quite possible that it has coincided with your release of 1.7. That said, as a hosted customer, I believe we were already on that version, but having just viewed source I see we are now on 1.8... not sure when this changed, but... is there any chance that my post has been effected because of this item from the listed of 1.8 features?

Implement mini-onebox for internal links (replace with title)

I am currently stuck not knowing whether to keep writing the post, knowing that I may need to go back and do something with all the links, or, if I have killed it because of the length of the post, stop writing the post. :confused:

Posts: 7

Participants: 3

Read full topic

Debugging a running Discourse on DigitalOcean

$
0
0

@adam_beers wrote:

I'm having some issues with uploading images and wanted to try to debug the upload_controller.rb. How do I do that? Can I add debug print statements? I've never done anything with Ruby, so I'm a beginner there.

Can I debug on a running Discourse image on DigitalOcean?

Posts: 2

Participants: 2

Read full topic

Should URL change as you scroll?

$
0
0

@charleswalter wrote:

A number of times, I've started reading a topic and then wanted to share it after I started reading it (either on the on the forums themselves or on social media). Only to remember that the URL I copied doesn't take users to the top of the topic. Just wondering if others have experienced this.

Does it make sense that the URL bar changes? I would expect that the share icon under each post would be used if users explicitly want to link users to a specific reply.

Posts: 6

Participants: 3

Read full topic

Sharing retention data (Google Analytics cohort analysis)

$
0
0

@charleswalter wrote:

Not sure if there's an appropriate category for discussing performance data (perhaps UX), but was curious to hear what others have found.

We seem to do a good job at attracting website visitors, but it very difficult for us to get them to come back (or register). Would anyone else be interested in sharing their weekly cohort analysis report from Google Analytics for benchmarking purposes?

Note that in week 1 after first vist, we see roughly 1/40 users coming back to the site. By week 7, we see less than 1/200 users coming back.

This very well may be expected behavior for communities, but would love to see what others are seeing, and any ideas for improving these metrics.

Posts: 1

Participants: 1

Read full topic

Blocking user from replying to my post or my posts

$
0
0

@charleswalter wrote:

Might seem like a crazy idea, but a user of our community just asked us about this, and I thought it was worth discussion.

We are constantly bombarded with complaints about trolling / harassment.

What if there was a feature (or plugin) that allowed users to have more control over the topics they create. And if they see someone replying inappropriately to their thread, they have the control to block the user from the thread (or perhaps all their threads).

Too crazy? Too DB intensive? or perhaps an iteration of the idea could make sense?

Discourse has a great number of features for flagging posts, but I think there could be opportunities on flagging users and the implications that flagging a User could have on their ability to participate in the community. ex: if we see a particular user is blocked by X other users, then we can take more serious action against this user.

Posts: 1

Participants: 1

Read full topic


The 'enter' key does nothing when logging in on Android

$
0
0

@ron_jeremy wrote:

I just downloaded the Android app and thought it was broken because I was unable to login. Then I realized that hitting the enter key at the bottom right corner of the keyboard does nothing. I had to lower the keyboard and then hit the Discourse login button to complete the process.

I am using a Nexus 6P on latest (as of today) Android Nougat.

Posts: 8

Participants: 2

Read full topic

You need to add rights to create edit the one category

$
0
0

@11145 wrote:

You need to add rights to create edit the one category of 3 people.

Created a group of "auto", it added 3 users who need to moderate exactly one category. But can not add the rights to change and edit and delete records.

Posts: 1

Participants: 1

Read full topic

Ember js routing not working in 2.10

$
0
0

@Aman_Jagga wrote:

I was using this Ember route file to map this URI www.example.com/home/page with the template main-page.hbs located in the home folder

export default {
    resource: 'home',
    path: '/home',
    map() {
        this.route('main-page', { path: 'page' });

    }
};

I was working fine as well until I upgraded my application from 1.2.0 to 2.1.0. I didn't find any difference in two versions with respect to routing in the documentation.Is there any change in routes documentation? Am, I doing something wrong? I am a newbie in Ember js and founding it difficult to understand the routing documentation

Full source code for the plugin is available @github

Posts: 1

Participants: 1

Read full topic

Can't login, reset password or create new account!

$
0
0

@poka wrote:

Hi everyone!

I got a big problem on my discourse. Since a few days, nobody can login anymore, neither in authentication by email nor by social login (Facebook, Google, Twitter ...)
That's very strange cause everything was working since 1 year with no problems. Everything broked overnight for no reason.

This is what happend for differents case (sorry it's french ...):

  • For the email connection:

Just the message " Unknown error"

  • For the social login auth:

The message says: "Sorry, there was an error authorizing your account. Perhaps you did not approve authorization?"

  • When I try to reset the password:

"403 Forbidden"

  • And when I want to create a new account:

"We can not detect if your account has been created, please verify that you have enabled cookies."
Of course, the cookies are enabled.

Any ideas ?

Posts: 1

Participants: 1

Read full topic

Custom font not working

$
0
0

@Becky wrote:

Hi there,

I'm trying to work a custom font (Museo Sans) into my forum to match my website. I've uploaded the webfont files through the site assets topic and added the appropriate CSS to no avail.

The same approach worked spot on with Wordpress so I don't think it's a normal coding error. I've tried referring to the webfont files on Wordpress instead of those uploaded to Discourse, and also tried using the .woff2 file only as suggested, but still no joy.

Using a Google Font on the other hand works beautifully and doesn't break the other CSS code - I've tried removing the rest of this code in case it was conflicting, this also makes no difference.

Has anyone had a similar experience with this? Help or ideas would be hugely appreciated!

Posts: 1

Participants: 1

Read full topic

Link username to external website

$
0
0

@techAPJ wrote:

Let's say you want to add a link of User's main profile page on Discourse user profile page and user card, clicking on that link will take user to main (external) website.

The link of main website user profile page will be like:

http://site.com/username

Where username is the Discourse username of that user. (It should be same on both main site and Discourse forum)

Let's get started!

Add custom CSS

Paste this CSS code in Admin > Customize > CSS/HTML > CSS section:

#user-card .metadata h3 {
  float: left;
}

h3.user-card-public-field {
 clear: both;
}

Add custom JS

Paste this JS code in Admin > Customize > CSS/HTML > </head> section:

<script type="text/discourse-plugin" version="0.6">
    const User = api.container.lookupFactory('model:user');

    api.registerConnectorClass('user-profile-primary', 'site-link', {
      setupComponent(args, component) {
        component.set('siteLink', args.model.get('siteLink'));
      }
    });

    api.registerConnectorClass('user-card-metadata', 'site-link', {
      setupComponent(args, component) {
        component.set('siteLink', args.user.get('siteLink'));
      }
    });

    if (User) {
        User.reopen({
            siteLink: function() {
                const username = this.get('username');

                if (username) {
                    const url = `http://site.com/${username}`;
                    const link = `<a href=${url} target='_blank'>${url}</a>`;

                    return Ember.Object.create({ link, name: "User Profile" });
                } else {
                    return null;
                }
            }.property('username')
        });
    }
</script>

<script type='text/x-handlebars' data-template-name='/connectors/user-profile-primary/site-link'>
  {{#if siteLink}}
    <div class="public-user-fields">
      <div class="public-user-field">
        <span class="user-field-name">{{siteLink.name}}</span>:
        <span class="user-field-value">{{{siteLink.link}}}</span>
      </div>
    </div>
  {{/if}}
</script>

<script type='text/x-handlebars' data-template-name='/connectors/user-card-metadata/site-link'>
  {{#if siteLink}}
    <h3 class="user-card-public-field">
      <span class="user-field-name">{{siteLink.name}}</span>:
      <span class="user-field-value">{{{siteLink.link}}}</span>
    </h3>
  {{/if}}
</script>

Update:

const url = `http://site.com/${username}`;

with your website user profile link.

Voilà :tada:

That's it, you will now see User Profile link on user profile page and user card.

Posts: 2

Participants: 2

Read full topic

Password reset confirm message should discourage social engineering

$
0
0

@vietnugent wrote:

The password reset logic confirms whether en email exists in the user database. This is generally considered bad practice as it enables malicious users to "query" discourse user db. DigitalOcean is a good example of being vague about the provided email, "if the email you specified exists in our system, we've sent a password reset link to it"

Posts: 3

Participants: 3

Read full topic


Allow users to lock, unlist, and delete their own topics

$
0
0

@zombieslayer124 wrote:

Ok. i know this is WAY too similar to an old suggestion.
You can lock, unlist, make private and delete YOUR topics. because that way if a thread gets out of hand WAY out of hand, you can use whichever one as you see fit. Only if it is unneeded arguing, swearing, stuff of that sort. but ONLY for regulars! ~IWantmoreLBSG



I don't know if we are able to allow this or not. Just want to put this out there.

Posts: 13

Participants: 5

Read full topic

Stable channel 1.6 -> 1.7 upgrade poll

$
0
0

@ljpp wrote:

So, the 1.7 has been released. Kudos to the team and contributors!

As so many of you are rolling on beta or tests-passed, I wan't run a poll for stable channel users, who have already made the big jump from 1.6.x to 1.7. Have you experienced any issues with the upgrade?

  • No issues, all good.
  • I ran into problems (describe below)

0voters

Thanks!

Posts: 2

Participants: 1

Read full topic

Plugin Installation on Amazon EC2

$
0
0

@chrismalone wrote:

I am having a terrible time trying to figure out why my plugins are not installing. I have followed the instructions. I have put the appropriate code into the app.yml file. The plugin folder is there (in the app) but the plugin I added to the app.yml file is not there. Meaning, the git clone command didn't run correction, I am thinking. There is no error from the rebuild app, either. I can enter the app and manually run the git clone command and it runs and creates the folder for the plugin inside the plugin folder. Even then, the plugin doesn't show up in Discourse. I have rebuilt the app every time. I have tried the git clone address as https and http.

Here's the code from the rebuild app command and it shows there is no error in the cloning...

I, [2017-01-07T20:30:04.690309 #13] INFO -- : > cd /var/www/discourse/plugins && git clone http://github.com/discourse/discourse-spoiler-alert.git
Cloning into 'discourse-spoiler-alert'...

I went to my install on Azure and did the same thing - put the same code into app.yml, rebuilt the app - and it works fine. Meaning - the plugin installs and functions.

I have terminated the virtual machine twice and started over. I'm using the exact same install steps as I did in Azure.

I would sure appreciate any assistance you can give. I know that installing on Amazon is not officially supported here, however, I'm hoping someone has had the same issue. I have searched and searched for an answer online and haven't found one.

Posts: 1

Participants: 1

Read full topic

Guardian bypassed through :skip_validations in TopicCreator but not in PostCreator

$
0
0

@meriksson wrote:

When creating a topic, the guardian check for permission to create is bypassed if skip_validations is set to true:

However, when creating a reply the equivalent check is not bypassed:

Perhaps I am missing something but this looks inconsistent to me, i.e. skip_validations should bypass the guardian check either in both cases or in none of them.

In any case, I fixed this because I needed it myself (to have an importer create posts in private categories). Here is what I did:

Posts: 1

Participants: 1

Read full topic

How to customize a RSS feed template

$
0
0

@slucas wrote:

I like the fact that every topic, tag... get a rss feed.

like the latest posts
* http://www.futurearchi.org/latest.rss

Even a json version for those who do not know
* http://www.futurearchi.org/latest.json

And I wanted to send a rss-driven campaign with Mailchimp.

But there are several problems about presentation but also missing RSS fields (no image field) I would like to add.

But how to access the RSS templates and customize them?
Why it is not in the customize section of admin dashboard?

I was also thinking using the JSON api to use other tool / or service to generate the RSS feed.
But not sure which one to choose.

Thanks.

Posts: 1

Participants: 1

Read full topic

Viewing all 60690 articles
Browse latest View live




Latest Images