Can I have a public-facing forum where membership is behind a Patreon paywall?

April 23, 2018, 3:17 pm

≫ Next: Hide Bio, location, and website unless member of specific group

≪ Previous: Questions regarding Discourse features

Hello! This is my first post, so please be kind if I’m asking stupid questions.

It’s my understanding one can set-up Discourse so that only Patreon users can post questions. That’s exactly what I want. However, I would also like the forum to be public-facing so that it’s still crawled by Google and readable to visitors.

So, is it possible for me to have a public-facing forum where only Patreon patrons can comment? Furthermore, if I wanted to turn off the option for visitors to post anonymously, is it possible to do this without hiding the entire forum? Or does the anonymous option have to be left on in order to allow “non-logged-in” bots to crawl it?

I sure hope my questions make sense…

Thanks for any help you can provide!

Posts: 5

Participants: 2

Read full topic

↧

Hide Bio, location, and website unless member of specific group

April 23, 2018, 3:59 pm

≫ Next: Hide Category from Latest

≪ Previous: Can I have a public-facing forum where membership is behind a Patreon paywall?

@pfaffman wrote:

I want to hide bio, location, and web site unless a user is a member of a specific group. I thought that this was going to be “easy”, but I don’t see how it’s possible, even if I knew CSS.

There is a group in the <body> tag, but that appears to be the group of the user looking, not the group of the user whose profile it is.

In case I’m looking for the wrong solution to my real problem, the rest of the story is that what is desired is for there to be a special class of user who gets to be a “pro” and have contact info, company, location, and so on visible. Normal users will not be able to share that info.

And it should be another topic, probably, but I think the solution is, but also part of the big picture is that It would probably be cool if Pros could receive PMs from Normal users too (but no PMs between regular users).

Posts: 1

Participants: 1

Read full topic

↧

Hide Category from Latest

April 23, 2018, 6:12 pm

≫ Next: [Paid] Restore broken images uploaded to S3

≪ Previous: Hide Bio, location, and website unless member of specific group

@biminiroad wrote:

I know this is discussed in many threads, but I read through as many of them as I can and none of the suggestions seem to work for me.

I have a Support section of my site that has multiple subcategories. I’d like to suppress them all from the latest category. How do I do this?

Screen Shot 2018-04-23 at 9.11.07 PM.png1166x286 21.7 KB

I tried under the “top menu” setting in Admin panel:

latest,-support
latest,-Support
Latest,-Support
Latest, -Support

Posts: 5

Participants: 2

Read full topic

↧

[Paid] Restore broken images uploaded to S3

April 23, 2018, 7:50 pm

≫ Next: Discourse admin login throws 403 ["BAD CSRF"] error

≪ Previous: Hide Category from Latest

@sebastien wrote:

Hi Guys,

While we were trying to setup a second CDN (check why here), we broke most of our images. Not sure what happened but now we have the following issues:

25-40% of all pictures have been replaced by transparent.png

Corresponding pictures have been moved to tombstone

When I browse through revisions of some posts, I can find references to an old (since removed) CDN. I guess one rebake operation did fail

Our ultimate goal would be to:
1/ Restore images copied to the tombstone folder
2/ Restore/rebuild HMTL so images appear again

The rake task “recover_from_tombstone” could do the job but it does not work on S3 (external storage).

So far, we tried to

rebake all posts

remove s3 cdn from the settings and then rebake all posts

No success…

Any idea?

We would happy to pay for some support. The best option (maybe the quickest) would be to use TeamViewer so we can run commands through my terminal.

Thank you for your help

Posts: 5

Participants: 2

Read full topic

↧

Discourse admin login throws 403 ["BAD CSRF"] error

April 23, 2018, 8:19 pm

≫ Next: Reconfirm user email (and delete account if not)

≪ Previous: [Paid] Restore broken images uploaded to S3

@lzhang wrote:

