@wiliamjoaquim wrote:

If I change the name of the discobot, and image, is this going to make it stop working? Or no problem?

Posts: 2

Participants: 2

Read full topic

@kodab wrote:

I'm currently using the import script provided by discourse to transfer my old vanilla forum tdiscrouse. After the import is done, I want to enable SSO and use my Laravel PHP website framework as my main user database.

Q: is it required to import all users in discourse with the import script or are they imported into discourse when they login for the first time in discourse? What about the threads that I import that are assigned to userID? If I don't import users, how is it possible to import content and match it against users?

Posts: 11

Participants: 3

Read full topic

@sam wrote:

image.png1224x562 21.3 KB

Edge has a giant black box around posts while selected which extends on to the timeline.

Posts: 7

Participants: 3

Read full topic

@jlippiner wrote:

Is it possible to automatically have any replies by admin be colored so we don't need to manually do it every time? Also can we add some kind of Admin label or badge to the posts so people know?

Posts: 2

Participants: 2

Read full topic

@tophee wrote:

Continuing the discussion from Google "no-reply" user pending approval:

I am using Gmail for my incoming emails (following this guide). When I recently signed into that Gmail account from a new device, Google sent me one of those security warning emails: "got a new device? Review sign-in from Samsung Galaxy S7". Discourse correctly rejected this email with an Email::Receiver::AutoGeneratedEmailError but it nevertheless created a staged user for no-reply@accounts.google.com. Can/should this not be avoided, given that discourse correctly noticed that

the 'precedence' header is set to: list, junk, bulk or auto_reply, or when any other header contains: auto-submitted, auto-replied or auto-generated.

Posts: 4

Participants: 3

Read full topic

@1kevgriff wrote:

Hello!

I have a client who would like to completely disable the autocomplete drop down when adding users to a private message. We already disable the user directory - but this still provides a list of users in the forum if someone spent enough time searching.

