CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 02:20:24 GMT
content-type: text/html; charset=utf-8
cache-control: no-cache
content-security-policy: default-src 'none'; base-uri 'self'; child-src github.githubassets.com github.com/assets-cdn/worker/ github.com/assets/ gist.github.com/assets-cdn/worker/; connect-src 'self' uploads.github.com www.githubstatus.com collector.github.com raw.githubusercontent.com api.github.com github-cloud.s3.amazonaws.com github-production-repository-file-5c1aeb.s3.amazonaws.com github-production-upload-manifest-file-7fdce7.s3.amazonaws.com github-production-user-asset-6210df.s3.amazonaws.com *.rel.tunnels.api.visualstudio.com wss://*.rel.tunnels.api.visualstudio.com github.githubassets.com objects-origin.githubusercontent.com copilot-proxy.githubusercontent.com proxy.individual.githubcopilot.com proxy.business.githubcopilot.com proxy.enterprise.githubcopilot.com *.actions.githubusercontent.com wss://*.actions.githubusercontent.com productionresultssa0.blob.core.windows.net/ productionresultssa1.blob.core.windows.net/ productionresultssa2.blob.core.windows.net/ productionresultssa3.blob.core.windows.net/ productionresultssa4.blob.core.windows.net/ productionresultssa5.blob.core.windows.net/ productionresultssa6.blob.core.windows.net/ productionresultssa7.blob.core.windows.net/ productionresultssa8.blob.core.windows.net/ productionresultssa9.blob.core.windows.net/ productionresultssa10.blob.core.windows.net/ productionresultssa11.blob.core.windows.net/ productionresultssa12.blob.core.windows.net/ productionresultssa13.blob.core.windows.net/ productionresultssa14.blob.core.windows.net/ productionresultssa15.blob.core.windows.net/ productionresultssa16.blob.core.windows.net/ productionresultssa17.blob.core.windows.net/ productionresultssa18.blob.core.windows.net/ productionresultssa19.blob.core.windows.net/ github-production-repository-image-32fea6.s3.amazonaws.com github-production-release-asset-2e65be.s3.amazonaws.com insights.github.com wss://alive.github.com wss://alive-staging.github.com api.githubcopilot.com api.individual.githubcopilot.com api.business.githubcopilot.com api.enterprise.githubcopilot.com; font-src github.githubassets.com; form-action 'self' github.com gist.github.com copilot-workspace.githubnext.com objects-origin.githubusercontent.com; frame-ancestors 'none'; frame-src viewscreen.githubusercontent.com notebooks.githubusercontent.com; img-src 'self' data: blob: github.githubassets.com media.githubusercontent.com camo.githubusercontent.com identicons.github.com avatars.githubusercontent.com private-avatars.githubusercontent.com github-cloud.s3.amazonaws.com objects.githubusercontent.com release-assets.githubusercontent.com secured-user-images.githubusercontent.com/ user-images.githubusercontent.com/ private-user-images.githubusercontent.com opengraph.githubassets.com marketplace-screenshots.githubusercontent.com/ copilotprodattachments.blob.core.windows.net/github-production-copilot-attachments/ github-production-user-asset-6210df.s3.amazonaws.com customer-stories-feed.github.com spotlights-feed.github.com objects-origin.githubusercontent.com *.githubusercontent.com; manifest-src 'self'; media-src github.com user-images.githubusercontent.com/ secured-user-images.githubusercontent.com/ private-user-images.githubusercontent.com github-production-user-asset-6210df.s3.amazonaws.com gist.github.com; script-src github.githubassets.com; style-src 'unsafe-inline' github.githubassets.com; upgrade-insecure-requests; worker-src github.githubassets.com github.com/assets-cdn/worker/ github.com/assets/ gist.github.com/assets-cdn/worker/
referrer-policy: no-referrer-when-downgrade
server-timing: pull_request_layout-fragment;desc="pull_request_layout fragment";dur=292.932038,conversation_content-fragment;desc="conversation_content fragment";dur=540.283077,conversation_sidebar-fragment;desc="conversation_sidebar fragment";dur=363.112992,nginx;desc="NGINX";dur=0.83015,glb;desc="GLB";dur=137.170163
strict-transport-security: max-age=31536000; includeSubdomains; preload
vary: X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, X-Requested-With,Accept-Encoding, Accept, X-Requested-With
x-content-type-options: nosniff
x-frame-options: deny
x-voltron-version: 266d7a9
x-xss-protection: 0
server: github.com
content-encoding: gzip
accept-ranges: bytes
set-cookie: _gh_sess=V0p1AIZPg14Z1uQNIgHN57385TiWeyoKLHhjiMEFEiLQEZG0VrVg5CA0WXurmlYT4DPGRHR0MmOEUYnKTeiBEZtHJjACvzSVAcIiub4PLgcqORclHfFsUAhVpUXohyHpTuhZHFHvck%2FnQsVhgT%2Bhm9Ej2qAaUGm3CwPw8tW4ANXWjG0TevmYYf8XmSJjZ0P8jWqx4eG0FVgcplFFjWkyNS3tRiliCko8Ja5N5eYKx6PrQgBNHDOQtw13paENRj%2FdpKTNUlH4ju3BiV%2FlzUL2aw%3D%3D--j%2BKCHZniavgtIRio--FxWJ3h8QuI1DywBP1z2rLA%3D%3D; Path=/; HttpOnly; Secure; SameSite=Lax
set-cookie: _octo=GH1.1.39485849.1760062823; Path=/; Domain=github.com; Expires=Sat, 10 Oct 2026 02:20:23 GMT; Secure; SameSite=Lax
set-cookie: logged_in=no; Path=/; Domain=github.com; Expires=Sat, 10 Oct 2026 02:20:23 GMT; HttpOnly; Secure; SameSite=Lax
x-github-request-id: E876:2B328A:1191C99:1552260:68E86D67
PHP 8.4 | Fix CSV escaping deprecation notices by jrfnl · Pull Request #5991 · wp-cli/wp-cli · GitHub
Skip to content
Navigation Menu
{{ message }}
-
Notifications
You must be signed in to change notification settings - Fork 1k
PHP 8.4 | Fix CSV escaping deprecation notices #5991
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
Merged
swissspidy
merged 3 commits into
wp-cli:main
from
jrfnl:feature/php-8.4-fix-csv-deprecation
Oct 1, 2024
Merged
PHP 8.4 | Fix CSV escaping deprecation notices #5991
swissspidy
merged 3 commits into
wp-cli:main
from
jrfnl:feature/php-8.4-fix-csv-deprecation
Oct 1, 2024
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Okay, so this is an awkward one.... The short of it, is that the custom escaping mechanism available for `fputcsv()`, `fgetcsv()` and `str_getcsv()` is kind of broken and using it is discouraged. However, the default parameter value for the optional `$escape` parameter is still `"\\"`, which activates it. Since PHP 7.4, it is allowed to pass an empty string to `$escape`, which effectively de-activates the PHP native custom escaping mechanism. Prior to PHP 7.4, passing an empty string would fall through to the default value of the parameter. Since PHP 8.4, not passing the `$escape` is deprecated - which effectively makes it a required parameter _after_ two optional parameters... 🤦🏻♀️ The intention is to change the default value to an empty string in a future PHP version (PHP 9.0?) and once that's done, the "required optional" `$escape` parameter can be removed again (providing you want to follow the advise of disabling the custom escaping mechanism)... Yes, don't ask. I've [challenged the implementation of this deprecation](php/php-src#15569 (comment)), but my objections were waved aside. So, generally speaking to handle this deprecation there are three options: * Pass the parameter and set it explicitly to the current default value `"\\"`. * Pass the parameter and set it explicitly to an empty string to deactivate the PHP custom escaping mechanism on PHP 7.4+ and let it fall through to the default value for escaping prior to PHP 7.4. This may cause issues when an export was created with the `"\\"` value for escaping and an import is done without escaping. * Silence the deprecation notice for the time being by using the `@` operator and run the risk of other notices/warnings (and prior to PHP 8.0 errors) from the function call being silenced. All things considering and keeping in mind that this code base still has a PHP 5.6 minimum, I think it would probably be best to go for option 1, to prevent potential import/export file compatibility problems. This commit implements this. Refs: * https://wiki.php.net/rfc/deprecations_php_8_4#deprecate_proprietary_csv_escaping_mechanism * https://wiki.php.net/rfc/kill-csv-escaping * php/php-src 15362 * php/php-src 15569
swissspidy
approved these changes
Oct 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
You can’t perform that action at this time.
Okay, so this is an awkward one....
The short of it, is that the custom escaping mechanism available for
fputcsv()
,fgetcsv()
andstr_getcsv()
is kind of broken and using it is discouraged. However, the default parameter value for the optional$escape
parameter is still"\\"
, which activates it.Since PHP 7.4, it is allowed to pass an empty string to
$escape
, which effectively de-activates the PHP native custom escaping mechanism. Prior to PHP 7.4, passing an empty string would fall through to the default value of the parameter.Since PHP 8.4, not passing the
$escape
is deprecated - which effectively makes it a required parameter after two optional parameters... 🤦🏻♀️ The intention is to change the default value to an empty string in a future PHP version (PHP 9.0?) and once that's done, the "required optional"$escape
parameter can be removed again (providing you want to follow the advise of disabling the custom escaping mechanism)...Yes, don't ask. I've challenged the implementation of this deprecation, but my objections were waved aside.
So, generally speaking to handle this deprecation there are three options:
"\\"
."\\"
value for escaping and an import is done without escaping.@
operator and run the risk of other notices/warnings (and prior to PHP 8.0 errors) from the function call being silenced.All things considering and keeping in mind that this code base still has a PHP 5.6 minimum, I think it would probably be best to go for option 1, to prevent potential import/export file compatibility problems.
This commit implements this.
Refs: