Fabian Niesen
My feedback
118 results found
-
91 votes
Fabian Niesen supported this idea ·
-
100 votes
Fabian Niesen supported this idea ·
-
102 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular. Everyone, please continue voting for this feature if you consider it important.
—
IGFabian Niesen supported this idea ·
-
102 votes
Fabian Niesen supported this idea ·
-
110 votes
Thank you for your input! We will consider this functionality in upcoming releases, if it will be popular.
Everyone, please continue voting for this feature if you consider it important.-DL
Fabian Niesen supported this idea ·
-
218 votes
Thank you for your input! We will consider this functionality in upcoming releases, if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
ETFabian Niesen supported this idea ·
-
235 votes
Thank you for your input! We will consider this functionality in upcoming releases, if it will be popular.
Everyone, please continue voting for this feature if you consider it important.—
IGFabian Niesen supported this idea ·
-
292 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
— IB
Fabian Niesen supported this idea ·
-
307 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.— rk
Fabian Niesen supported this idea ·
-
465 votes
Fabian Niesen supported this idea ·
-
1,338 votes
Fabian Niesen supported this idea ·
-
20 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular. Everyone, please continue voting for this feature if you consider it important.
—
IGAn error occurred while saving the comment Fabian Niesen supported this idea ·
-
13 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
— AY
Fabian Niesen supported this idea ·
-
178 votes
Fabian Niesen supported this idea ·
-
213 votes
Fabian Niesen supported this idea ·
-
234 votes
Fabian Niesen supported this idea ·
-
466 votes
Thank you for your input. We will definitely look into integrating DynDNS in our future releases
Fabian Niesen supported this idea ·
-
616 votes
Since Plesk Onyx you will be able to install memcache as a Docker container and configure http(s) proxy rule for it to map to your web app.
Docker and proxy rules are available in Plesk Onyx Preview already, you can try it here https://talk.plesk.com/threads/plesk-onyx-preview-and-feedback.337172/
SE
Fabian Niesen supported this idea ·
-
861 votes
Would you mind to try Nginx caching in Plesk Onyx 17.8 Preview?
This would be very helpful to get your experienced feedback here http://www.surveygizmo.com/s3/4165754/Plesk-17-8-Preview
Fabian Niesen supported this idea ·
-
6 votes
In WP Multisite installations you have one single WP controlling many different websites and domains. "Cloning" a multisite installation seems to be a challenge, because when you clone a site, you need to mention a target where to clone the site to (a new URL, a new subdomain). As a multisite installation has many URLs, it seems impossible to clone these to one single domain. It will be unclear which domain is actually cloned or how to map source to target.
But as always, we're open for ideas and would love to hear more details from you how you imagine the workflow. Please describe in your comments what you expect to happen when you clone a multisite installation, e.g. how you'd want to map source to target(s). Would you for example want to see a dialog where you can enter new domains and subdomains for each existing URL in the…
Fabian Niesen supported this idea ·
It would be practical to mirror the backup directory via RSync with an external system, for example a NAS or a server in the office. This would allow us to prevent manipulation and compromise of the backup, for example via corresponding on-premise solutions.
Currently, I have to manually adjust the authorisations after each backup so that the NAS can download the new backups. So it's about pulling the backups from Plesk, not pushing them from the server to the backup.