Here are two of the most common questions we get from Drupal newcomers:
Because the answers are not easy to find, these kinds of questions can be confusing.
Here's a clear explanation of what happens when you delete a content type or field.
There are three questions to consider when deleting a content type:
The short answer to this question is, the nodes remain in the database. You can see the nodes listed in the Find Content admin page.
However, just because you can see them listed, does not mean you can open them. In fact, you can't; you get an error if you try.
The test content type that was just deleted had a test field (a field unique to the test content type) and the image field that comes with the Article content type. As you can see from the screen shot above, the image field is still there but the test field is not.
There are contributed modules that add features to content types such as AddToAny and Webform to name two. In order to add the features provided by the module to the content type, quite often you check a box on the module's configuration page. The module then stores that decision as a configuration setting in the database.
What happens if you delete a content type without telling the module that is no longer needs to do something to that content type? In order to answer this question, I'd have to test quite a few modules to see if the developers of those modules took steps in their code to accommodate a content type suddenly going away. I offer you this however, if you have a content type you want to delete and you have modules on your site that add features to content types, consider disconnecting the content type from these other modules before you delete it.
In order to delete a field, you must go the content type where the field resides and delete it, unless of course you are deleting a content type. We saw earlier what happens to fields when we delete a content type. The fields shared across multiple content types remained but the fields unique to the deleted content type were also deleted. This same logic applies when you simply want to delete a field.
If the field you delete is unique to a content type, then the field is gone from the database (that includes it's data). If you delete a shared field from, the field is removed from that content type along with the data unique to the contenty type.
If you find that you need to keep the data associated with the field but you need a different type of field for the data, you need to plan ahead.
Before you delete anything in Drupal, ask yourself how the "thing" you are about to delete is related to other things on the site. Is the content type related to existing nodes? Does the content have features managed by other modules? Has the field been used? If yes, will you need to save the data stored with the field?
Think things through before you delete.
Via Ostraining.com
Drupal Developer having 9+ year experience, implementation and having strong knowledge of technical specifications, workflow development. Ability to perform effectively and efficiently in team and individually. Always enthusiastic and interseted to study new technologies
Up till now, Front-end Developers have been working with a display layer that was originally introduced in Drupal 4.5, here’s how it worked...
The new Drupal Commerce module brings shop building to a new level by fully leveraging the functionalities of Drupal 7. On the other hand the great flexibility of Drupal Commerce provides so many options sometimes it's unclear how to implement the right solution.
Vào tháng 5 năm 2004, Google cài đặt một bộ lọc mới được giới webmaster gọi là Sandbox.
