@net_deamon wrote:
If I add a plugin outlet in list item,
ie <plugin name>/assests/javascripts/discourse/templates/list/connectors/topic-list-tags/<unique name>.raw.hbsWhere should I add the js.es6 file for this outlet?
I tried it in following location, but it didnt work
ie <plugin name>/assests/javascripts/discourse/list/connectors/topic-list-tags/<unique-name>.js.es6export default { setupComponent(args, component) { .... } }
Posts: 1
Participants: 1
@tassawarr wrote:
This is my first topic on official forum. I need some basic info about discourse .
Package available at github is free from all issues/errors?
Is that the sandbox version?
What is the basic price of discourse application?
is the github version have all the plugins and integrations valued into core filesLooking forward for more efficient replies.
thanks
Posts: 6
Participants: 3
@tophee wrote:
I can't seem to upload any picture to my forum. It gets stuck at 100%.
Avatar image:
Image in post:
There is no S3 or any other external storage involved.
I have checked:
*Discourse error log: nothing
* NGINX error.log: nothing
* MYSQL error.log (if that has anything to do with anything at all): nothing
Posts: 5
Participants: 2
@Steve_Pavlina wrote:
I'm configuring a private Discourse forum and would like to restrict the ability to send invites, such that only admins have that ability. I'm not using SSO.
What settings should I use to prevent all non-admin members from being able to send invites, regardless of their trust level?
Posts: 1
Participants: 1
@zbor wrote:
I would like to turn autohighlight for Microsoft Visual Basic for Applications (VBA)
but it doesn't work as expected.
As I see it only works if code is indented.
But if that's true why language recognition?Could it be forced to recognize language?
Is it possible that first post in this thread https://online-excel-solutions.com/t/preformatted-text-vba-testing/358 is automatically preformatted?
Posts: 4
Participants: 2
@tolkin wrote:
Not sure if this is the best place to comment about this but I will.
Are there any future plan to prepend "Solved:" in front of the solved question's title?
That way the Solved: will also appear within the Search Engine Result Pages making it more likely to be clicked thus improving the Forums CTR.
Regards
Posts: 4
Participants: 4
@sam wrote:
Bugs, Feature requests, support and so on relating to the Discourse solved plugin
Posts: 1
Participants: 1
@charleswalter wrote:
Not sure if this was intentional, but we noticed that the Flags screen no longer has the approve or reject buttons. Unless you navigate to active screen. Is this intentional?
Posts: 2
Participants: 2
@Hotrin wrote:
A certain game or something I found it off of mm2 forums and I'm new
Posts: 1
Participants: 1
@Bruges wrote:
Hi everyone,
I installed Discourse yesterday every thing seem to work just fine.
I've been working on the Arabic translation for some time now & i thought once the instance will be installed it will be as per the latest translation in transfix but it's not!
is there a way to update my instance language?
thank you,
Posts: 2
Participants: 2
@raoulette wrote:
I've read a few of the topics on the matter of discourse breaking browser search, I understand this is by design and a discourse feature. Breaking a basic user interface principle is not the correct way to fix the situation.
"If a necessary feature has a high astonishment factor, it may be necessary to redesign the feature."
Discourse devs should know about Principle of Least Astonishment or POLA and that it requires extraordinary circumstances for breaking it.
To make matter worse, the hijacking occurs at times but not others under circumstances that seems random,To worsen the matter further some search shortkeys are always hijacked such as '/' while some are only hijacked under circumstances that the user cannot foresee. Usually when hijacking one such shortkey the other is left alone so one can still have the expected behaviour.
I could go at length why this is so bad I'd never consider discourse for anything and would switch to a competitor instantly if I was site admin, but more often than not I'm a simple user. So where is the user setting to disable this behaviour ? the admin setting setting to disable it globally ?
Of course the correct way would be to fix the broken design that leads to this situation in the first place, if the root cause is that all posts are not loaded in the browser then load them, or provide me with a button to load them or just allow me to only search in what's currently loaded which is what I expected from the browser page search in the first place.
Posts: 3
Participants: 2
@tophee wrote:
This feature may be useful in other scenarios too, but my use case is a multi-lingual site. A key challenge of a multi-lingual forum is how to best configure it to allow the use of different languages while not spamming users with posts in languages they don't understand.
At present, I think the best solution is to use language groups and show categories for each language only to members of the respective language group. Like this:
But there is a significant problem with this approach: all content (perhaps except for the default language) will be hidden from users that are not logged in.
So here is my suggestion for a feature: the problem would be solved with a category security setting "hide category from these groups". That way all content would be visible to everyone but when you login, you only see your languages. (Positive side effect: people are encouraged to log in)
Posts: 1
Participants: 1
@codinghorror wrote:
I recently moved my own Discourse from Digital Ocean to a colocated mini-PC I purchased from Ali Express. This is a good apples to apples of increasing CPU performance with the exact same Discourse instance.
Digital Ocean Droplet specs
- E5-2630L v2 (Ivy Bridge 2.4 - 2.8, 2 core)
- 2 GB RAM
- 30 GB disk (unknown SSD)
cost $20/month
AliExpress box specs
- i7-7500u (Kaby Lake 2.7 - 3.5, 2 core, 4 thread)
- 16 GB RAM
- 500 GB disk (Samsung 850 Evo SSD)
cost $700 plus colocation hosting fees ($15/month)
CPU benchmarks
sysbench --test=cpu --cpu-max-prime=20000 runsysbench --test=cpu --cpu-max-prime=40000 --num-threads=8 run35.6s vs 21.3s
41.9s vs 15.7s(1.7x faster single core, 2.7x faster multiple core)
Disk benchmarks
ioping -RD -w 10 .12.8k iops, 50.0 MiB/sec vs 13.6k iops, 53.2 MiB/sec
(roughly the same disk performance)
Discourse benchmarks
Before and after I did the move, I compared performance in three places:
- Topic back button (same topic)
- Topic refresh (same topic)
- Homepage refresh (latest)
I did this 10+ times in the same browser. Here are my results. Digital Ocean droplet on the left, Ali Express mini-pc on the right.
1.6x faster, 1.8x faster, 2x faster
As to the question in the topic title, Discourse scales more or less linearly with the CPU speed you throw at it. If you want a faster Discourse, have enough memory, sure, but you want the fastest possible single threaded performance.
Posts: 3
Participants: 2
@acinonyxjubatus wrote:
I think it would be useful to disable/enable group of tags.
e.g. I have a few dozens of tags in a group that I do not need now, but I might need them in future. Instead of deleting them I'd be glad to just disable them.
Posts: 5
Participants: 2
@eagleeye wrote:
My Forum is running with the german locale and when I try to grant an user to admin or mod I got an 422 reponse
in the logs is
ActiveRecord::RecordInvalid (Validierung gescheitert: Name wird bereits verwendet) /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/validations.rb:79:in `raise_rWhen I switch to english locale everything works fine
Log
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/validations.rb:79:in `raise_record_invalid' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/validations.rb:43:in `save!' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/attribute_methods/dirty.rb:29:in `save!' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:291:in `block in save!' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:351:in `block in with_transaction_returning_status' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/database_statements.rb:211:in `transaction' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:220:in `transaction' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:348:in `with_transaction_returning_status' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:291:in `save!' /var/www/discourse/app/models/group.rb:247:in `refresh_automatic_group!' /var/www/discourse/app/models/group.rb:271:in `block in refresh_automatic_groups!' /var/www/discourse/app/models/group.rb:270:in `each' /var/www/discourse/app/models/group.rb:270:in `refresh_automatic_groups!' /var/www/discourse/app/models/concerns/roleable.rb:38:in `block in save_and_refresh_staff_groups!' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `block in transaction' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:220:in `transaction' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:277:in `transaction' /var/www/discourse/app/models/concerns/roleable.rb:36:in `save_and_refresh_staff_groups!' /var/www/discourse/app/models/concerns/roleable.rb:44:in `set_permission' /var/www/discourse/app/models/concerns/roleable.rb:20:in `grant_moderation!' /var/www/discourse/app/controllers/admin/users_controller.rb:121:in `grant_moderation' /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/routing/mapper.rb:49: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:38: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/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:17:in `call_with_quiet_assets' /var/www/discourse/config/initializers/100-silence_logger.rb:29: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:519:in `maintain_worker_count' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.2.0/lib/unicorn/http_server.rb:283:in `join' /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>'Request
General: Request URL:https://<host>/admin/users/257/grant_moderation Request Method:PUT Status Code:422 Remote Address:138.201.7.220:443 Response Headers: content-length:0 content-type:text/html; charset=utf-8 date:Sun, 05 Mar 2017 12:01:42 GMT server:nginx/1.11.9 set-cookie:__profilin=p%3Dt%2Ca%3Dbdd62121b9a9cbbcded0b217d29e5931%7C488d3b115676e2968a457844f11a3f0e; path=/ status:422 x-request-id:9f0db8ff-3734-42ca-a683-cf57dcdc763b x-runtime:0.052743 Request Headers: :authority:<host> :method:PUT :path:/admin/users/257/grant_moderation :scheme:https accept:*/* accept-encoding:gzip, deflate, sdch, br accept-language:de-DE,de;q=0.8,en-US;q=0.6,en;q=0.4 cache-control:no-cache content-length:0 cookie:bb_lastvisit=1461953829; bb_lastactivity=0; bb_userid=1; bb_password=96685ad5fa8c8883e649e8cc14a7e178; editor_height=qr%23176px; bb_languageid=3; bb_cpsession=b96e303eecd3287bef250aefc1be3769; bb_sessionhash=9ca09ebc4421c6d0baec04e106b79e1a; _pk_ref.1.0ee2=%5B%22%22%2C%22%22%2C1488704685%2C%22https%3A%2F%2Fwww.google.de%2F%22%5D; _pk_id.1.0ee2=5cfc29c3cea9e131.1461953829.185.1488704685.1488704685.; _t=004424793f0f9f3e72c67c9c31a8ee18; _forum_session=OU9JZ0RVdjdOb3FoTEpJdDBvVWsyU3hTMmVWREhUODhvbnFZTjNnRXZjcnZpRWdSV3ltaGNsYi9MUEh6dUJ1bVFpQlc0S3h5SzdEUkQ5cy82YnJUREpPdVlHREpLMUU5blhUbHJVRXd6MVk5a2d0SCtHQnpieGI5RVV6OGVtRTNuUE9xZm5XV2RjZVNMWTlhTFBqaCtBdzErVWNGekV4bjRQakxIZjRtWDJacjFwRmVNUGcwZC9wNlc3aGMybUVYcDdaMmxQVCtFKzZIVmZRNmN1UDBXRnJMUnAwZFEwcDIwdGdpNmI1Q0ROSmVQbm5PQVZuc1JULy8rMGpReE9lLy9jMTYxUmxOcEx6dEVyMVl4NjR1UlkxYU1na09IZHhYTGNaUVcxbnFyNWpHV2xHQ3VMMXBaVk5PMEhydFVreThBK1Z1N28yajFzTHdFR3dMYlorakR3PT0tLWRWTmZNM1NJMzB0TzNHTGlSQ2EwWlE9PQ%3D%3D--edd9f12d6ca08edc6d9610427b9f415558cd061e; __profilin=p%3Dt%2Ca%3Dbdd62121b9a9cbbcded0b217d29e5931%7C488d3b115676e2968a457844f11a3f0e discourse-visible:true dnt:1 origin:https://<host> pragma:no-cache referer:https://forum.byte-welt.net/admin/users/257/noctarius user-agent:Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 x-csrf-token:vCveUF5/sCS1C4AXTonCgXZEUsrVHTxgOXVPkQH8UAi/HuThxYwr2Jg5YIHvm+LOQHKUIPlflaxafN6N5lmqxg== x-requested-with:XMLHttpRequest
Posts: 3
Participants: 2
@meglio wrote:
We have created a new category in our goat keepers community: "Veterinary first aid online".
We want everyone to be able to ask questions in that category (by creating a new topic).
Once a question asked, we want only the members of the Veterinaries group and the topic owner to be able to answer.
A new permission type for this in the category permissions screen would be very helpful to implement our idea.
Posts: 1
Participants: 1
@vinothkannans wrote:
In my development environment I am unable to run
plugin:spec. It returning the below error/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/seed-fu-2.3.5/lib/seed-fu/runner.rb:46:in `eval': PG::UndefinedTable: ERROR: relation "user_auth_tokens" does not exist (ActiveRecord::StatementInvalid) LINE 5: WHERE a.attrelid = '"user_auth_tokens"'::regc... ^ : SELECT a.attname, format_type(a.atttypid, a.atttypmod), pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod FROM pg_attribute a LEFT JOIN pg_attrdef d ON a.attrelid = d.adrelid AND a.attnum = d.adnum WHERE a.attrelid = '"user_auth_tokens"'::regclass AND a.attnum > 0 AND NOT a.attisdropped ORDER BY a.attnumI also tried to run individual
plugin:speccommand. I already done db migration too.
Posts: 2
Participants: 2
@acinonyxjubatus wrote:
By default tags are sorted in popularity order.
Is it possible to show all tags simultaneously in drop-down?
I mean even unused tags.
Posts: 1
Participants: 1
@Lutz wrote:
Request:
The color schemes should be completely switched off in the admin area or switch to the default.Reason:
Many pages use the Color Schemes in combination with Custom CSS to create the desired effects. Since the CSS in the admin area is switched off, it looks in part ugly and has a bad usability.
Posts: 1
Participants: 1
@Mie_Goreng wrote:
So I see that there is
Heading 'H'
Are there any options for the User to change the fonts-size when they make a post?
Some message boards and wysiwyg text editors allow this. You can apply a font size to portions of the text in your posts.
Posts: 4
Participants: 2
