@mmkiyan Thank you for reaching out. Can you please tell me your WordPress and PHP version?
Also, when it is throwing you this error?
Regards,
Sami
I see a similar error when I test PHP 8.0. I think they said they are working on a new release for this.
@jimhill10 Thank you for pointing to PHP 8.0. I will check this issue with PHP 8.0, With PHP 7 everything seems fine to me.
@mmkiyan Please confirm your PHP version.
I was doing testing on PHP 8.0 for a retheming project, that is where I saw it. I am confident in your fixes in the new paid version. Thanks so much for your excellent service.
@jimhill10 @mmkiyan I am not able to generate this issue. I have created a new site on PHP 8.0 and everything is working fine. I am using Twenty Twenty-One theme and Custom Permalinks v2.2.0 on WordPress v5.8.1.
Is there anything else (Plugin, Theme) I need to install to re-generate this issue or can you help to replicate it?
Thanks & Regards,
Sami
This is the error on get on my dev site when I change it from PHP 7.4 to PHP 8.0:
Fatal error: Array and string offset access syntax with curly braces is no longer supported in /home/oyjgnovv/public_html/wp-content/plugins/custom-permalinks-pro/frontend/class-custom-permalinks-frontend.php on line 501
-
This reply was modified 4 years, 7 months ago by
Jim Hill.
This change does at least make it work in PHP other than deprecation errors from my theme:
wp-content/plugins/custom-permalinks-pro/frontend/class-custom-permalinks-frontend.php on lines 499-505:
if ( trim( $_CPRegisteredURL, '/' ) == trim( $request, '/' ) ) {
if ( isset( $url['path'] ) ) {
return ( $string[0] == '/' ? '/' : '' ) . trailingslashit( $url['path'] ) . $_CPRegisteredURL;
} else {
return ( $string[0] == '/' ? '/' : '' ) . $_CPRegisteredURL;
}
}
@jimhill10 Both of the above mentioned issues are no longer exist in the FREE version of the plugin. You are using PRO version of the plugin which doesn’t contains these fixes.
I am waiting for resolving all the issues first with the FREE version then I will release the updates in the PRO version of the plugin.
@mmkiyan As per not getting any response from you and not able to generate the issue you were mentioned, I am marking this thread as resolved. If you will find any issue then please open a new thread.
Thanks & Regards,
Sami
I tested this on my dev server and it resolved the issue. Please add some clarification for the upgrade procedure. I installed the new plugin by uploading it. I did not activate it. I then deactivated the version 1.x pro. I then activate the new 2.0 plugin. It copied the existing settings from 1.x over nicely. Is this the correct upgrade method?
