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

Fix Windows Cache Busting #946

Merged
merged 1 commit into from
Aug 26, 2016

Conversation

maddhatter
Copy link
Contributor

Description

Replace flask-cachebust requirement with my forked version.

Motivation and Context

Cache busting on Windows is broken due to a bug in flask-cachebust. I've sent a PR to the original package, but until it is accepted, switching to my fork will resolve the issue.

How Has This Been Tested?

Cache busting is working on my Windows systems.

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)

Checklist:

  • My code follows the code style of this project.

@maddhatter maddhatter force-pushed the windows-cache-busting branch from 412c361 to 9a418e5 Compare August 23, 2016 01:17
@maddhatter maddhatter changed the title Switch to fork of flask-cachebust Fix Windows Cache Busting Aug 23, 2016
@maddhatter maddhatter mentioned this pull request Aug 26, 2016
6 tasks
@BaIthamel BaIthamel merged commit fb979d5 into RocketMap:develop Aug 26, 2016
creatingwake pushed a commit to creatingwake/PokemonGo-Map that referenced this pull request Sep 5, 2016
* Add support for Heroku deploy buttons

* Allow user to explicitly specify a Google Maps API Key
creatingwake pushed a commit to creatingwake/PokemonGo-Map that referenced this pull request Sep 5, 2016
creatingwake pushed a commit to creatingwake/PokemonGo-Map that referenced this pull request Sep 5, 2016
wobblybobz pushed a commit to wobblybobz/PokemonGo-Map that referenced this pull request Sep 29, 2016
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

Successfully merging this pull request may close these issues.

2 participants