Skip to content

Conversation

@PhilETaylor
Copy link
Contributor

Summary of Changes

On write or delete of a file, invalidate the opcache for that file, so that changes are loaded into memory on servers with opcache caching set to maximum, or incorrect configured, or set to preload/never revalidate.

Testing Instructions

everything should work as before.

If you really want to test then install php with opcache preload and revalidate timestamps set to never, and use an opcache gun to view what's in the cache, make a change to a file using this class, and compare what is in the cache after.

Documentation Changes Required

none

Why/History

Experience: joomla/joomla-cms#32592
Joomla 3 joomla/joomla-cms#32918
Joomla 4 joomla/joomla-cms#32915

Signed-off-by: Phil E. Taylor <phil@phil-taylor.com>
Signed-off-by: Phil E. Taylor <phil@phil-taylor.com>
@PhilETaylor
Copy link
Contributor Author

Another PR, another drive by thumbs down from @SharkyKZ - why do you do this without commenting what you dont like...

Screenshot 2021-03-29 at 15 55 07

Signed-off-by: Phil E. Taylor <phil@phil-taylor.com>
@PhilETaylor
Copy link
Contributor Author

renamed method as requested joomla/joomla-cms#32915 (comment)

@nibra nibra merged commit a37d340 into joomla-framework:2.0-dev Apr 1, 2021
@nibra
Copy link
Contributor

nibra commented Apr 1, 2021

Thank you!

@SharkyKZ
Copy link
Contributor

SharkyKZ commented Apr 1, 2021

This shouldn't have been merged.

@PhilETaylor
Copy link
Contributor Author

but for the fourth time ... I ask you ... WHY?

You can't just go around closing PRs and shouting its wrong without explaining why.

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

Labels

None yet

3 participants