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

Twig error when update is available: "Impossible to access an attribute ("releases") on a boolean variable ("1")." #461

Closed
aelvan opened this issue Sep 4, 2023 · 4 comments · Fixed by #464
Assignees

Comments

@aelvan
Copy link

aelvan commented Sep 4, 2023

CleanShot 2023-09-04 at 11 51 31

Resolved by updating to the latest version of the plugin.

PHP 8.2.9
Craft 4.4.17
Translations v3.2.9

@bhupeshappfoster
Copy link
Collaborator

@aelvan

We tried to reproduce the issue but didn't see any, can you please provide us the steps following which we can see this error too?

Dashboard page
image

Utility updates
image

Note: Please let us know if you updated the craft version too when trying to fix this issue if yes do let us know which version were you at when you saw this error.

Version details:

  • Craft: 4.5.3
  • Php: 8.1
  • Translations: 3.2.7

@aelvan
Copy link
Author

aelvan commented Sep 4, 2023

When I first saw this, I was on Craft 4.4.17 and Translations 3.2.9. Upgraded to Craft 4.5.3 and Translations 3.2.10, and the error went away.

Tried downgrading to 3.2.9 on Craft 4.5.3 now, and the same error appears.

Are you running that test in dev mode, if not Craft will not show the twig error, but it's still there.

@bhupeshappfoster
Copy link
Collaborator

@aelvan

Thanks for bringing this issue in our notice.

Update:
This issue has been addressed in our next release which is expected to be released at end of this week or early next week.

@shnsumit
Copy link
Collaborator

Resolved in Release/3.3.0

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

Successfully merging a pull request may close this issue.

3 participants