andful / netlify-cms-widget-create-select Goto Github PK

Especially with netlify-cms widget list, multiple requests are sent to the same resource. This can be prevented with a cache system.

Last Issue today, this one is less pressing because I know it works on production servers just not localhost/127.0.0.1

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at <URL>. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).

Uncaught (in promise) TypeError: NetworkError when attempting to fetch resource.

I'm using the netlify-cms-proxy-server and local_backend option, and getting this error. This is normal CORS limitation, but the uncaught error means that the widget displays "Loading" forever, and the create functionality doesn't work. I think it would be a good alternative to have it catch the failed html scraping and still allow you to manually enter values.

Thank you for your prompt work on this today!

Error thrown:

Configuration

- label: "Tags"
  name: "tags"
  hint: 'Do not duplicate any tags you would rather add for the whole Story!'
  widget: "create-select"
  mode: html
  url: FOO
  query: "h2.tag-title"
  attribute: "data-tag"
  multiple: true
  required: false

When this is used as a field, the html data is properly pulled and scraped into a list in the dropdown, but Save/Publish fails silently with an uncaught promise rejection, the field highlighting red and displaying the error above. Any assistance would be much appreciated. I was very excited to use this widget of yours.

Hi,

Thanks for the awesome widget 😀

I have set up the widget to get existing values from an API route (server/api route in a Nuxt3 app).
I was wondering if you could add functionality such that when creating an entry, the widget makes a POST request to an endpoint specified in another property of the widget.

With such functionality, I can sync my entries without having to visit the collection itself and make the additions manually (interrupts the editing flow).

In some of my markdown files with frontmatter, I created them before netlify-cms with a template consisting of all usable fields being present but blank. I am using this widget to adjust a tags: list that has no entries yet, and upon opening the post edit page, I receive an error:

TypeError: e is null
Source: render, https://unpkg.com/netlify-cms-widget-create-select@^1.1.0:10

I believe this is from an unhandled exception to an empty read of that field.

In the demo site the "Hugo Tags Example Using sitemap" select has an empty string option.

Unable to install as normal under React 17. When forcing it, it breaks the page:

Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

Check the render method of 'm'.

import dynamic from 'next/dynamic'
import {
  CreatableSelectControl,
  CreatableSelectPreview
} from 'netlify-cms-widget-create-select'

const CMS = dynamic(
  () =>
    import('netlify-cms-app').then(cms => {
      cms.init()
      cms.registerWidget(
        'create-select',
        window.CreatableSelectControl,
        window.CreatableSelectPreview
      )
    }),
  {
    ssr: false
  }
)

const CMSPage: React.FC = () => {
  return (
    <>
      <CMS />
    </>
  )
}
export default CMSPage