New columns in directory (/users)

[Anshul_TM (Anshul Kushwaha)]

Hello everyone,

I want to add a few columns in the directory items model. ( ‘Solutions’ and ‘Points’ )
I was able to modify the code for the model and templates directly, but how can I achieve this via a plugin ?

If not possible via plugin, is it possible to use my own github repo ( with these changes ) instead but somehow continue to get updates from Discourse repo.

Thanks

[itsbhanusharma (Bhanu Sharma)]

I’m Not able to understand the exact usecase but definitely adding some columns can be achieved via plugins!

You may start writing a plugin using the official Guidelines and Then use it in order to ensure You get official updates.

Here is Some Help:

Developing Discourse Plugins - Part 1 - Create a basic plugin

Building a plugin in Discourse can be really simple, once you learn a couple of quirks. The goal of this post is to create a skeleton plugin and introduce you to the basics. Your development environment Make sure you have a development environment of Discourse running on your computer. I recommend you use the appropriate setup guide and come back when you’re done. plugin.rb Use GitHub - discourse/discourse-plugin-skeleton: Template for Discourse plugins to create a complete discourse p…

[Anshul_TM (Anshul Kushwaha)]

Hey @itsbhanusharma, thanks for the link.
I’ve gone through the Beginner’s Guide, but couldn’t find DB modifications in it.

You’ve any plugin in mind which does something similar ?

[itsbhanusharma (Bhanu Sharma)]

Have You gone through the whole series?

I’d have a look in the Plugin repo to find if there is something.

EDIT: have a Look Here maybe this Helps!

Create custom db table and fields from plugin

Hi everyone, I’m working on developing a new plugin and I need to store some values in the database but I do not want to modify the discourse base system in any fashion. I’ve read through the beginners guide on plugin development and I did not see anything addressing this, essentially what i need is a table that has two fields that reference a single user that links another user or multiple users. database → plugin_users → column 1 would be user_id and column 2 could be a comma separated list o…

[gdpelican (James Kiesel)]

FWIW I’ve decided to go this route with a plugin of mine, where PluginStoreRow and CustomFields didn’t qqquite cut it on their own. Caveat emptor You should be trying really hard not to do this - It’s not recommended behaviour to modify the database from within a plugin, but it can be done unobtrusively in small, additive doses (I’d say you never for any reason want to remove or change existing columns)

Here’s how I did it:

• Write a migration in the plugin which modifies the DB

# plugins/my_plugin/migrations/add_column.rb
class AddColumn < ActiveRecord::Migration[5.1]
  def change
    add_column :post_custom_fields, :my_column, :jsonb, default: {}, index: true
  end
end

NB: it’s a good idea to namespace your column with the name of your plugin, since adding a column with a generic name like ‘value’ could end up actually existing in the future and then you’d have a real problem.

• When the plugin is loaded, check to see if the migration has been run, and if not, run it

# plugin.rb
if !PostCustomField.new.respond_to?(:my_column)
  require Rails.root.join('plugins', 'my_plugin', 'migrations', 'add_column')
  AddColumns.new.up # <-- this runs the migration
end

• The first time you run rails s or rails c after this, you should see the following:

add_column(:post_custom_fields, :my_column, :jsonb, {:default=>{}, :index=>true})

that means it worked! Subsequent boots of the app shouldn’t display this message.

• Important, don’t skip plz - Provide a method for users to clean up your database changes if they don’t want your plugin anymore. I did it with a rake task.

# plugins/my_plugin/tasks/remove_column.rake

# (I think there's a better way to do this, but this line works.)
# Essentially, we need the environment loaded so that ActionRecord::Migration is defined.
require File.expand_path(File.dirname(__FILE__) + '../../../config/environment'

desc "remove my_column from the database"
task "my_column:remove" do
  require Rails.root.join('plugins', 'my_plugin', 'migrations', 'add_column')
  AddColumn.new.down
end

Then, in your README, instructions on how to use it

This plugin adds a column to the database. If you want to remove this plugin and don't plan on using it again, perform the following steps:

- Enter your discourse container 
./launcher enter app
- Run the following command to reverse the database changes
bundle exec rake -f plugins/my_plugin/tasks/remove_column.rake -T
- Remove the 'git clone' line from your app.yml
- Rebuild your container
./launcher rebuild app

Note that dropping this column is permanent and irreversible for the data stored there..

As always, let me know if I’ve missed something or if this can be improved.

[spirobel]

لم أتمكن من العثور على استدعاء نشط لطريقة up في وثائق Rails Active Record.

AddColumns.new.up  

يبدو أن عمليات الترحيل تُنفذ عادةً عبر أوامر rake db:migrate وليس مباشرة بلغة Ruby.
لذا، يبدو لي أنه من الأفضل وجود مجلد migrate خاص بالإضافة، ثم إنشاء روابط رمزية منه إلى مجلد /discourse/db/migrate داخل ملف plugin.rb. بهذه الطريقة، يمكن استخدام بنية Rails الخاصة بالترحيل أيضًا في حالات التراجع. ربما يُضاف توضيح في ملف README الخاص بالإضافة حول كيفية التراجع عن التغييرات المحددة. يبدو أنه من الممكن التراجع عن ترحيلات محددة باستخدام أمر مشابه لهذا:

rake db:migrate:down VERSION=20100905201547

https://stackoverflow.com/questions/3647685/how-to-rollback-a-specific-migration
سأكون ممتنًا للحصول على بعض التعليقات حول هذا الأمر. كما أعتقد أنه غير مثمر الاكتفاء بالربط إلى حقول مخصصة. أريد استخدام Discourse لإنشاء قاموس صيني-إنجليزي، ولا يمكنني الاعتماد فقط على الحقول المخصصة لهذا الغرض.

[spirobel]

لقد قمت بإنشاء مولد هجرات ونماذج للإضافات: GitHub - spirobel/discourse at plugin_model_and_migrations · GitHub
أعتقد أن الطريقة المعروضة هنا للتعامل مع هجرات الإضافات ليست فكرة جيدة.