The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

I want to customize markdown schema. For example add an element with a class when I want to attach a link. How can i do it? (Sorry for my English. I hope you understand it :))

The issue occurs while working with: (check one with "x")

• app.storyblok.com

I'm submitting a ... (check one with "x")

• feature request

Restrict Content Types

Current behavior:
Cannot restrict content types for folder, hence all content types are shown, even "setting" contents (app-nav). This feature is needed to prevent a "content" folder from adding "setting" contents.

Show Content Type In List

Current behavior:
Content type not showing in content list

Expected behavior:
There are lots of space on the list, we might as well add some form of information so that there's no need to click on the content to figure out what content type it is. Content type should be colored in "unimportant" colors so that it's not confused with the title.

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:

Search function is only applicable to the whole story and not the individual components/blocks within the story.

Expected behavior:

API returns only the components/blocks within a story that satisfy the search term in the GET request if specified (Maybe an extra parameter called filter_blocks can be added? If not specified, API call will work normally and return the whole story.)

Related code:

curl https://api.storyblok.com/v1/cdn/stories?token=XXXXXX&search_term=hello&filter_blocks=true

This will only return the blocks in the stories that have the word "hello" in them.

The issue occurs while working with: (check one with "x")

• api.storyblok.com

I'm submitting a ... (check one with "x")

• feature request

Current behavior:
Tags returned from cdn/tags is an array of objects
Tags returned from tag_list in cdn/story is an array of strings
Tags object does not have slug

Expected behavior:
I think both of them should return an array of objects for consistency purposes. The object should ideally contain the following: name, slug, taggings_count and etc.

Slug is the urgent fix. At the moment there's no way to manage a multi word tag (e.g. Marketing News). If you could introduce a slug for the tags, then we could do stuff like url.com/tag/marketing-news. Leaving it as is like url.com/tag/Marketing News is non-standard and may cause all kinds of unimaginable error.

If taggings_count is not required in a story, then it can be omitted. However the returned type should be consistent so that applications do not need to write extra layer of filter to manage the tags.

I understand that this may affect a lot of existing applications so it could be a hard thing to change. So it is up for discussion.

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:
When creating a story via the Management API the position field is ignored and gets overwritten . This results in the incorrect sorting of the stories/folders on the Storyblok Interface and the wrong position value when accessing the story via the API. This also happens when trying to update the position field once the story has been created.

Expected behavior:
The position field should be set correctly when creating a Story via the Management API

Steps to reproduce:

• Create a story containing the position field via the the Management API .
• Fetch the story via Management/Content API. The field position will have the wrong value.

Related code:

const story = {
    name: 'test-story',
    slug: 'test-story',
    is_folder: true,
    position: 5,
}

const response = await Storyblok.post(`spaces/${spaceId}/stories/`, { story } )

Other information:

The issue occurs while working with: (check one with "x")

• app.storyblok.com
• api.storyblok.com
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:

Expected behavior:

Steps to reproduce:

Related code:

insert any relevant code here

Other information:

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

insert any relevant code here

Other information:

Is there any way to get localised/translated stories (ie. both /home and /en/home, translated using Single tree and field level translation), from the links endpoint? As it seems now i can't see them in the /v1/cdn/links endpoint. Unsure if i'm doing something wrong, if this is a bug or a feature request :) Would be awesome to be able to get the translated stories into our sitemap at least.

Thanks for an amazing product, cheers!

The issue occurs while working with: (check one with "x")

• [x ] app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• [x ] feature request
• question

Current behavior:

When I mark items in the interface and I click into free space nothing happens and the edit-menu remains open.
Expected behavior:

In the case of normal workflow the user can expect to unmark all items and the edit-menu closes clicking into free space of the interface what makes the work with the frontend more intuitive.
Steps to reproduce:

Related code:

insert any relevant code here

