This came up while working on #3384
@Graham-72:
... I found that once I had made sure that my browser was using the revised plugin script (by forcing it to clear its cache and hard reload) I was no longer getting the
TypeError: Argument 1... error report.
@quicksketch:
... Yeah a problem with CKEditor is that it loads the JavaScript via it's own mechanism AND it's inside of an iframe, so plugin changes don't show up right away. Seems like something we might want to try and figure out if we can cache-bust based on Backdrop version numbers or something, to prevent this problem for end-users that update.
GitHub Issue #:
3460
Recent comments
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists
Thanks, I have to go out now, I will try later on and report back
Importing the staged config throws an error: another field with the same name already exists
Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....
Importing the staged config throws an error: another field with the same name already exists