Dont use cache.ttl, but use entrust.cache_ttl instead #735
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.
I've set up caching for my laravel application and it suddenly failed to run due to "Unsupported operand types" which was confusing and misleading because the only thing I've done setting cache.ttl:
in
config/cache.php
I actually was surprised that Entrust uses
cache.ttl
which it really shouldn't.config/cache.php
is a good place to store USER-DEFINED cache settings like minecache.ttl.products
,3rd parties should use own configuration to not interfere with user settings.
It wasn't nice that Entrust has occupied certain namespace in my domain that I control.
I propose store cache ttl for Entrust in
entrust.cache_ttl
(it's more explicit also).