Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot add blocks with Vizy fields since 3.9.x #788

Closed
scandella opened this issue Sep 26, 2023 · 2 comments
Closed

Cannot add blocks with Vizy fields since 3.9.x #788

scandella opened this issue Sep 26, 2023 · 2 comments

Comments

@scandella
Copy link
Contributor

Bug Description

Since upgrading to Neo 3.9.x I can no longer create blocks with Vizy fields in it.
JS error appears when pushing the add button.
axios.js?v=1695756066:2 POST http://localhost:8888/pang/dev/web/index.php?p=admin%2Factions%2Fneo%2Finput%2Frender-blocks&v=1695756830224 500 (Internal Server Error)
Input.js:1149 Uncaught (in promise) o {message: 'Request failed with status code 500', name: 'AxiosError', code: 'ERR_BAD_RESPONSE', config: {…}, request: XMLHttpRequest, …}

Downgrading to 3.8.6 solved the issue.

Steps to reproduce

  1. Upgrade to Neo 3.9.x
  2. Create a Neo field
  3. Add a Vizy field in it
  4. In a section, try to add an entry to this Neo Field

Expected behaviour

No response

Neo version

3.9.2

Craft CMS version

Craft Pro 4.5.5

What is the affected Neo field's propagation method?

No response

Does this issue involve templating, and if so, is eager-loading used?

This is not a templating issue

@ttempleton
Copy link
Contributor

Fixed for the next release - see verbb/vizy#260 (comment) for an explanation of what caused this.

@ttempleton
Copy link
Contributor

Neo 3.9.3 has now been released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants