We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Inside _scan_files() you can filter out any cachebusting on the files.
for example, some would use /style.css?version=1 this creates an error so you'll want to discard anything after ?
something like: $filename = $directory . '/' . preg_replace('#\?.*#', '', $file);
$filename = $directory . '/' . preg_replace('#\?.*#', '', $file);
You find this again inside _concat_files() $file_name = $directory . '/' . preg_replace('#\?.*#', '', $file_name);
$file_name = $directory . '/' . preg_replace('#\?.*#', '', $file_name);
You should strip all the filenames entered into Minify.
The text was updated successfully, but these errors were encountered:
Adding any parameters to file names shouldn't take place. This library has an option to do this automatically.
So... in this case, raising an error is a good thing. I like to think that developers are smart people :)
Sorry, something went wrong.
No branches or pull requests
Inside _scan_files() you can filter out any cachebusting on the files.
for example, some would use /style.css?version=1
this creates an error so you'll want to discard anything after ?
something like:
$filename = $directory . '/' . preg_replace('#\?.*#', '', $file);
You find this again inside _concat_files()
$file_name = $directory . '/' . preg_replace('#\?.*#', '', $file_name);
You should strip all the filenames entered into Minify.
The text was updated successfully, but these errors were encountered: