Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / decaporg/decap-cms issues and pull requests

#5815 - TypeError: Cannot read properties of undefined (reading 'path')

Issue - State: closed - Opened by dara-icf about 3 years ago - 10 comments

#5815 - TypeError: Cannot read properties of undefined (reading 'path')

Issue - State: closed - Opened by dara-icf about 3 years ago - 10 comments

#5815 - TypeError: Cannot read properties of undefined (reading 'path')

Issue - State: closed - Opened by dara-icf about 3 years ago - 10 comments

#5812 - Cloudinary using a string value instead of an array when selecting a single image

Issue - State: open - Opened by saulchavezr about 3 years ago - 7 comments
Labels: good first issue, area: media-library, area: extensions/media-libraries, type: bug

#5812 - Cloudinary using a string value instead of an array when selecting a single image

Issue - State: open - Opened by saulchavezr about 3 years ago - 7 comments
Labels: good first issue, area: media-library, area: extensions/media-libraries, type: bug

#5812 - Cloudinary using a string value instead of an array when selecting a single image

Issue - State: open - Opened by saulchavezr about 3 years ago - 7 comments
Labels: good first issue, area: media-library, area: extensions/media-libraries, type: bug

#5812 - Cloudinary using a string value instead of an array when selecting a single image

Issue - State: open - Opened by saulchavezr about 3 years ago - 7 comments
Labels: good first issue, area: media-library, area: extensions/media-libraries, type: bug

#5812 - Cloudinary using a string value instead of an array when selecting a single image

Issue - State: open - Opened by saulchavezr about 3 years ago - 7 comments
Labels: good first issue, area: media-library, area: extensions/media-libraries, type: bug

#5812 - Cloudinary using a string value instead of an array when selecting a single image

Issue - State: open - Opened by saulchavezr about 3 years ago - 7 comments
Labels: good first issue, area: media-library, area: extensions/media-libraries, type: bug

#5812 - Cloudinary using a string value instead of an array when selecting a single image

Issue - State: open - Opened by saulchavezr about 3 years ago - 7 comments
Labels: good first issue, area: media-library, area: extensions/media-libraries, type: bug

#5812 - Cloudinary using a string value instead of an array when selecting a single image

Issue - State: open - Opened by saulchavezr about 3 years ago - 7 comments
Labels: good first issue, area: media-library, area: extensions/media-libraries, type: bug

#5812 - Cloudinary using a string value instead of an array when selecting a single image

Issue - State: open - Opened by saulchavezr about 3 years ago - 7 comments
Labels: good first issue, area: media-library, area: extensions/media-libraries, type: bug

#5812 - Cloudinary using a string value instead of an array when selecting a single image

Issue - State: open - Opened by saulchavezr about 3 years ago - 7 comments
Labels: good first issue, area: media-library, area: extensions/media-libraries, type: bug

#5812 - Cloudinary using a string value instead of an array when selecting a single image

Issue - State: open - Opened by saulchavezr about 3 years ago - 7 comments
Labels: good first issue, area: media-library, area: extensions/media-libraries, type: bug

#5812 - Cloudinary using a string value instead of an array when selecting a single image

Issue - State: open - Opened by saulchavezr about 3 years ago - 7 comments
Labels: good first issue, area: media-library, area: extensions/media-libraries, type: bug

#5812 - Cloudinary using a string value instead of an array when selecting a single image

Issue - State: open - Opened by saulchavezr about 3 years ago - 7 comments
Labels: good first issue, area: media-library, area: extensions/media-libraries, type: bug

#5812 - Cloudinary using a string value instead of an array when selecting a single image

Issue - State: open - Opened by saulchavezr about 3 years ago - 7 comments
Labels: good first issue, area: media-library, area: extensions/media-libraries, type: bug

#5812 - Cloudinary using a string value instead of an array when selecting a single image

Issue - State: open - Opened by saulchavezr about 3 years ago - 7 comments
Labels: good first issue, area: media-library, area: extensions/media-libraries, type: bug

#5795 - Update the SlateJS Editor

Issue - State: closed - Opened by taineriley1 about 3 years ago - 10 comments
Labels: area: extensions/widgets/markdown, pinned, type: feature

#5792 - Customize list view for individual entries in nested collections

Issue - State: open - Opened by doompadee about 3 years ago - 2 comments
Labels: good first issue, type: feature, area: nested-collections

