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

Contributor Interviews – Jay Pfaffman

$
0
0

@erlend_sh wrote:

Every week, we’ll be posting an interview with one of our many beloved contributors here on Meta. Find them all in #user-interviews. This week:

Jay Pfaffman @pfaffman

image

Tell us a bit about yourself!

Location: Reno, Nevada, USA

In my last life, I was a college professor who taught future and current teachers to use computers to support their teaching. I thought and taught that Open Source Software was important for education (e.g., It’s time to consider Open Source Software). Before that, I was an early adopter of Linux and once ported Sendmail, UUCP, and a couple different mailing list managers to Linux to run a mailing list for about 600 English teachers over a dial-up link.

I play guitar, though haven’t much lately, and plan to ski this season, as Lake Tahoe is less than an hour away. I spend the vast preponderance of my time doing stuff with Discourse these days. I’ve always liked managing computers and now I get paid for it.

How did you first find out about Discourse?

I was unhappy with the Learning Management System that my last university used and thought that I wanted something like Stack Exchange to support students learning about various computer applications in my classes. Somehow I found Discourse, and adopted it as a way to teach my classes.

What are you using Discourse for?

I do Discourse training, support, installations, and imports full time. I have a Discourse instance that I’ve been using as a means to keep track of what I need to do for my clients, and a tiny instance that I’ve been using with my family. Meta is the Discourse instance that I use the most.

How did you get so involved in the Meta community?

I’ve always been a big Open Source Software advocate and liked the community when I started using Discourse and wanted to give back. About a year ago, I left my faculty job for my wife to take hers and started doing Discourse consulting full time. @codinghorror handed over the $99 community install business to me, and on I’ve gone.

What compels you to contribute to Discourse?

I’ve always been interested in helping those who aren’t “good at” computers learn to use them. Discourse gives me a new way to do that.

Tell us about a non-Discourse community that you’re involved in!

I’m still new in Reno and don’t have much community here, though I have recently joined a wine tasting group.

What kind of significance does the open source movement have to you?

When I was teaching educators how to use computers in their classrooms I was a staunch advocate for Open Source Software. When teachers are spending a bunch of money out of their own pockets for copy paper, I thought it all the more importer for them not to spend money on software. Software, unlike diamonds, is more valuable the more people who have it. I know many people who use a certain very popular word processor primarily because the people that they collaborate with use it. (I can’t stand word processors and use Markdown, LaTeX org-mode and LaTeX pretty much exclusively.) I used to make moral arguments about why schools should adopt and embrace OSS, but no one really listened.

What has been the greatest challenge in learning about Discourse and its community?

It took me a very long time to figure out the multi-container config.
It took me a very, very, very long time to figure out multisite.

Any ideas on how to improve the Meta community?

  • No good place for real RTFM questions, which is compounded by the fact that there’s no FM.
  • Perhaps there should be a “newbie” category (probably with a better name), where people could ask rudimentary questions like “How do I control access to categories” with impunity. That’d offer a place where nearly-new members could provide useful help.

Any advice to future contributors?

My current peeve is people who ask a zillion questions about Discourse before installing it. My advice is to just do it.

I think there’s a big need now for some documentation, so even if you’re not a programmer, you can help out by creating tutorials or other kinds of documentation to help new administrators figure out the basics.

I’d love to see a small suite of proof-of-concept plugins that include just enough to demonstrate overriding a particular thing. This could be a good project for someone just starting out with writing plugins.

Posts: 3

Participants: 3

Read full topic


Notification of new users joining

Pre-Built Theme?

Download list of members by Group

$
0
0

@Lilly_S wrote:

Hi Discourse,

We’re looking to download a list of all members belonging to a particular Group. We need both usernames and emails of users belonging to a certain Group. If this functionality already exists, could you please instruct us in how to use it? Otherwise, this would be an incredibly helpful feature for us.

Thanks!

Posts: 3

Participants: 2

Read full topic

Want to delete - want to delete this topic

Polls permission enhancements

$
0
0

@leog wrote:

Following up the thread “How to Create Polls” about improving polls permission handling.

Considering polls are embedded in a post, if the post is within a category with permissions, the polls should take into consideration those permissions.

Beyond considering a vote a reply or not, any sort of interaction with the post should be considered in those permissions, as they are essentially part of the entity controlled by permissions. Does not makes sense to me that anyone can interact with a “View only” post because the post is fundamentally its content, and that includes polls.

