[In der nächsten Version behoben] Identified error in toolset views code

[Author]

Artikel

[jasonH-4]

Hi there,

I am following up on the resolved ticket https://toolset.com/forums/topic/fatal-error-with-toolset-views-and-php-8-1/

When I upgraded to Toolset Views from 3.6.16 to 3.6.18 it still produces this error. You said it might not be fixed in the latest release but want to make sure it's still going to get included in a future release.

As a reminder, it's this bit of code:

wp-content\plugins\wp-views\vendor\toolset\toolset-common\inc\autoloaded\utils\Attachments.php line 68:
// Split the $url into two parts with the upload directory as the separator.
// MODIFIED TO HANDLE CUSTOM UPLOAD LOCATION AT ROOT URL WITH NO TRAILING SLASH
$wp_parsed_url = wp_parse_url( $this->get_base_upload_directory(), PHP_URL_PATH );
$parsed_url = is_string($wp_parsed_url) ? explode( $wp_parsed_url, $url ) : [];

Thanks!

[Mateus Getulio]

Hi Jason,

Thank you for reaching out and I apologize for the delay caused by the weekend.

I wanted to let you know that we recently launched a new version of Toolset to address compatibility with WordPress 6.7, which included some fixes for Toolset Blocks: https://toolset.com/errata/image-block-displays-wrong-image-size-with-wordpress-6-7/.

However, this release does not yet include the definitive fix for the issue that was discussed in your previous ticket (https://toolset.com/forums/topic/fatal-error-with-toolset-views-and-php-8-1/).

Our developers are actively working on resolving this, and we’re making it a priority to include the fix in an upcoming release. I’ll keep you updated on the progress, and we appreciate your understanding as we work to ensure everything is thoroughly tested before it goes live.

Please let us know if you have any further questions or concerns in the meantime.

Best regards,
Mateus