Netlify-cms: [bug] Cannot upload or view image in media assets

[caelialuk]

- Do you want to request a feature or report a bug?
bug

- What is the current behavior?

Images not uploading to media assets

and image links are broken

- If the current behavior is a bug, please provide the steps to reproduce.
created a site using hugo site starter with gitlab as backend
unable to upload images and view them

- What is the expected behavior?

Images can be uploaded and image links are not broken

Netlify CMS version: 1.9.2
Browser version: Chrome 67

- Please link or paste your config.yml below if applicable.

media_folder: "site/static/img"

[tech4him1]

The thumbnail problem is a duplicate of https://github.com/netlify/netlify-cms/issues/1436, can you confirm?

I'll try to reproduce the uploading problem.

[caelialuk]

Yes! Thank you, the thumbnail is a duplicate of #1436. But how do I implement solution #1433 (gitlab api) to my current project?

[erquhart]

@caelialuk we'll be getting that merged and released soon.

[tech4him1]

Sorry for the delay on this -- I just confirmed uploading is broken on the git-gateway backend with GitLab, but not when using the GitLab backend directly. @Benaiah any thoughts? No media shows up at all for me when using GG, so maybe it's related to the current PR?

[idiazroncero]

+1 here on a fresh install of netlifycms official gatsby starter based on gitlab... can we know if this is going to be fixed soon? Thanks!

[pojntfx]

+1 here as well. See my GitLab repo for the exact site where it appears.

[tech4him1]

Splitting this out into two separate issues:

• #1436 for viewing media.
• #1565 for uploading.

[piedoom]

Hi, I'm still experiencing this issue despite it being marked closed. Anyone else having issues?

[estherholleman]

It is also still not working for me. It builds fine, but when I try to change or upload an image I still get 'no assets found' even with a fresh install of the official Gatsby starter with GitLab and after updating gatsby-plugin-netlify-cms to version ^1.0.12, gatsby-plugin-netlify to ^1.0.21, and netlify-cms" to "^1.9.3. Is there perhaps anything else I should be updating or something I'm forgetting?

[estherholleman]

I found out so far that the newest version of netlify-cms is 2.08, however the gatsby plugin is setting the netlify-cms version so it needs to be overriden with 'resolutions' in the package.json file. I attempted this following the instructions here (https://www.npmjs.com/package/npm-force-resolutions), which included removing the node-modules folder, running npm-force-resolutions, and then npm install. This seemed to work for the gatsby-plugin-netlify-cms, but not for netlify-cms, which, even after I manually install it again with 'npm install --save netlify-cms' after the whole force-resolutions thing, cannot be found anymore/is empty when I run 'npm ls netlify-cms' (even though it appears in the node-modules folder). I'm stumped for now, will retry it again tomorrow.

[piedoom]

I'm not very familiar with this stack but let me know if I can help test anything on my end!

[tech4him1]

@piedoom @estherholleman See my last comment above -- fixes are still in progress, it has just been split into two different issues.

[piedoom]

I believe this is related to #1565 (I am getting the console error, not thumbnail issue) which is apparently resolved. Should I take my discussion there?

[tech4him1]

@piedoom Yes please. Also, make sure you are on the latest version of the CMS (v2.0.8) -- there were a lot of recent bug fixes.