#5792 - Customize list view for individual entries in nested collections

Issue - State: open - Opened by doompadee about 3 years ago - 4 comments
Labels: good first issue, type: feature, area: nested-collections

#5792 - Customize list view for individual entries in nested collections

Issue - State: open - Opened by doompadee about 3 years ago - 2 comments
Labels: good first issue, type: feature, area: nested-collections

#5792 - Customize list view for individual entries in nested collections

Issue - State: open - Opened by doompadee about 3 years ago - 2 comments
Labels: good first issue, type: feature, area: nested-collections

#5792 - Customize list view for individual entries in nested collections

Issue - State: open - Opened by doompadee about 3 years ago - 2 comments
Labels: good first issue, type: feature, area: nested-collections

#5792 - Customize list view for individual entries in nested collections

Issue - State: open - Opened by doompadee about 3 years ago - 2 comments
Labels: good first issue, type: feature, area: nested-collections

#5792 - Customize list view for individual entries in nested collections

Issue - State: open - Opened by doompadee about 3 years ago - 2 comments
Labels: good first issue, type: feature, area: nested-collections

#5792 - Customize list view for individual entries in nested collections

Issue - State: open - Opened by doompadee about 3 years ago - 2 comments
Labels: good first issue, type: feature, area: nested-collections

#5792 - Customize list view for individual entries in nested collections

Issue - State: open - Opened by doompadee about 3 years ago - 2 comments
Labels: good first issue, type: feature, area: nested-collections

#5792 - Customize list view for individual entries in nested collections

Issue - State: open - Opened by doompadee about 3 years ago - 2 comments
Labels: good first issue, type: feature, area: nested-collections

#5792 - Customize list view for individual entries in nested collections

Issue - State: open - Opened by doompadee about 3 years ago - 2 comments
Labels: good first issue, type: feature, area: nested-collections

#5792 - Customize list view for individual entries in nested collections

Issue - State: open - Opened by doompadee about 3 years ago - 2 comments
Labels: good first issue, type: feature, area: nested-collections

#5792 - Customize list view for individual entries in nested collections

Issue - State: open - Opened by doompadee about 3 years ago - 2 comments
Labels: good first issue, type: feature, area: nested-collections

#5792 - Customize list view for individual entries in nested collections

Issue - State: open - Opened by doompadee about 3 years ago - 2 comments
Labels: good first issue, type: feature, area: nested-collections

#5778 - IndexSizeError: Failed to execute 'setStart' on 'Range': There is no child at offset 38.

Issue - State: closed - Opened by AdrianaFadel about 3 years ago - 3 comments
Labels: status: more info needed, status: stale

#5778 - IndexSizeError: Failed to execute 'setStart' on 'Range': There is no child at offset 38.

Issue - State: closed - Opened by AdrianaFadel about 3 years ago - 3 comments
Labels: status: more info needed, status: stale

#5778 - IndexSizeError: Failed to execute 'setStart' on 'Range': There is no child at offset 38.

Issue - State: closed - Opened by AdrianaFadel about 3 years ago - 3 comments
Labels: status: more info needed, status: stale

#5778 - IndexSizeError: Failed to execute 'setStart' on 'Range': There is no child at offset 38.

Issue - State: closed - Opened by AdrianaFadel about 3 years ago - 3 comments
Labels: status: more info needed, status: stale

#5778 - IndexSizeError: Failed to execute 'setStart' on 'Range': There is no child at offset 38.

Issue - State: closed - Opened by AdrianaFadel about 3 years ago - 3 comments
Labels: status: more info needed, status: stale

#5778 - IndexSizeError: Failed to execute 'setStart' on 'Range': There is no child at offset 38.

Issue - State: closed - Opened by AdrianaFadel about 3 years ago - 3 comments
Labels: status: more info needed, status: stale

#5778 - IndexSizeError: Failed to execute 'setStart' on 'Range': There is no child at offset 38.

Issue - State: closed - Opened by AdrianaFadel about 3 years ago - 3 comments
Labels: status: more info needed, status: stale

#5778 - IndexSizeError: Failed to execute 'setStart' on 'Range': There is no child at offset 38.

Issue - State: closed - Opened by AdrianaFadel about 3 years ago - 3 comments
Labels: status: more info needed, status: stale

#5778 - IndexSizeError: Failed to execute 'setStart' on 'Range': There is no child at offset 38.

Issue - State: closed - Opened by AdrianaFadel about 3 years ago - 3 comments
Labels: status: more info needed, status: stale

#5778 - IndexSizeError: Failed to execute 'setStart' on 'Range': There is no child at offset 38.

Issue - State: closed - Opened by AdrianaFadel about 3 years ago - 3 comments
Labels: status: more info needed, status: stale

#5778 - IndexSizeError: Failed to execute 'setStart' on 'Range': There is no child at offset 38.

Issue - State: closed - Opened by AdrianaFadel about 3 years ago - 3 comments
Labels: status: more info needed, status: stale

#5778 - IndexSizeError: Failed to execute 'setStart' on 'Range': There is no child at offset 38.

Issue - State: closed - Opened by AdrianaFadel about 3 years ago - 3 comments
Labels: status: more info needed, status: stale

#5778 - IndexSizeError: Failed to execute 'setStart' on 'Range': There is no child at offset 38.

Issue - State: closed - Opened by AdrianaFadel about 3 years ago - 3 comments
Labels: status: more info needed, status: stale

#5778 - IndexSizeError: Failed to execute 'setStart' on 'Range': There is no child at offset 38.

Issue - State: closed - Opened by AdrianaFadel about 3 years ago - 3 comments
Labels: status: more info needed, status: stale

#5778 - IndexSizeError: Failed to execute 'setStart' on 'Range': There is no child at offset 38.

Issue - State: closed - Opened by AdrianaFadel about 3 years ago - 3 comments
Labels: status: more info needed, status: stale

#5778 - IndexSizeError: Failed to execute 'setStart' on 'Range': There is no child at offset 38.

Issue - State: closed - Opened by AdrianaFadel about 3 years ago - 3 comments
Labels: status: more info needed, status: stale

#5768 - Preview Template isn't registered correctly

Issue - State: closed - Opened by quansenB about 3 years ago - 1 comment
Labels: type: bug

#5768 - Preview Template isn't registered correctly

Issue - State: closed - Opened by quansenB about 3 years ago - 1 comment
Labels: type: bug

#5768 - Preview Template isn't registered correctly

Issue - State: closed - Opened by quansenB about 3 years ago - 1 comment
Labels: type: bug

#5768 - Preview Template isn't registered correctly

Issue - State: closed - Opened by quansenB about 3 years ago - 1 comment
Labels: type: bug

#5768 - Preview Template isn't registered correctly

Issue - State: closed - Opened by quansenB about 3 years ago - 1 comment
Labels: type: bug

#5768 - Preview Template isn't registered correctly

Issue - State: closed - Opened by quansenB about 3 years ago - 1 comment
Labels: type: bug

#5768 - Preview Template isn't registered correctly

Issue - State: closed - Opened by quansenB about 3 years ago - 1 comment
Labels: type: bug

#5768 - Preview Template isn't registered correctly

Issue - State: closed - Opened by quansenB about 3 years ago - 1 comment
Labels: type: bug

#5765 - Creating a custom editor widget that is matched by a built in editor widget's regex causes the built in widget to render in place of the custom widget when the article is re-opened.

Issue - State: closed - Opened by edazpotato about 3 years ago - 2 comments
Labels: area: extensions/widgets/markdown, area: extensions/editor-components, type: bug

#5765 - Creating a custom editor widget that is matched by a built in editor widget's regex causes the built in widget to render in place of the custom widget when the article is re-opened.

Issue - State: closed - Opened by edazpotato about 3 years ago - 2 comments
Labels: area: extensions/widgets/markdown, area: extensions/editor-components, type: bug

#5765 - Creating a custom editor widget that is matched by a built in editor widget's regex causes the built in widget to render in place of the custom widget when the article is re-opened.

Issue - State: closed - Opened by edazpotato about 3 years ago - 2 comments
Labels: area: extensions/widgets/markdown, area: extensions/editor-components, type: bug

#5765 - Creating a custom editor widget that is matched by a built in editor widget's regex causes the built in widget to render in place of the custom widget when the article is re-opened.

Issue - State: closed - Opened by edazpotato about 3 years ago - 2 comments
Labels: area: extensions/widgets/markdown, area: extensions/editor-components, type: bug

#5765 - Creating a custom editor widget that is matched by a built in editor widget's regex causes the built in widget to render in place of the custom widget when the article is re-opened.

