image upload err not processing images
akwatra opened this issue · comments
Summary
image upload err not processing images. i have dig deep into and found in upload_controller.js
// Process images (all but SVG)
.write(req.file.path, (err) => {
if(err) {
console.log(req.file.path);
console.log( JSON.stringify(err) );
// images was uploading successfully and req.file.path also correct but its returning empty err object
and that falls into error block, hope this help you close to issue, I am trying also further to resolve, but you have better idea of whole flow, might be some other... please tell me how to resolve.?
Steps to Reproduce
Upload any image sitewide and watch inspect console BAD REQUEST error
POST http://127.0.0.1:3000/api/uploads 400 (Bad Request) lib.bundle.js:81
Additional info
- Postleaf version: 1.0.0-beta.1
- Node version: 8.4.0
- Affected browsers: chrome
- Operating system: linux / ubuntu 64
Note: This issue tracker is ONLY for bug reports and feature requests. If this is a personal support issue, please visit postleaf.org/support.
We need to see the content of the error that's being thrown. Maybe try console.log(err).
Hi Cory,
I have resolved this. I have upgraded GM lib at os level.
-just to know: is there a category option in postleaf? should I have to develop? Post Comments too?
functional flow wise there are lots of things missing. as user confirmation in admin/user URL and that show all admin things, which is not good. ex: When we set the user as a contributor he should not allow to change its role while login. Doc to connect with MongoDB and Postgres.
not working in mode = dev / development as not wanted to compiled assests while testing ?
Good UI work done!
is there a category option in postleaf?
By design, only tags are supported.
Post Comments too?
Please see: https://www.postleaf.org/thoughts-on-comments
functional flow wise there are lots of things missing.
I'm interested to hear your thoughts on what's missing, but keep in mind the goal of the project was to be simpler than some of the complex alternatives out there :)
ex: When we set the user as a contributor he should not allow to change its role while login.
Whoops. If this is possible, it should be filed as a bug 🐞
Doc to connect with MongoDB and Postgres.
The project uses Sequelize, so only certain databases are potentially supported.
Closing since the original issue has been resolved.