I know it may sound extremely silly, but this is a big deal for me because I've got a ton of SEO juice pointing at specific posts.
I saw https://meta.discourse.org/t/redirecting-old-forum-urls-to-new-discourse-urls/20930/11 but I'm very hesitant to update my urls to point at a url structure of "thread/#ofpost_in_that_thread". That just feels like forum software lock-in to me, which is scary when I think of myself sitting here in 5-10 years wanting to migrate to different forum software, and having this brittle mapping of "original post_id" >> "discourse_url_structure">>"new forum software url structure".
Much prefer a world where even in the future I can just do "original post_id" OR "discourse_post_id" >> "new forum software url structure". Otherwise I'll always have to retain the Discourse URL mapping in order to correctly 301 links on external sites that I don't control.
Today I switched over some CSS customizations to the color scheme system. However, after doing so, I no longer see my custom background image for topic pages in the categories where I've defined such a background image.
This seems like a bug to me; perhaps someone can confirm?
I get this question alot and it's one I can't answer well. We have topics in varying degrees of blackness, alongside post/view counts in varying degrees of blackness and redness, and dates that are also in varying degrees of blackness and blueness.
WARNING: skipping "pg_type" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_authid" --- only superuser can vacuum it
WARNING: skipping "pg_attribute" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_proc" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_class" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_user_mapping" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_constraint" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_inherits" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_index" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_operator" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_opfamily" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_opclass" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_am" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_amop" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_amproc" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_language" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_rewrite" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_trigger" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_event_trigger" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_description" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_cast" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_enum" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_largeobject_metadata" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_namespace" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_conversion" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_depend" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_database" --- only superuser can vacuum it
WARNING: skipping "pg_db_role_setting" --- only superuser can vacuum it
WARNING: skipping "pg_tablespace" --- only superuser can vacuum it
WARNING: skipping "pg_pltemplate" --- only superuser can vacuum it
WARNING: skipping "pg_auth_members" --- only superuser can vacuum it
WARNING: skipping "pg_shdepend" --- only superuser can vacuum it
WARNING: skipping "pg_shdescription" --- only superuser can vacuum it
WARNING: skipping "pg_ts_config" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_ts_config_map" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_ts_dict" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_ts_parser" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_ts_template" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_extension" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_foreign_data_wrapper" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_foreign_server" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_foreign_table" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_default_acl" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_seclabel" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_shseclabel" --- only superuser can vacuum it
WARNING: skipping "pg_range" --- only superuser or database owner can vacuum it
WARNING: skipping "sql_implementation_info" --- only table or database owner can vacuum it
WARNING: skipping "sql_languages" --- only table or database owner can vacuum it
WARNING: skipping "sql_packages" --- only table or database owner can vacuum it
WARNING: skipping "sql_sizing" --- only table or database owner can vacuum it
WARNING: skipping "sql_sizing_profiles" --- only table or database owner can vacuum it
WARNING: skipping "pg_attrdef" --- only superuser or database owner can vacuum it
WARNING: skipping "pg_aggregate" --- only superuser or database owner can vacuum it
WARNING: skipping "sql_features" --- only table or database owner can vacuum it
WARNING: skipping "pg_collation" --- only superuser or database owner can vacuum it
WARNING: skipping "sql_parts" --- only table or database owner can vacuum it
WARNING: skipping "pg_largeobject" --- only superuser or database owner can vacuum it
Question - now when I paste YouTube video in Discourse editor, it embeds automatically YouTube way. How can I make it to embed my way? I wanna use own player that works with YouTube API. Example. Also, testing link to a video from Twitch:
When topic is very long and you scroll and scroll, your browser can start to lagg because of amount of content on page. Imagine if this topic about cat videos and there's several cat videos in each post. So there's can be thousand of flash objects on page if you scroll hard enought. I request new feature - auto delete content when you scroll long enought in one way. So there could be, let's say only 30 post shown on the page.
I am new to Discourse but I love it already. I want to change "category" to "city" or "college" I tried to edit language file and changed "category" in many places but it has no effect on the website. I restarted the servers after saving the new files. I edited both client and server files
So I created a mobile app with Cordova. Just basic cordova project and added some native plugins + edited the www/index.html to add Discourse website link.
Then I tried running the app on emulator/phone However, when I login with twitter/facebook. It opens the twitter/facebook, completes the login and then comes to screen
One thing I don't like about Discourse now that it doesn't have breadcrumbs. Let's say I read a topic in "feature" category. How can I go back? I press "feature" on top, list drops down and then I have to eyeball "feature" cagegory and press it. It's 2 clicks and one eyeballing. It's should be just one click, like this:
Breadcrumb is one of many semantic markup described in http://schema.org. Search engines rely on these markups to improve the display of search result.
This feature request is to add more things for crawler.
More microdata can be added into topic view, lists, category list and faq page. Maybe it can help for displaying topic list in the search engines.
Beyond that, add some content for crawler in some views.
Add category description in the category list.
Add link to category list in topic list page. There is no link to get there.
I am concerned about the way users have to go back to the Discourse install to sign up inorder to make comments on wordpress posts. My wish is that the same way the log in popup shows up when signing in or signing up within Discourse be the same way it happens when a user wants to comment. See the implementation in The Verge. This is so that when a user comes in to comment on the post, they don't need to leave the post.
I maintain a Discourse installation http://discuss.ropensci.org/. I am on v1.2.0.beta6 of Discourse, and there is an available upgrade (v1.2.0.beta8) - The page at /admin/upgrade is blank. Looking at chrome devtools, looks like there's a 500 error in requesting that page. Is this a problem with my installation?
The default site setting may not make sense for different language. I'll list my Chinese(zh_CN) forum site setting to illustrate:
min_post_length: 3, default: 20
min_topic_title_length: 4, default: 15
min_search_term_length: 1, default: 3
uncategorized_description: need translation
Chinese characters can express more per word which requires to change the default site setting anyway. If not to do so, Discourse can't even post moderator post since the character of some translation for that moderator post is less than 20. it's also suggested by @sam.
Basically, it can be done by load separate default setting file to override based on locale settings, like config/site_settings.<LANG>.yml
scss
It's also good to set default font size and font family based on locale! foundation/variables.<LANG>.scss do the work, but would look horrible. And have to respect the user's locale.
I'm on 1.2.0.beta6 but /admin/upgrade returns a 500 status.
Am I missing an obvious way to upgrade the plugins on Discourse?
Here's the log for the error:
env:
HTTP_HOST: forum.strats.co
REQUEST_URI: /admin/docker/repos
REQUEST_METHOD: GET
HTTP_USER_AGENT: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.111 Safari/537.36
HTTP_ACCEPT: */*
HTTP_REFERER: http://forum.strats.co/admin/upgrade
I have some badge queries I'd like to implement, but due to the fact they're using post_timings they're rather time consuming and the whole group of them will take about 3 minutes (currently, 11 badges, 17 seconds each).
Sidekiq indicates that backfill currently takes 2 minutes to complete with the currently implemented badges.
Am I likely to bump into any problems if I implement these new badges? (Assume that backfill is the only time these will run)
