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

TYPO3 10/11 compatibility #15

Closed
klodeckl opened this issue Mar 2, 2022 · 7 comments · Fixed by #18
Closed

TYPO3 10/11 compatibility #15

klodeckl opened this issue Mar 2, 2022 · 7 comments · Fixed by #18

Comments

@klodeckl
Copy link

klodeckl commented Mar 2, 2022

Will there be a version for TYPO3 10 and 11? Is the project alive?

@CDRO
Copy link
Owner

CDRO commented Mar 2, 2022

At the moment, we do not have any customers using this version in TYPO3 10 or 11, so I cannot tell you when and if there will be a new version.

For the last three years, the extension was community maintained and we publish them after reviewing the changes, but we are not actively developing this extension anymore.

@klodeckl
Copy link
Author

Thank you for the info :)

@klodeckl
Copy link
Author

klodeckl commented May 3, 2022

@cweiske I just tested your pull request. When I am logged out from the backend and log in in the frontend I get the following error: "" is not a valid cache entry identifier.
The error does not occur when I am already logged in in the backend.

@cweiske
Copy link
Contributor

cweiske commented May 3, 2022

@klodeckl This is strange, because simulatebe does not use any caches.

@klodeckl
Copy link
Author

klodeckl commented May 3, 2022

If I uninstall simulatebe the error is gone. Very strange.

@cweiske
Copy link
Contributor

cweiske commented May 3, 2022

Do you have a backtrace for that error?

@klodeckl
Copy link
Author

klodeckl commented May 3, 2022

I installed the extension again and it seems to work now…
In the earlier days updating a big TYPO3 system was less frustrating ;)

@CDRO CDRO closed this as completed in bebf952 May 25, 2022
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