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

Broken Page Backend Preview in TYPO3 v13.4 and yoast_seo v10.0 #584

Open
2 tasks done
eckonator opened this issue Oct 23, 2024 · 1 comment
Open
2 tasks done

Broken Page Backend Preview in TYPO3 v13.4 and yoast_seo v10.0 #584

eckonator opened this issue Oct 23, 2024 · 1 comment

Comments

@eckonator
Copy link

  • I've read and understood the contribution guidelines.
  • I've searched for any related issues and avoided creating a duplicate issue.

Please give us a description of what happened.

JavaScript files can't be loaded in my local DDEV project in TYPO3 v13.4 Backend:

Uncaught (in promise) TypeError: Der Spezifizierer "@yoast/yoast-seo-for-typo3/dist/plugin.js" war ein blanker Spezifizierer, wurde aber nicht zu etwas neu zugeordnet. Relative Modulspezifizierer müssen mit "./", "../" oder "/" beginnen. java-script-item-processor.js
Uncaught (in promise) TypeError: Der Spezifizierer "@yoast/yoast-seo-for-typo3/yoastModalEs6.js" war ein blanker Spezifizierer, wurde aber nicht zu etwas neu zugeordnet. Relative Modulspezifizierer müssen mit "./", "../" oder "/" beginnen. java-script-item-processor.js

Howto fix this issue?

I have compared the backend integration of JavaScripts in EXT:yoast_seo with EXT:news extension from Georg Ringer. I noticed that there is an incorrect spelling of a file in the yoast_seo extension.

Wrong:
vendor/yoast-seo-for-typo3/yoast_seo/Configuration/JavascriptModules.php

Correct:
vendor/yoast-seo-for-typo3/yoast_seo/Configuration/JavaScriptModules.php

After changing this and flush caches, the preview works fine in backend now. Please fix it in next v10 release. Thank you!

Technical info

  • TYPO3 version: v13.4
  • Yoast SEO version: v10.0
@RinyVT
Copy link
Collaborator

RinyVT commented Oct 23, 2024

Thanks for raising this issue! Apparently this worked on my case-insensitive ddev environment?
But I've opened up a PR for the next 10.1.0 where this issue has been fixed and I've added some new functionality.
I'm hoping to add some more bugfixes to that release but if that takes too long I'll release it first :)

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

2 participants