I propose that polls behave the following way according to the permissions applied to the category of the post:

  • See: Only see the results (partial or closed), taking into account the “Public” to show or not voters.
  • Reply / See: Same as See plus the ability to vote
  • Create / Reply / See: Same as Reply / See plus the ability to create posts with polls.

Posts: 1

Participants: 1

Read full topic

[PAID] Install Discourse on Plesk and import phpBB data

$
0
0

@D.VE wrote:

Hi there
we have a Plesk Server (Debian) with a phpBB Form and want to migrate the board to discourse.

I tried this:

But I can’t get it to work. is there someone who could help me with that? We don’t have much budget, but we are willing to pay for help (please tell me what you want).

thanks a lot
best regards,
Dave

Posts: 3

Participants: 2

Read full topic

Option to mark as solved


Limit post replies in a category?

$
0
0

@Chris_S wrote:

Imagine you have a support category. Is there a way to let anyone create a support topic but only allow the original posted and moderators/staff access to reply?

The problem we are running into is that users create a support request but the community muddys up the request with random posts in an effort to resolve it. Often times it confuses the original poster with so many responses.

Asking for a model where:
Everyone - see & create
Only the op + group x (mod, staff + selected users) can reply.


This is for community.infinite-flight.com

Posts: 2

Participants: 2

Read full topic

Thanks to our 2017 translators!

$
0
0

@codinghorror wrote:

Per Transifex and @Simon_Cossar, here’s a summary of everyone that contributed to translating Discourse in 2017. Thank you for your help in bringing the 100% free, open source experience of Discourse to so many people in the world! :world_map:

Discourse translators for 2017

Arabic

ibraheem.alhashim, bruges, hoxhe, LostEchelon, MohamedAbd_Elaziz, ahmed_medhat, khafagy

Azeri

voogarix, KamranAliyev

Bengali

thehungrycoder, safwanrahman, Swarnava

Bosnian

arnelh, ivke, Rux, elAhmo, hernad

Bulgarian

plezzz

Catalan

quimgil, xexu77, sysbrk, joan.vallve, im_dario

Catalan (Spain)

Unpaisencomu, joan.vallve, OctaviRodriguezBlanco, im_dario

Chinese (China)

dfpoon, xyau, LiveLikeLastDay, Albatron, boltomli, zola, littlemo, mr_yeast, xiasummer001, larryisthere, yfdyh000, ckeboss

Chinese (Taiwan)

ans10023, clkao, s8321414, cco1234, twngbm, saluzi, kmtu, 張竣佑, simon70828, ms06895178, andy0130tw, mark19891107, ckeboss, targee, zerng07

Croatian

Readycool

Czech

tompeace, danielhollas, davidhrbac, zdenek.svarc, ladislav.sulc, cz.lang, MekliCZ

Danish

aputsiaq, frold, dimsedane, valberg, oblakeerickson

Dutch

rafalno45, patrick.woldberg, Rourke, dbunskoek, Zapper, philippevg, wdijkhuizen, JordyLangen

Esperanto

keirwilliams, pwierzbowski, elopio

Estonian

priit.varik, mihkeltepp

Farsi

SAlavizadeh, Raddah, Alir3z4, jalal051, Goudarz, Alireza_Farahani, mkamyar

Finnish

MarkoK, erlend_sh

French

gauthier59, Sammuel, egilli, zogstrip, thecellmc, Akaiha, arthak, timelord, yann_d, olexandratesliuk_gtc_OTM4YW, jeremielondon, Ctouw, rui.liu, jomaxro

French (Canada)

rui.liu

Galician

antiparvos, barreeeiroo

German

rizka, claasaug, Stranikevg, tophee, Adorfer, Johannes.Paul.Frank, terraboss, noyainrain, GregoryS, Atalanttore, fefrei

Greek

stavi93, emmanouelakam, OrestisKats, stella1997, electrapan, LukeVidalis, Michaliss1993, kokos88, panayiotis.nikolettos, Anthoula, skarmoutsosv, Eva88, moumtzidou.elli, elinajordan, manios

Gujarati

Hemang

Hebrew

eburcat, Avner, Yaron

Hindi

Hemang

Hungarian

arpadlukacs, denem, theanimefan00, cohenaron, pushrbx, madaraszcsaba

Indonesian

iidbae, tadityar, bRionZ, wowena, eljuno

Italian

Trash74, hardest, dluc, massimog, piero_tasso, LordAndrew