Other information:

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:
While using the SEO app in the CMS interface, adding an og:image does not load the image from the asset directory. The asset is not sent to the front-end. No console errors are reported.

Expected behavior:
Every other app that uses the asset interface correctly adds the asset to the data list and shows a preview of the image URL. Also, there is no ability to add an external URL link like in other instances of the asset manager.

Steps to reproduce:
Install the SEO app into an instance of Storyblok.
Add the plugin to a component schema.
Edit the meta for the component.
Click "Show/Hide advanced"
Click "Select asset" under OG Image
Attempt to add existing asset as OG Image

Other information:
This may just be due to the SEO plugin using an out-of-date version of the asset manager. Utilizing the asset manager in any other context does not produce this bug.

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:

The user can upload assets via the frontend but not delete them using the same.
Expected behavior:

For organization and usability reasons editors rely on being able to remove assets directly in the frontend without the need to consult a developer removing the unnecessary assets if bigger portions of the content changes or content changes frequently.
Steps to reproduce:

Related code:

insert any relevant code here

Other information:

The issue occurs while working with: (check one with "x")

• [ x] app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• [x ] feature request
• question

Current behavior:

There are three colors for showing if the story hasn't been published now (light grey), has been published but also has been modified (light blue) and has been published (blue)
Expected behavior:

As in some cases it is useful to be able see if there are still stories in the workflow stage Drafting / Reviewing / Ready to Publish but not published yet or have been modified and been published before it would be a help to have a ring outside of the already existing indicator to see in what stage the story actually is.
Another variation could be a colored dot in the middle to indicate the stage or two overlapping dots.

Steps to reproduce:

Related code:

insert any relevant code here

Other information:

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:
When duplicating a space with POST to /spaces and specifying space.dup_id, it seems that duplication is never done, but instead simply new empty space is created. It does not even work when I have "Make this space duplicatable by all users" enabled.

Expected behavior:
I would expect space.dup_id to be respected and space completely duplicated (as it is via UI panel).

Steps to reproduce:
Trigger a "Duplicate a space" request for a space you own.

The issue occurs while working with: (check one with "x")

• [x ] app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• [x ] bug report
• feature request
• question

There is a problem when i want to resend confirmation email. No email coming to me.

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:
When per_page and page parameters are specified on /spaces/:spaceId/components GET endpoint they seem to be ignored and no headers are returned. It even does not respect 25 default page size. The same call to /stories endpoint works as expected.

Expected behavior:
I would expect paging on components endpoint to work as specified in documentation. Modifying documentation to say all records are returned and there is no paging on that endpoint would be ok too.

Steps to reproduce:

1. Have a space with more than 1 component
2. Make a API call to retrieve all components for that space, specifying page=1 and per_page=1
3. Observe no paging headers are returned and both components returned in body (should be 1).

The issue occurs while working with: (check one with "x")

• app.storyblok.com
• api.storyblok.com
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request

Current behavior:
The storyblok-latest.js file is referenced in several tutorials, but there is no documentation around it use or api.

Expected behavior:
It would be excellent to have more details about the use of this script, in particular:

• Is it published on NPM, and can it be bundled rather than required.
• Is it possible to use this library to request data with a public key to get the live version of a page
• Is there a mechanism to detect if the library has been loaded in an iFrame (i.e. in the Storyblok backend)

Storyblok is very promising and has been great to use, great work!

The issue occurs while working with: (check one with "x")

• app.storyblok.com
• api.storyblok.com
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request

Current behavior:
When I make Post call to add a story story[published] = true doesn't set the story to be published automatically. I think it could be by design because I don't see it's documented anywhere.
It's not a bug, please let me know an alternative way to set it publish automatically

Expected behavior:

Steps to reproduce:

Related code:

insert any relevant code here

Other information:

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:

The user has to go into the "scheme editor", type a name/key in the name field and click add. This is a repeating work process for all fields even for fields of the same type and configuration. Each element has to be configured individually even when they have the same configuration.
Expected behavior:

For faster duplication there could be a button in front of the field element what creates a copy of the actual original with all settings and an appendix added to the name the like testbox1, textbox2... or with an underscore. This is an adaptation of the repeating field concept of WP expanded to all field type to make field duplication easier.

Steps to reproduce:

Related code:

insert any relevant code here

Other information:

The issue occurs while working with: (check one with "x")

• app.storyblok.com
• api.storyblok.com
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request

Current behavior:
The API to list stories does not show the current page neither the number of total pages.

Expected behavior:
As the API to list stories allow to define stories per per page and a page it also should return number of pages and the currently selected page.

Steps to reproduce:

Related code:

Other information:

The issue occurs while working with: (check one with "x")

• app.storyblok.com

I'm submitting a ... (check one with "x")

• bug report

Current behavior:
This happens I think after we save the page and move between blocks hierarchies.

No style formats

Style format position is goes haywire

Expected behavior:
On page reload it loads properly.

Steps to reproduce:

1. Load page
2. Edit an existing child block.
3. Add a new block.
4. Save.
5. Go back to the root block
6. Error should occur 80% of the time.

I suspect this is TinyMCE vue component loading too many times in the DOM. All in all, the TinyMCE isn't working very well at the moment with the StoryBlok app and needs some integration work to be done.

Related code:
Almost the same code as storyblok's tinymce plugin provided by Alexander, just added a few tinymce settings and styles.
Plugin link: http://app.storyblok.com/#!/me/plugins/103

Let me know if you need more info.

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:
On my current screen the editable/preview area is cca 1150 pixels, which sets the viewport to tablet mode, hence the preview is not very accurate.

Expected behavior:
Allow sidebar to be in a floating mode to provide enough space for the preview area to go full screen.

Steps to reproduce:

Related code:

insert any relevant code here

Other information:

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:

The user takes an asset or more during marking them in the "file upload" window and clicks on the open button. He has to create manually the directory or directories before he uploads the files which can be a time consuming task when the project has several directories that need to be created and change frequently.
Expected behavior:

The user chooses one directory or several in the "file upload" window and when clicking on open, the "assets manager" creates the folder(s) itself and uploads the content into the automatically created folder(s).
In the case that a directory already exists the user can choose to overwrite (assets with same name but different size etc gets deleted into the trashbin, this adds some security in the case of user errors), replace (deletes the content but files remain in the trashbin) or merge (just adds new content without touching the existing) the whole directory with the new (content).
Steps to reproduce:

Related code:

insert any relevant code here

Other information:

The issue occurs while working with: (check one with "x")

• [ x] app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• [x ] mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• [x ] bug report
• feature request
• question

Current behavior:

4-char language codes in the CMS interface are listed with a dash-> en-gb : but in the API they are used with an underscore -> en_gb -> as in : https://gist.github.com/DominikAngerer/f685f2c988171faef3fb6c2ffff4c78c

Therefore non of my attempts to use the field-level i18n technique .eg. "headline__i18n__en-gb" would work, as I was using the ones listed in the interface - might be worth harmonising these!

The issue occurs while working with: (check one with "x")

• app.storyblok.com

I'm submitting a ... (check one with "x")

• feature request

Current behavior:
Currently there are no settings to make a field "required" in storyblok

Expected behavior:
Create a checkbox to enable "required" verification on components. Ideally, the verification should accept mixed data, so that it could support regex as well.

The issue occurs while working with: (check one with "x")

• api.storyblok.com (CMS - Content Delivery API)

I'm submitting a ... (check one with "x")

• bug report

Current behavior:
The URL for requesting the API includes stories/undefined which doesn't work. It doens't append "undefined" with these settings for some reason.

window.storyblok.get(
  {
    starts_with: "work/",
    version: "draft"
  },
  (data) => {
    console.log("this works", data);
  }
)

