Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Image and File sources are not properly configured for this field. #7

Closed
Zae opened this issue Feb 6, 2019 · 6 comments
Closed

Image and File sources are not properly configured for this field. #7

Zae opened this issue Feb 6, 2019 · 6 comments

Comments

@Zae
Copy link
Contributor

Zae commented Feb 6, 2019

I keep getting this error, not idea what I'm doing wrong, I supplied a images and files folder.

Image and File sources are not properly configured for this field.

Am I doing something wrong or isn't the plugin updated for craft 3.1 yet?

froala/craft-froala-wysiwyg (2.9.2)
craftcms/cms (3.1.8)

@bertoost
Copy link
Contributor

bertoost commented Feb 6, 2019

Do you have configured volumes and set those in the field settings?
I have tested the plugin with the newest Craft version.
The error is newly added since otherwise the image and file features are not working

@Zae
Copy link
Contributor Author

Zae commented Feb 6, 2019 via email

@bertoost
Copy link
Contributor

bertoost commented Feb 6, 2019

Strange. I will investigate a.s.a.p. (bed time now)

@bertoost
Copy link
Contributor

bertoost commented Feb 7, 2019

Fixed

@Zae
Copy link
Contributor Author

Zae commented Feb 7, 2019

Thanks for fixing this @bertoost!

I did notice that packagist did not see the tag yet.

@bertoost
Copy link
Contributor

bertoost commented Feb 7, 2019

Yeah. And also the webhook for Craft's plugin store is down. Already notified P&T about it.
Weird that packagist isn't getting my new version...

[edit]
Argh! I forgot to change the version in the composer.json file.. hang on! I try to fix it

[edit]
Fixed! And suddenly it appears in the plugin store as well (since the webhook is showing unauthorized issues, whatever 😋 )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants