There is a validation-step that will check the permissions based on the path. Is very strange that it works sometimes - I have not seen that issue before.
I'm thinking that it might be some of these problems:
Does the folder exist?
Does the running process for the website have write permissions to the folder?
I might be able to extend the logging around this to indicate more details in the logs but could you please make sure that the two bullets above is checked?
If the folder exists, the path is right and the permissions are correct I can't really understand why this is happening. However, I will take this feedback into account as the first experience with the package might be quite bad if you do not have this folder in place.
I will investigate better ways to handle this and keep you posted.
'SMTP Pickup Path' shows error on saving Workspace with no reason
When trying to edit a workspace the error appears under
SMTP Pickup Path
field:This happens with no apparent reason as the field is filled in and the provided folder exists/ didn't change.
Sometimes it happens with no changes made to the workspace despite it was saved before in the current shape.
Sometimes clicking this or that within the workspace and saving again works.
That looks like there is something causing the issue without any interaction within
SMTP Pickup Path
field.Also as you can see the error shows a placeholder rather than a correct comment.
Hi!
There is a validation-step that will check the permissions based on the path. Is very strange that it works sometimes - I have not seen that issue before.
I'm thinking that it might be some of these problems:
I might be able to extend the logging around this to indicate more details in the logs but could you please make sure that the two bullets above is checked?
// m
I noticed that this happens when we for example change the folder name.
Hi!
If the folder exists, the path is right and the permissions are correct I can't really understand why this is happening. However, I will take this feedback into account as the first experience with the package might be quite bad if you do not have this folder in place.
I will investigate better ways to handle this and keep you posted.
/ m
is working on a reply...