Hi,
So the permission is denied when the plugin tries to create a temporary directory. That’s a problem.
Can you try the development version 4.3.8b01? And post what it says in Dashboard -> Amazon Auto Links -> Help -> About -> File Permissions?
The development version includes a patch that avoids the warnings you reported but it does not solve the root problem yet.
Thanks for the reply.
I’ve installed the dev version as requested and get the following info in the File Permissions box:
[System Temporary Directory]
path: /tmp
exist: Yes
writable: Yes
[Plugin Temporary Directory]
path: /tmp/WPAAL/a2a50a2615fe9b82e5c3fa6743e27280
exist: No
writable: No
I still get warnings displayed on the site, this time they are both permissions related:
Warning: mkdir(): Permission denied in /…/public_html/wp-content/plugins/amazon-auto-links/include/core/_common/utility/file/AmazonAutoLinks_VersatileFileManager.php on line 74
Warning: mkdir(): Permission denied in /…/public_html/wp-content/plugins/amazon-auto-links/include/core/_common/utility/file/AmazonAutoLinks_VersatileFileManager.php on line 78
-
This reply was modified 5 years, 4 months ago by
will678.
I’ve uploaded the development version 4.3.8b02 (the same link), which applies a different directory permission when creating it. This might fix the problem so please try that.
Also, this version adds some more info in the File Permissions field so please post it again (Dashboard -> Amazon Auto Links -> Help -> About -> File Permissions).
Thanks.
I’ve uploaded the new dev version, and not had any error messages so far.
The File Permission info now reads:
[System Temporary Directory]
path: /tmp
exist: Yes
writable: Yes
chmod: 1777
[Plugin Temporary Directory]
path: /tmp/WPAAL
exist: Yes
writable: No
chmod: 0755
[Plugin Site Temporary Directory]
path: /tmp/WPAAL/a2a50a2615fe9b82e5c3fa6743e27280
exist: No
writable: No
chmod: 0
Many thanks for the support.
If I leave this version installed will it still continue to auto-update in the future to the main release of the plugin?
Hi,
If I leave this version installed will it still continue to auto-update in the future to the main release of the plugin?
Yes but actually, your problem hasn’t solved yet. The plugin temporary directory must be writable and somehow you get non-writable one. With the current directory permission, you’ll lose some internal important functionality and it can cause problems.
I’ve uploaded the development version 4.3.8b02 (the same link). This might fix it. So please try that and post the File Permissions field content again as same as the previous replies. This development version includes some more additional permission related info which includes the owner id and user name. If you think these are sensible, mask them before posting. And please remember that the both [Plugin Site Temporary Directory] and [Plugin Temporary Directory] should say writable. Otherwise, it becomes a problem.
Thanks for the response with this.
I’ve posted the new details, but it looks like both the plugin directories are still not writable.
[System]
umask: 22
user: master_masked
user_id: 1007
[System Temporary Directory]
path: /tmp
exist: Yes
writable: Yes
chmod: 1777
owner_id: 0
owner: {
name: root
passwd: x
uid: 0
gid: 0
gecos: root
dir: /root
shell: /bin/bash
}
[Plugin Temporary Directory]
path: /tmp/WPAAL
exist: Yes
writable: No
chmod: 0755
owner_id: 1005
owner: {
name: masked
passwd: x
uid: 1005
gid: 33
gecos:
dir: /home/…
shell: /usr/sbin/nologin
}
[Plugin Site Temporary Directory]
path: /tmp/WPAAL/a2a50a2615fe9b82e5c3fa6743e27280
exist: No
writable: No
chmod: 0
owner_id:
owner: {
name: root
passwd: x
uid: 0
gid: 0
gecos: root
dir: /root
shell: /bin/bash
}
[wp-content]
path: /home/…/public_html/wp-content
exist: Yes
writable: Yes
chmod: 0775
owner_id: 1003
owner: {
name: master_masked
passwd: x
uid: 1003
gid: 33
gecos:
dir: /home/master
shell: /usr/bin/mysecureshell
}
I think I found the cause. Thanks for posting the information.
I’ve uploaded v4.3.8b04 (same link) and probably it fixes the issue. This time, please check [Plugin Site Temporary Directory] and [Plugin Site Temporary Test Directory] say writable. If not, please post the File Permissions field content again.
This time both of these directories are writable when I check the About page.
I’ve not seen errors after testing a few pages so it looks to be fixed.
Thanks so much for the support!
Great! You’re welcome. Thanks for providing the information that helped to solve the issue.
