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

Wp-Discourse Comments has error

$
0
0

Jason Wojo wrote:

I just installed the wp-discourse plugin and checked the box on a post to override the comments with Discourse. I have this error where the comments should be. Anybody else have this issue?

Warning: Invalid argument supplied for foreach() in /home/mysite/public_html/wp-content/plugins/wp-discourse-master/comments.php on line 32

Posts: 5

Participants: 4

Read full topic


Broken assets on meta.d

$
0
0

Bill Ayakatubby wrote:

Two assets are broken on meta.d: favicon.ico and default-apple-touch-icon.png

<link rel="icon" type="image/png" href="/assets/favicon.ico">
<link rel="apple-touch-icon" type="image/png" href="/assets/default-apple-touch-icon.png&#39;">

Assets loaded from the CDN are fine. The favicon exists on the CDN, but the Apple touch icon doesn't.

Also note the extraneous &#39; (apostrophe) in the Apple touch icon line.

Posts: 1

Participants: 1

Read full topic

Improvements to self-deleted posts

$
0
0

Jeff Atwood wrote:

We added the ability to self-delete posts very early after release. Using the delete function on a post replaces the body with a predefined self-edit of

(post removed by author)

... to elide the content of the post. You can still see the original post in the revisions, so nobody can hide weird or abusive content behind deletion.

But we've noticed it is a bit of a chore for moderators to see

(post removed by author)

... then check the revisions, find nothing untoward, and click the "real" delete button available only to staff. (This is still a soft delete, we have no concept of hard deletion yet.) Cleaning up topics of unneeded delete stubs helps keep topics concise, but it's also kind of busywork -- and self-deletion of posts is more common than we thought it would be.

So, we decided to improve things a bit on the self-deletion front:

  1. If a self-deleted post has no flags, it will automatically be deleted by the system after 24 hours*. The effect is exactly the same as a moderator manually deleting the post, except it's all automated now!

  2. For 5 minutes* after deleting a post, users will be able to change their mind and click 'undelete' to undelete the post. This simply reverts the post to the prior revision. Right now the only way to "undo" a delete is to manually edit a post back to its prior state... not exactly a good time. But with this change, for 5 minutes after the delete at least, it is a one-click operation to undo. To err is human, so easy undo is good!

* This will be an admin setting so you can configure it to 1 hour or 96 hours or whatever you like.

Posts: 11

Participants: 4

Read full topic

Is there any way to subscribe to categories

$
0
0

Chris Leong wrote:

I think it would be useful to be able to receive notifications when someone posts in a particular category

Posts: 9

Participants: 6

Read full topic

Potential feature: bitcoin / litecoin address

$
0
0

Pablo Corral wrote:

I've been navigating many forums, and people is using the signature as a place to share a litecoin or bitcoin wallet address (yes, those old phpbb and vbulletin forums). Also, I've noticed something similar in Reddit.

Suggestion:
Would be great if Discourse can take this as an opportunity to do something better.

  • Maybe a particular special field for litecoin and bitcoin address.
  • An easy way to copy and share it.
  • Maybe it is just a plugin, but I feel this would be more important than your own URL at the profile.

Posts: 2

Participants: 2

Read full topic

Internal Server error on some img tags

$
0
0

YOU wrote:

Internal Server error, upon following tags

<img src="http://www.test.com">
<img src="a.jpg">

Posts: 1

Participants: 1

Read full topic

Expanding to drive mailing lists

$
0
0

Bob Watson wrote:

If this is the evolution of the discussion forum - is it possible that a later plugin API (or even core feature) would be able to expand to driving discussion email lists to replace our crusty old listservs?

Posts: 24

Participants: 12

Read full topic

Forum activity email "from" truncates the board name

$
0
0

Gael wrote:

Good morning!

I have something strange on the weekly forum activity email.

My board name is: "I, Entrepreneur"
And the "from:" field only contains the letter "I": " I@imeuk01.ientrepreneur.me.uk"

