I have seen this code in discourse_signatures plugin User.register_custom_field_type('see_signatures', :boolean) User.register_custom_field_type('signature_url', :text) User.register_custom_field_type('signature_raw', :text) if SiteSetting.signatures_enabled then add_to_serializer(:post, :user_signature, false) { if SiteSetting.signatures_advanced_mode then object.user.custom_fields['signature_raw'] else object.user.custom_fields['signature_url'] end } # I guess this should be the default @ discourse. PR maybe? add_to_serializer(:user, :custom_fields, false) { if object.custom_fields == nil then {} else object.custom_fields end } end In discourse national flags plugin User.register_custom_field_type('nationalflag_iso', :text) if SiteSetting.nationalflag_enabled then byebug; add_to_serializer(:post, :user_signature, false) { object.user.custom_fields['nationalflag_iso'] } byebug; # I guess this should be the default @ discourse. PR maybe? add_to_serializer(:user, :custom_fields, false) { if object.custom_fields == nil then {} else object.custom_fields end } end I am not able to understand what is add_to_serializer is doing. I checked in def add_to_serializer def add_to_serializer(serializer, attr, define_include_method=true, &block) klass = "#{serializer.to_s.classify}Serializer".constantize rescue "#{serializer.to_s}Serializer".constantize klass.attributes(attr) unless attr.to_s.start_with?("include_") klass.send(:define_method, attr, &block) return unless define_include_method # Don't include serialized methods if the plugin is disabled plugin = self klass.send(:define_method, "include_#{attr}?") { plugin.enabled? } end I understand that User.register_custom_field_type('signature_raw', :text) will register a custom field type to User object. But what is add_to_serializer doing? I am not able to understand, can you explain me in plain english?

[image] fzngagan: in my main plugin file, I am doing add_to_serializer(:basic_category, :default_tag){object.custom_fields[“default_tag”]} My custom fields aren’t getting saved to the db. does doing: add_to_serializer(:basic_category, :default_tag, false ){object.custom_fields[“default_tag”]} now work?

I had solved it that time by adding a function on :before_action event and converted the array to a delimited string and vice versa while retrieving. I didn’t actually dig into why an array couldn’t be stored as custom field out of the box.

So this might streamline the code potentially?

Yes it would if it worked in this case. I’ll try this in sometime and get back to you.

Poor you that must’ve been painful at the time :wink:

It was a sunday evening and curiosity took over. It was somewhat painful but fun. It was something that @pfaffman was trying to do. [image] merefield: Poor you that must’ve been painful at the time :wink: No pain no gain :wink:

[image] fzngagan: No pain no gain :wink: haha, so true! …

Hello, I have the same issue (custom_fields are submitted in the js console, but are not getting saved to the db) I used the add_to_serializer(:basic_category, :default_tag, false ){object.custom_fields[“default_tag”]} way in my main plugin file. Would you still reccomend this solution?

There are a lot of questions arising here. Custom fields of what first of all?

I’m working on a plugin to automate discourse group syncing with ldap. I added a custom field to Group (ldap_dn) to save the ldap group name in. I’m trying to retrieve the custom_field value from an input field that i added in the membership plugin-outlet and save that to the db to later use it. To do so i added this to my plugin.rb file Group.register_custom_field_type(‘ldap_dn’, :text) Group.preload_custom_fields<< “ldap_dn” if Group.respond_to? :preloaded_custom_fields if SiteSetting.groups_sync_enabled then add_to_serializer(:group_show, :custom_fields, false) { object.custom_fields } end I’m new to rails and ember so I’m not sure if there is another step I should be doing in order to get the custom_fields saved to the db, or where the problem lies.

What is this code add_to_serializer in all these plugins

Development

riking (Kane York) January 21, 2021, 9:58pm 27

This should absolutely not be the default. Not all user custom fields should be displayed to the user (e.g. see Staff Notes).

Topic		Replies	Views
Adding to user serializer does not work for the current user object Development	4	168	August 2, 2024
Category serializer modification is behaving differently in 2.4.0 Development	10	1456	August 27, 2019
Custom plugin: cannot add to serializer Development	1	661	March 17, 2021
Customizing create topic form to add more custom fields, what does add_to_serializer or register_custom_field_type do? Extras	2	6880	February 23, 2017
Overriding include_* methods in serializers Development	6	716	June 13, 2023

What is this code add_to_serializer in all these plugins

Related topics