forked from nexcess/magento-turpentine
-
Notifications
You must be signed in to change notification settings - Fork 0
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
update Devel #1
Merged
Merged
update Devel #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merge devel into master. Bump version to 0.6.3
refs PR #817 and Travis CI
refs #821 modified config.xml to prevent 404 page.
refs #521 Fix for search input field on search results page and PHP 5.6.
The config setting [web/unsecure/base_url] can be https://... but ESI can never be HTTPS. Varnish 3 will treat HTTPS URLs as relative, leading to a 404 in Magento, leading to recursive ESI includes.
refs Fixed build XML.
refs Fixed build XML.
Varnish 4 Support - based off PR #541
Fix for HTTPS ESI URLs
Implemented load balancing support
Improved ESI Ajax: load async + fixed jQuery fallback.
When there were no messages, but there was HTML for the ESI Ajax container, it was thrown. When that happened, there was no ESI container on that page, so messages would never work on that cached page.
Pull request #825 broke the ESI messages. This commit fixes it.
refs Added PRs to CHANGELOG.md.
refs Added PRs to CHANGELOG.md and bump version.
Added button to the ESI Decoder tool to show the content of the ESI block. Added auto-detect for Magento root.
The code here is doing a boolean check but the setting is saved as a string (no, yes or yes_admin) As per #904 this fixes the config geneator
Fix for: ignores backend settings #904
…-content ESI Decoder: Button to show block content.
… version when possible
add check to admin to enable/disable restricting varnish to matching …
Fix for version detection on socket when connecting
addEntityFilter to banProductReview
fix use of getStoreConfig in getDefaultBackend and getAdminBackend
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.