@1c7 wrote:

1. A little backgroud

Hi, I am Ember.js newbie, I have a bit experience with Ruby on Rails (1 years+)
I been looking Discourse source code.

2. Curious why Discourse put Ember & Rails code together?

what’s the benefit of this? what’s the downside?

3. Anyone can explain? Thank you very much!

I already done my homework, search on this forum, so far I haven’t found anything on this topic.

Thanks again~

Posts: 2

Participants: 1

Read full topic

@Stranik wrote:

Hi. Where can I get acquainted, how information is stored in the Wiki post?

For example, I am interested in this question. There is a Wiki post:

We see 14 changes over time.

Each time a change is made, a separate copy is created in the database and then compared to the output. In our case we have 14 copies of the post (with different changes), or is the information stored in some other way?

Similarly, there is a question about displaying answer edits (not in the grace period).

There as the same are created a complete copy of the posts, or as something else. The question itself is about the size of the base. (In this case, we have a size in the database 14 times more than the original post?)

Posts: 2

Participants: 2

Read full topic

@Tungki wrote:

Hello i just installed discourse
my site is https://forum-id.com/

But when you try to click “Top” Button you see there a broken Timestamp, such as “Year BBB 17, TTTT” how can i fix this?
i use Indonesia localization

Posts: 7

Participants: 3

Read full topic

@_vincent wrote:

Hi,

I’m currently trying to rebuild my container, which desperately fails:

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LANG = "fr_FR.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").

The first time, I got this message:

les valeurs de lc_collate de la base de données « postgres » ne correspondent pas : ancien « en_US.UTF-8 », nouveau « fr_FR.UTF-8 »

Échec, sortie

-------------------------------------------------------------------------------------

UPGRADE OF POSTGRES FAILED

You are going to need to export your data and import into a clean instance:

In containers/app.yml: Change "templates/postgres.template.yml" TO "templates/postgres.9.5.template.yml"

Run ./launcher rebuild app again

When your instance is running:

Run ./launcher enter app

Run apt-get remove postgresql-client-9.5

Run cd /shared/postgres_backup && sudo -u postgres pg_dump discourse > backup.db

Undo the base_image in your container config

Run: ./launcher stop app

Run: sudo mv /var/discourse/shared/standalone/postgres_data /var/discourse/shared/standalone/postgres_data_old

Run: ./launcher rebuild app

Run: ./launcher enter app

Run: cd /shared/postgres_backup

Run: sv stop unicorn

Run: sudo -iu postgres dropdb discourse

Run: sudo -iu postgres createdb discourse

Run: sudo -iu postgres psql discourse < backup.db

Run: exit

Run: ./launcher rebuild app

I’m trying to follow the instructions but it keeps failing, apparently due to the previous locale error.
I did locale-gen the correct locales.

Help anyone?

Thanks!

Posts: 2

Participants: 2

Read full topic

@adamepcc wrote:

Is it possible to block/suspend users or prevent them from logging in until they accept a new privacy policy, in effect putting them back in the state they were in as they were creating an account but without resetting their levels of trust or their previous posts?

I’ve looked through the admin settings, but I cannot see how to do this. Apologies if I’ve missed something.

Thanks!

Posts: 1

Participants: 1

Read full topic

@aschrijver wrote:

I am admin of community.humanetech.com and just changed my profile picture from default to an uploaded jpeg image. It seemed to work fine, but when I went to the main page there were no changes and all topics were shown as unread. What happened was that my account had changed and was now named ‘anonymous10’. I had no access to my real account anymore (which was unchanged).

So I logged out, logged in again, and there was no change to the profile picture. So I did the same action again. My previously uploaded photo was still present, and after just changing the option to this setting and pressing ‘Save’ everything worked fine (no cache refresh needed as well).

But I thought I’ll mention it anyway.

I am using FF 60.0 on Ubuntu 16.04

Posts: 2

Participants: 2

Read full topic

@Robin_Fisher wrote:

Hi guys,

We use Discourse over at zenAud.io community and I really want to make a poll that allows users to add their own option to vote for like Facebook does:

Screen Shot 2018-05-16 at 14.31.44.jpg982x618 104 KB

Could this be an option for a future update?

Posts: 4

Participants: 4

Read full topic

@reinchek wrote:

Hi all,
i’m embedding the possibility to post discourse’s topic from external site through javascript. For this i need to generate an user’s api key, but if user isn’t logged on discourse is needed to shown a login form to do it. Only after the login (javascript) creates the new topic through REST.

Posts: 1

Participants: 1

Read full topic

@Johani wrote:

This is a theme component that will allow you to easily add links the hamburger menu.

---

Repository link
https://github.com/hnb-ku/discourse-custom-hamburger-links

Preview:
https://theme-creator.discourse.org/theme/Johani/hamburger-links

---

Samples

Desktop

Capture.PNG1896x979 179 KB

Mobile

Capture2.PNG740x1398 99.8 KB

---

Settings

You add links via comma delimited values in this order:

Text,URL,Location

Text
is the name of the link that shows on the menu.

URL
is the path you want the link to have. You can use relative paths like

/tags/funny
or
/t/231

if you prefer.

Location
can have one of two values. Either the letter g or the letter f

Use “g” if you want the link to appear in the generalLinks section:

Capture3.PNG526x827 36.9 KB

or use “f” if you want the link to appear in the footerLinks section:

Capture4.PNG570x860 37.4 KB

---

How do I install this theme?

follow the official theme installation guide here:

Then add the component to your theme as a theme component and you’re all set!

Posts: 2

Participants: 2

Read full topic

@supermathie wrote:

Right now it’s possible for PMs to show up in Top Referred Topics - we should prevent that.

Posts: 3

Participants: 2

Read full topic

@arengo wrote:

I need remote team Discourse Developers to develop my new project. I consider the option of hiring offshore specialists, but I doubt the choice of the country. Maybe someone has encountered, and can give feedback, or knows companies with which already have a positive experience or even constant cooperation

Posts: 2

Participants: 2

Read full topic

@nixie wrote:

None of the plugins on my site are working after I resized my droplet

I did ./launcher rebuild app - twice - but made no difference.

I tried disabling and enabling the plugin - still no difference.

What could be wrong?
There are tons of errors in site.com/log

Example error from log

Error: Could not find module discourse/lib/push-notifications imported from discourse/plugins/discourse-push-notifications/discourse/initializers/setup-push-notifications

Posts: 8

Participants: 3

Read full topic

@pfaffman wrote:

Uploads now generate Markdown like:

![square-abc-640|500x500](upload://md1vKocQHFmG9K4vpC57cKCTQv9.png)

script/import_scripts/base/uploader.rb does this:

    def embedded_image_html(upload)
      image_width = [upload.width, SiteSetting.max_image_width].compact.min
      image_height = [upload.height, SiteSetting.max_image_height].compact.min
      %Q[<img src="#{upload.url}" width="#{image_width}" height="#{image_height}"><br/>]
    end

Should this be updated to use the new format? If so, should it call whatever it is that generates the new format (and if so, where do I find that?) or just do it like

    def embedded_image_html(upload)
      image_width = [upload.width, SiteSetting.max_image_width].compact.min
      image_height = [upload.height, SiteSetting.max_image_height].compact.min
      upload_name = upload.url.split('/').last
      %Q~![#{upload.original_filename}|#{image_width}x#{image_height}](#{upload_name})~
    end

Posts: 1

Participants: 1

Read full topic

@Drew_Warwick wrote:

If I click the wrench at the bottom of a topic, and select Topic Timer, I see the option for auto-delete even though I don’t have the appropriate permissions to delete a topic. (Weirdly, it even lets me schedule the auto-delete and put a timer on the thread, but when the timer expires, nothing happens). The auto-delete option shouldn’t show up in Topic Timer for users who don’t have the appropriate permissions to use it.

Posts: 1

Participants: 1

Read full topic

@Drew_Warwick wrote:

My ideal workflow for closing threads is:

1. Lock thread
2. Add post explaining why it was locked
3. Leave it listed so users see why it was locked instead of it mysteriously disappearing
   • Otherwise it may look like we’re just closing topics we don’t like without good reason
4. Unlist thread a day later
   • Duplicates don’t clutter search
   • Inappropriate topics can’t be dug up

Manually unlisting the thread a day later is inconvenient. I could use the auto-delete timer, but generally we prefer unlisting over deleting. Even if the OP misses the 24 hour window before the thread gets hidden, we still want them to be able to get back into the thread with the link we sent them in feedback PMs so they can:

• Copy info from their thread that wasn’t posted in the topic they duplicated and add it there
• Review a thread of theirs that got closed and reason about it with a level head

Since deleting a thread isn’t a great option in our case, it’d be nice if forum mods/admins could use the Topic Timer to schedule the topic to be unlisted automatically in addition to the existing options.

Posts: 1

Participants: 1

Read full topic

@Simon_Cossar wrote:

The Security tab on the category edit modal is used to control both the visibility of categories and what users can do in a category. This is done by defining category permissions that associate a group name with an access level. The default permission for a new category is that the group everyone can Create/Reply/See. This means that all users on your forum, including anonymous users, have access to the category. You can change this state by adding or removing permissions.

Screen Shot 2018-05-16 at 10.55.18 AM.png1388x418 26.8 KB

Adding permissions

To add a permission, click the Edit Permission button. This will open two dropdown fields. The first field is used to select the group to add the permission for, the second field is to select the permission level.

On a new forum, the group dropdown will have the everyone, admins, staff, and moderators groups, as well as a group for each of the four Discourse trust levels. If you have added a custom group to your forum, that group will appear in the group dropdown menu.

The permission level dropdown lets you select between three levels of access: Create/Reply/See, Reply/See, and See. Create is the permission to create a topic in the category. Reply is the permission to post in a topic. See is the permission to see the category’s content. Combining groups with permission levels gives you control over what users can do in a category.

Removing permissions

To remove a permission, click the Edit Permissions button. A blue ‘x’ button will appear next to the existing permissions for the category. Click the ‘x’ to remove the permission.

Category visibility

If a group cannot See a category, that category will not appear in the user interface for its members. Members of groups who have access to a category that can’t be seen by everyone will see a padlock icon next to the category’s badge.

A group that can See a category, but can’t Create or Reply will have the category badge and content displayed normally in their user interface. On the category’s page, the New Topic button will be greyed out and disabled for them. The category will also not be available for them in the composer’s category dropdown menu. Users who can only See a category can still receive notifications for the category and have the category’s content included in their digest email.

Permissions for Admins and Moderators

Admins are always able to Create/Reply/See in a category. Moderators do not have default access to a category - for moderators to access a category they must be included in a permission rule. Moderators are in the staff and moderators groups, they can also gain access to a category by being a member of a custom group.

The difference between the everyone group and Trust Level 0

The everyone group is made up of all users, including anonymous users. The Trust Level 0 group is all users who have created an account and are logged into your forum. You can disallow anonymous access to a category by setting the group to trust_level_0 instead of everyone.

Examples:

Limiting access to a category to members of a custom group

Screen Shot 2018-05-16 at 10.17.39 AM.png1404x480 30 KB

Allowing all users to see a category, but only group members to create content

Screen Shot 2018-05-16 at 10.50.22 AM.png1400x532 33.7 KB

Allowing all users to reply in a category, but only group members to create topics

Screen Shot 2018-05-16 at 10.52.14 AM.png1404x538 35.3 KB

Allowing all users except anonymous users to access a category

Screen Shot 2018-05-16 at 1.38.00 PM.png1390x432 24.2 KB

Posts: 1

Participants: 1

Read full topic

@Jeff_Vienneau wrote:

These seems to only occur on my site so I’m hesitant to report it. When I edit a post or reply the left arrow does not allow me to move the caret.

My version is 1.9.7 stable with following plugins:

Name	Version	Enabled?
discourse-details	0.4	Y	Settings
discourse-events	0.1	Y
discourse-locations	0.1	Y
discourse-narrative-bot	0.0.1	Y	Settings
discourse-nginx-performance-report	0.1	Y
discourse-presence	1.0	Y	Settings
docker_manager	0.1	Y
lazyYT	1.0.1	Y
poll	0.9	Y
strava_onebox	1.0	Y
trailforks_onebox	0.3	Y

As I type this on this instance of discourse left arrow is working.

Posts: 10

Participants: 4

Read full topic

@AstonJ wrote:

I definitely think All is more useful and meaningful than today - `today’s stats won’t really mean anything unless you look at them around the same time every day…

Posts: 9

Participants: 4

Read full topic

@qianqiang wrote:

Can I update the login status of the forum asynchronously after I log in at the main station?

Posts: 1

Participants: 1

Read full topic

@jomaxro wrote:

New features in 2.0.0.beta10

New admin dashboard

The first release of our new admin dashboard is ready to go! The new dashboard highlights community health statistics in easy to review graphs, as well as additional activity metrics, top referred topics, trending internal searches, and more. Need a statistic from the old dashboard? You can still access it from the link at the bottom.

The new dashboard is just v1, we have more to add going forward. Learn more and share your feedback in:

image.png1701x1652 269 KB

Mobile navigation cleanup

We’ve improved the mobile navigation section to better scaled with different size devices, removing the “jumbled buttons” that previously existed.

Improved email handling

• Keep EmailLogs records without a reply_key for 90 days by default.
• Clearer error message when receiving a reply to an old notificaiton

Improved username change support

• Update avatars in posts and revisions when user gets renamed
• Replace username in notifications when user gets renamed
• Update mentions and quotes when user gets merged

Keep formatting when quoting

We’ve taken advantage of improved HTML to Markdown support to keep most formatting when quoting formatted content

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

GitHub Linkback

• Allow all user repositories wildcard

Data Explorer

• Improve UX when no queries exist
• Prevent creation of query without name

Spoiler Alert

• Remove spoilers in embedded comments

Assign

• Add “Unassign All” button to user’s assigned topics view
• Bug Fix

Discourse WordPress Plugin

• Fix timezone offset that is used for displaying Discourse comments published-at date

Patreon

• Bug Fix

Additional Features and Fixes

Click to expand

New Features

• New ‘staged’ users list for admins
• Add a 30 seconds grace window for 2-factor token checks
• Hide plugins that ship with core from plugins panel
• Allow plugins to modify class statics
• New site setting min_flags_staff_visibility
• Display description for group cards
• Add profile_background fields into SSO
• Add plugin outlet for desktop (live) notifications area
• Push notifications for Android

Bug Fixes

• Infinite loading was broken on group activity posts/mentions pages
• Do not replace hashtags in URLs
• Do not replace twitter handles in URLs
• PostOwnerChange should update ‘topic.last_poser’
• Don’t purge unactivated users with a message
• Keep ‘<kbd>’ formatting when quoting posts
• Puts the datepicker on it’s own line on mobile device in the feature topic modal
• Changing owner of deleted reply didn’t work
• Don’t use PMs in Incoming Links reports
• Tags in a ‘visible by everyone but usable only by staff’ group weren’t visible by everyone
• UTF-8 encode feed response body
• Message bus had corrupt internal state for first 30 secs
• Copyedit plugin to feature for built ins
• Allow editing post that belongs to deleted topic
• Transaction in UserAnonymizer prevented avatar from updating
• Changing tag group privacy setting was not consistent
• Automatically in/decrement topic_tags.pm_topic_count
• Search icon is rendered outside of tag-selector filter-input
• Scrub all settings that has ‘_secret’ in name
• Scrub secret setting values from logs
• Automatic group membership when using SSO
• IncomingLink: do not log IP of logged-in users
• Makes report description optional
• Username update should ignore revisions without raw
• Update search index after renaming user within posts
• Update avatar in oneboxed posts when renaming user
• Anonymizing user didn’t replace uploaded avatar in posts
• Only unstage staged users
• Allow user quotes in HTML digest emails
• Staff members should see all tags
• Always unstage users when they log in
• Redirect users after signing up with a social login when using SSO provider
• Remove unneeded escape when building a Quote
• Redirect users after signing up using SSO provider
• Redirect to sso_destination_url after account activation
• Show a json api response when deleting a user with posts
• Format posts for embedded comments as we do for emails
• Clicking a group mention on mobile was 404ing
• Always update bounce score (instead of doing it once per day)
• Supports user/group mentions and category hashtags when quoting posts
• Prevent theme uploads from overwriting existing variables
• De-duplicate push subscriptions - ensure unique user/key
• Automatically add user to groups after updating email address
• Temporary redirect for service worker scripts
• Better handling of invite links after they are redeemed
• Use default locale for flag reason
• Deprecate invite_passthrough_hours setting
• Replace username in deleted posts when user gets renamed
• Exact matching should also match on title
• Add context for deactivated user logs
• Regenerate vapid keys when the public key bytes is blank
• Retrigger notification when a topic is recategorized.
• Topic search wasn’t working for unlisted topics
• Retrigger search scoped to a topic if topic changes.
• Search term scoped to topic should be highlighted in widget dom era.
• Don’t downcase group name.
• Incorrect query when removing a group owner.
• Decorate user stream should include element
• Proper category >` subcategory order in List-Id description header
• Revert to es5 function syntax

UX Changes

• Show footer on groups pages
• Don’t show ‘auto delete’ option for TL4
• Add link to /groups from Admin>Users
• Show a message when more than 30 site settings matches the current filter
• Show the counts when displaying only overridden settings
• Show 30+ count when more than 30 site settings matches the current filter
• Show an envelope icon when a badge is used in messages
• Remove obsolete warning about changing post ownership
• Show close date on automatically closed polls
• Add proper titles to topic navigation links in hamburger menu.
• Don’t set width to auto for select kit combo box.
• The first sentence in the line had a period but the second did not.
• Display site settings shortcut for poll and discourse-nginx-performance-report.
• Improved performance of emoji dialog

Performance

• Defer user notifications
• Use cached reports for dashboard if available
• Remove N+1 query.

Posts: 1

Participants: 1

Read full topic