-
-
Notifications
You must be signed in to change notification settings - Fork 4
🐞 ... causes problems with classic-SEO using php 8.1 ... #139
Comments
Thank you for reporting. This is due to Classic SEO not already being compatible with PHP > 8.0. In this branch there are a lot of fixes for those errors, if you can try it it will be very helpful. |
Classic SEO v2.2.0-alpha.0 is out to test PHP 8.1 and 8.2 compatibility. |
bravo!!! ... first five minutes testing with 8.1 ... everything works fine (anwalt-und-kommunalrecht.de)!!! ... tomorrow I 'll update another page ... and I'll try with 8.2 ... kind regards, if I should or can do something, I ask for a short message ... |
Hallo, testing with php 8.2: only problems with plugins:
Deprecated: Creation of dynamic property WP_Piwik::$statsPageId is deprecated in /.../wp-content/plugins/wp-piwik/classes/WP_Piwik.php on line 387
Deprecated: Creation of dynamic property YARPP::$is_custom_template is deprecated in /.../wp-content/plugins/yet-another-related-posts-plugin/classes/YARPP_Core.php on line 56 Otherwise everything is going well. Kind regards |
Hallo, php 8.1: in backend "dashboard -> updates" warning and deprecation: Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /homepages/23/d278325892/htdocs/kommunalrecht/wp-includes/formatting.php on line 4414 Kind regards |
Hallo, updated another website (rechtsanwalt-und-verwaltungsrecht.de) to 2.0 and there are using php 8.1 the following warnings and deprecations in backend: Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /.../wp-includes/functions.php on line 7048 Kind regards |
The |
Hallo, testing with php 8.1: causes problems with plugin "blog2social": Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /.../wp-includes/functions.php on line 7048 Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /.../wp-includes/functions.php on line 2165 Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /.../wp-includes/functions.php on line 7048 Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /.../wp-includes/functions.php on line 2165 Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /.../wp-includes/functions.php on line 7048 Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /.../wp-includes/functions.php on line 2165 Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /.../wp-includes/functions.php on line 7048 Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /.../wp-includes/functions.php on line 2165 Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /.../wp-includes/functions.php on line 7048 Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /.../wp-includes/functions.php on line 2165 Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /.../wp-includes/functions.php on line 7048 Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /.../wp-includes/functions.php on line 2165 Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /.../wp-includes/functions.php on line 7048 Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /.../wp-includes/functions.php on line 2165 Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /.../wp-includes/functions.php on line 7048 Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /.../wp-includes/functions.php on line 2165 Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /.../wp-includes/functions.php on line 7048 Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /.../wp-includes/functions.php on line 2165 Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /.../wp-includes/functions.php on line 7048 Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in vwp-includes/functions.php on line 2165 Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /.../wp-includes/functions.php on line 7048 Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /.../wp-includes/functions.php on line 2165 Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /.../wp-includes/functions.php on line 7048 Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /.../wp-includes/functions.php on line 2165 Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /.../wp-includes/functions.php on line 7048 Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /.../wp-includes/functions.php on line 2165 Warning: Cannot modify header information - headers already sent by (output started at /.../wp-includes/functions.php:7048) in /.../wp-admin/includes/misc.php on line 1444 Warning: Cannot modify header information - headers already sent by (output started at /.../wp-includes/functions.php:7048) in /.../wp-includes/functions.php on line 6891 Warning: Cannot modify header information - headers already sent by (output started at /.../wp-includes/functions.php:7048) in /.../wp-admin/admin-header.php on line 9 |
php 8.2 warnings and deprecations changed little bit: Deprecated: Creation of dynamic property YARPP::$is_custom_template is deprecated in /homepages/23/d278325892/htdocs/kommunalrecht/wp-content/plugins/yet-another-related-posts-plugin/classes/YARPP_Core.php on line 56 |
Those last ones are all caused by a specific plugin, which evidently hasn't yet been updated for PHP 8.1. (That's true of many plugins.) You need to report those issues to the plugin developer. |
Hallo, without plugins enabled I get the following deprecation message in backend -> Media -> Media Library updating to php 8.1 (20230710): Deprecated: preg_match(): Passing null to parameter #2 ($subject) of type string is deprecated in .../wp-includes/post.php on line 3017 without plugins enabled I get the following deprecation message in backend -> dashboard -> updates updating to php 8.1 (20230710): Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in .../wp-includes/formatting.php on line 4414 (anwalt-und-kommunalrecht.de) Kind regards |
@Soenke2 You need to work out what's causing this: |
Hallo,
thanks for the answer!
As far as I understand, I'm looking for errors in the formatting.php – line 4414.
(Warning: Cannot modify header information - headers already sent by (output started at /homepages/23/d278325892/htdocs/verwaltungsrecht/wp-includes/formatting.php:4414) in …)
In formatting.php from line 2706 – after the comma – everything is "grayed out" up to the end in line 6273:
…
2705 // WP fix for the bug with HTML comments.
2706 $newtext = str_replace( '< !--', '<!--', $newtext );
2707 $newtext = str_replace( '< !--', '<!--', $newtext );
…
Therefore I deleted - not knowing what I'm doing – line 2706. … as a result, the warning disappeared … but I doubt that this is the right approach …
Kind regards
Sönke
Von: Tim Kaye ***@***.***>
Gesendet: Dienstag, 11. Juli 2023 20:07
An: ClassicPress/ClassicPress-v2 ***@***.***>
Cc: Soenke2 ***@***.***>; Mention ***@***.***>
Betreff: Re: [ClassicPress/ClassicPress-v2] 🐞 ... causes problems with classic-SEO using php 8.1 ... (Issue #139)
@Soenke2 <https://github.com/Soenke2> You need to work out what's causing this: Warning: Cannot modify header information - headers already sent. It seems specific to your site(s) and it's going to cause other problems, which makes it difficult to know whether the other issues you've reported are actually caused by CP or, again, just specific to your site(s).
—
Reply to this email directly, view it on GitHub <#139 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKUKDVKOSFHBSWG46KJLCKDXPWI4TANCNFSM6AAAAAAZ5MZ3QM> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AKUKDVNKPZOLI6PRFJI7XHDXPWI4TA5CNFSM6AAAAAAZ5MZ3QOWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTBHMTRU.gif> Message ID: ***@***.*** ***@***.***> >
|
Hallo,
please consider my last mail irrelevant.
The correct solution is: add @ before line 9 in admin-header.php.
kind regards
Von: Tim Kaye ***@***.***>
Gesendet: Dienstag, 11. Juli 2023 20:07
An: ClassicPress/ClassicPress-v2 ***@***.***>
Cc: Soenke2 ***@***.***>; Mention ***@***.***>
Betreff: Re: [ClassicPress/ClassicPress-v2] 🐞 ... causes problems with classic-SEO using php 8.1 ... (Issue #139)
@Soenke2 <https://github.com/Soenke2> You need to work out what's causing this: Warning: Cannot modify header information - headers already sent. It seems specific to your site(s) and it's going to cause other problems, which makes it difficult to know whether the other issues you've reported are actually caused by CP or, again, just specific to your site(s).
—
Reply to this email directly, view it on GitHub <#139 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKUKDVKOSFHBSWG46KJLCKDXPWI4TANCNFSM6AAAAAAZ5MZ3QM> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AKUKDVNKPZOLI6PRFJI7XHDXPWI4TA5CNFSM6AAAAAAZ5MZ3QOWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTBHMTRU.gif> Message ID: ***@***.*** ***@***.***> >
|
Hallo, 12.07.2023 - v2.2023-11-07 - php 8.1: on two websites everything works fine php 8.2: on one site there are reports about yarpp: Deprecated: Creation of dynamic property YARPP::$is_custom_template is deprecated in /homepages/23/d278325892/htdocs/verwaltungsrecht/wp-content/plugins/yet-another-related-posts-plugin/classes/YARPP_Core.php on line 56 It is not clear to me why no messages are displayed on the other website, on which I also use yarpp. Sönke p.s.: I'll update another side to v2 |
This one is YARPP not fully supporting PHP 8.2. |
Hallo, third website (rechtsanwalt-und-mietrecht.de) updated - I'll contact yarpp-support and report the bugs. When it's done I'll report - blog2social solved problems with an update. Well done! Sönke |
p.s.: using php 8.1 -> dashboard -> updates there are shown two deprecations clicking updates: Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /.../mietrecht/wp-includes/formatting.php on line 4414 When I click refresh in the browser, the messages go away. Sönke |
YARPP has been updated to fully support PHP 8.2 in v5.30.7 |
Expected behavior
Hallo,
I'm not sure, if it is helpful, ...
but I was curious to try v2.
Everything works using 8.0 ..., only error messages using php 8.1.
... only causes problems with classic-SEO using php 8.1, not with ... 8.0 ...
kiind regards
I think I am not in the position to really help ...
Current behavior
see above
Possible solution
see above
Steps to reproduce bug
see above
Context
see above
ClassicPress version
v2
PHP version
8.1
Can you help?
No, I can't help
The text was updated successfully, but these errors were encountered: