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

Require a user to show up

0
0

@Hotfirenet wrote:

Hello, do you think it is possible to oblige users to post a message in a certain category before posting elsewhere?

Thank's

Posts: 1

Participants: 1

Read full topic


About the voting category

0
0

@sam wrote:

Bugs, Feature requests, support and so on relating to the official Discourse feature voting plugin

Posts: 1

Participants: 1

Read full topic

User "Mailing list mode" setting spontaneously changed

0
0

@pelcami wrote:

I am hesitant to classify this as a "bug" because I haven't been able to reproduce the problem with repeatable builds. Here is what happened:

I have three identical instances of Discourse running on separate servers. Each server has a different FQDN. One account on each of these instances is has "Mailing list mode" turned on, and is configured to "Send daily updates." The email address of this account is the address of a distribution group. On Feb. 22nd, all members the distribution group on each instance are receiving the daily summary. No problems.

On Feb. 23rd, I update each of the Discourse instances from v1.7.0beta10+12 to v1.8.0beta6. Later that day, a distribution group on one of the instances stops receiving the daily summary. Distribution groups on each of the other two instances continue to work without problems. I track the problem down to the one account that is supposed to have "Mailing list mode" turned on (the account whose email is the distribution group address). I observe the setting is turned off. !! I do not observe this change on the account running in the other two instances.

Fast forward to March 3rd. The "Mailing list mode" setting again reverted back to the "unchecked" configuration. Same instance as before. The other two instances are working just fine. Not sure what could be causing this. Anyone have any ideas?

Posts: 1

Participants: 1

Read full topic

Create user automatically in Discourse when they sign up in Wordpress?

0
0

@lkramer wrote:

Hi everyone. We've been using WordPress and the wp-discourse plugin for the past several months and it's working great.

Here's how it currently works: Someone signs up via our WordPress site and then when/if they visit the forum part of our site and click the blue Login button, Discourse automatically creates an account for them.

This all works great.

So, here's the only problem -- If they don't go over to the forum section and click the Login button, they don't get an account setup for them in Discourse and they don't get all of Discourse's awesome "Summary" emails etc etc. We really want our new users to be enticed to participate in the forums right off the bat.

What we'd like to do is automatically setup an account in Discourse for them upon them signing up for WordPress. I can use the API to create a Discourse user, but I'm just not sure if I do this whether that account will "play well" with the wp-discourse plugin sso code.

Just wondering if anyone has already been down this road and wants to share how they did it? :slight_smile:

Posts: 5

Participants: 5

Read full topic

Customize signup page layout

Adding new tags to tag groups via API

0
0

@grodeska wrote:

Hello all,

Is it possible to create a new tag and assign it to an existing tag group via the Discourse API? I don't see anything in the API documentation about accessing tag groups.

Thanks for any insight you can offer!

Lawrence

Posts: 2

Participants: 2

Read full topic

Embeding FunnyOrDie link forces browser to redirect to FunnyOrDie.com

0
0

@PaulFORegan wrote:

I was posting a link to a video on funnyordie.com, and put it on a new line to try to embed the video.

Instead, it caused the browser to redirect to the link as soon as the post loaded. As the redirect happened immediately, it was very difficult to select the post to edit/delete in order to remove the link.

I'm not sure what can be done about this, except disabling embeds from the site.

Here's the link I was using: http://www.funnyordie.com/videos/f4cacc863f/daddy-s-boy

Posts: 1

Participants: 1

Read full topic

Infinite spinner /about on private forum when logged out

0
0

@Steve_Pavlina wrote:

When I'm logged out of a private Discourse forum, I can still view /faq (or /guidelines), /tos, and /privacy. Is it the intended behavior for non-members to be able to view such pages for a private forum? It seems questionable to make these pages public. Some private forums may still want to keep their guidelines private.

Second, those three pages link to /about (especially the /faq page which has multiple links to /about), but when I click to visit /about while logged out, I get an infinite spinner page that never finishes loading. Perhaps these links should redirect back to the home page, inviting people to log in, or the About links could be removed for a private forum. This /about page shouldn't be displayed for non-members since then it would reveal some forum stats.

Posts: 4

Participants: 3

Read full topic


URL rewrite for domain change in permalinks

0
0

@modius wrote:

I have a forum URL change from foo.discourse.com to bar.discourse.com.

If I have both domains pointing at the Discourse server is it possible to use Permalinks to redirect all foo domain traffic to the bar domain? Or do I have to take care of this elsewhere?

For Example

foo.discourse.com/blah/post -->  bar.discourse.com/blah/post

Posts: 6

Participants: 3

Read full topic

Discourse API Documentation Released!

0
0

@codinghorror wrote:

Originally published at: https://blog.discourse.org/2017/03/discourse-api-documentation-released/

Today we would like to announce our much anticipated Official API Docs! You can find them at: http://docs.discourse.org Today, more than ever, an application needs to be able to integrate with other applications and the Discourse API allows you to easily integrate your Discourse forum with any other application. We do have a Ruby based…

Posts: 3

Participants: 3

Read full topic

Add ability to withdraw a vote

0
0

@phi wrote:

It seems that there is no way to withdraw a vote once a vote has been cast. In the case of voting for a requested features on a product, it seems important for users to be able to freely assign their votes so they are able to update their preferences based on the current development focus.

Posts: 6

Participants: 3

Read full topic

MediaFire onebox uses insecure image

0
0

@jomaxro wrote:

Going through some posts on Stonehearth, I discovered a page with a mixed content warning. I went ahead and changed the link from http to https, but it seems that the onebox is including an insecure image. I saw a topic from 2 years ago that's seemed similar (old topic). I'm hoping that if this is the same issue there might now be a solution.

Here's the link causing the issue:
https://www.mediafire.com/file/1ntykblml3x818v/magical_jobs.smod

Posts: 1

Participants: 1

Read full topic

Prefixing `@` symbol in the usernames

0
0

@vinothkannans wrote:

Discourse using @ symbol to mention both users and groups. So I think it will be nice to display @ symbol on both user and group profiles (even in posts too) like below.

Posts: 6

Participants: 3

Read full topic

The discourse stopped working with error 500 Internal Server Error

0
0

@11145 wrote:

The discourse stopped working with error 500 Internal Server Error

With what it is connected I do not know. But the error form ceased to work after moving to this page https://site/users/admin/preferences from under an unregistered user.
Here are the same logs

500 Internal Server Error
If you are the administrator of this website, then please read this web application's log file and/or the web server's log file to find out what went wrong.

ctionView::Template::Error (Discourse::InvalidAccess) /var/www/discourse/lib/auth/default_current_user_provider.rb:67:inrescue in current_user

/var/www/discourse/lib/auth/default_current_user_provider.rb:67:in `rescue in current_user'
/var/www/discourse/lib/auth/default_current_user_provider.rb:64:in `current_user'
/var/www/discourse/lib/current_user.rb:34:in `current_user'
/var/www/discourse/app/helpers/application_helper.rb:71:in `html_classes'
/var/www/discourse/app/views/layouts/application.html.erb:2:in `_app_views_layouts_application_html_erb___54261872801364914_70168090153500'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/template.rb:145:in `block in render'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications.rb:166:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/template.rb:333:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/template.rb:143:in `render'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/mini_profiler/profiling_methods.rb:76:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/renderer/template_renderer.rb:66:in `render_with_layout'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/renderer/template_renderer.rb:52:in `render_template'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/renderer/template_renderer.rb:14:in `render'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/renderer/renderer.rb:46:in `render_template'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/renderer/renderer.rb:27:in `render'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/rendering.rb:100:in `_render_template'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/streaming.rb:217:in `_render_template'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/rendering.rb:83:in `render_to_body'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rendering.rb:32:in `render_to_body'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/renderers.rb:37:in `render_to_body'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/rendering.rb:43:in `render_to_string'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rendering.rb:21:in `render_to_string'
/var/www/discourse/app/controllers/application_controller.rb:549:in `build_not_found_page'
/var/www/discourse/app/controllers/application_controller.rb:158:in `rescue_discourse_actions'
/var/www/discourse/app/controllers/application_controller.rb:141:in `block in <class:ApplicationController>'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/rescuable.rb:112:in `instance_exec'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/rescuable.rb:112:in `block in handler_for_rescue'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/rescuable.rb:80:in `rescue_with_handler'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rescue.rb:15:in `rescue_with_handler'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rescue.rb:32:in `rescue 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:76: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/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.7/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/config/initializers/100-silence_logger.rb:27: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:171: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>'

Posts: 3

Participants: 2

Read full topic

Change the activity indicator

0
0

@codmakr wrote:

Hi,

can someone tell me how i can change this in the topic stream

I wanna show direct

First Post
Last Post

Not with mouse over.

Thx for your help.

Posts: 1

Participants: 1

Read full topic


Discourse embedding still has some bugs?

0
0

@hnaseri wrote:

Continuing discussion from here, I still think my problem isn't solved, even after updating to the newest version.

I have provided a test condition at : https://zabanshenas.com/test/embedding/

The embedding topic is created here appropriately: https://talk.zabanshenas.com/t/page-title/509

However I don't see any embedded comment at my test page.

I have included the following javascript:

<div id='discourse-comments'></div>

<script type="text/javascript">
  DiscourseEmbed = { discourseUrl: 'https://talk.zabanshenas.com/',
                     discourseEmbedUrl: 'https://zabanshenas.com/test/embedding/' };

  (function() {
    var d = document.createElement('script'); d.type = 'text/javascript'; d.async = true;
    d.src = DiscourseEmbed.discourseUrl + 'javascripts/embed.js';
    (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(d);
  })();
</script>

and the host is allowed here:

the only possible issue that I can think of, is that discourse suggests to use http:// as discourseUrl, However since I want to use https, I have changed that myself. However I have tried different combination http/s but it doesn't work with anyone.

Any Idea?

Posts: 3

Participants: 2

Read full topic

Internal link: expand button has disappeared

0
0

@Trash wrote:

The expand/collapse button for internal link has disappeared (but still works).
Is it intentional? My users are confuse, because they tend to click on the link now (so they change page) instead to expand a guide and continue reading in the same page.

Posts: 6

Participants: 3

Read full topic

Tags not visible to user can no longer be used

0
0

@jomaxro wrote:

Recently, @Sam's done some great work updating tags support in Discourse. One of the best new features (in my opinion) is that the tag filter in a category only shows the tags used in that category - removing the "no topics match the filters" issue that use to be able to occur.

However, this change has broken a specific use of tags that relied on said flexibility. In the past, when a site wanted to have staff control tag creation, but wanted to have all the tags always available, it was recommended to make a #staff topic, create the tags you need, and then they could be used by users. With the new change, this doesn't work anymore. As users can't see the tags (they can't see staff topics), they can't use the tags (as they don't have create tag permissions).


Is there a new procedure to accomplish this? This was a critical feature (or side-effect) that a site I administer used fully, and now does not work.

Suggested solution: create a site setting called global tags (or similar) which allows for admins to create tags (just like staff tags are created). These global tags can be seen and used by all users with the appropriate trust level to use tags, regardless of if they're in use yet.

Posts: 9

Participants: 4

Read full topic

500 internal server error at first page call in the morning

0
0

@tophee wrote:

Earlier this morning I accessed the admin panel of my forum via my smartphone, I incorporated discobot to change its name and then logged out. This may or may not be related to the following errors which I saw when I woke up my office PC from hibernation and did the following:
- navigated to the browser tab with a (private) forum discussion that was still open from last night,
- clicked on the Admin item in the hamburger menu,
- received the standard discourse "Ooops, this message is private or deleted" (or so)
- reloaded the browser page

After that, I first received a simple plain-text 500 internal server error. Reloading the page again didn't help so I think the next I tried was /admin which didn't lead anywhere (not sure what exactly the server response was). Last, I tried /login which gave me this basic login screen (plus an oversized logo of my site due to lack of CSS):

I was then able to login using that login-button and the page rendered fine.

In the error logs I find three instances of the following error (can send backtrace details for each of them if required):

ActionView::Template::Error (Discourse::InvalidAccess)
/var/www/discourse/lib/auth/default_current_user_provider.rb:67:in `rescue in current_user'

I am on discourse version b2cfad5 (or v1.8.0.beta5 +202 according to the dashboard).

Posts: 4

Participants: 3

Read full topic

Rendering Component in decorativeWidget API

0
0

@Clement_Decou wrote:

Hello,

I have a component to render ads in my discourse {{numeramaAdsBlock "side_ad"}} and i want to render this component inside the sticky sidebar in a topic. So i use decorateWidget to add my component inside the widget "topic-timeline-container"

export default {
    name: 'sidebar-topic',
    initialize(container) {

        withPluginApi('0.2', api => {
            api.decorateWidget('topic-timeline-container:before', dec => {
                // rendering my component with params
            });
        });
    },
};

How can i render my component with the params ? Thanks.

Posts: 1

Participants: 1

Read full topic

Viewing all 60279 articles
Browse latest View live




Latest Images