We had a discourse build on AWS with CentOS 7 operation system, we followed the document and used docker to build discourse with almost default settings. It was working well at first, but since last Friday suddenly we couldn’t login to it, got 403 [“BAD CSRF”] error doing any POST calls.

We didn’t use any reverse proxy in front of docker, we directly map the docker instance with 80 port of AWS server, we didn’t use ssl.

After getting the error, we tried pulling latest git code and did a full rebuild, but still getting the 403 error.

Any suggestions what else we could do?

Thanks,
Lei Zhang

Posts: 5

Participants: 3

Read full topic

↧

Reconfirm user email (and delete account if not)

April 23, 2018, 11:52 pm

≫ Next: Tag editor keyboard bug (mobile)

≪ Previous: Discourse admin login throws 403 ["BAD CSRF"] error

@iamntz wrote:

One of the perks of the GDPR is that we must confirm with ALL users that they agree with us keeping their email. If they are not responding, it means that they don’t want their account anymore, so we delete/anonymize the user.

My question is this: there is a built in way of doing this? Or should I just code a custom solution?

Related: How to make users to explicitly agree to ToS

Posts: 1

Participants: 1

Read full topic

↧

Tag editor keyboard bug (mobile)

April 24, 2018, 12:01 am

≫ Next: Comparison of some platforms

≪ Previous: Reconfirm user email (and delete account if not)

@ChrisBeach wrote:

When adding a tag to a topic, the keyboard keeps minimising while typing, making the process infuriating and error prone! Would appreciate if this could be looked at

Tested on iPhone X, Discourse app and Safari

Posts: 5

Participants: 3

Read full topic

↧

Comparison of some platforms

April 24, 2018, 12:19 am

≫ Next: Discourse and GDPR?

≪ Previous: Tag editor keyboard bug (mobile)

@petter wrote:

