Maya

Hi,
Is there a way to contact privately where to send the details?

Thanks

Hi,
If blocking the default wp-admin cause the issue for the Tutor LMS, it means that plugin has the wp-admin hard-coded somewhere in the code. Can you contact them for a fix, they should use something like https://developer.www.ads-software.com/reference/functions/admin_url/ to avoid hard-coding things.

Thanks

Hi,
The Tutor LMS might use the JSON REST service to interact with the PHP code. Can you ensure you didn’t blocked or disabled the service at WP Hide > Rewrites > JSON REST ?

Thanks

Hi,
You can try the followings:
1) Use the New JSON Path
2) Use Block default /wp-json with the selection Non-logged-in

3) Activate the PostProcessing for CSS and PostProcessing for JavaScript with the InPlace selection.
4) Add Replacements for your elementor, for more details see Hide Elementor Page Builder
5) Ensure you use the Document Loaded Assets PostProcessing option ( see the last part of the article ).

That should completely hide your Elementor on your site.
If you cannot figure out the options, since you are using the PRO, contact us directly and someone will help with that.

Thanks

Hi,
Can you ensure you didn’t disabled/blocked the JSON service through WP Hide > Rewrite > JSON REST. That is used by Elementor within it’s editor.

Thanks

Hi,
I’m not sure i can follow what you meant “When setting the response header, there will be a htaccess prompt. After refreshing, there is no such prompt.”.
Changing the default plugins slugs is part of the hiding process. So use that along with the other plugin options.

Thanks

Hi,
That should be fixed in the latest plugin version 2.5.6.

Thanks

Hi,
This should be fixed in the latest plugin version 2.5.6

Thanks

Hi,
What plugin version do you run at the moment ?

Thanks

Hi,
Sorry for the issue. I think you are using the WP Hide PRO ? If so, please contact us through the plugin website and a developer will assist with the Content Security Policy security header setup.

Thanks

Hi,
The message “cannot be written to your .htaccess” indicates that the plugin was unable to successfully write to the .htaccess file and verify that the rewrite rules were deployed and functioning correctly. If this message appears occasionally, yet the code is eventually written to the system, it may be due to your server’s configuration. Specifically, the server might use a core cache, which delays the processing of Apache rewrites by a few seconds. In that case you just have to hit again the interface Save button.

Regarding the login URL, if another code fails to work with the custom login, it might be relying on a hard-coded default (wp-admin) instead of dynamically retrieving the URL through a WordPress filter (e.g., admin_url). In such cases, there’s little that can be done from this side. You could try disabling the block on the default wp-admin temporarily or disabling the option until the other code is configured correctly.

When you mention “I set the response header,” are you referring to security headers? If so, these require a thorough understanding of each option, as well as the site’s structure and the services it uses. Automating this process is nearly impossible because misconfigured security headers can easily disrupt functionality. Instead, you can manually configure them by testing different options. Ensure you thoroughly check the front end to confirm everything continues to work as expected. Misconfigured headers can easily break the site.

Thanks

Hi,
Consider the security -> Headers plugin interface to add the security headers. There is a sample set-up for the headers which you can use to deploy a basic configuration.

Thanks

Hi,
Thanks for your feedback. This is already fixed in the latest 7.5.8 which you should be able to automatically update through the WordPress dashboard. Or consider to manually downloads it through your account at the plugin website.

Thanks

Hi,
You can use the filter pto/interface/query/args to change the arguments of the query that return the items to re-order:

add_filter ( 'pto/interface/query/args', 'pto_interface_query_args' );
function pto_interface_query_args( $args )
    {
        $args['post_status'] =  array ( 'publish' );

        return $args;            
    }

As alternative, consider the Advanced Post Types Order which has a visual interface through which you can select the post statuses to show in the list:

Thanks

Hi,
Sorry but the plugin can handle the archive ( all posts ). When filtering by a specific term (e.g., categories), it overwrites other sorting options, which can make things confusing.
The Advanced Post Types Order plugin can handle all sorting types. It uses a separate table to save order indexes, ensuring that sorting is not disrupted when updating the order for a specific category or other filters.

Thanks