Startseite›Toolset Professional Support›[Warten auf die Bestätigung des Benutzers] Deprecated error PHP on wp-content/plugins/wp-views/vendor/toolset/divi/includes
[Warten auf die Bestätigung des Benutzers] Deprecated error PHP on wp-content/plugins/wp-views/vendor/toolset/divi/includes
This support ticket is created vor 1 week, 3 days. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Sun
Mon
Tue
Wed
Thu
Fri
Sat
-
10:00 – 13:00
10:00 – 13:00
10:00 – 13:00
10:00 – 13:00
10:00 – 13:00
-
-
14:00 – 18:00
14:00 – 18:00
14:00 – 18:00
14:00 – 18:00
14:00 – 18:00
-
Zeitzone des Unterstützers: Asia/Kolkata (GMT+05:30)
Deprecated: Optional parameter $content declared before required parameter $render_slug is implicitly treated as a required parameter in /home/clients/cacdc1c3b1cfee8a704c1472149ea49b/sites/dev/wp-content/plugins/wp-views/vendor/toolset/divi/includes/modules/View/View.php on line 56
I resolved it by changing :
public function render( $attrs, $content = null, $render_slug ) {
To
public function render( $attrs, $content = null, $render_slug = '' ) {
Deprecated: strtolower(): Passing null to parameter #1 ($string) of type string is deprecated in /home/clients/cacdc1c3b1cfee8a704c1472149ea49b/sites/dev/wp-content/plugins/types/vendor/toolset/toolset-common/inc/m2m/DatabaseLayer/Version2/Migration/MigrationController.php on line 172
Deprecated: strtolower(): Passing null to parameter #1 ($string) of type string is deprecated in /home/clients/cacdc1c3b1cfee8a704c1472149ea49b/sites/dev/wp-content/plugins/types/vendor/toolset/toolset-common/inc/m2m/DatabaseLayer/Version2/Migration/MigrationController.php on line 172
Hello. Thank you for contacting the Toolset support.
Thank you for sharing that. I've escalated the deprecated notices in front of our Devs and they will do their best in order to fix this. I will udpate you here when we release the hotfix version that contains the fix for this issue (Deprecated notices).