I am part of a small community (max 200 members) that is looking to replace a NING forum with something new. I’ve used Discourse and am partial to it, but the following are up for evaluation: Spruz, SocialenginePHP, Socibd, phpfox, jamroom, Elgg, and Slack. Any thoughts on whether any of these other platforms are comparable in sophistication and usability to Discourse? (Aha…now I see - another useful feature from Discourse - some potentially interesting messages in “Your topic is similar to…” over on the right there…From the quick look I’ve had at these other programs they do not seem nearly as sophisiticated as Discou

Posts: 8

Participants: 7

Read full topic

↧

Discourse and GDPR?

April 24, 2018, 3:28 am

≫ Next: How to add page information

≪ Previous: Comparison of some platforms

@adrianbblk wrote:

Hi,

Anyone knows how the new GDPR affect discourse platform? There’s need some changes on the platform or/and the TOS and Privacy Policy?

Posts: 3

Participants: 2

Read full topic

↧

How to add page information

April 24, 2018, 5:24 am

≫ Next: Passing "Location" and "Web Site" from SSO?

≪ Previous: Discourse and GDPR?

@mattdamod wrote:

Hi, I’m having a total mental block here.

Can anyone please (with a cherry on top) tell me where to enter the page information for Google. This is currently what you see on Google when you google our forum

Meh!

I just can’t find where to add the description>

Posts: 4

Participants: 3

Read full topic

↧

Passing "Location" and "Web Site" from SSO?

April 24, 2018, 6:15 am

≫ Next: How to create login in discourse with out using sso feature

≪ Previous: How to add page information

@Denis_Heraud wrote:

I’ve been a’searchin’ but can’t find an answer to this question.

Is it possible to pass values to Discourse’s “Location” and “Web Site” fields in users’ profiles using SSO? Didn’t see those specific ones in the list of accessors.

Thanks!

Posts: 1

Participants: 1

Read full topic

↧

How to create login in discourse with out using sso feature

April 24, 2018, 6:54 am

≫ Next: Where to change the account_suspended email?

≪ Previous: Passing "Location" and "Web Site" from SSO?

@saurabh.shukla wrote:

I am creating react-native application and want to login in with out SSO. So how can I do this.

Posts: 2

Participants: 2

Read full topic

↧

Where to change the account_suspended email?

April 24, 2018, 7:08 am

≫ Next: Pictures don't upload well into tables because of the straight bar symbol

≪ Previous: How to create login in discourse with out using sso feature

@Bas wrote:

I can find many emails under /admin/customize/email_templates, but I don’t seem to be able to change the account_suspended email template.

Can someone point me in the right direction?

Posts: 3

Participants: 2

Read full topic

↧

Pictures don't upload well into tables because of the straight bar symbol

April 24, 2018, 7:10 am

≫ Next: Can we have an Edit Log please?

≪ Previous: Where to change the account_suspended email?

@biminiroad wrote:

Our forum uses tables to describe the function of digital synthesizer modules. In the first column, we use a picture. Because Discourse inserts a | between the file name and resolution, it breaks the link to the picture when using it in a column.

The solution is you have to delete the | symbol. Not a big deal, but also not intuitive for beginners.
Meter | Displays
---|---
![Meter-Pattern|108x108](upload://9DAOKRFuJI7XfTYXxm9fsalRgbM.png) | `Pattern`
Meter Displays

![Meter-Pattern 108x108](upload://9DAOKRFuJI7XfTYXxm9fsalRgbM.png)

vs.
Meter | Displays
---|---
![Meter-Pattern108x108](upload://9DAOKRFuJI7XfTYXxm9fsalRgbM.png) | `Pattern`
Meter Displays

Pattern

Thanks!

Meter	Displays
![Meter-Pattern	108x108](upload://9DAOKRFuJI7XfTYXxm9fsalRgbM.png)

Meter	Displays
	`Pattern`

Posts: 7

Participants: 3

Read full topic

↧

Can we have an Edit Log please?

April 24, 2018, 7:27 am

≫ Next: Broken emoji links

≪ Previous: Pictures don't upload well into tables because of the straight bar symbol

@AstonJ wrote:

A list of all edits viewable by Admin (perhaps sortable by member).

I think this would be useful for some very good reasons:

Help keep a lookout for edit-spam

Help see which members are being helpful (those adding tags, re-categorising Topics, editing titles, etc) (and so to see who would make good moderators)

Help ensure workload between Mods is equal

What should be logged?

Perhaps…

Post edits

Title edits

Re-categorisation of Topics

Appending/editing of tags

Post deletions

Maybe if time allows (or this proves a success), go further, and add logs for:

Topics that have been pinned/unpinned

Wikis (made/unmade)

Anything else that would allow an admin to quickly overview what’s been going on on the forum

I think this would be very useful for large companies/busy admins in particular

Posts: 7

Participants: 3

Read full topic

↧

Broken emoji links

April 24, 2018, 7:54 am

≫ Next: Discourse in an AWS context

≪ Previous: Can we have an Edit Log please?

@ThriceGood wrote:

Hello,

I have a standalone docker install of discourse running. But the emojis are failing to display because the link to them is a little strange. example:

https://https//community.ist.ac.at:443/images/emoji/twitter/kissing_closed_eyes.png?v=5

I have no idea why the extra https// is being added here.

Discourse is running a standard http set up, behind a https proxy that forwards requests from https://community.ist.ac.at to the discourse host machine port 80.

I have the DISCOURSE_HOSTNAME set as community.ist.ac.at

Any ideas?
Thanks

Posts: 3

Participants: 3

Read full topic

↧

Discourse in an AWS context

April 24, 2018, 9:41 am

≫ Next: Recurring 403 Forbidden error on posts with multiple images

≪ Previous: Broken emoji links

@jacobm241 wrote:

The problem I ran into was the version of Discourse that was available as an AWS image (aka AMI) did not seem compatible with the developer version we’ve been working on: Although I got it up and running, I was unable to do a restore…it kept throwing errors. Beyond that, it was shown as version 1.9.3-dirty and I couldn’t even do a backup/restore of the default install without errors being thrown.

So what are the options to use Discourse in an AWS context?
What are your recommendations?
What are the costs?
If we wanted to host ourselves (at AWS) and ensure it scales and is resilient by using such services as RDS and Elasticache (for Redis), with that work with these solutions?

Posts: 2

Participants: 2

Read full topic

↧

Recurring 403 Forbidden error on posts with multiple images

April 24, 2018, 10:19 am

≫ Next: Discourse 2.0.0.beta7 Release Notes

≪ Previous: Discourse in an AWS context

@MentalNomad wrote:

We have a recurring problem on large posts throwing a 403 Forbidden on attempts to edit the post.

We’re currently running v2.0.0.beta3+20 in Docker.

The posts in question are large, they contain a couple of images, a little formatting, and a couple of images. The pages are generated strictly using the Discourse editor features. On testing, I find that the problem is related to the images embedded.

For example, I have a large post created by someone else where I was asked to edit text. Even adding a single space to the post and saving throws the Forbidden, even if I’m logged in as admin.

If I enter the editor, copy-paste the entire contents, abandon the edits, and then do a reply, I can paste the entire things, make my edits, and save.

So the “save,” itself, works… however, if I go in to edit that post, even adding a single space, attempting to save the edit will throw the Forbidden.

As an experiment, I just chopped up a post into pieces, and tested which pieces are editable - the pieces which weren’t editable, I chopped down smaller, until they were editable an not throwing errors.

I took a long post which had four images, and ended up with 4 smaller pieces… each of which had one image. If a post has two images, it’s uneditable.

The images were originally inserted with simple image pasting; the editor content looks like this:

![kasse|356x220](upload://fkfT6T1qlWXrolyhjDMSedmhPL6.png)

All the posts - copied or edited - render the images just fine.

How can we troubleshoot this further or address the error?

Posts: 8

Participants: 3

Read full topic

↧

Discourse 2.0.0.beta7 Release Notes

April 24, 2018, 10:50 am

≫ Next: How to Prevent Users from Editing Topic Titles?

≪ Previous: Recurring 403 Forbidden error on posts with multiple images

@jomaxro wrote:

New features in 2.0.0.beta7

Moderation Improvements

We believe that moderating your Discourse community should be simple and easy to do. As such we’re always looking for ways to improve our moderation tools. In beta5 we added the following improvements to our moderation tooling:

Add option to delete all replies of flagged post

Add staff action log for post approvals

Staff can see the delete button on a post that was marked for deletion by the author

Tag visibility and usage

Tags are a great way to help organize topics on your Discourse site. By default tags can be applied by any user, and are visible to all. Now, using tag groups you can configure tags to be visible only to staff, and/or used only by staff.

It should be noted that if you previously used the “staff tags” site setting it has been migrated to the “staff_tags” tag group automatically. The “staff tags” site setting has been removed. See How to use staff tags properly? for more details.

image.png1051x437 14.8 KB

Better handling of load spikes

Out of the box Discourse can handle significant traffic without major tweaks. However, say you’re a company that runs an online server, your server goes down, and all your users flood a single topic on your Discourse site. This sudden flood of traffic can overwhelm your Discourse server with requests, slowing down the site for all. To help combat this we added an “anon view” trigger. If more than 3 requests within 10 seconds to a single topic queue for longer than 1 second, users will see the topic as if they were not logged in (anonymous). Anonymous views of a topic take significantly less resources, allowing Discourse to better handle the load spike without affecting the rest of your site.

Group Cards

Discourse has supported user cards since nearly the beginning. Now we also support group cards, allowing you to see the Group name, it’s users, as well as to join, request to join, or leave the group (as applicable).

image.png704x152 19.8 KB

Suppressing the word “likes”

In beta6 we we suppressed the word “likes” from posts. We’ve continued to tweak how likes look, and now display empty hearts for posts you haven’t liked. Posts you have liked will be pink, and your own posts will be grey.

Unliked:

Liked:

Own post:

Security Updates

This beta includes 5 security fix for issues reported by our community and HackerOne.

Prevent XSS when showing diffs

Do not show private topic title on /unsubscribed page

Escape HTML entities from topic title

Do not disclose topic titles on /unsubscribed page to unauthorized users

Santize tags when creating new topic via URL

Even more!

But wait, there’s more! We do our best to highlight new features and changes for you, but there’s always too many changes to detail. For a full list of new features, bug fixes, UX improvements, and more, be sure to review the Additional Features and Fixes listed below.

Plugin improvements

Solved

Alignment fixes

OAuth2 Basic

Allow both GET and POST fetch methods

Chronos

Default date format to auto-localized

Only show help text in advanced mode

Multiple bug fixes

Onebox

Improve Github commit onebox

Bug fix

Additional Features and Fixes

Click to expand

New Features

Allow safe mode to be disabled

Enable the Web Share Target API

Ctrl click on links allowed in preview

Track request queueing as early as possible

An API to help sites build robots.txt files programatically

Bug Fixes

Merging users failed when PM was sent to source and target user

Specify path for dosp cookie

Exclude topics from latest in /categories on refresh

Remove check for deprecated site setting

Deadlock when topic with auto close topic timers exceeds auto_close_topics_post_count.

Only show offline page when user is offline.

Calculate z-index for fixed usercard on preview

Message bus now properly detects log off

Better error message in GroupsController#add_members.

Remove auth cookie if we see InvalidAccess

Export download link was broken

Create upload record for exported csv files

Don’t break when posting invalid URIs

Localize everyone group name in default category permissions

Error when non-staff user edits their topic after a hidden tag is added to it

Strip emoji string from slug

Trigger group card on a post’s primary group click

Blacklisted crawlers could get through by omitting the accept header

Don’t allow spaces in ‘reply_by_email_address’ site setting

Missing Group#bio_raw attribute for group owners.

Sanitize click track links

Incorrect formatter used when logstash formatter is enabled.

Display user card background image

Don’t add diff classes more than once

Set notification level when changing post owner (#5616)

Do not notify last post editor if they mention themself

Missing action to trigger add group members modal for group owners.

Verify filtered tags when checking for category minimum required tags

Parameterize tag_id

Use new-password instead

Header nav should be tabbable and have focus state

UX Changes

Tag each autocomplete dialog so they can be hidden

Better github commit onebox

Display staged status on user summary page

Ensure topic progress indicator isn’t floating in very short topics

Don’t match emails in user selector in group add members modal.

Update placeholder for full page search

Require an extra click to open topic draft

Moved posts message links to the first post at the destination topic

Performance

Disables composer transitions in tests

Improve performance once logged in rate limiter hits

Only save site setting if values have been changed.

Posts: 1

Participants: 1

Read full topic

↧

How to Prevent Users from Editing Topic Titles?

April 24, 2018, 11:11 am

≫ Next: Two line breaks in a row not working

≪ Previous: Discourse 2.0.0.beta7 Release Notes

@biminiroad wrote:

The digital modular synth forum I’m setting up is built so that people will probably be doing a lot of cross referencing.

I used the heart of so and so’s module [link] in my module here and adapted it for my own purposes.

The problem is, users want to update their modules, and have gotten in the habit of changing the title of the original post to include My Module v2, My Module v3, My Module Deluxe v3.5 etc.

Doing this would seem to break any links that had referenced those modules.

Is there a way I can prevent our users from editing their topic titles after they’re created (or after say, 10 minutes, or a day?).

Thank you!

Posts: 4

Participants: 3

Read full topic

↧