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

[4.x]: New entry button on entry selection modal is available for not supported sites. #14923

Closed
vnali opened this issue May 2, 2024 · 2 comments
Assignees

Comments

@vnali
Copy link
Contributor

vnali commented May 2, 2024

What happened?

Description

New entry button on entry selection modal is available for not supported sites.

Steps to reproduce

  • Create a new section section1 with en and en2 as supported sites
  • Create a new section section2 with en as supported site
  • Create an entry field with section2 as source and add it to section1 entry type

Show the site menu for that entry field is not checked

  • Craft 4: When create a new section1 entry for en2 site, on selecting that entry field, there is new entry button that clicking on that throws an error.
  • Craft 5: it seems handles this by redirecting user to supported site.

Show the site menu for that entry field is checked

  • Craft 4: When create a new section1 entry, on selecting that entry field, the new entry button is displayed even if en2 is selected on site menu on modal and clicking on that throws an error.
  • Craft 5: Changing site menu on modal to en2 throws an error.

Expected behavior

I guess the correct behavior is to hide create new entry button for not supported sites and not to list not supported sites on modal.

Craft CMS version

4.9.0, 5.1.0

PHP version

8.0.2, 8.2

Operating system and version

No response

Database type and version

No response

Image driver and version

No response

Installed plugins and versions

@i-just
Copy link
Contributor

i-just commented May 7, 2024

Hi, thanks for reporting! I raised a PR for this.

@brandonkelly
Copy link
Member

Craft 4.9.2 and 5.1.2 are out with that fix. Thanks again!

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

3 participants