http://api.storyblok.com/v1/cdn/stories/undefined?by_uuids=684bdaf1-f145-43b3-b241-040c973193ff%2Ca2ba88e0-2fc8-4b33-bf3e-2011942521c0&cv=1556993370&token=_STRIPPED_BECAUSE_OF_PRIVACY_&from_release=

Expected behavior:
Not having undefined in url.

Steps to reproduce:

window.storyblok.get(
  {
    by_uuids: blok.cases.join(",")
  },
  (data) => {
    console.log("this doesn't work as the URL has `undefined` in it", data)
  }
)

Other information:
I'm using the Storyblok Gatsby example, and I'm getting the error while trying to query related stories. I have to fetch more Stories, because I have a component that references other Stories, so the basic query for the current path in editor.js is not sufficient.

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:
'Multi-Options' ordering is reset by the CMS interface.

Expected behavior:
The CMS interface should respect previous ordering updates.

Steps to reproduce:
Multi-Options can be ordered if you select 'show only selected' in the web UI.
Reordering the list allows the underlying data collection to be re-ordered, this
can be verified by getting the data from the content API. If the CMS page is
refreshed the list is no longer shown in the correct order, subsequent
publishing of this page will result in the oredering being reset to this default
order even if the field is left untouched. This means that every edit to a Story
with ordered Multi-Options will require every Multi-Options field to be manually
set to the correct order in addition to the desired update.

Other information:

Present on Firefox on Ubuntu 18.10 & Chome on OSX

The issue occurs while working with: (check one with "x")

• app.storyblok.com
• api.storyblok.com
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request

Current behavior:
Saving the date within the story settings with hour, minutes and seconds is not possible, allthough you can select this data.

Expected behavior:
Saving the date withing the story settings with hour, minutes and seconds should be possible.

Steps to reproduce:

Related code:

insert any relevant code here

Other information:

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:
Clicking the Execute button for a task calls a webhook 👍🏽

Desired behavior:
It would be nice to have a prompt to add some extra data to the webhook URL at execute time. At the moment I have multiple tasks that do the same thing, but each passes a different ?confirmation_address=<custom email address> query parameter at the end of the webhook URL to notify someone when their deployment has finished. Having a single URL with a placeholder that gets replaced at execution time would be much niftier.

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• [X ] mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• [ X] bug report
• feature request
• question

Current behavior:
POSTing an update via API content with {"force_update": 1 } doesn't 'force update' if the component previously had a user-defined slug. Instead, it returns the error 'Unprocessable Entity'. Removing the user-defined slug from the component POST allows {"force_update": 1 } to work as I would expect.

Expected behavior:
Using {"force_update": 1 } would update the component even if with a defined slug.

E.g. POSTing story: { "name": "object name", "slug": "my_defined_slug" ) would be able to be updated if I set {"force_update": 1 }.

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:
All component groups are currently treated as top-level groups. Current structure:

Components
--> Layout (Group)
-->--> Grid (Component)
-->--> gridItem (Sub-component)
-->--> gridSpacer (Sub-component)
--> Common (Group)
-->--> someComponent1 (Sub-component)
-->--> someComponent2 (Sub-component)
--> Helpers (Group)
-->--> someComponent1 (Sub-component)

Requested behavior:
Would like the ability to nest these groups similar to a file tree in order to reflect the Vue component structure. This gives greater flexibility in whitelisting sub-components within their respective schemas. Requested structure:

Components
--> Layout (Group)
-->--> Grid (Component)
-->--> Grid (Group)
-->-->--> gridItem (Sub-component)
-->-->--> gridSpacer (Sub-component)
--> Common (Group)
-->--> someComponent2 (Sub-component)
-->--> Helpers (Group)
-->-->--> someComponent1 (Sub-component)

Other information:
Currently, in order to achieve the desired effect, you'd have to set up the Common and Helpers groups to have overlapping components contained within them (see current structure) to avoid having to either individually whitelist components - a nightmare if your component list is large, shared between multiple spaces, or when you deprecate and remove components over time - or whitelist a top-level group containing other components that you do not wish to be whitelisted (someComponent1 vs someComponent2 in the Common and Helpers groups).

Under the proposed feature, an admin could choose to only whitelist for the Grid its own subcomponents and the Helpers sub-components. Conversely whitelisting the Common group would whitelist all components contained within Common AND Helpers because Helpers is nested within it.

This greatly reduces the time overhead in managing and maintaining a clean component directory in Storyblok, and it also reduces the risk of accidental overlap or permission deficit when whitelisting, deprecating, and managing components in a complex instance of Storyblok.

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:

The actual stand of the behavior is that when the user decides to choose cloudinary to organize assets he can't access already uploaded assets through the assets manager anymore. The cloudinary app overwrites the access to all assets, even files.
Expected behavior:

A switch to be able to access -->already available<-- assets uploaded to storyblok and to be able to use cloudinary when the app has been installed.
Steps to reproduce:

Related code:

insert any relevant code here

Other information:

The issue occurs while working with:

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ...

• bug report
• feature request
• question

Current behavior:
The behavior in gatsby boilerplate will lead to a publicly accessible access token. And this token needs to be able to access drafts to work with the editor. This behavior should not be specific to the gatsby boilerplate though.

Expected behavior:
There should be a way to keep the access token secret. What is your recommendation?

The site should not need an access token when used in an iframe inside storyblok. There should be a way for storyblok to pass a temporary access token via a query parameter. Are you planning doing this?

Is there any other strategy you can recommend for keeping the access token secret?

The issue occurs while working with: (check one with "x")

• app.storyblok.com
• api.storyblok.com
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request

Current behavior:

Expected behavior:

Steps to reproduce:

Related code:

insert any relevant code here

Other information:

The issue occurs while working with: (check one with "x")

• api.storyblok.com

I'm submitting a ... (check one with "x")

• bug report

Current behavior:
Default value not clearly stated in the docs

Expected behavior:
Should state the default version that is pulled if version is not set.

How does the published or draft version differ from cv.

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:

https://cl.ly/4425b0d43111
The selected content type is not visible below the dropdown. Only the main "page" is working.
This modal appears when I want to add a new Entry.

Expected behavior:

Every selected content type should be visible.

Steps to reproduce:

We use shared components.

1. Create a new content type component.
2. Try to add a new entry and select something other than "page"

Related code:

insert any relevant code here

Other information:

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:
While duplicating a space the content tags are not duplicated/copied.

Expected behavior:
Everything including tags should be duplicated.

Steps to reproduce:
Create a new space. Add a tag to a content entry like a page. Save/Publish. Create a second space and choose the first space as a source in the advanced options of the New Space dialog. Look in the newly created Space if the tag got copied.

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Tweet:

"I always forget to push "Save Schema" and I lose my changes. Can you make the button more obvious or add a dialog to ask to save changes?"

https://twitter.com/failpunk/status/1040087751620624384

The issue occurs while working with: (check one with "x")

• app.storyblok.com
• api.storyblok.com

I'm submitting a ... (check one with "x")

• feature request

Current behavior:
Currently there isn't an author property in the story api object.

Expected behavior:
I would think that the author is can be selected or automatically selected from the user's first and last name to fill the author property in story api object. But that isn't the case.

Not sure what was the approach behind this, but if you could explain why the author is not included into the story api object that'll be great!

I suppose for now the only solution for this is to create a list of authors and then select authors using the single option field. Correct?

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

I am unable to sign in to storyblok. I keep getting this message: "ERROR You have to confirm your email address before continuing." But I already did that, and there were no problems signing in last week.

I have tried to click both "Forgot password?" and "Resend confirmation email" - but I am not receiving any emails. And as mentioned: It worked fine last week.

Help, please.

