Jan Bludau
My feedback
7 results found
-
1 vote
Thank you for your suggestion. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
-- KvDAn error occurred while saving the comment -
229 votes
An error occurred while saving the comment Within the domain settings under databases it must be possible to rename a database within Plesk, because an external renaming of the database leads to information that is incorrect, which is why faulty backups are created.
SHOW CREATE DATABASE `jbs_translator_2024`;
ALTER DATABASE `jbs_translator_2024` COLLATE 'utf8mb4_general_ci';
UPDATE `psa`.`data_bases` SET `name`='jbs_translator_2024' WHERE `id`=57;
-
1 vote
Thank you for your suggestion. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
-- KvD
An error occurred while saving the comment Thanks Admin, I think that would be a huge improvement.
In general, it would certainly make sense to save all logs in SQLLite so that they are available more quickly, instead of analyzing and displaying *.txt *.bak -
1 vote
Thank you for your feedback Jan. We are however unsure about your request and are unable to replicate the issue you're describing. We love to know more about the issue and would appreciate if you could share more details about the issue and the steps you took when you encountered this issue.
-- KvD
An error occurred while saving the comment I'll try to explain it again:
1. Importing the database failed, only the framework (the created empty database) of the database is there, including the user of the database with password and rights.
2. An attempt to import the database again (Database -> Under Database -> Upload) overwrites the empty database and does not fill it.
I think that's a mistake.
Solution: The entire databases must be deleted directly, then the manual upload works
-
1 vote
Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important
-- SH
-
1 vote
Thank you for your suggestion. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
-- KvD
-
12 votes
Thank you for your idea! 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
In the domain overview you have the option to start a cron job. At the bottom right you can see that the cron job has been started. If the cron job has errors or was completed without errors, only a small part of the shell output is displayed. In my case, these are PHP cron jobs which also have corresponding output. It would be useful to see the complete output, especially in the event of an error.
Ideally, you would be able to enlarge the small window at the bottom left to enable a meaningful display of the output.
In the event of an error, you would immediately see the error directly in the cron script without having to start it manually via the SSH terminal.