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

Send no-cache headers when in CP #1386

Closed
Rias500 opened this Issue Apr 12, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@Rias500

Rias500 commented Apr 12, 2017

Behaviour

In the CP the title & slug of a page are prefilled with the default locale, even though different values are set in the content

Steps to reproduce

  1. Create a page
  2. Set the title and slug in 1 locale
  3. Change locale
  4. Save different values for the 2nd locale
  5. See that title & slug are prefilled with the default locale

What is seen in CP:
image

What is in the content file (en.index.html):
image

@Rias500

This comment has been minimized.

Show comment
Hide comment
@Rias500

Rias500 Apr 12, 2017

When I close the page and edit it again the fields are correctly filled. So this might have to do with some caching

Rias500 commented Apr 12, 2017

When I close the page and edit it again the fields are correctly filled. So this might have to do with some caching

@Rias500

This comment has been minimized.

Show comment
Hide comment
@Rias500

Rias500 Apr 12, 2017

Ah some more digging it seems browser cache is the issue because we set caching rules in a .htaccess, this could be solved by sending no-cache headers from the CP

Rias500 commented Apr 12, 2017

Ah some more digging it seems browser cache is the issue because we set caching rules in a .htaccess, this could be solved by sending no-cache headers from the CP

@Rias500 Rias500 changed the title from Title and slug are filled from default locale in CP to Send no-cache headers when in CP Apr 12, 2017

@jackmcdade jackmcdade self-assigned this Jun 5, 2018

@jackmcdade jackmcdade closed this Jun 7, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment