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
"Class 'p\\Php80' not found" when use str_starts_with() in PHP7.3 or PHP7.4 #378
Comments
No idea. Can you provide a simple reproducer? |
Unfortunately no because big project in encrypted case ... |
Do you do some special things in composer.json? |
Do you encrypt your vendor folder? |
Hi everyone,
there is a "post-autoload-dump" script that modify autoload but nothing linked with this error.
Yes. In a similar project, we have to downgrade polyfill to 1.19 version to avoid errors. |
Can you copy/paste the content of |
`<?php /*
use Symfony\Polyfill\Php80 as p; if (\PHP_VERSION_ID >= 80000) { if (!defined('FILTER_VALIDATE_BOOL') && defined('FILTER_VALIDATE_BOOLEAN')) { if (!function_exists('fdiv')) { |
That might be the issue. |
Hi @nicolas-grekas, I removed our post-autoload-dump but the problem is still there. The "vendor\composer\autoload_static.php" seems to be good (before encryption) :
I don't understand where is the resolution error. Perhaps a link with the backslash used in class name ? (we can see double "\" in files on Windows) Greetings. |
The double I suspect that the issue might be related to your encryption layer then. |
Hi @stof, I have open a ticket on the encryption software. Thank you for your help everyone. |
We experience same problems, did you found a solution for this ? |
Hi @admindotnu, a ticket has been opened at our used encryption software, I will inform you if they find something. for information, a possible workaround we use temporarily is to replace all occurrences of "p\Php80" by "Symfony\Polyfill\Php80\Php80". Greetings. |
Hi,
In an encrypted environment, in a Windows PHP 7.3 or 7.4 project , we have this error :
Any idea what cause this problem ?
Greetings.
The text was updated successfully, but these errors were encountered: