Skip to content

Jan Bludau

My feedback

10 results found

  1. 605 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jan Bludau supported this idea  · 
  2. 851 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jan Bludau supported this idea  · 
  3. 1,298 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jan Bludau supported this idea  · 
  4. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Jan Bludau commented  · 

    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.

    Jan Bludau shared this idea  · 
  5. 231 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Jan Bludau commented  · 

    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;

    Jan Bludau supported this idea  · 
  6. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Jan Bludau commented  · 

    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

    Jan Bludau shared this idea  · 
  7. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Jan Bludau commented  · 

    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

    Jan Bludau shared this idea  · 
  8. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jan Bludau shared this idea  · 
  9. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jan Bludau shared this idea  · 
  10. 12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jan Bludau supported this idea  · 

Feedback and Knowledge Base