Another alternative, if disabling is too much would be to enable the drop down after X characters (i'd say 4 or 5 characters would be better accepted than just one) or if an exact match is found.

I didn't see anything in the settings for limiting this - so any guidance would be greatly appreciated it.

Thanks!

Posts: 4

Participants: 3

Read full topic

@hnaseri wrote:

I am seeing suspicious activity in my user to user private message chart. Its been 20 times more in 3 successive days. now how can I detect who has messaged others the most on those days?

Posts: 8

Participants: 4

Read full topic

@fefrei wrote:

I just realized that the system users sends a message for every backup that completed successfully – even if the backup was a regular scheduled backup. In that case, the system user just messages itself:

image.png987x732 55.4 KB

Is that intentional? It seems... weird.

Posts: 3

Participants: 3

Read full topic

@pfaffman wrote:

Continuing the discussion from Discourse Version 1.8:

It seems like I now have to log in to Discourse nearly every day. Before, it was much less often that I would need to re-authenticate. Is this related to these increased security cookie stuff?

Security is a drag.

Posts: 8

Participants: 5

Read full topic

@gauthier wrote:

I've an user TL2 who like every new post. it's useless and we have lot of notification for nothing.
This user gave 500 likes and has receive only 20. Is it possible to set a ratio for each TL? For example, he cannot give more than 10x the number of like received?

Thanks

Posts: 4

Participants: 2

Read full topic

@yanokwa wrote:

I recently used mbox-experimental.rb (v1.9.0.beta1 +35) and it worked amazingly well. It's a big improvement over the existing mbox.rb, so thanks to @gerhard for the great work there!

I only had one problem with the script and I've posted the stack trace and email message below. Removing the message allowed the script to continue, but it'd be nice if there as no crash (or the message was ignored or the user was asked if they wanted to stop or ignore this message).

Stack trace

/var/www/discourse/lib/email/receiver.rb:274:in `[]': no implicit conversion of Regexp into Integer (TypeError)
        from /var/www/discourse/lib/email/receiver.rb:274:in `parse_from_field'
        from /var/www/discourse/script/import_scripts/mbox/support/indexer.rb:60:in `block in index_emails'
        from /var/www/discourse/script/import_scripts/mbox/support/indexer.rb:104:in `block (2 levels) in all_messages'
        from /var/www/discourse/script/import_scripts/mbox/support/indexer.rb:143:in `each_mail'
        from /var/www/discourse/script/import_scripts/mbox/support/indexer.rb:103:in `block in all_messages'
        from /var/www/discourse/script/import_scripts/mbox/support/indexer.rb:96:in `foreach'
        from /var/www/discourse/script/import_scripts/mbox/support/indexer.rb:96:in `all_messages'
        from /var/www/discourse/script/import_scripts/mbox/support/indexer.rb:57:in `index_emails'
        from /var/www/discourse/script/import_scripts/mbox/support/indexer.rb:23:in `block in execute'
        from /var/www/discourse/script/import_scripts/mbox/support/indexer.rb:20:in `each'
        from /var/www/discourse/script/import_scripts/mbox/support/indexer.rb:20:in `execute'
        from /var/www/discourse/script/import_scripts/mbox/importer.rb:34:in `index_messages'
        from /var/www/discourse/script/import_scripts/mbox/importer.rb:25:in `execute'
        from /var/www/discourse/script/import_scripts/base.rb:45:in `perform'
        from mbox-experimental.rb:14:in `<module:Mbox>'
        from mbox-experimental.rb:8:in `<module:ImportScripts>'
        from mbox-experimental.rb:7:in `<main>'

Email message

X-Received: by 10.42.51.141 with SMTP id e13mr3117823icg.28.1394816204975;
        Fri, 14 Mar 2014 09:56:44 -0700 (PDT)
X-BeenThere: opendatakit@googlegroups.com
Received: by 10.182.55.73 with SMTP id q9ls345718obp.98.gmail; Fri, 14 Mar
 2014 09:56:42 -0700 (PDT)
X-Received: by 10.182.81.7 with SMTP id v7mr3655066obx.28.1394816202052;
        Fri, 14 Mar 2014 09:56:42 -0700 (PDT)
Received: by 10.50.6.16 with SMTP id w16msigw;
        Thu, 13 Mar 2014 14:21:09 -0700 (PDT)
X-Received: by 10.182.24.134 with SMTP id u6mr1633212obf.24.1394745669261;
        Thu, 13 Mar 2014 14:21:09 -0700 (PDT)
Return-Path: <quqapwgm@kgbgj.net>
Received: from kgbgj.net ([219.82.53.150])
        by gmr-mx.google.com with ESMTP id s1si1229168ign.1.2014.03.13.14.21.03
        for <opendatakit@googlegroups.com>;
        Thu, 13 Mar 2014 14:21:09 -0700 (PDT)
Received-SPF: neutral (google.com: 219.82.53.150 is neither permitted nor denied by best guess record for domain of quqapwgm@kgbgj.net) client-ip=219.82.53.150;
Authentication-Results: gmr-mx.google.com;
       spf=neutral (google.com: 219.82.53.150 is neither permitted nor denied by best guess record for domain of quqapwgm@kgbgj.net) smtp.mail=quqapwgm@kgbgj.net
Message-ID: <83D010B68028B8398B7E6F8BB8BF9A30@kgbgj.net>
From: =?utf-8?B?5bi46Z2S5rO9?=
To: <opendatakit@googlegroups.com>
Subject: =?utf-8?B?6YKT57uP55CG6ZmE5Lu26K+35p+l6ZiF77yb?=
Date: Fri, 14 Mar 2014 05:20:56 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0423_01892B10.10703A20"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512

------=_NextPart_000_0423_01892B10.10703A20
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

5b6u5L+h5pyq5p2l5bCG5pS55Y+Y55qE5YWt5aSn6KGM5Lia77ybDQoNCuS4gOOAgeW5v+WRiuS4
muKAlOKAlOaJvuWbnumCo+a1qui0ueeahDUwJeW5v+WRiui0uQ0K5LqM44CB55S15ZWG5Lia4oCU
4oCU55S15ZWG572R56uZ5LiN5piv5bmz5Y+w5piv6LSn5p62DQrkuInjgIHlh7rniYjkuJrigJTi
gJTmlbDlrZflh7rniYjliLDoh6rlh7rniYjnmoTov5vljJYNCuWbm+OAgeW9semZoumkkOmlruS4
muKAlOKAlOe6v+S4i+acjeWKoeS4mueahE8yTw0K5LqU44CB6aKE5LuY5Y2hL+S8muWRmOWNoeKA
lOKAlENSTei/mOWPr+S7pei/meagt+eOqQ0K5YWt44CB6ZO26KGM5Z+66YeR5Lia4oCU4oCU5LqS
6IGU572R6YeR6J6N55qE6K+V6aqM55SwDQo=
------=_NextPart_000_0423_01892B10.10703A20
Content-Type: application/octet-stream;
	name="=?utf-8?B?6YKT57uP55CG6ZmE5Lu26K+35p+l6ZiFLmRvYw==?="
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="=?utf-8?B?6YKT57uP55CG6ZmE5Lu26K+35p+l6ZiFLmRvYw==?="

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAOQAAAAAAAAAA
EAAAOwAAAAEAAAD+////AAAAADgAAAD/////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////s

lots and lots of other random text

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==

------=_NextPart_000_0423_01892B10.10703A20--

Posts: 2

Participants: 2

Read full topic

@Horus wrote:

Hello,

I just did a fresh setup of my discourse installation. The existing one was for testing and so on, now I'm going to production.

Since I'm hit by https://meta.discourse.org/t/first-mail-validation-mail-never-sent/62952 I resend the activation mail for users.

I have a user that is approved, but not yet active, since he didn't replied to the activation mail so far. I try to resend it, but only get

(original) Du hast nicht die Erlaubnis, die angeforderte Ressource zu betrachten.
(translation) You don't the necessary permissions to watch the requested ressources.

The user is trust level 1 (I start from 0)

I work with the default administrator. It says:

Administrator: yes
Moderator: no
trust level: 1

I recently deactivated the bootstrap mode, the forum banner says it's due to be deactivated in the next 24 hours.

I am bit surprised that I'm not moderator, though it's probably included in Administrator.

Why can't I trigger resending the activation mail.

Thanks!

Posts: 1

Participants: 1

Read full topic

@Sean_R wrote:

Basically, what I would like to do is link a discussion in Discourse to every article we have in our KB in Zendesk. Then make it so that these show in Zendesk as comments to the document. Like the WP integration but for document commenting. Not very different functionally but may be harder than I am thinking?

I would think that we would need some kind of script on each article page that would recognize the link to the discussion and show the comments and point people to Discourse link to add comments.

I could turn commenting on in Zendesk but then we would have to answer people in another place instead of making a group effort out of it.

Thoughts?

Posts: 1

Participants: 1

Read full topic

@Sean_R wrote:

We are allowing our Trust Level 3 customers to mark Solved, but we have no good way to see how many they are doing. For example, see if a small number of this group are actually doing this work.

I did see

... and I do want that as well.

Could I use data Explorer? I am looking for total accepted Solution over a time period by a user.

From date to date
Name | Total
Mike | 8
Jim | 5
Tim | 3
Tom | 2
Jessica | 1
Beth | 0

Staff would be on the list and the OP would as well (nice to have would be listed as OP)

Posts: 1

Participants: 1

Read full topic

@jlippiner wrote:

I'd LOVE a website thumbnail preview plugin, similar to what Slack does, when someone posts a URL. As an example, here is what Slack does:

Screen Shot 2017-06-05 at 3.38.24 PM.png1290x780 85.5 KB

Would it be possible for someone to create something like this or does it not fall into the architecture?

Posts: 2

Participants: 2

Read full topic

@neil wrote:

Google AdSense offers the option to show ads that fit within the dimensions of their container at the time they will be rendered using the responsive ad size option. The official Discourse Ad Plugin supports AdSense responsive ad sizes.

Defining your AdSense ad units

Simply define your ad unit(s) in AdSense using the responsive option:

Google_AdSense.png654x646 38.6 KB

It can take a few hours before AdSense has any inventory to show in the ad unit, so it's useful to define some fallback creative in the "If no ads available" field to verify that the ad unit is working and to see which ad sizes AdSense is choosing.

Once you create the ad unit, it will show up in your ad units list with a numbered ID. You'll need the ID to enter in Discourse.

Discourse Settings

On your Discourse instance, go to Admin > Settings > AdSense. Enter your publisher ID as usual (the number after pub-), enter the ad unit ID in the location(s) where you want it to appear, and choose "responsive" as the size.

Admin_-_Neil_Tests_The_Things.png748x314 32.3 KB

That's it!

(Optional) Controlling Ad Sizes

You can have full control over the dimensions of the responsive ad units because AdSense looks at the size of the container when choosing the size of ads to show.

Using a custom theme, you can use CSS to set the size of each ad slot. For example, to limit the height of the ads that show above topic lists:

.adsense-topic-list-top.adsense-responsive {
  height: 200px;
}

Posts: 1

Participants: 1

Read full topic

@marc.kriezl wrote:

Would it be possible to change "Categories" to "Departments" across the entire application?

This would affect:
- the dropdown menu "all categories" on the front page
- The column heading "Category" on the list of topics
- The "Categories" tab on the front page
- The heading "Category" on https://meta.discourse.org/categories
- The heading "Categories" upon clicking the hamburger
- etc

Basically, everywhere there is a depiction of "Category" or "Categories"

Thanks!

Posts: 2

Participants: 2

Read full topic

@r3d_f0x wrote:

I have a comments category that all embedded comment topics are in. Can these be hidden from the main list? I don't want them to clutter the forum and get bumped every time someone posts a comment.

Posts: 2

Participants: 2

Read full topic

@E-junkie_Guru wrote:

Would setting newuser_spam_host_threshold to 0 disable that feature? It isn't apparent if that would be supported from the inline help text or documentation I can find, or should we just set that to an absurdly high value like 9999?

FWIW, our Discourse instance is a support forum for a SaaS product that our clients implement on their own sites, so it would be common for them to link to their own site repeatedly as needed in support inquiries.

Posts: 1

Participants: 1

Read full topic

@pfaffman wrote:

I've got an import script that was working. I changed databases that I was importing from.

Now when I try to create a category, it fails, complaining about last_post_user_id. The first line shows what I'm passing to create_category. It doesn't look like that topic insert includes a username. Could that be it? Has something changed that broke this? I don't see any recent changes to base.rb or category.rb. I'm rather stumped.

Cat: 1: Reporting Forums -- When problems are reported they go in this forum.
/home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rack-mini-profiler-0.10.4/lib/patches/db/pg.rb:90:in `async_exec': PG::NotNullViolation: ERROR:  null value in column "last_post_user_id" violates not-null constraint (ActiveRecord::StatementInvalid)
DETAIL:  Failing row contains (15, About the Reporting Forums category, null, 2017-06-05 23:33:54.162645, 2017-06-05 23:33:54.162645, 0, 0, null, null, 0, null, null, null, null, null, 0, null, 0, 0, 19, t, 0, f, f, 2017-06-05 23:33:54.162931, f, 0, regular, null, 0, 0, 2017-06-05 23:33:54.108265, null, 1, null, about-the-reporting-forums-category, null, null, null, null, 1, null, null, f, f, null, null, About the Reporting Forums category, 0, null, null, null, null, null, null).
: INSERT INTO "topics" ("slug", "title", "pinned_at", "category_id", "fancy_title", "created_at", "updated_at", "bumped_at") VALUES ('about-the-reporting-forums-category', 'About the Reporting Forums category', '2017-06-05 23:33:54.108265', 19, 'About the Reporting Forums category', '2017-06-05 23:33:54.162645', '2017-06-05 23:33:54.162645', '2017-06-05 23:33:54.162931') RETURNING "id"
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rack-mini-profiler-0.10.4/lib/patches/db/pg.rb:90:in `async_exec'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/postgresql_adapter.rb:592:in `block in exec_no_cache'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract_adapter.rb:484:in `block in log'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract_adapter.rb:478:in `log'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/postgresql_adapter.rb:592:in `exec_no_cache'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/postgresql_adapter.rb:584:in `execute_and_clear'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/postgresql/database_statements.rb:160:in `exec_query'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/postgresql/database_statements.rb:192:in `exec_insert'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/database_statements.rb:108:in `insert'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/query_cache.rb:14:in `insert'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/relation.rb:64:in `insert'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/persistence.rb:524:in `_create_record'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/counter_cache.rb:139:in `_create_record'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/locking/optimistic.rb:75:in `_create_record'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/attribute_methods/dirty.rb:133:in `_create_record'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/callbacks.rb:306:in `block in _create_record'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:117:in `call'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:505:in `call'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:778:in `_run_create_callbacks'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/callbacks.rb:306:in `_create_record'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/timestamp.rb:57:in `_create_record'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/persistence.rb:504:in `create_or_update'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/callbacks.rb:302:in `block in create_or_update'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:117:in `call'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:505:in `call'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:778:in `_run_save_callbacks'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/callbacks.rb:302:in `create_or_update'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/persistence.rb:142:in `save!'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/validations.rb:43:in `save!'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/attribute_methods/dirty.rb:29:in `save!'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:291:in `block in save!'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:351:in `block in with_transaction_returning_status'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/database_statements.rb:211:in `transaction'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:220:in `transaction'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:348:in `with_transaction_returning_status'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:291:in `save!'
        from /home/pfaffman/src/discourse/app/models/category.rb:206:in `create_category_definition'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:432:in `block in make_lambda'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:228:in `block in halting_and_conditional'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:506:in `block in call'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:506:in `each'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:506:in `call'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:778:in `_run_create_callbacks'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/callbacks.rb:306:in `_create_record'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/timestamp.rb:57:in `_create_record'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/persistence.rb:504:in `create_or_update'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/callbacks.rb:302:in `block in create_or_update'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:117:in `call'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:505:in `call'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:778:in `_run_save_callbacks'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/callbacks.rb:302:in `create_or_update'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/persistence.rb:142:in `save!'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/validations.rb:43:in `save!'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/attribute_methods/dirty.rb:29:in `save!'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:291:in `block in save!'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:351:in `block in with_transaction_returning_status'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `block in transaction'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:220:in `transaction'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:348:in `with_transaction_returning_status'
        from /home/pfaffman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:291:in `save!'
        from /home/pfaffman/src/discourse/script/import_scripts/base.rb:408:in `create_category'
        from /home/pfaffman/src/discourse/script/import_scripts/base.rb:377:in `block in create_categories'
        from /home/pfaffman/src/discourse/script/import_scripts/base.rb:358:in `each'
        from /home/pfaffman/src/discourse/script/import_scripts/base.rb:358:in `collect'
        from /home/pfaffman/src/discourse/script/import_scripts/base.rb:358:in `each'
        from /home/pfaffman/src/discourse/script/import_scripts/base.rb:358:in `create_categories'
        from script/import_scripts/telligent.rb:135:in `import_categories'
        from script/import_scripts/telligent.rb:56:in `execute'
        from /home/pfaffman/src/discourse/script/import_scripts/base.rb:45:in `perform'
        from script/import_scripts/telligent.rb:348:in `<main>'

Posts: 1

Participants: 1

Read full topic