Robin
My feedback
7 results found
-
24 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
An error occurred while saving the comment An error occurred while saving the comment Robin
commented
I'm trying to actually use Plesk's Git extension in prod for the first time and I find it's absolutely useless as it doesn't support this feature.
Using a dev / master branch is the very basic of Git.
Please support this feature ASAP.Robin
supported this idea
·
-
5 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 Robin
commented
This KB article talks about Plesk's limitation here:
https://support.plesk.com/hc/en-us/articles/360014490834-How-to-change-default-charset-from-utf8-unicode-ci-to-utf8mb4-unicode-ci-in-MySQL-in-Plesk-for-Linux-By defaults, collation is "utf8" which is "utf8bm3" which is very very obsolete.
Plesk should now use utf8mb4_unicode_ci at least, or utf8mb4_unicode_520_ci when supported.Robin
supported this idea
·
-
406 votes
As UserVoice staff cleaned up the most of twisted voices, I’ve returning this suggestion to open discussion.
Everyone, please continue voting for this feature if you consider it important.
—IB
Robin
supported this idea
·
-
79 votesRobin
supported this idea
·
-
26 votes
This is a valid request, for example when a provider does not want to offer free certificates to some customers. 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.
-- PD
Robin
supported this idea
·
-
18 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.Robin
supported this idea
·
-
12 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.
—
IGRobin
shared this idea
·
Workaround: Add the repo a second time, change "Repository name" (otherwise it will tell you it already exists), change branch, change deploy path. Done.