Hi @lalexandwporg thanks for raising the issue.
I wasn’t able to reproduce it using the Blocksy theme. It is working fine both in the editor and the frontend. (Please see the image below)
Character rendering using Blocksy theme To narrow down the root cause of the issue, try the following:
Switch to a WordPress default theme such as TwentyTwenty Two.
Deactivate all plugins except Insert Special Characters and see if the character is visible.
If yes, then switch theme to Blocksy and check if the character is still correctly visible.
If the character is not visible using Blocky then you will have to reach out to the theme developer for additional support.
If the character works with Blocksy, then start activating the plugins one by one to identify which plugin breaks the character.
Let us know if this work for you.
Awesome! I’m glad that worked!
I will close this ticket and mark it as resolved.
Hi @tien-nguyen
Thank you for reporting this issue.
I was able to reproduce it on my setup.
I have raised the issue on GitHub, you can track it here .
Hi @ld2002
wp-config.php loads before the Restricted Site Access plugin.
This is the reason why running Restricted_Site_Access::add_ips( array( 'five' => $server_ip) ); inside wp-config.php throws an error.
I would suggest creating a small plugin and running this code on the plugins_loaded hook.
Or, if you’re not comfortable with creating a plugin, then you can use the Code Snippets Pro plugin and achieve the same result.
Let us know if that helps.
Cheers!
This reply was modified 3 years, 6 months ago by Siddharth Thevaril
Hi all, this has been fixed in the patch release 7.3.4.
@mikegibbons4 Thanks for the details.
I was able to reproduce this, confirming this as a bug. We will be working on the fix soon.
Hi @webteambd
Thanks for raising those questions. Answering them below:
1. Is it okay if we’re still using v7.3 without anything breaking/functions are working properly?
RSA 7.3.2 does not introduce any changes that would break on PHP 7.3. However, if you are planning to use RSA 7.3.2 on PHP 7.3 by modifying the PHP requirement in the plugin header, then as a good safety practice, please test it on a staging environment before you push it to live.
2. Are the functions from PHP v7.4 used to fix vulnerabilities so that we’re forced to upgrade to v7.4 to be safe?
The main reason to upgrade to 7.4 here is to officially support the minimum stable version of PHP. Whenever a PHP version reaches its end of life , we bump up the minimum supported version of PHP in our plugin, along with any changes required in the plugin to support the min PHP version.
3. Could you guys make a patch for v7.3?
As per the process we follow, I don’t think it is possible at the moment. I will still discuss this internally with the team.
This reply was modified 3 years, 9 months ago by Siddharth Thevaril
Hi @sequence10
There was a similar question regarding exempting a page which we answered here –
https://wordpress.org/support/topic/exclude-restric-access-for-one-page/
Let us know if that works for you.
Hey @lucyhoggescc we haven’t heard from you in a while, I will mark this as resolved. Please feel free to open a new ticket if this is still an issue.
Hi @cassbones
A similar question has been answered with examples here:https://wordpress.org/support/topic/exclude-restric-access-for-one-page/
Let us know if that helps.
For multiple pages, you will have to add multiple conditionals similar to:
if ( isset( $wp->request ) && 'profil-membre' === $wp->request ) {
$is_restricted = false;
}where profil-membre will be replaced by the path of the page you want unrestricted.
Hi @debby78018
Apologies for the delay.
Please test the following code snippet on a staging environment before running it on a production/live site just to be safe.
add_filter( 'login_redirect', 'debby_redirect_to_home_after_login', 10, 3 );
function debby_redirect_to_home_after_login( $redirect_to, $requested_redirect_to, $user ) {
$path = wp_parse_url( $requested_redirect_to, PHP_URL_PATH );
if ( empty( $path ) ) {
return $redirect_to;
}
$path = trailingslashit( $path );
if ( '/connexion/' === $path ) {
return get_home_url();
}
return $redirect_to;
}Let us know if this works.
Hi @debby78018 , I’ve updated the code, can you try again?
Hi @debby78018
Assuming the URL for the member login page is:
https://intranet-lecompagnonnage.fr/profil-membre
You can try the following:
add_filter( 'restricted_site_access_is_restricted', 'exclude_membre_page', 10, 2 );
function exclude_membre_page( $is_restricted, $wp ) {
if ( isset( $wp->request ) && 'profil-membre' === $wp->request ) {
$is_restricted = false;
}
return $is_restricted;
}Let us know if this works for you.
Hi @redorca Thank you for reporting this. I was able to reproduce the issue.
You can track it here – https://github.com/10up/insert-special-characters/issues/127