What I would like is to have the "from:" field set to the full name of the board.
Maybe by dropping the comma? Where would I need to do that though?

Any idea how I can do that?

Thanks so much in advance!!

Gaël

Posts: 2

Participants: 1

Read full topic


Can't post a message on a fresh install 0.9.7.8

$
0
0

Julien Dumétier wrote:

I'm trying to post a new message without a category with some lorem ipsum text.

Here is the log i got:production_errors.log.txt (16.2 KB)

[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activemodel-4.0.2/lib/active_model/attribute_methods.rb:439:in `method_missing'
[RAILS_ROOT]/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/attribute_methods.rb:155:in `method_missing'

 undefined method `auto_close_hours' for #&lt;Category:0x00000009678348&gt;
  <exception-class>NoMethodError</exception-class>

Posts: 6

Participants: 3

Read full topic

Maybe some mistakes in official Discourse Ubuntu Install Guide

$
0
0

Roberto_Pezzali wrote:

I'm following the Official Guide to install Discourse on a total clean "ubuntu server".

Something is wrong with the Discourse user creation:

1) When I type sudo su - discourse I lose the shell... I must press CTRL + X to recorver the shell
2) I have always to type source ~/.rvm/scripts/rvm before every command or I have this error "RVM is not a function, selecting rubies with 'rvm use ...' will not work."

Maybe some changes in these days?

Posts: 13

Participants: 5

Read full topic

Please visit our Discourse Forum! (Directory)

$
0
0

F. Randall Farmer wrote:

I know I'd like to visit various new Discourse servers once in awhile as they come up. As you'd like a visitor or two, please post your URL here and a description of the purpose of your site and any other notes...

So far, the public Discourse servers I know about are:

Posts: 94

Participants: 70

Read full topic

Uploading images from mobile device

$
0
0

David García-Navas wrote:

So, could we upload an image stored on our Android phone or iPhone?
I only see this:

...but how do i drag or paste on a little mobile device?
Is it a planned feature?

Posts: 1

Participants: 1

Read full topic

Thin configuration on CentOS

$
0
0

Dev wrote:

Can somebody share the steps required to get Thin and Discourse running on CentOS?

I followed and completed the installation steps for Discourse on Digital Ocean
and official install guide on GitHub and everything completed with success. But then Nginx started giving 502 error and I figured is because of lack of Thin installation. I installed thin as a discourse user, however, I don't think it is running as seen in the output from "netstat -tulpn".

How do I make sure Thin is installed correctly and how do I configure correct rights for www-data on CentOS?

Posts: 2

Participants: 2

Read full topic

Vagrant error :NFS is reporting that your exports file is invalid

$
0
0

Hunter wrote:

Hello I am trying to get stated with Discourse development, and am having a Vagrant error that google hasn't been able to shed any light on. I asked about it on stack overflow but so far haven't had any responses. Running Vargrant gets me the error:

NFS is reporting that your exports file is invalid. Vagrant does this check before making any changes to the file. Please correct the issues below and execute "vagrant reload":

Can't open /etc/exports

I don't have a /etc/exports folder, and manually generating one led to Vagrant throwing this monster of an error message:

/Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/hosts/bsd/host.rb:146:in read': Is a directory - /etc/exports (Errno::EISDIR) from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/hosts/bsd/host.rb:146:innfs_prune' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/synced_folders/nfs/synced_folder.rb:68:in cleanup' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builtin/synced_folder_cleanup.rb:24:inblock in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builtin/synced_folder_cleanup.rb:22:in each_key' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builtin/synced_folder_cleanup.rb:22:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/providers/virtualbox/action/prepare_nfs_valid_ids.rb:12:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:118:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/providers/virtualbox/action/prepare_forwarded_port_collision_params.rb:30:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builtin/env_set.rb:19:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builtin/provision.rb:52:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/providers/virtualbox/action/clear_forwarded_ports.rb:13:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/providers/virtualbox/action/set_name.rb:19:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/providers/virtualbox/action/clean_machine_folder.rb:17:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/providers/virtualbox/action/check_accessible.rb:18:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:95:inblock in finalize_action' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builder.rb:116:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/runner.rb:69:inblock in run' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/util/busy.rb:19:in busy' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/runner.rb:69:inrun' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builtin/call.rb:51:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:95:in block in finalize_action' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builder.rb:116:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/runner.rb:69:in block in run' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/util/busy.rb:19:inbusy' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/runner.rb:69:in run' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builtin/call.rb:51:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:95:inblock in finalize_action' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builder.rb:116:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/runner.rb:69:inblock in run' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/util/busy.rb:19:in busy' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/runner.rb:69:inrun' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builtin/call.rb:51:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builtin/config_validate.rb:25:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builtin/call.rb:57:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builtin/config_validate.rb:25:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:95:in block in finalize_action' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builder.rb:116:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/runner.rb:69:in block in run' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/util/busy.rb:19:inbusy' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/runner.rb:69:in run' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builtin/call.rb:51:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/providers/virtualbox/action/check_virtualbox.rb:17:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builder.rb:116:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/runner.rb:69:in block in run' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/util/busy.rb:19:inbusy' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/runner.rb:69:in run' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/machine.rb:147:inaction' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/commands/reload/command.rb:37:in block in execute' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/plugin/v2/command.rb:193:inblock in with_target_vms' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/plugin/v2/command.rb:191:in each' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/plugin/v2/command.rb:191:inwith_target_vms' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/commands/reload/command.rb:36:in execute' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/cli.rb:38:inexecute' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/environment.rb:484:in cli' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/bin/vagrant:127:in' from /Applications/Vagrant/bin/../embedded/gems/bin/vagrant:23:in load' from /Applications/Vagrant/bin/../embedded/gems/bin/vagrant:23:in'

So I deleted it which returned the original error when rerunning vagrant. I am on a Mac (OS X 10.6.8). Does anyone know how to fix this? I tried searching for the original error message and all I found was the a few repositories containing the Vargant source code that throws it. Also the blockquote button isn't working for me.

Posts: 1

Participants: 1

Read full topic

Category not listed under parent category

$
0
0

Dale-Kurt Murray wrote:

I have created a Category with three (3) sub-categories

Tablets / Smartphones
- Windows Phone
- iOS
- Android

Editing the iOS category the parent category displays (no category)

When editing the Android category works fine and the iOS is not listed.

Is this a bug or did I do something wrong?

Posts: 1

Participants: 1

Read full topic


Install error: 'require' no such file to load rubygems

$
0
0

Dev wrote:

Hello,
I am trying to install Discourse on Ubuntu 12.04 and I have run all the steps upto "RUBY_GC_MALLAC_LIMIT" in the official install guide. However, I am now running into following error.
Any help will be appreciated.

Posts: 5

Participants: 2

Read full topic

</script> Tags could break revision history

$
0
0

YOU wrote:

</script> tags could break revision history (another internal server error)

Try to see edit history of this post or following post.

Posts: 1

Participants: 1

Read full topic

Anonymous posting mode

$
0
0

WinRAR wrote:

Could we get the anonymous posting mode turned on (preferably on certain "categories"), if the forum administrator decides to?

Or at least, allowing logged in members to post anonymously (forum administrators can still ban that username, but the post will appear as anonymous to every other members).

That'd be sweet.

Posts: 10

Participants: 7

Read full topic

1 Billion Rows BREAKS stuff

Provide more settings to be overridden in GlobalSetting

$
0
0

Dan Porter wrote:

I used to use

openssl_verify_mode  => 'none'

for my SMTP config in discourse. Now, with the settings being passed through from that of GlobalSetting, I am reluctant to make changes in favour of this centralised (or not wink) configuration file.

It would be cool if discourse added a few more (or possibly all) settings for any module that uses GlobalSetting, which doesn't necessarily need documented in the default discourse.conf.

Posts: 3

Participants: 2

Read full topic

Viewing all 60721 articles
Browse latest View live




Latest Images