Running directus v9.0.0-rc.64

I have a collection with a M2M to another collection with a sort field. Adding items and saving alements works, but if I change the order I get an internal server error:

I always updated using npm and migrated the DB. Thanks for your help

Another option is XDM (https://github.com/wooorm/xdm) which is a lighter implementation of MDX 2, which has remark ^13 on it's stable release.

@fballan93 Could you share a DB dump where this is happening? It's a little difficult to reproduce just based on the information provided.

It also sounds like this could be a duplicate of #5538 just popping up in a different location 🤔

I think it is different . the issue here is in interface . and can be summarized in two points :

• Adding any field from directus_users in M2M M2O O2M interface to display inside a collection item will result in a permission denied error while updating although im the admin .

• Adding any item from another sub collection in the interface will not display when clicking on it

Of course . how you want it to be shared . you want t a link for the dump or should i uploaded it here .

Something else is wrong...

I am getting not all Articles, but only those, which have Categories. This is for my previous query also (https://github.com/directus/directus/issues/4471#issuecomment-828670002)

I have checked, that this filter (with [undefined] value) is ignoring now, but something else is filtering Articles... Can it be something inside addWhereClauses or addJoins?

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/mdx/mdx/3BLdbeZGJRPsQLrHCQeDCkZhzVPi
✅ Preview: In Progress

Bumps url-parse from 1.4.7 to 1.5.1. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/unshiftio/url-parse/commit/eb6d9f51e395b7e47bf2594e457d541db21c713b"><code>eb6d9f5</code></a> [dist] 1.5.1</li> <li><a href="https://github.com/unshiftio/url-parse/commit/750d8e8a9d45dbce9ff09759f0fe4564cdd47d74"><code>750d8e8</code></a> [fix] Fixes relative path resolving <a href="https://github-redirect.dependabot.com/unshiftio/url-parse/issues/199">#199</a> <a href="https://github-redirect.dependabot.com/unshiftio/url-parse/issues/200">#200</a> (<a href="https://github-redirect.dependabot.com/unshiftio/url-parse/issues/201">#201</a>)</li> <li><a href="https://github.com/unshiftio/url-parse/commit/3ac777474ba5dc48a7e33771cbb311fc6f69bef8"><code>3ac7774</code></a> [test] Make test consistent for browser testing</li> <li><a href="https://github.com/unshiftio/url-parse/commit/267a0c6f7ef1a58271be61611c5103daace602c9"><code>267a0c6</code></a> [dist] 1.5.0</li> <li><a href="https://github.com/unshiftio/url-parse/commit/d1e7e8822f26e8a49794b757123b51386325b2b0"><code>d1e7e88</code></a> [security] More backslash fixes (<a href="https://github-redirect.dependabot.com/unshiftio/url-parse/issues/197">#197</a>)</li> <li><a href="https://github.com/unshiftio/url-parse/commit/d99bf4cf259b7378c855f786edc253e70405ffdc"><code>d99bf4c</code></a> [ignore] Remove npm-debug.log from .gitignore</li> <li><a href="https://github.com/unshiftio/url-parse/commit/422c8b5e4cac6a79cd35b4e86731476dcbeec7e4"><code>422c8b5</code></a> [pkg] Replace nyc with c8</li> <li><a href="https://github.com/unshiftio/url-parse/commit/933809d630c7b21399b4e5df59fccccd80033b21"><code>933809d</code></a> [pkg] Move coveralls to dev dependencies</li> <li><a href="https://github.com/unshiftio/url-parse/commit/190b2168035899a2a88f2dc2625963bf7e2f338f"><code>190b216</code></a> [pkg] Add .npmrc</li> <li><a href="https://github.com/unshiftio/url-parse/commit/ce3783f4ea25753cfa36376769c14e4e2fe6ea80"><code>ce3783f</code></a> [test] Do not test on all available versions of Edge and Safari</li> <li>Additional commits viewable in <a href="https://github.com/unshiftio/url-parse/compare/1.4.7...1.5.1">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

1. Create Article with 2 translations:

2. Filter articles with GraphQL:

fragment Article on article {
  id
  ...
  translations(filter: { languages_code: { code: { _eq: $lang } } }) {  # Getting filtered translations
    slug
    content # Filter added to filter large content for specified lang only
    ...
  }
  all_translations: translations { # Getting all translations without filter
    slug
    languages_code {
      code
      name
    }
  }
}

query getArticle($slug: String, $lang: String = "ru") {
  article(filter: { translations: { slug: { _eq: $slug } } }) { # This filter does not affect the problem
    ...Article
  }
}

3. Problem: all_translations contains filtered items (but it should not have translations filter):

PS: Without a filter at translations:

Project details

Directus Version: 9.0.0-rc.64 Environment: production OS: Linux 5.4.0-66-generic Node: 10.19.0

I was checking downloads on pinia and there is a lot on 0.0.7 and was wondering where to help migrate. I saw you had #5427 and that you migrated to it in Vue 3 but I wanted to see how hard it was to migrate on a real project by myself.

I couldn't run the tests locally. Maybe I need to use npm 7, so I only did some replacements based on the breaking changes hoping for the best.

Let me know if you need help with this one or if I should add something

Feel free to dismiss this if you don't want to migrate 🙂

I new add role name member, then upload files via AWS storage. but it can not be delete via this role, only can delete by Admin

role permission settings is: { "owner": { "_eq": "$CURRENT_USER" } }

My version: RC.62

Hi.

I have the latest version .64 and I see that .csv file is detected as FILE:

While the other CSV files I upload are detected as CSV:

I see that the one that is detected as FILE has this .bin extension in file name:

But eventually, I can download that and process it as CSV.

Any idea why?

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/mdx/mdx/EC2gCjDb4yi3tabZmn3AxEqGsehq
✅ Preview: In Progress

Bumps handlebars from 4.7.6 to 4.7.7. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/handlebars-lang/handlebars.js/blob/master/release-notes.md">handlebars's changelog</a>.</em></p> <blockquote> <h2>v4.7.7 - February 15th, 2021</h2> <ul> <li>fix weird error in integration tests - eb860c0</li> <li>fix: check prototype property access in strict-mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>) - b6d3de7</li> <li>fix: escape property names in compat mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>) - f058970</li> <li>refactor: In spec tests, use expectTemplate over equals and shouldThrow (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1683">#1683</a>) - 77825f8</li> <li>chore: start testing on Node.js 12 and 13 - 3789a30</li> </ul> <p>(POSSIBLY) BREAKING CHANGES:</p> <ul> <li>the changes from version <a href="https://github.com/handlebars-lang/handlebars.js/blob/master/release-notes.md#v460---january-8th-2020">4.6.0</a> now also apply in when using the compile-option "strict: true". Access to prototype properties is forbidden completely by default, specific properties or methods can be allowed via runtime-options. See <a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1633">#1633</a> for details. If you are using Handlebars as documented, you should not be accessing prototype properties from your template anyway, so the changes should not be a problem for you. Only the use of undocumented features can break your build.</li> </ul> <p>That is why we only bump the patch version despite mentioning breaking changes.</p> <p><a href="https://github.com/wycats/handlebars.js/compare/v4.7.6...v4.7.7">Commits</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/a9a8e403213583ca90cb7c872d3a22796c37d961"><code>a9a8e40</code></a> v4.7.7</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/e66aed5b99c1b6c93564f37d627e34e5d60eb76e"><code>e66aed5</code></a> Update release notes</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/7d4d170ce46a53084a41920c5c7387c131357989"><code>7d4d170</code></a> disable IE in Saucelabs tests</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/eb860c08998f8f506360d305d89e1f4b40f72a0a"><code>eb860c0</code></a> fix weird error in integration tests</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/b6d3de7123eebba603e321f04afdbae608e8fea8"><code>b6d3de7</code></a> fix: check prototype property access in strict-mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>)</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/f0589701698268578199be25285b2ebea1c1e427"><code>f058970</code></a> fix: escape property names in compat mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>)</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/77825f8d3522356feb8e4160fac16344104d192b"><code>77825f8</code></a> refator: In spec tests, use expectTemplate over equals and shouldThrow (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1683">#1683</a>)</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/3789a309554fd600caeae442f40881cf93eb3b54"><code>3789a30</code></a> chore: start testing on Node.js 12 and 13</li> <li>See full diff in <a href="https://github.com/wycats/handlebars.js/compare/v4.7.6...v4.7.7">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Custom endpoint located at directus/extensions/endpoints and looks like this:

const PasswordChangeService = require('../../lib/services/pass-change-email');

module.exports = function registerEndpoint(router, { services, env, database }) {
  router.post('/password-reset', (req, res) => {
    let { email, reset_url } = req.body;

    try {
      const data = await database.where({ email }).select('email', 'status').limit(1).from('directus_users');

      if (typeof data !== 'undefined' || data.length > 0) {
        const { status } = await new PasswordChangeService().send(email, reset_url);
        console.log({ status });
        res.json({ data, status });
        return;
      }
      return res.status(404).json({ error: 'No such email found in database!' });
    } catch (e) {
      res.status(404).json({ error: e });
    }
  });
};

There are also other endpoints which are also not working (404). Running in Docker. Starting with docker-compose up --build. Tried to rebuild containers, remove containers and then build again. Did not help. Tried also logging to Docker container and inspecting files from inside: /directus/extensions/endpoints custom endpoints are visible, files are there.

Directus extensions and uploads folders are mapped via docker-compose.yml:

When trying to access my endpoint I get: {"errors":[{"message":"Route /custom/user/password-reset doesn't exist.","extensions":{"code":"ROUTE_NOT_FOUND"}}]}

However strange thing is that the same branch is working fine on one computer, and on another two computers custom endpoint is not reachable. Same setup, same database. It used to work before locally. When deployed to dev env, it is also working fine. What might be the problem?

Project details

Directus Version: 9.0.0-rc.64 Environment: production OS: Linux 5.4.0-72-generic Node: 14.16.1

yes

~@cdwmhcc What database is this on?~

Guessing MySQL 5 (without support for JSON types in options). Migration has been fixed 👍🏻 You can roll back and try again, or manually delete the options column contents for fields where options starts with with {"0": "{", "1": if you haven't made a backup before migrating 👍🏻

set null?