When creating an image-clip field, I get this error message:
Anyone using this plugin have any idea, how, why? I checked the source and didn’t find anything looking like a wrong indent or something like that. It has 10 stars already, so I guess there are people using it just fine
There’s nothing special here, what do you think @texnixe?
What could be causing this specific error?
// Edit: When choosing another name for my field, it works as expected. I’m not fond of changing my field name, as cover is exactly what it is … I’ll tell the plugin author over at Github and maybe we can sort this out … thanks for your effort, as always!
Will check that. Most content files were there from the beginning of K2 - any method to clean them, and only keep what’s actually defined in the corresponding blueprint file?
Well, my problem persists, and it might be even harder to debug:
Now, I enter an image, save the page, visit another page, and everytime I come back, the field has the error shown above. When I change the field name once more, reload the page: I can select an image again! But, when saving, leaving the page, coming back: again, Illegal offset error …
@S1SYPHOS thank you for finding this. I haven’t considered that fields are just swaped out, but it is a valid use case. I will look into it and see whether the plugin can or should handle it. Changing the content file structure automatically could be a problem if you decide to go back to the core images field…