You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when saving on 8.1.0 an Image on Twitter Social section within a news Item, it gets persisted in DB via sys_file_reference on fieldname tw_image.
The MetaTagGeneratorHook otherwise is seraching for tx_csseo_. (Line 119).
I migrated from v10, so currently only old Fields get shown in Frontend, but not in Backend, seems like caused by this mixture.
Would be nice, if we could keep tx_csseo_tw_image so we do not need to migrate.
Thanks!
The text was updated successfully, but these errors were encountered:
This happens also on another upgraded instance with a new cs_seo entity. Searching for tx_csseo_og_image but in sys_file_reference the og_image is given
Hi,
when saving on 8.1.0 an Image on Twitter Social section within a
news
Item, it gets persisted in DB viasys_file_reference
on fieldnametw_image
.The
MetaTagGeneratorHook
otherwise is seraching fortx_csseo_
. (Line 119).I migrated from v10, so currently only old Fields get shown in Frontend, but not in Backend, seems like caused by this mixture.
Would be nice, if we could keep
tx_csseo_tw_image
so we do not need to migrate.Thanks!
The text was updated successfully, but these errors were encountered: