I have a model in a plugin. The model is Pfaffmananger::Server, the table is pfaffmanager_servers. For Reasons, I want to have custom fields for this model (I expect there to be ways that I want to extend the server data that are likely to be used only for a few instances and I don’t want a zillion …

[이미지] pfaffman: If I use pfaffmanager_server_id instead of server_id the migration fails because it can’t find server_id Did you also update the add_index call to point to pfaffmanager_server_id?

Thanks so much, David! [이미지] david: Did you also update the add_index call to point to pfaffmanager_server_id ? Yes. That could be my problem. I guess that’s the error message I should have included. And I can make the migration work with either field (though with pfaffmanager_server_id as …

[이미지] pfaffman: It doesn’t care what the index name is, does it? I don’t think so, no I think the second approach is probably the one to aim for (using pfaffman_server_id as the column name) I wonder if overriding this method may help: app/models/concerns/has_custom_fields.rb m…

Or maybe it’s this bit :thinking: app/models/concerns/has_custom_fields.rb main value.to_i when :json

Thanks so much! So Server.new.custom_fields_fk is pfaffmanager_server_id if I use pfaffmanager_serfver_id. So maybe I should use server_id and then override as you suggested above. It looks like refresh_custom_fields_from_db is trying to use the wrong names. I don’t quite understand what _custom_f…

Ha! You did it! Thanks so much. I switched it to server_id and then did this in my server.rb model: def custom_fields_fk @custom_fields_fk ||= "server_id" end As long as that’s going to override that only for this model and not break user_custom_field and friends I think I should be …

[이미지] pfaffman: I switched it to server_id and then did this in my server.rb model: Great! :tada: If you can think of a way to make it more generic then that would certainly be PR-welcome.

If something occurs to me I’ll let you know or submit a PR, but I have to think that a plugin that wants to use custom fields is pretty far out on the edge.

OM_fk_G. custom_fields_fk seemed so stupid that I assumed it was something that I meant to delete and had named it something stupid so I’d know it was safe to delete it later. It was later, so I deleted it. And then my specs failed. There was even a comment with a link to this topic in the code.

플러그인에서 HasCustomFields 사용

개발

david (David Taylor) 1월 18, 2021, 9:16오후 8

좋아요! 더 범용적으로 만들 수 있는 방법을 생각할 수 있다면, PR을 환영합니다.

글		댓글	조회수
Error: PG::UndefinedColumn. Custom field not creating column Support	4	1633	8월 11, 2021
Best convention for custom plugin DB data for 2021? Development	4	663	3월 17, 2021
User custom field with plugin Development	2	2064	5월 5, 2017
Custom field casting affected by recent update? Development	5	1269	8월 25, 2020
Plugin to validate a text type custom field value Development	1	100	9월 9, 2024

플러그인에서 HasCustomFields 사용

Related topics