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

[3.7] Cache changes #14649

Closed
brianteeman opened this issue Mar 15, 2017 · 7 comments
Closed

[3.7] Cache changes #14649

brianteeman opened this issue Mar 15, 2017 · 7 comments

Comments

@brianteeman
Copy link
Contributor

brianteeman commented Mar 15, 2017

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)

  1. The option to turn on cache is now after the configuration of the cache and not before - this seems wrong?

  2. 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??

screenshotr18-54-41

@mbabker
Copy link
Contributor

mbabker commented Mar 15, 2017

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??

No. If $cache_path is set in your configuration.php file, that path is used for all filesystem caching. When it isn't set, the JPATH_CACHE constant is used (administrator/cache, cache, depends on active app). Setting that value lets you move the cache path somewhere else on the system (like outside the web root, but this could be problematic if extensions writing cached images or CSS like galleries or minifiers do sometimes are using the cache path config and not hardcoding the /cache path).

If we're going to set a default value in here, it would have to be done for 4.0 and the JPATH_CACHE constant fully deprecated now and removed there to avoid confusion. Calculating it would be easy, same as we are tmp and administrator/logs for those paths during install.

@brianteeman
Copy link
Contributor Author

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

COM_CONFIG_FIELD_CACHE_PATH_DESC="Please specify a folder to store cache files."
to
COM_CONFIG_FIELD_CACHE_PATH_DESC="Please specify a writable folder to store cache files if you do not wish to use the default folder."

And what abou the change in order of the fields?

@mbabker
Copy link
Contributor

mbabker commented Mar 15, 2017

Not sure on that one, I can only comment in depth on the change I made (exposing cache path config).

@brianteeman
Copy link
Contributor Author

brianteeman commented Mar 15, 2017 via email

@mbabker
Copy link
Contributor

mbabker commented Mar 15, 2017

Works for me.

@brianteeman
Copy link
Contributor Author

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

brianteeman added a commit to brianteeman/joomla-cms that referenced this issue Mar 15, 2017
PR for joomla#14649
Correctlly describe the newly exposed cache_path field
@brianteeman
Copy link
Contributor Author

Closed as we have a PR - thanks @mbabker

rdeutz pushed a commit that referenced this issue Mar 16, 2017
PR for #14649
Correctlly describe the newly exposed cache_path field
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants