- 🇺🇸United States mlncn Minneapolis, MN, USA
This is really important, and getting retroactive serial numbers needs to be documented at least if it cannot be made to work this way reasonably easily.
Thank you for this amazing and useful module.
I'm developing in my local machine then commit my changes and push it to a test server. So, when I tried to create a new (serial) field for an already exists content type I choose yes for (Start on existing entities) field setting. To make sure to apply the serial on all previous nodes.
But it didn't work when I imported my new field in my test server. It just created the field but didn't fill the old nodes with a serial number.
Steps to reproduce the problem:
1. Install Drupal on a local machine for example.
2. Install and enable (Serial field) module.
3. Create a new content type (page). (This content type already exists in Drupal standard installation).
4. Add new (page) node for a test.
5. Add new (serial) field to (page) content type.
6. On field settings step choose (yes) for (Start on existing entities) option.
7. Save and go to see the old node that we created before adding this field. It is work and getting a serial number filled.
The issue happen in the next steps now:
8. Push your changes to the test server. Or install a new Drupal site. and install and enable (serial) module.
9. Create a new content type (page) and add a couple of nodes.
10. Try to export the configuration of (page) content type from the old site and import it to this new site so you can get your (serial) field.
11. After import, you will see the (serial) field created successfully. But the serial value of the old nodes didn't fill with serial values.
To fix this I have to go to my field settings and just hit (save). Now the all old nodes have a (serial) value.
I believe it should create values for existing entities directly when importing the configuration without the need to click (save) manually in the field settings page of this newly created field.
Many thanks!
Active
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This is really important, and getting retroactive serial numbers needs to be documented at least if it cannot be made to work this way reasonably easily.