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

Incompatibility with TYPO3 v8 due to missing TYPO3\CMS\Core\Site\SiteFinder #24

Closed
julianhofmann opened this issue May 7, 2020 · 4 comments · Fixed by #25
Closed

Incompatibility with TYPO3 v8 due to missing TYPO3\CMS\Core\Site\SiteFinder #24

julianhofmann opened this issue May 7, 2020 · 4 comments · Fixed by #25

Comments

@julianhofmann
Copy link
Contributor

\IchHabRecht\Filefill\Repository\DomainResourceRepository uses TYPO3\CMS\Core\Site\SiteFinder which does not exist in TYPO3 v8. So the package could not be compatible with TYPO3 v8.7 anymore.

@IchHabRecht
Copy link
Owner

Hi @julianhofmann,

Thanks for your report. The SiteFinder is called only in versions of 9.5 and above. See https://github.com/IchHabRecht/filefill/blob/master/Classes/Repository/DomainResourceRepository.php

This is perfectly fine for TYPO3 8.7 as the class isn't used here.

@julianhofmann
Copy link
Contributor Author

Theoretically, you're right.

But the version_compare() does not match because of wrong parameter order:
version_compare(TYPO3_version, '<', '10')

Should be:

version_compare ( string $version1 , string $version2 , string $operator ) : bool

@IchHabRecht
Copy link
Owner

Hi @julianhofmann,

That's a better report than the first one ;-) Thanks for your pull request.

@julianhofmann
Copy link
Contributor Author

You're right. I had not analyzed the reason for the problem before you pointed out the version compare. Because I had the extension installed in a TYPO3 v8.7 and got an exception when running it, I took a deeper look.

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.

2 participants