Facebook
Twitter-
Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring. We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design. If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
-
Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations. -
The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
Wordpress toolkit hotlink protection - RSS feed
- Thread starter Vipa
- Start date
Yes I know that RSS-feed readers do exactly what "hotlink protection" tries to prevent.
That's why I asked if it is possible to include an exception for this.
For example to exclude featured images from this protection as they are used for RSS feeds or if the page is posted to facebook or twitter.
Otherwise you cannot use hotlink protection if you want to use any of these services.
That's why I asked if it is possible to include an exception for this.
For example to exclude featured images from this protection as they are used for RSS feeds or if the page is posted to facebook or twitter.
Otherwise you cannot use hotlink protection if you want to use any of these services.
At the moment, this is impossible to do.
The whitelist of domains includes only the domain of the site and google.com, and is not available for manual configuration.
The only workaround is to add directives ("Additional Apache directives"/"Additional nginx directives" in the web server settings for the domain) that take priority over "hotlink protection" rules and return images for the required services.
The whitelist of domains includes only the domain of the site and google.com, and is not available for manual configuration.
The only workaround is to add directives ("Additional Apache directives"/"Additional nginx directives" in the web server settings for the domain) that take priority over "hotlink protection" rules and return images for the required services.