Issue - State: closed - Opened by edazpotato about 3 years ago - 2 comments
Labels: area: extensions/widgets/markdown, area: extensions/editor-components, type: bug

#5765 - Creating a custom editor widget that is matched by a built in editor widget's regex causes the built in widget to render in place of the custom widget when the article is re-opened.

Issue - State: closed - Opened by edazpotato about 3 years ago - 2 comments
Labels: area: extensions/widgets/markdown, area: extensions/editor-components, type: bug

#5765 - Creating a custom editor widget that is matched by a built in editor widget's regex causes the built in widget to render in place of the custom widget when the article is re-opened.

Issue - State: closed - Opened by edazpotato about 3 years ago - 2 comments
Labels: area: extensions/widgets/markdown, area: extensions/editor-components, type: bug

#5765 - Creating a custom editor widget that is matched by a built in editor widget's regex causes the built in widget to render in place of the custom widget when the article is re-opened.

Issue - State: closed - Opened by edazpotato about 3 years ago - 2 comments
Labels: area: extensions/widgets/markdown, area: extensions/editor-components, type: bug

#5765 - Creating a custom editor widget that is matched by a built in editor widget's regex causes the built in widget to render in place of the custom widget when the article is re-opened.

Issue - State: closed - Opened by edazpotato about 3 years ago - 2 comments
Labels: area: extensions/widgets/markdown, area: extensions/editor-components, type: bug

#5765 - Creating a custom editor widget that is matched by a built in editor widget's regex causes the built in widget to render in place of the custom widget when the article is re-opened.

Issue - State: closed - Opened by edazpotato about 3 years ago - 2 comments
Labels: area: extensions/widgets/markdown, area: extensions/editor-components, type: bug

#5765 - Creating a custom editor widget that is matched by a built in editor widget's regex causes the built in widget to render in place of the custom widget when the article is re-opened.

Issue - State: closed - Opened by edazpotato about 3 years ago - 2 comments
Labels: area: extensions/widgets/markdown, area: extensions/editor-components, type: bug

#5765 - Creating a custom editor widget that is matched by a built in editor widget's regex causes the built in widget to render in place of the custom widget when the article is re-opened.

Issue - State: closed - Opened by edazpotato about 3 years ago - 2 comments
Labels: area: extensions/widgets/markdown, area: extensions/editor-components, type: bug

#5752 - `logo_url` appears not to be used when `local_backend:true`

Issue - State: closed - Opened by paulmsmith about 3 years ago - 3 comments
Labels: good first issue, area: extensions/backends, type: bug, area: local-proxy

#5751 - feat: add field validation before publish

Pull Request - State: closed - Opened by trfv about 3 years ago - 5 comments
Labels: type: feature

#5735 - Content added directly to a markdown file with a text editor does not appear in CMS web portal

Issue - State: closed - Opened by jamesbungay about 3 years ago - 2 comments
Labels: good first issue, area: extensions/widgets/markdown, type: bug

#5735 - Content added directly to a markdown file with a text editor does not appear in CMS web portal

Issue - State: closed - Opened by jamesbungay about 3 years ago - 2 comments
Labels: good first issue, area: extensions/widgets/markdown, type: bug

#5735 - Content added directly to a markdown file with a text editor does not appear in CMS web portal

Issue - State: closed - Opened by jamesbungay about 3 years ago - 2 comments
Labels: good first issue, area: extensions/widgets/markdown, type: bug

#5735 - Content added directly to a markdown file with a text editor does not appear in CMS web portal

Issue - State: closed - Opened by jamesbungay about 3 years ago - 2 comments
Labels: good first issue, area: extensions/widgets/markdown, type: bug

#5735 - Content added directly to a markdown file with a text editor does not appear in CMS web portal

Issue - State: closed - Opened by jamesbungay about 3 years ago - 2 comments
Labels: good first issue, area: extensions/widgets/markdown, type: bug

#5735 - Content added directly to a markdown file with a text editor does not appear in CMS web portal

Issue - State: closed - Opened by jamesbungay about 3 years ago - 2 comments
Labels: good first issue, area: extensions/widgets/markdown, type: bug

#5735 - Content added directly to a markdown file with a text editor does not appear in CMS web portal

Issue - State: closed - Opened by jamesbungay about 3 years ago - 2 comments
Labels: good first issue, area: extensions/widgets/markdown, type: bug

#5735 - Content added directly to a markdown file with a text editor does not appear in CMS web portal

Issue - State: closed - Opened by jamesbungay about 3 years ago - 2 comments
Labels: good first issue, area: extensions/widgets/markdown, type: bug

#5735 - Content added directly to a markdown file with a text editor does not appear in CMS web portal

Issue - State: closed - Opened by jamesbungay about 3 years ago - 2 comments
Labels: good first issue, area: extensions/widgets/markdown, type: bug

#5735 - Content added directly to a markdown file with a text editor does not appear in CMS web portal

Issue - State: closed - Opened by jamesbungay about 3 years ago - 2 comments
Labels: good first issue, area: extensions/widgets/markdown, type: bug

#5735 - Content added directly to a markdown file with a text editor does not appear in CMS web portal

Issue - State: closed - Opened by jamesbungay about 3 years ago - 2 comments
Labels: good first issue, area: extensions/widgets/markdown, type: bug

#5735 - Content added directly to a markdown file with a text editor does not appear in CMS web portal

Issue - State: closed - Opened by jamesbungay about 3 years ago - 2 comments
Labels: good first issue, area: extensions/widgets/markdown, type: bug

#5735 - Content added directly to a markdown file with a text editor does not appear in CMS web portal

Issue - State: closed - Opened by jamesbungay about 3 years ago - 2 comments
Labels: good first issue, area: extensions/widgets/markdown, type: bug

#5724 - Search, sort, group by template tags in summary

Issue - State: open - Opened by martinjagodic about 3 years ago - 5 comments
Labels: good first issue, area: ux, type: feature

#5701 - Make 'Save' button's state more visible

Issue - State: closed - Opened by taineriley1 over 3 years ago - 2 comments
Labels: type: feature

#5701 - Make 'Save' button's state more visible

Issue - State: closed - Opened by taineriley1 over 3 years ago - 3 comments
Labels: type: feature

#5674 - Add/Edit links inline

Issue - State: open - Opened by bradystroud over 3 years ago - 4 comments
Labels: good first issue, area: ux, area: extensions/widgets/markdown, type: feature

#5674 - Add/Edit links inline

Issue - State: open - Opened by bradystroud over 3 years ago - 4 comments
Labels: good first issue, area: ux, area: extensions/widgets/markdown, type: feature

#5674 - Add/Edit links inline

Issue - State: open - Opened by bradystroud over 3 years ago - 4 comments
Labels: good first issue, area: ux, area: extensions/widgets/markdown, type: feature

#5674 - Add/Edit links inline

Issue - State: open - Opened by bradystroud over 3 years ago - 4 comments
Labels: good first issue, area: ux, area: extensions/widgets/markdown, type: feature

#5674 - Add/Edit links inline

Issue - State: open - Opened by bradystroud over 3 years ago - 4 comments
Labels: good first issue, area: ux, area: extensions/widgets/markdown, type: feature

#5674 - Add/Edit links inline

Issue - State: open - Opened by bradystroud over 3 years ago - 4 comments
Labels: good first issue, area: ux, area: extensions/widgets/markdown, type: feature

#5674 - Add/Edit links inline

Issue - State: open - Opened by bradystroud over 3 years ago - 4 comments
Labels: good first issue, area: ux, area: extensions/widgets/markdown, type: feature

#5673 - 🐛 Rich text editor adding '\' to Markdown

Issue - State: open - Opened by bradystroud over 3 years ago - 8 comments
Labels: area: extensions/widgets/markdown, pinned, type: bug

#5659 - Improve Table /Overflow UX

Issue - State: open - Opened by willbuck over 3 years ago - 5 comments
Labels: good first issue, area: docs, type: feature

#5659 - Improve Table /Overflow UX

Issue - State: open - Opened by willbuck over 3 years ago - 5 comments
Labels: good first issue, area: docs, type: feature

#5659 - Improve Table /Overflow UX

Issue - State: open - Opened by willbuck over 3 years ago - 5 comments
Labels: good first issue, area: docs, type: feature

#5659 - Improve Table /Overflow UX

Issue - State: closed - Opened by willbuck over 3 years ago - 6 comments
Labels: good first issue, area: docs, type: feature

#5659 - Improve Table /Overflow UX

Issue - State: open - Opened by willbuck over 3 years ago - 5 comments
Labels: good first issue, area: docs, type: feature