Posts made by Komal Sharma

@Michael-Neo

How can I add customer contact as a workflow condition? Currently there are only Customer Name and Emal address.

We are informing to you. At this moment, we have not added the phone number field in the workflow condition.

@luisc2101

Is it possible to delete the contents of the log folder? since it is consuming a lot of server space

You can delete the log file directly from your project. Please follow the below path for the log file in your project:

your-project-folder-name/var/log/dev.log

Also, you can delete your dev file using the command line, run this command in your project root directory:

$ rm -rf var/log/dev.log

@ivanmanzanolh

Everything is okay now. After configuring Swiftmailer and the email settings, it's working. Thanks for your prompt response.

We are glad to know that your issue has been resolved now.

If would request you take a spare minute of yours and leave your valuable feedback with us if you liked our product & support.

and leave your positive reviews here:
https://reviews.capterra.com/new/158346
https://www.trustpilot.com/review/uvdesk.com

It helps a lot to catch more customers like you and keeps us motivated and helps us to do better for this UVdesk opensource project.

Looking forward to seeking 5-star reviews from your side.

Awaiting your response.

@ivanmanzanolh

I'm getting this error when I try to refresh the mailbox: "Undefined constant Webkul\UVDesk\MailboxBundle\Console\CURLOPT_NOBODY" in RefreshMailboxCommand.php."

Let us know, you have verified the curl and dom extension is installed or not. For checking the extension follow the below command:

$ php -m

If curl extension is not installed then follow the below command for installed curl extension:

$ sudo apt install curl

Verify install of curl verison on Ubuntu by running:

$ curl --version

@ivanmanzanolh

I tried to set a password directly from phpMyAdmin with MySQL. When I try to log in, it says "Invalid credentials".

No, its not possible password setup with directly from phpmyadmin. First you will login with any admin and using the same password string in another agent or customer so that login with the same password.

If you added directly from phpmyadmin so here shown direct password instead of password string like above customer email:

Then this is not a login with this password, also showing a invalid credentials.

So you will setup of the swiftmailer, and email settings. After setup you will received a create password email.

For swiftmailer setup you can follow the below blog:

https://www.uvdesk.com/en/blog/setup-gmail-mailbox-uvdesk-open-source-helpdesk/

@Bayu-Nugroho

Once you can check cross verify again your settings because your mailbox url showing something like this publi instead of public:

http:/your-domain-name/publi/en/mailbox/listener

and in your uvdesk.yaml file showing site_url like this till public:

Can you please share a composer.lock and composer.json file of your project. Also, share your configured email id details.

Let us know, which environment you are using in dev or prod mode.
Also, once you have cleared cache of your project after mailbox setup using the below command:

php bin/console c:c

Once you can setup again delete all setup and after that cleared cache of project. After that try again fetch mailbox command.

We have checked and followed the above same steps but we are not able to reproduce this issue. Here, increase the session time also.

Currently we have used swift mailer normal email sending process in code as we are sending email using this.

For Amazon AWS you need to update some code for the same to send using Amazon AWS here.

You can check below link for help:
https://stackoverflow.com/questions/69093958/error-while-sending-email-from-symfony-mailer-via-aws-ses

@peopleinside
Yes, you can mark as solved this topic.

@isaacwilsonk12

Hello, added the Custom Fields plugin to our Open-Source UVDesk. The issue that we are having is that when using the Ticket Search Bar, the data entered into the custom fields is not searchable.

At this moment, we have not added this feature in search filter view with custom fields on the ticket list page. Here search results works with only ticket id, subject, customer name, and email id.

Also, you can check your custom fields details on the ticket view page like this:

If you want any modify in your opensource project then this will be going with the customization work.

@Bayu-Nugroho said in UVDesk not sending emails with SMTP (ssl):

i try install like your suggest. but i found error

Let us know, you have installed the version-1.2.0 uvdesk. After that you have configured mailbox setup.

Also, let us know which email option you are configured. Can you please share a screenshots of the mailbox setup.

@AK_4_Life said in Invalid credentials:

On a new install, I am receiving error "Invalid credentials" when trying to login with my Agent login or as a customer that I created. I am sure of the password, and have reset it multiple times to be sure.

Let us know, you have using the correct URL's for the login account for customer and agent.

For admin/agent URL like this:

localhost/your-project-folder-name/public/en/member/login

For customer URL like this:

localhost/your-project-folder-name/public/en/customer/login

Also, check in your database that user exists or not with password.

@yl_adc

Are there files that should not be excluded so that uvdesk works correctly when restoring the application from the backup (eg the cache.yaml file)?

You have to backup of uvdesk, so you will backup of the below files and folders:

• config folder

• public folder (for your images and files)

• composer.json

• composer.lock

• Also, you will export your data from the database:

After export your data from the database, you will import this data in the new created database.

Also, you can use the same name of the previous database name in your created new project in .env file. If you are not export your data.

@illo

I got an exceptions while installing UVDesk. The error message is "Unable to write in the "cache" directory (/var/www/html/uvdesk/var/cache/dev)"
Currently I am not sure, how to fix this error. What I tried to fix the problem:

This issue generete due to permission problem.

You can follow the below links for more information:

https://stackoverflow.com/questions/20127884/runtimeexception-unable-to-create-the-cache-directory-var-www-sonata-app-cach

https://stackoverflow.com/questions/13211829/symfony2-failed-to-write-cache-directory

@MikeJ

Can you please share you composer.json and composer.lock file.
Also, share your .env file with your setup details.

I've attached a code that will help us in debugging the database connection issues. Please copy and paste it to the ./src/Console/ directory relative to the project and then run the following command from the terminal:

php bin/console uvdesk:test:validate-database-credentials;

This command will use the currently available credentials and establish a connection with your database server. In case of issue, it will output the used credentials that you can cross-verify to ensure they are valid. In case the credentials are valid, then in order to proceed further and resolve this issue, we will need you to either provide us with temporary access to your server where the project is hosted, or share with us temporary access credentials to your database server that we can use to debug any connection related issues in the project at our end locally.

<?php

namespace App\Console;

use Doctrine\DBAL\DBALException;
use Doctrine\ORM\EntityManagerInterface;
use Symfony\Component\Dotenv\Dotenv;
use Symfony\Component\Console\Command\Command;
use Symfony\Component\Console\Input\ArrayInput;
use Symfony\Component\Console\Output\NullOutput;
use Symfony\Component\Console\Input\InputArgument;
use Symfony\Component\Console\Input\InputInterface;
use Symfony\Component\Console\Output\OutputInterface;
use Symfony\Component\DependencyInjection\ContainerInterface;
use Symfony\Component\Console\Question\ConfirmationQuestion;

class ValidateDatabaseCredentials extends Command
{
    public function __construct(ContainerInterface $container, EntityManagerInterface $entityManager)
    {
        $this->container = $container;
        $this->entityManager = $entityManager;

        parent::__construct();
    }

    protected function configure()
    {
        $this
            ->setName('uvdesk:test:validate-database-credentials')
            ->setDescription('Review database connection parameters and report and issues encountered while establishing a connection with database.')
        ;
    }

    protected function execute(InputInterface $input, OutputInterface $output)
    {
        if ('dev' != $this->container->get('kernel')->getEnvironment()) {
            throw new \Exception("\nThis command is only allowed to be used in development environment.", 500);
        }

        if (false == $this->isDatabaseConfigurationValid()) {
            $connection = $this->entityManager->getConnection();
            
            $database = $connection->getDatabase();

            $output->writeln("\n<comment>Unable to establish a connection with database. Please review the credentials in .env(.local) configuration files accordingly.</comment>\n");

            $helper = $this->getHelper('question');
            $question = new ConfirmationQuestion('Display database connection credentials?', false);

            if (!$helper->ask($input, $output, $question)) {
                $params = $connection->getParams();

                $output
                    ->writeln([
                        "", 
                        "Connection URL:\t\t{$params['url']}", 
                        "Database Name:\t\t{$params['dbname']}", 
                        "Database Driver:\t{$params['driver']}", 
                        "Host:\t\t\t{$params['host']}", 
                        "Port:\t\t\t{$params['port']}", 
                        "User:\t\t\t{$params['user']}", 
                        "Password:\t\t{$params['password']}", 
                        "Server Version:\t\t{$params['serverVersion']}", 
                        "", 
                    ])
                ;

                $output->writeln([
                    "Please review and ensure that these database credentials are valid before proceeding.", 
                    "In case the credentials are correct, please ensure that your database is not behind a firewall that could be interfering while trying to establish a connection.", 
                    "", 
                ]);
            }
            
            return Command::SUCCESS;
        }

        $database = $this->entityManager->getConnection()->getDatabase();

        $output->writeln("\nNo issues found establishing a connection with database <info>$database</info>.\n");

        return Command::SUCCESS;
    }

    private function isDatabaseConfigurationValid()
    {
        $databaseConnection = $this->entityManager->getConnection();

        if (false === $databaseConnection->isConnected()) {
            try {    
                $databaseConnection->connect();
            } catch (DBALException $e) {
                // dump($e);
                
                return false;
            }
        }

        return true;
    }
}

@swebervna

We have received your review, Thanks for your appreciation to us.

Also, Can we list out your company here: https://www.uvdesk.com/en/success-stories/

Kindly provide your confirmation so that we will proceed ahead accordingly.

@swebervna

Just submitted my reviews on both sites!

Thanks for share with us your valuable feedback !!

@Pedro-Kerche

would you teach me how to create this cronjob. the command line to create this automation

Please follow the below steps for running the cronjob clear cache:

Step 1: Open your terminal with your project root directory

Step 2: Now you will run the below command in project root directory:

$ crontab -e

After edit your crontab save and close the crontab for now (CTRL + X, CTRL + Y, then ENTER if you selected nano).

Step 3. Now check your view the contents of your crontab, but not edit it, you can use the following command:

$ crontab -l

Step 4: Now check the setup is correct or not, so you will run the showing file path command till end in your crontab terminal check the below screenshot:

Note:

If you are not showing like this, so you will followed the below steps:

Go to the project root directory with you want to delete the folder path, and check the current directory of your project folder, run the below command:

pwd

It will show the current project file path.

2. Once again check this is working or not, please follow the above 4 step again. You will run the showing file path command till end in your crontab terminal.

Now your crontab is saved, and project folder removed in every 2 days.

Also, you can check the below links for more information:

https://stackoverflow.com/questions/16325350/setting-cron-job-to-delete-file-after-24-hours

@swebervna

Yes, that was it! I needed to install php-xml for PHP 8.1 specifically (php8.1-xml) since that's what UVdesk is using.

We are glad to know that your issue has been resolved now.
If would request you take a spare minute of yours and leave your valuable feedback with us if you liked our product & support.

and leave your positive reviews here:
https://reviews.capterra.com/new/158346
https://www.trustpilot.com/review/uvdesk.com

It helps a lot to catch more customers like you and keeps us motivated and helps us to do better for this UVdesk opensource project.

Looking forward to seeking 5-star reviews from your side.

Awaiting your response.

@swebervna

I followed the steps in that GitHub issue and now I no longer get the "imap_open" error but at the very end of the fetching email, I get the following error:

This seems like an issue being caused due to missing packages. Please ensure that you have the php xml extension installed within your environment and restart your apache service. Use the "php -m | grep xml" command to check if the extension is installed and available, alternatively you could also use the phpinfo(); to review the available php extensions.

In case the issue persist, we would suggest you to reinstall the extension itself.