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: Key "heading" for array with keys "manageSitemap, manageRedirects" does not exist. #406

Open
MarkOlijslagers opened this issue May 19, 2022 · 6 comments

Comments

@MarkOlijslagers
Copy link

Description

When i try to access my account page in the Craft control panel (/admin/myaccount) the following error occurs:

Twig Runtime Error – Twig\Error\RuntimeError
Key "heading" for array with keys "manageSitemap, manageRedirects" does not exist.

I am using Craft CMS 4.0.2 and SEO 4.0.0

Steps to reproduce

  1. Login the admin panel and go to /admin/myaccount

Additional info

  • Craft version: 4.0.2
  • SEO version: 4.0.0
  • PHP version: 8.1
  • Database driver & version: MySQL
  • Other Plugins: Redactor
@rostockahoi
Copy link

This one is fixed in 4.0.2 but there is no release in Packagist, so it is not installable right now.

@rostockahoi
Copy link

See #405

@braedencrankd
Copy link

Can also confirm I have this error

@niektenhoopen
Copy link
Contributor

I have already fixed this one but it's not tagged correctly in Packagist. Please follow the instructions in #405

@Tam: Any idea when the tagging in Packagist will be fixed? It would solve #405 and #406

@dejury
Copy link
Contributor

dejury commented Jun 3, 2022

@niektenhoopen see my suggestion in #405. This will fix the issue.

@niektenhoopen
Copy link
Contributor

@dejury I don't have the issue. Technically I was the person who touched the version in composer in the PR that added Craft 4 support so a git blame would probably point to me ;-) I kept in in the composer.json file because it was already there: https://github.com/ethercreative/seo/pull/397/files#diff-d2ab9925cad7eac58e0ff4cc0d251a937ecf49e4b6bf57f8b95aab76648a9d34R5

Thanks for PR #411. Hope it will be merged soon.

Tam added a commit that referenced this issue Jun 8, 2022
Fixing #405 & #406: Remove version number
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

No branches or pull requests

5 participants