Closed sybbear closed 4 years ago
Thank you for the detailed write-up @vikingmaster !
Due to the holidays I'm not exactly sure when I can release a fix (hopefully this weekend), but in the mean time you can use one of two work-arounds:
enqueueScript()
and enqueueStyle()
usage with the equivalent from here:
https://github.com/htmlburger/wpemerge-theme-core/blob/master/src/Assets/Assets.php#L110-L134OR
Thank you for the hint :) Looking forward to see the fix in upcoming updates, WP Emerge rocks! 🤘
Hey @atanas-dev Wanted to check, is there a fix planned any time soon?
@vikingmaster just released 0.15.1
of htmlburger/wpemerge-theme-core
which fixes the issue.
To get the update use this:
composer update htmlburger/wpemerge-theme-core
Very much appreciated!
Version
Expected behavior
wpemerge-theme-core/src/Assets/Assets::generateFileVersion()
should return file versions with Bedrock Wordpress installations.Actual behavior
The function always returns false, even that asset file exists.
Steps to reproduce (in case of a bug)
Comments
We are using Bedrock boilerplate for wordpress projects, as it provides modern file structure, supports managing plugins, themes and localizations through composer and treats Wordpress as a dependency. Bedrock has the following project structure by default:
The issue is that while generally WP Emerge works fine with Bedrock, the function
wpemerge-theme-core/src/Assets/Assets::generateFileVersion()
does not return a file version.How to resolve (example
project.com
)https://project.com
https://project.com
and site_url will behttps://project.com/wp
home_url
instead ofsite_url
wp/
from ABSPATH:Bottom line
Could you implement a fix to this or suggest a way to override
generageFileVersion
?