Japanese

shinji_abe, Siro, Tripper, Laica_Lunasys, rrrobo, maa123

Korean

Changjoon, onebone, BasixKOR, choipd, finalchild, areum, Hoto_Cocoa, 이종은

Korean (Korea)

onebone, BasixKOR, choipd, Baristacus, samsee, rebel1324, finalchild, areum, Hoto_Cocoa, ckeboss, 이종은

Latvian

mzvejnieks, Gusts, Davisgolds, baltgrolv, lapsa

Lithuanian

Paulens

Norwegian (Bokmål)

gustavf, jordr, Menomenta, dasjoen, krav, drawliqaz

Norwegian (Nynorsk)

erlend_sh

Polish

mbajdel, Shaki81, Luxter, kpc21, rafalno45, Jqmey, AndrzejS, p.jankiewicz, critical, Py64, ipepe, Fajfi, heinzek, spike200, sauler, jhnwsk, iJuliusz, wujeksok, MakaryGo, NitroFuN, tobeornot, marekelis, blubisu, piotrek.marat, brianifex, zarie, Matrikx

Portuguese (Brazil)

Muleke_Trairao, hartmnn.p, jonathasdantas, caiovmatos, brunopicinini, chalassa, xfalcox, reinaldo.corso, andreyduarte, Romoaldo, niemeyer, lselbach, diegocouto, yuriebc, adrianovalle

Portuguese (Portugal)

TigPT, TDF2001

Romanian

iamntz

Russian

Stranikevg, aiska, Husteln, danunafig, KarelWintersky, meinhof, hugsy, govlad, lifegifted, egorsmkv, alff0x1f, Veizdem, somecharm, makeyko, dalerka, rapekas, kmicic, allustin, dergousov_ds, ckeboss, dmitry.murzin

Serbian

mladjoa, ivke, surrealan, ivan.avdic, SrdjanTemerinac, dux, ivan.jovanovic, srka99

Serbian (Latin)

ivke, surrealan, dux

Slovak

valasek, xkatka, alexanderzatko, Suchardo, dami12

Slovenian

rajitha.wijayaratne

Spanish

Apecengo, davidgnavas, elopio, raulvillares, im_dario

Spanish (Castilian)

Morell, nando.dominios, barreeeiroo, OctaviRodriguezBlanco, raulvillares, im_dario, erlend_sh

Swahili

luse

Swedish

hannawekell, orjan.lundberg, tophee, rutinerad, MattiasSE, erikxxon, henrikn

Tamil

navinspm

Thai

statpr, thisisapen, sipp11, buriramworld

Turkish

kabadayi28, Berc21, eminov, berkan, hugsy, ysfcn, alperguven, DuaL, alquirel, ysrarl

Ukrainian

Davilgin_Always, dismine, KovalRobert, olexandratesliuk_gtc_OTM4YW

Urdu

AhmadF.Cheema

Vietnamese

laocoi, quangbuule, hongquan

Welsh

curondavies

Yiddish

Yisroel

Posts: 1

Participants: 1

Read full topic

Discourse 1.9 released!

$
0
0

@codinghorror wrote:

Originally published at: Discourse 1.9 released!

As of January 3rd, we’re pleased to release Discourse 1.9 today, building on Discourse 1.8 from June. Show Who’s Replying Discourse is all about replies being disconnected in time and space, but we agree that showing when people are actually replying to a topic is genuinely useful in a variety of contexts. So we’ve added…

Posts: 1

Participants: 1

Read full topic

Policy notice: no private solicitations for work, paid or free

$
0
0

@codinghorror wrote:

We want people to be able to participate freely on meta without being badgered about doing work for others – so just a heads up, we’re now formally enforcing a policy that has been informally enforced in the past:

All solicitations for any kind of work, paid or free, must be in public in the #marketplace category

This is a part of our community guidelines and terms of service. Basically, no private soliciting:

image

The primary bit that’s important here is asking in public in the correct category, and avoiding private solicitations.

If you are open to being directly contacted about Discourse-related work opportunities, indicate that on your user profile with external contact information. We would prefer that this contact not occur here on meta, but it is OK if you have explicitly indicated you want to be contacted on your user profile, or of course in a public #marketplace post.

Posts: 2

Participants: 1

Read full topic

How to Create Polls

$
0
0

@jomaxro wrote:

May we copy-paste this guide into our communities?

This is excellent - a similar guide to other significant features of Discourse would be valuable.

Posts: 6

Participants: 2

Read full topic

How to use the current color scheme variables in your custom sheets

$
0
0

@lll wrote:

This one is quick and dirty.

Background

Discourse themes generate different element colors based on color schemes. Color schemes are made of variables for colors that can be set in the admin.

If you’re developing a plugin (or theme - but that’s slightly different), inheriting those variables from the current theme’s color scheme can save a lot of time because the finished product would automatically inherit the current color scheme on the users end whatever it may be.

How?

Add this to the top of any custom stylesheet and you’re all set:

@import "//stylesheets/app/assets/stylesheets/common/foundation/colors";

This enables you to use those variables. The root-relative link means that it’s universal.

The default names for the variables are:

$primary:
$secondary:
$tertiary:
$quaternary:
$header_background:
$header_primary:
$highlight:
$danger:
$success:
$love:

Which match the names of the color scheme fields in the admin:

Examples:

Create a new theme (the same idea works for plugin custom sheets)

Notice that the current color scheme is set to “Light scheme” (same color scheme in the screenshot above)

Now add the line from above to import the color scheme variables in the theme’s custom sheet like so:

You should now be able to use the variables at any time.

Let’s say I want to set the <body> background to match the $highlight variable of the current color scheme. Well, I can do that like so:

body {
    background: $highlight;
}

And the color would be pulled automatically from the current color scheme, like so:

(This background color is not recommended :sweat_smile:)

Now, let’s say the color scheme is not set to “Light scheme” for the the current theme. Instead, let’s say it’s set to the default “Dark scheme” which looks like this:

The same code would yield a different result because the variable is different.

You can see how the <body> background follows the current $highlight variable whatever it may be at the time.


feel free to edit this topic for clarity / better explanation

Posts: 1

Participants: 1

Read full topic

Don't show enable css check box


Mute/hide categories for a specific user from API?

$
0
0

@jonobacon wrote:

Hi Everyone,

I am working with a client who has a number of categories and we want to provide a dedicated UI where they can select which ones they do and don’t see.

I am thinking we can hide categories by muting them via the Discourse API for the logged in user. Is this possible via the API?

Thanks,

Posts: 2

Participants: 2

Read full topic

Backup to S3 configuration problem

$
0
0

@supervazi wrote:

Configuring automatic backups conform this topic:

When I want to enter my s3 bucket name I get the following error:

s3_backup_bucket: Value doesn’t match the required format.

The bucket I use exists, it is accessible with the credentials entered in “Files” section, as mentioned in the topic. We have a bucket naming standard and conform that I need to name my bucket in the following format:

[bucket-purpose].[domainname]

So, this backup is named: community-backup.mydomain.com
I think the problem is with dots in the bucket name.
Is there any possibility to use my bucket?

Posts: 5

Participants: 2

Read full topic

Excerpt gets too long under certain circumstances: "ActiveRecord::ValueTooLong"

$
0
0

@niko wrote:

Under certain circumstances the excerpt gets longer than 1000 characters and the server throws a 500 and logs ActiveRecord::ValueTooLong (PG::StringDataRightTruncation: ERROR: value too long for type character varying(1000) : UPDATE "topics" SET "excerpt" = '<details><summary>Ich habe meine Playlisten gefüll.

We stumbled over this when we where trying to save a topic consisting only of detail/summary content. It can be reproduced by trying to save this as a new topic:

[details="Some question?"]
Some answer.
[/details]

[details="Some question?"]
Some answer.
[/details]

[details="Some question?"]
Some answer.
[/details]

[details="Some question?"]
Some answer.
[/details]

[details="Some question?"]
Some answer.
[/details]

[details="Some question?"]
Some answer.
[/details]

[details="Some question?"]
Some answer.
[/details]

[details="Some question?"]
Some answer.
[/details]

[details="Some question?"]
Some answer.
[/details]

[details="Some question?"]
Some answer.
[/details]

[details="Some question?"]
Some answer.
[/details]

[details="Some question?"]
Some answer.
[/details]

[details="Some question?"]
Some answer.
[/details]

[details="Some question?"]
Some answer.
[/details]

[details="Some question?"]
Some answer.
[/details]

[details="Some question?"]
Some answer.
[/details]

… and works fine when removing one of the details blocks.

Backtrace
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.7/lib/patches/db/pg.rb:93:in `exec'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.7/lib/patches/db/pg.rb:93:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:614:in `block (2 levels) in exec_no_cache'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.4/lib/active_support/dependencies/interlock.rb:46:in `block in permit_concurrent_loads'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.4/lib/active_support/concurrency/share_lock.rb:185:in `yield_shares'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.4/lib/active_support/dependencies/interlock.rb:45:in `permit_concurrent_loads'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:613:in `block in exec_no_cache'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract_adapter.rb:612:in `block (2 levels) in log'
/usr/local/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract_adapter.rb:611:in `block in log'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.4/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract_adapter.rb:603:in `log'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:612:in `exec_no_cache'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:599:in `execute_and_clear'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/postgresql/database_statements.rb:92:in `exec_delete'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:140:in `update'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract/query_cache.rb:17:in `update'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-5.1.4/lib/active_record/relation.rb:380:in `update_all'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-5.1.4/lib/active_record/persistence.rb:333:in `update_columns'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-5.1.4/lib/active_record/persistence.rb:306:in `update_column'
/var/www/discourse/lib/post_revisor.rb:436:in `update_topic_excerpt'
/var/www/discourse/lib/post_revisor.rb:430:in `revise_topic'
/var/www/discourse/lib/post_revisor.rb:162:in `block in revise!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:235:in `block in transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract/transaction.rb:194:in `block in within_new_transaction'
/usr/local/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract/transaction.rb:191:in `within_new_transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:235:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-5.1.4/lib/active_record/transactions.rb:210:in `transaction'
/var/www/discourse/lib/post_revisor.rb:150:in `revise!'
/var/www/discourse/app/controllers/posts_controller.rb:193:in `update'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_controller/metal/basic_implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/abstract_controller/base.rb:186:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_controller/metal/rendering.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:131:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_controller/metal/rescue.rb:20:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.4/lib/active_support/notifications.rb:166:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.4/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.4/lib/active_support/notifications.rb:166:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_controller/metal/params_wrapper.rb:252:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-5.1.4/lib/active_record/railties/controller_runtime.rb:22:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/abstract_controller/base.rb:124:in `process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-5.1.4/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.7/lib/mini_profiler/profiling_methods.rb:102:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_controller/metal.rb:189:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_controller/metal.rb:253:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/route_set.rb:49:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/route_set.rb:31:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_dispatch/journey/router.rb:50:in `block in serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_dispatch/journey/router.rb:33:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_dispatch/journey/router.rb:33:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/route_set.rb:834:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/builder.rb:63:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/conditional_get.rb:38:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/head.rb:12:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:149:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/session/abstract/id.rb:232:in `context'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/session/abstract/id.rb:226:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/cookies.rb:613:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/callbacks.rb:26:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:97:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/callbacks.rb:24:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/debug_exceptions.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.9/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-5.1.4/lib/rails/rack/logger.rb:36:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-5.1.4/lib/rails/rack/logger.rb:26:in `call'
/var/www/discourse/config/initializers/100-quiet_logger.rb:16:in `call'
/var/www/discourse/config/initializers/100-silence_logger.rb:29:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/remote_ip.rb:79:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/request_id.rb:25:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/method_override.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/runtime.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/executor.rb:12:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/sendfile.rb:111:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.7/lib/mini_profiler/profiler.rb:282:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.1.2/lib/message_bus/rack/middleware.rb:63:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:138:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-5.1.4/lib/rails/engine.rb:522:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-5.1.4/lib/rails/railtie.rb:185:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-5.1.4/lib/rails/railtie.rb:185:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/urlmap.rb:68:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/urlmap.rb:53:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/urlmap.rb:53:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.1/lib/unicorn/http_server.rb:606:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.1/lib/unicorn/http_server.rb:702:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.1/lib/unicorn/http_server.rb:549:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.1/lib/unicorn/http_server.rb:142:in `start'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.1/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: 1

Participants: 1

Read full topic

Why does the `SiteSettings` class use the `DistributedCache` without a `require 'distributed_cache';` statement?

Embed Google Calendar

$
0
0

@McBlu wrote:

I would like to embed a Google Calendar into a topic on my forum. I opened a topic and pasted the following customized code from Google Calendar which did not work:

I pasted the following unedited code from the Google Calendar which also did not work:

Is it possible to embed a google calendar? If so, what are the steps? Does anybody know? Thanks!

Posts: 5

Participants: 2

Read full topic

Viewing all 60690 articles
Browse latest View live




Latest Images