Hi 👋 I believe the ssl issue could be a misconfiguration in Netlify. Netlify is not correctly issuing an SSL cert for choo.io, see docs: https://docs.netlify.com/domains-https/custom-domains/#assign-a-domain-to-a-site

Maybe contact Netlify support and ask what could be causing the ssl issue? 🙂

@yoshuawuyts

Describe the bug

Validation error is not displayed in portable text for annotation referring to a named object with validation.

To Reproduce

Steps to reproduce the behavior:

1. Create a document with portable text field.
2. Create a named object with validation on a field.
3. Define an annotation type in the portable text which refers to the named object.
4. Write content that breaks the validation on the annotation.
5. Observe that the document reports a validation error, but the error is not noted in the portable text editor.

Expected behavior

Would expect to see the validation error displayed somewhere close to where the error occurred.

Screenshots

Which versions of Sanity are you using?

Run sanity versions in the terminal and copy-paste the result here.

@sanity/cli 1.149.16 (latest: 1.150.7) @sanity/base 1.150.7 (up to date) @sanity/cli 1.150.7 (up to date) @sanity/components 1.150.7 (up to date) @sanity/core 1.150.7 (up to date) @sanity/dashboard 1.150.7 (up to date) @sanity/default-layout 1.150.7 (up to date) @sanity/default-login 1.150.1 (up to date) @sanity/desk-tool 1.150.7 (up to date) @sanity/production-preview 1.150.1 (up to date) @sanity/studio-hints 1.150.7 (up to date) @sanity/vision 1.150.6 (up to date)

What operating system are you using?

MacOS.

Which versions of Node.js / npm are you running?

Run npm -v && node -v in the terminal and copy-paste the result here.

NPM 6.14.8 Node v12.16.2

Additional information

I have a custom component that wraps the portable text field that sees this error. Could it be the culprit?

My bad. I discovered that I was not passing all necessary props through my custom component. Discovered this by testing without a custom component only to see that everything worked. Closing this. 😸

The invalid markdef disappeared after I cut out the sentence and pasted it back in. Works nice for me, but hard to debug for content editors. I believe that this is still an issue that invalid annotations are not properly displayed in context.

On further inspection, I see that the invalid annotation is located in a markdef that is not refered to in the text.

Describe the bug

Validation error is not displayed in portable text for annotation referring to a named object with validation.

To Reproduce

Steps to reproduce the behavior:

1. Create a document with portable text field.
2. Create a named object with validation on a field.
3. Define an annotation type in the portable text which refers to the named object.
4. Write content that breaks the validation on the annotation.
5. Observe that the document reports a validation error, but the error is not noted in the portable text editor.

Expected behavior

Would expect to see the validation error displayed somewhere close to where the error occurred.

Screenshots

Which versions of Sanity are you using?

Run sanity versions in the terminal and copy-paste the result here.

@sanity/cli 1.149.16 (latest: 1.150.7) @sanity/base 1.150.7 (up to date) @sanity/cli 1.150.7 (up to date) @sanity/components 1.150.7 (up to date) @sanity/core 1.150.7 (up to date) @sanity/dashboard 1.150.7 (up to date) @sanity/default-layout 1.150.7 (up to date) @sanity/default-login 1.150.1 (up to date) @sanity/desk-tool 1.150.7 (up to date) @sanity/production-preview 1.150.1 (up to date) @sanity/studio-hints 1.150.7 (up to date) @sanity/vision 1.150.6 (up to date)

What operating system are you using?

MacOS.

Which versions of Node.js / npm are you running?

Run npm -v && node -v in the terminal and copy-paste the result here.

NPM 6.14.8 Node v12.16.2

Additional information

I have a custom component that wraps the portable text field that sees this error. Could it be the culprit?

Describe the bug

We've experienced that some Office 365 Outlook users report errors when trying to sign up to our newsletters. We have activated double-opt email verification. It seems that Office 365 ATP Safe Links somehow leads to an extra click which results in the user never seeing the verification success screen and instead they see the error "verification link expired" even though they just successfully signed up.

To reproduce

Steps to reproduce the behaviour:

1. Signup to newsletter with double-opt in activated, using an email that has Office 365 ATP Safe Links protection activated.
2. Click on verification link in email.
3. Get error "verification link expired", possibly because the link was automatically visited more than once by Safe Links.

Expected behaviour

Ideally, if the verification link has not expired and the user manages to visit the link more than once within the expiration window it should only show the success screen.

Additionally, I think any code that hooks into user subscription events should not be triggered more than once, even though a user visits a non-expired verification link multiple times.

Screenshots

If applicable, add screenshots to help explain your problem.

Versions

• Plugin version: 1.15.6
• Craft version: 3.3.20.1

Arcustech has moved to Mysql 8, this dev setup should mimic that. We tried to do that quickly but ran into authentication errors.

Possible fix:

• https://stackoverflow.com/a/52364450

Fixed in: 9831aa6cf3e99e073942f8e7277dc6d11e011cf3

Html tag is missing in _layout.twig, however browsers seems to add it if missing. Missing lang attribute cause validation warnings.

Possible fixes: Add html tag to _layout.twig: <html lang="nb"> or this might work for sites with multiple languages: <html lang="{{ currentSite.language }}">

• Upgrade Craft to 3.5.7
• Upgrade to php 7.4
• Upgrade to mysql 8
• Fix configuration issues.

• Upgrade Craft to 3.5.7
• Upgrade to php 7.4
• Upgrade to mysql 8
• Fix configuration issues.

Following the steps in craft starter and Guide: Deploy av Craft CMS til ArcusTech ( https://intranett.netlife.com/frontend-backend-og-cms/guide-deploy-craft-cms-til-arcustech) is leading to an error.

Database Exception – yii\db\Exception Redis error: ERR Client sent AUTH, but no password is set Redis command was: AUTH

Check redis config in config/app.php

Fixed in 3b77dc6191567431948b87d5a40749c630c4b02d

Closing as stale, better to redo the update I think.

Bumps acorn from 6.3.0 to 6.4.1. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/acornjs/acorn/commit/9a2e9b6678e243d66846b91179d650d28453e70c"><code>9a2e9b6</code></a> Mark version 6.4.1</li> <li><a href="https://github.com/acornjs/acorn/commit/90a9548ea0ce351b54f956e2c4ed27cca9631284"><code>90a9548</code></a> More rigorously check surrogate pairs in regexp validator</li> <li><a href="https://github.com/acornjs/acorn/commit/df0cf1a3e2b1a51a26c14984dc0f5412b7151b10"><code>df0cf1a</code></a> Mark version 6.4.0</li> <li><a href="https://github.com/acornjs/acorn/commit/53034126864b492da4e278628bb972cb2a9313d4"><code>5303412</code></a> Also export Parser via Parser.acorn</li> <li><a href="https://github.com/acornjs/acorn/commit/efe273e70123449a458157dbf578afaf109a49ab"><code>efe273e</code></a> give token types and etc to plugins</li> <li>See full diff in <a href="https://github.com/acornjs/acorn/compare/6.3.0...6.4.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>

Closing as stale

Bumps lodash from 4.17.15 to 4.17.19. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/lodash/lodash/releases">lodash's releases</a>.</em></p> <blockquote> <h2>4.17.16</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/d7fbc52ee0466a6d248f047b5d5c3e6d1e099056"><code>d7fbc52</code></a> Bump to v4.17.19</li> <li><a href="https://github.com/lodash/lodash/commit/2e1c0f22f425e9c013815b2cd7c2ebd51f49a8d6"><code>2e1c0f2</code></a> Add npm-package</li> <li><a href="https://github.com/lodash/lodash/commit/1b6c282299f4e0271f932b466c67f0f822aa308e"><code>1b6c282</code></a> Bump to v4.17.18</li> <li><a href="https://github.com/lodash/lodash/commit/a370ac81408de2da77a82b3c4b61a01a3b9c2fac"><code>a370ac8</code></a> Bump to v4.17.17</li> <li><a href="https://github.com/lodash/lodash/commit/1144918f3578a84fcc4986da9b806e63a6175cbb"><code>1144918</code></a> Rebuild lodash and docs</li> <li><a href="https://github.com/lodash/lodash/commit/3a3b0fd339c2109563f7e8167dc95265ed82ef3e"><code>3a3b0fd</code></a> Bump to v4.17.16</li> <li><a href="https://github.com/lodash/lodash/commit/c84fe82760fb2d3e03a63379b297a1cc1a2fce12"><code>c84fe82</code></a> fix(zipObjectDeep): prototype pollution (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4759">#4759</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/e7b28ea6cb17b4ca021e7c9d66218c8c89782f32"><code>e7b28ea</code></a> Sanitize sourceURL so it cannot affect evaled code (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4518">#4518</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/0cec225778d4ac26c2bac95031ecc92a94f08bbb"><code>0cec225</code></a> Fix lodash.isEqual for circular references (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4320">#4320</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4515">#4515</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/94c3a8133cb4fcdb50db72b4fd14dd884b195cd5"><code>94c3a81</code></a> Document matches* shorthands for over* methods (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4510">#4510</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4514">#4514</a>)</li> <li>Additional commits viewable in <a href="https://github.com/lodash/lodash/compare/4.17.15...4.17.19">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~mathias">mathias</a>, a new releaser for lodash since your current version.</p> </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>

Closing as stale

Bumps elliptic from 6.5.0 to 6.5.3. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/indutny/elliptic/commit/8647803dc3d90506aa03021737f7b061ba959ae1"><code>8647803</code></a> 6.5.3</li> <li><a href="https://github.com/indutny/elliptic/commit/856fe4d99fe7b6200556e6400b3bf585b1721bec"><code>856fe4d</code></a> signature: prevent malleability and overflows</li> <li><a href="https://github.com/indutny/elliptic/commit/60489415e545efdfd3010ae74b9726facbf08ca8"><code>6048941</code></a> 6.5.2</li> <li><a href="https://github.com/indutny/elliptic/commit/9984964457c9f8a63b91b01ea103260417eca237"><code>9984964</code></a> package: bump dependencies</li> <li><a href="https://github.com/indutny/elliptic/commit/ec735edde187a43693197f6fa3667ceade751a3a"><code>ec735ed</code></a> utils: leak less information in <code>getNAF()</code></li> <li><a href="https://github.com/indutny/elliptic/commit/71e4e8e2f5b8f0bdbfbe106c72cc9fbc746d3d60"><code>71e4e8e</code></a> 6.5.1</li> <li><a href="https://github.com/indutny/elliptic/commit/7ec66ffa255079260126d87b1762a59ea10de5ea"><code>7ec66ff</code></a> short: add infinity check before multiplying</li> <li><a href="https://github.com/indutny/elliptic/commit/ee7970b92f388e981d694be0436c4c8036b5d36c"><code>ee7970b</code></a> travis: really move on</li> <li><a href="https://github.com/indutny/elliptic/commit/637d0216b58de7edee4f3eb5641295ac323acadb"><code>637d021</code></a> travis: move on</li> <li><a href="https://github.com/indutny/elliptic/commit/5ed0babb6467cd8575a9218265473fda926d9d42"><code>5ed0bab</code></a> package: update deps</li> <li>See full diff in <a href="https://github.com/indutny/elliptic/compare/v6.5.0...v6.5.3">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>

Closing as stale

Arcustech has moved to Mysql 8, this setup should mimic that.