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
[3.7] Cache changes #14649
Comments
No. If If we're going to set a default value in here, it would have to be done for 4.0 and the |
Ah ok - I understand what you mean about the displayed content of the cache path - I would recommend that the description is updated then to reflect that eg changing
And what abou the change in order of the fields? |
Not sure on that one, I can only comment in depth on the change I made (exposing cache path config). |
So are you ok on the changed string?
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
…On 15 March 2017 at 19:22, Michael Babker ***@***.***> wrote:
Not sure on that one, I can only comment in depth on the change I made
(exposing cache path config).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#14649 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABPH8Sk8w6ktfGXg6grItW6WIrarSHUhks5rmDpzgaJpZM4MeYll>
.
--
Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
https://brian.teeman.net/ <http://brian.teeman.net/>
|
Works for me. |
and it seems that moving the field to the end was my idea to resolve a confusion as to what the values refer to as they also apply to system cache #12742 so I will leave that |
PR for joomla#14649 Correctlly describe the newly exposed cache_path field
Closed as we have a PR - thanks @mbabker |
PR for #14649 Correctlly describe the newly exposed cache_path field
In 3.7 there are some changes to the cache settings in the Global configuration that dont seem correct to me (I might be missing something)
The option to turn on cache is now after the configuration of the cache and not before - this seems wrong?
There is a new field to set the path to the cache folder but it does not have a default entry? Shouldnt it have a default of /cache??
The text was updated successfully, but these errors were encountered: