Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Telegram Notifications Module: impossible to update to 1.0.8 #2709

Closed
ilyakonovalenko opened this issue Feb 11, 2023 · 6 comments
Closed

Telegram Notifications Module: impossible to update to 1.0.8 #2709

ilyakonovalenko opened this issue Feb 11, 2023 · 6 comments

Comments

@ilyakonovalenko
Copy link
Contributor

It is impossible to update Telegram Notifications Module to 1.0.8.
An error is "Failed to create folders". Absolutely nothing in app logs.

изображение_2023-02-12_001437016

@freescout-helpdesk
Copy link
Contributor

@ilyakonovalenko
Copy link
Contributor Author

Well, I have no way to debug it as I don't have source ZIP to unzip it. Other modules are updating just fine.

@freescout-helpdesk
Copy link
Contributor

Remove and install again the module. Comment try and catch to get the full error message in Manage > Logs > App Logs.

@freescout-helpdesk
Copy link
Contributor

Here is the error message you are receiving: https://github.com/freescout-helpdesk/freescout/blob/dist/vendor/chumper/zipper/src/Chumper/Zipper/Zipper.php#L167

Zipper can not create some folder. It means you have an issue with permissions in Modules folder: https://github.com/freescout-helpdesk/freescout/wiki/Installation-Guide#-permissions-issue

@andy-a2c
Copy link

In my case it was not permission issue but problem with recursive symlink

# ls -la /var/www/freescout/Modules/Telegram/Public
lrwxrwxrwx 1 www-data www-data 42 Dec  8 18:17 /var/www/freescout/Modules/Telegram/Public -> /var/www/freescout/Modules/Telegram/Public

After I removed symlink (rm /var/www/freescout/Modules/Telegram/Public) I was able to update plugin and it created normal directory by path /var/www/freescout/Modules/Telegram/Public

@ilyakonovalenko
Copy link
Contributor Author

In my case it was not permission issue but problem with recursive symlink

Yes, you are correct. It is the same here. I have seen such things before with other modules.
So it is actually a thing someone may need to investigate to prevent this from happening.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants