Closed (fixed)
Project:
Google Tag
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
16 Feb 2018 at 14:19 UTC
Updated:
19 Mar 2018 at 14:39 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
recrit commentedAdded a helper function _google_tag_file_directory_is_writable() similar to the patch #130 provided in the core issue #944582: Check for execute permissions on directories that require file write permissions.
Comment #3
solotandem commentedThanks for referencing the core issue discussion. I agree the executable permission needs to be enabled on the snippet directory, but the proposed patch will not solve this problem on a stream wrapper (nor will the core patch resolve this issue for core and other modules that rely on it).
Comment #4
hkirsman commentedStill getting:
Not sure if Drupal is stuck and even cache clear doesn't work?
How could I manually fix this?
Comment #5
hkirsman commentedOk, did "chmod -R 777" for that folder.
Comment #6
solotandem commentedFor those having this problem, how do the directory permissions get changed (assuming they were correct at one point)? Is this on deploy to another server? Is this on module enable? What is the workflow in which they are changed?
Comment #8
solotandem commentedFirst commit in #7 checks executable bit on directory permission using custom function as workaround to PHP bug in is_executable with stream wrappers.
Second commit in #7 makes for a self-contained change and avoids the need for a core patch. This commit can be reverted if core is updated to check the executable bit.
These commits are sufficient for purposes of this module but represents a partial solution to the is_executable() check missing in other parts of core. Hopefully this is the real cause of what has been reported here.
Thanks to those who reported this and commented. Please test commit and report back.
Comment #9
podarokHi, guys
This commit broking installation via drush on php 7 (I don't know about other PHP versions)
google_tag enabled via profile.info.yml
See https://github.com/ymcatwincities/openy/blob/8.x-1.x/openy.info.yml#L81
This is a not safe practice to make hook_requirements so complicated as well as adding there functions that aren't exist
Comment #11
solotandem commentedThanks for reporting this.
Comment #12
podarokSame for _google_tag_doesnt_exists in condition
Comment #13
solotandem commented@podarok Your comment could use a bit explanation as to what you are referring to. Without such there is no basis to change status. If not related to this then create another issue.