nsp-code

Thanks for your feedback.
Can you share details on what what the problem and how you managed to make a fix?

Hi,
Can you make sure you use the latest plugin code, also the last ACF add-ons ? Possible you’re rely on ACF v4 instead the last series v5?

Thanks

Thanks for your feedback.
1) Actually this need to stay as .php to prevent certain glitches and incompatibilities.

2) Yes this is possible, but it will need to be created. I suggest something like this:
a) Add a filter for wph/ob_start_callback through which you will modify any admin.php? to admin?
b) You should add a custom rule within .htaccess
RewriteCond %{HTTP_COOKIE} ^.*wordpress_logged_in.*$ [NC]
RewriteRule ^admin(.*) /wp-admin/admin.php$1 [L]
You should change the wp-admin.php path accordingly to your actual site structure. Also this rule should be placed outside of #START – WP Hide & Security Enhancer and #END – WP Hide & Security Enhancer to prevent from being removed when you change a setting within the plugin.

Thanks

Hi,
Thanks for your feedback, i’ll check the src and srcset issue, possible there’s a glitch with that part.
As clarification of the Uploads setting, within the editor it will use the virtual address only if Block uploads URL is turned on. Since no files are being available through default url, it will rely on virtual. But when you disable the plugin, the virtual urls will stay, however there’s no rewrite code anymore.
All new links will be the same, there’s no difference between admin and front side, this is the way it works.
There’s a bit of additional description for that part within the plugin interface.

Thanks

Did you tried to set to No the Wp Hide -> Rewrite -> URL Slash as this is the only option which possible decrease an overall site speed.

This JavaScript error is produced by another code, can you try to de-activate other plugins one by one to see the exact cause? Or see the browser console and the error message above, there should be a path to exact file.

As far as i understand the Autosort is turned ON. IN such case you need to include a ignore_custom_sort within custom query arguments more details at http://www.nsp-code.com/advanced-post-types-order-api/sample-usage/

Hello,
This is a limitation of menu_order post attribute which can held only a value at a time. That means, if you make a sort in one area, you will lose the previous order for another section. For that reason the Post Types Order make sorting only for Archive (all posts).

As alternative you may want to check with Advanced Post Types Order plugin which use advanced coding techniques and a separate table to held all sort indexes so there’s no limitation on the sorting area.

Thanks