Nouvelles colonnes dans le répertoire (/users)

Dev
1

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

2

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:

3

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 ?

4

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!

5

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. :warning: Caveat emptor :warning: 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.

6

Je n’ai pas trouvé cet appel explicite de la méthode up dans la documentation d’Active Record de Rails.

AddColumns.new.up

Il semble que les migrations soient généralement effectuées via les commandes rake db:migrate et non directement avec Ruby.
Il me semble donc préférable d’avoir un répertoire migrate dédié au plugin, puis de créer des liens symboliques depuis celui-ci vers le répertoire /discourse/db/migrate dans le fichier plugin.rb. De cette façon, l’infrastructure de migration de Rails peut également être utilisée pour les retours en arrière. Peut-être faudrait-il ajouter une documentation expliquant comment annuler les modifications spécifiques dans le fichier README du plugin. Il semble possible d’annuler des migrations spécifiques avec une commande comme celle-ci :

rake db:migrate:down VERSION=20100905201547

https://stackoverflow.com/questions/3647685/how-to-rollback-a-specific-migration
Je serais ravi de recevoir vos commentaires à ce sujet. Je pense également qu’il n’est pas productif de simplement faire un lien vers les champs personnalisés. Je souhaite utiliser Discourse pour créer un dictionnaire chinois-anglais. Je ne peux pas me fier uniquement aux champs personnalisés pour cela.

7

J’ai créé un générateur de migrations et de modèles pour les plugins : GitHub - spirobel/discourse at plugin_model_and_migrations · GitHub
Je pense que la méthode présentée ici pour gérer les migrations de plugins n’est pas une bonne idée.