Email SMTP Configuration Update

​I've mostly covered all the above requirements in this thread
​regarding mail
​I've checked that fossetts smtp details were not working
​So for now I'm replaced it with google smtp details.
​email functionality is working with attached qrcode.
​FYI
​Due to I'm using google smtp currently its taking 1 to 2 minute to show order successful screen
Correct above

Here's a corrected and professionally worded version of your message:

—

I've addressed most of the requirements discussed in this thread.

Regarding the email functionality:
I found that the Fossetts SMTP details were not working, so I’ve temporarily replaced them with Google SMTP credentials. The email is now being sent successfully with the attached QR code.

**FYI:** Since Google SMTP is currently in use, it takes approximately 1 to 2 minutes for the "Order Successful" screen to appear.

—

Let me know if you'd like a shorter or more casual version.

I've gone through the task requirement and below are our understanding
there is a need to fix syncronizatuion form data from page like https://www.liftoffertes.nl/prijzen-vergelijken/huislift to google doc
also
change the doc name to suggested in other mail thread

Here’s a corrected and professional version of your message:

—

I've reviewed the task requirements, and below is our understanding:

– There is a need to fix the synchronization of form data from pages like [https://www.liftoffertes.nl/prijzen-vergelijken/huislift](https://www.liftoffertes.nl/prijzen-vergelijken/huislift) to the connected Google Sheet.
– Additionally, the Google Sheet name should be updated as suggested in the other email thread.

—

Let me know if you'd like this in a more formal or more concise tone.

but its better to do a call for much better undertanding of tasks specially first task before start

Here’s an improved and professional version including your note about the call:

—

I've reviewed the task requirements, and here’s our understanding so far:

– The synchronization of form data from pages like [https://www.liftoffertes.nl/prijzen-vergelijken/huislift](https://www.liftoffertes.nl/prijzen-vergelijken/huislift) to the connected Google Sheet needs to be fixed.
– The Google Sheet name should be updated as suggested in the previous email thread.

However, I believe it would be best to have a quick call to ensure a clear understanding of the tasks—especially the first one—before proceeding.

—

Let me know if you'd like to propose a time for the call or have this formatted more casually.

I’ve reviewed the task requirement below are my suggestion
1- Automatic archive process may be dangours without manual interaction because site customer sesntivity and finanacial
So it is better to apply archive process manully when ever required to avoid any data loss that may affect bussiness
Although we can create an automation archive script and test on it demo but I still suggest Manuall archive process safe and better than automatic archive
Correct above to more appropriate to send to client

Here's a polished and client-appropriate version of your message:

—

I’ve reviewed the task requirements, and here are my suggestions:

1. **Automatic archiving** may be risky without manual oversight, especially considering the sensitivity of customer and financial data on the site.
To avoid any potential data loss that could impact the business, I recommend handling the archive process **manually as needed**.

2. That said, we can certainly create an **automated archive script** and test it in a staging/demo environment. However, I still believe a **manual archiving process is safer and more reliable** in this context.

—

Let me know if you'd like to add anything further or schedule a time to review this together.

I’ve reviewed the task requirements, and here are my suggestions:

Automatic archiving may be risky without manual oversight, especially considering the sensitivity of customer and financial data on the site. Also we will set cron job then for it may it takes long to execute script whenever process will archive data
To avoid any potential data loss that could impact the business, I recommend handling the archive process manually as needed.

That said, we can certainly create an automated archive script and test it in a staging/demo environment. However, I still believe a manual archiving process is safer and more reliable in this context.

As you know, we have now a ready-made script for data archiving.It will take around 10 to 12 hours (deployment time included) each time we manully archive data

If you prefer still to create automatic scripts then it will take 5 to 6 hours to create a automatice script and test at demo
Please note that as I mentioned above automatic script will take own time archive process

Here’s a refined, professional version of your message suitable for sending to a client:

—

I’ve reviewed the task requirements, and here are my recommendations:

– **Automatic archiving** may pose risks without manual oversight, especially given the sensitivity of customer and financial data on the site. Additionally, if we set up a cron job for this, the execution time could be significant depending on the volume of data, potentially affecting site performance during the archive process.

– To minimize the risk of any data loss that could impact the business, I strongly recommend proceeding with **manual archiving as needed**.

That said, we already have a **ready-made script for manual data archiving**, and running it typically takes around **10 to 12 hours**, including deployment time.

If you still prefer to move forward with automation, we can develop and test an **automated archiving script in a staging environment**. This would require approximately **5 to 6 hours** of development and testing time.
However, please note that the automated script will run independently and may take considerable time during execution, depending on data volume.

Let me know your preference, and I’ll proceed accordingly.

—

Let me know if you'd like to make it more concise or add a call-to-action.

I’ve reviewed this and above moillie update will not affect our current plugin.
But I would prefer to update Moillie plugin to latest version 8.0.2

Here’s a polished version of your message for client communication:

—

I’ve reviewed this, and the above Mollie update will **not affect our current plugin** functionality.

However, I recommend updating the Mollie plugin to the **latest version (8.0.2)** to ensure we benefit from the latest features, improvements, and security updates.

—

Let me know if you want to include a timeline or steps for the update.