The issue occurs while working with: (check one with "x")

• app.storyblok.com

I'm submitting a ... (check one with "x")

• feature request

Current behavior:
Folders and pages are sorted only one dimensional, alphabetical order. It will get messy when the site gets to medium sized.

Expected behavior:
I feel that different file types should be separated. In this case, the files should be sorted by

1. File types
2. Alphabetical
3. Or just implement manual sorting by numbers

So the default output should be:
Blog
Folder
Settings
Home
Marketing

This is up for discussion. Inputs will be appreciated.

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:

I have cherry-picker your nuxt boilerplate into my app, and I am wondering what cacheVersion actually do. I would expect the API to respond saying nothing has changed and nuxt falling back to using store values, but it doesn't look like it's the case. Could you please clarify how YOU envision caching? There will be days when content changes a lot, but there will be stretches of weeks, where there will be no changes. So, I am trying to think of the best way to optimize the API calls and server response times.

Expected behavior:

Steps to reproduce:

Related code:

insert any relevant code here

Other information:

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:

When marking a field as required and a setting a name in "display name" isn't being used in the error message when one doesn't fill it when clicking on save.

Expected behavior:

The users expectation is that the error message uses the actually shown name of the field.

Steps to reproduce:

Related code:

insert any relevant code here

Other information:

The issue occurs while working with: (check one with "x")

• [ x] app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• [x ] feature request
• question

Current behavior:

Custom Languages doesn't show up in the selected language in the top bar
Expected behavior:

When using a customized language / locale it would be useful to see the selection in the top bar in the editor view.

Steps to reproduce:

Related code:

insert any relevant code here

Other information:

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:

The user can create a multi tree structure for the internationalization utilizing the dimensions app. The root of the tree structure starts also in the root of the space what can bring some caveats with it for example that editor can overwrite accidentally other directories or merge the content so to say it can cause some confusion.
Expected behavior:

A whitelist option could limit the count of directories (improves clarity), reduces the chance to modify the wrong directory and saves time in the long run when many directories are placed into the root of the space.
Furthermore it should be possible to restrict access to the whitelist in respect of the different user roles.
Steps to reproduce:

Related code:

insert any relevant code here

Other information:

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:

The tinymce WYSIWYG plugin doesn't scale in the width direction in the form only mode.

Expected behavior:
The plugin should be able to use the available width in the form only mode to fit the overall appearance of the frontend.

Steps to reproduce:

Related code:

insert any relevant code here

Other information:

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Taglist Plugin doesn't work.

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:
I want to create a preview gallery of all stories (e.g. Testimonial, which is set to be a page/content type). If I use bloks type, I can create new components of type Testimonial. But how I do allow picking existing ones?

Expected behavior:

Steps to reproduce:

Related code:

insert any relevant code here

Other information:

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• [x ] mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• [x ] feature request
• [x ] question

Current behavior:
If I attempt to create a folder, and that folder already exists, I get back the error 422 Unprocessable entity.

Expected behavior:
What I would like to know is what is the ID of that folder, so I can list it as a component's parent_id and put components in it. Is there a way to do this?

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:
Select components you want to move, click Move to group in the popup menu: there is some message that pops up saying you need to select the component group in the left.

Expected behavior:
Select a bunch of components, move by drag and drop or provide a different way to select a target group

Steps to reproduce:

Related code:

insert any relevant code here

Other information:

The issue occurs while working with: (check one with "x")

• app.storyblok.com (CMS - Interface)
• api.storyblok.com (CMS - Content Delivery API)
• mapi.storyblok.com (CMS - Management API)
• capi.storyblok.com (Commerce - API)
• Commerce - Interface
• Other

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question

Current behavior:
There is no way to specify an anchor id, when using internal links

Expected behavior:
It would be great if it were possible to specify #anchor after selecting the internal link.

Steps to reproduce:

Related code:

insert any relevant code here

Other information: