one problem when working from the front-end with K2 is however, that one cannot upload images to the /images directory, as everything is locked.
I have to upload images with JCE and then choose them with K2 Image.
I wish this could be fixed since it's highly problematic.
You mean K2 images? K2 images are stored in a specific problem. So apart from K2 images you can upload wherever you like since you set the desired path to media manager.
When accessing the 'images' folder from the frontend via K2's Media Manager ('Image' tab > Browse server") - when writing an article and wanting to upload an image and even create a folder for that image, the folders appear locked, no possibility to create a new one as well as upload an image to the server...
I read somewhere that the reason was that: "Since the media manager opens up a common folder, in the frontend all that is read-only"...
But it is not that great an alternative to use JCE to create folder and upload image, then exit JCE and use K2 to pick the newly uploaded image...
You are right, i forgot. We have disabled the uploading in the front-end for security reasons.
I see, but I wish this can be reverted because
1) it is time consuming to do this via the content editor like JCE or an FTP program and then go back to K2 Image tab to point to a picture
2) If the users need that specific function, they will just go on another way to get it, which kind of defeats the purpose...It won't be a K2 security issue in the narrower sense, but if K2 users need to upload pictures and do it within K2 items, just not via K2, does the process become any more secure if K2 itself doesn't allow it?
Last Edit: 10 months, 2 weeks ago by etkritikonspoudon.