i have different content types with a image.
Do I create a new field in each content type or do I always use the same one?
It's a matter of not overloading the database
Weekly office hours
Bring your questions to our weekly virtual office hours, every Wednesday. Everyone is welcome.
Recent topics
Posted 6 days 7 hours ago by (Irina Zaks) in How-To and Troubleshooting
Posted 6 days 18 hours ago by (onyx) in How-To and Troubleshooting
Posted 6 days 22 hours ago by (NormPlum) in How-To and Troubleshooting
Posted 1 week 17 hours ago by (bartl) in How-To and Troubleshooting
Posted 1 week 20 hours ago by RS Snyder (theflightrs) in How-To and Troubleshooting
Recent comments
On D7 project we are using openid_connect. We need to have similar functionality for Backdrop CMS, sooner rather than later.
OpenID?
Why not insert the script using a custom block at the very top of the page? Who said that it won't work correctly if you don't place it in the <head>? Especially when the question...
Google tag and event snippet on the conversion page
You can use https://statichost.host for hassle free static experience.
Generate a Static Site
that was the first thing i tried, but thanks. i cannot see css file changes without clearing the css/js cache. for that reason i have been adding css snippets (<style> tags) into my...
Bandwidth optimization settings
I asked ChatGPT and the answer helped me to place a conversion tracking tag in the Head section of a specific page, like this: code in template.php function my_theme_preprocess_page...
Comments
Hi @rafke
Welcome to Backdrop CMS. There are different schools of thought on this topic. Some create new fields for each content type.
Many like myself have what I consider to be a more pragmatic view:
If the purpose of the field is the same then there is a strong benefit to re-use the field as it will then be much easier to create a View across multiple content types. However, if they are a different purpose, then it makes sense to create new so the field machine name can reflect the purpose.
This is often a matter of opinion, and I have given my opinion (that is shared by others, but not all in the community) with my reason for doing so.
From the "dev" point of view, keep in mind that fields have two types of settings: global settings and instance settings. Instance settings are those that apply only to a specific content type (for example whether the field is required). Global settings apply to a field in ALL content types (for example, cardinality).
Change a global setting for a field will change it in ALL content types. That should help you decide whether you want to use the same or different fields in different content types. If the global settings will be the same everywhere, then use the same field. If not, go for different fields.
When I was a "newbie" in Drupal I often inadvertently changed a global setting for a field (e.g. the cardinality number), creating a lot of issues since I didn't want to change that for every content type. This is not uncommon.