Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I debugged this a bit, and I see that Metatag stores it as a string. However, features_var_export()
(or something) is outputting it as an integer in the actual export file.
The workaround is to manually copy the actual value into the myfeature.features.metatag.inc
export file.
Comments
Comment #1
olofbokedal CreditAttribution: olofbokedal commentedCan confirm this. However, it seems like a float, not an integer.
The exported value looks like "5.3270xxxx8026E+14" when the stored value is "53270xxxx802596". I checked the value in the database, and it is indeed stored as a string. Don't know if this issue is caused by the metatag module or ctools or maybe features.
Comment #2
DamienMcKennaThis needs to be fixed.
Comment #3
Dave ReidSounds like features is messing up the value. There should be way to force it to not try and convert a string that contains only numbers into an actual number.
Comment #4
steveOR CreditAttribution: steveOR commentedThis exact bug confirmed again, fb:app_id mangled, don't think opengraph will have much of a taste for scientific floats, doing manual workaround after features export as mentioned in issue summary. We are using:
features 7.x-2.0-beta2
metatag 7.x-1.0-beta7
metatag_opengraph 7.x-1.0-beta7
ctools 7.x-1.3
Comment #5
olofbokedal CreditAttribution: olofbokedal commentedHmm. I'm using the Easy Social module as well, and entered the same FB App ID for it's settings. When I reviewed the overrides for the feature where the variable is stored, it's displayed as a float. But when I exported the feature, the variable is stored as a string.
It seems as if this is related to Strongarm, Ctools or Features.
Comment #6
plopescHello
I tried to reproduce this issue, but I can't, here is the chunk of code from my exported feature:
The fb:app_id is exported successfully.
Here is my current env:
So, marking this issue as closed.
Feel free to reopen it if the problem persists.
Regards
Comment #7
DamienMcKennaLets wait for one of the people who originally had the problem to test it with the latest Features v2.0.
Comment #8
DamienMcKennaNo response in six months, am marking this as being fixed.