@donncha, thanks for the quick and informative response.
Thank you for providing protection from user errors.
Yes, yes, I looked carefully – it is inactive, that is, it was, but I did not notice it. Sorry for misleading.
Indeed, the timestamp was disabled for me … I turned it on and the “Check” button became active. The first check failed:
Then I cleared the previously created cache and checked again – the check was successful (the timestamps match). Using Chrome DevTools, I made sure that the cached version is given by the server and that means everything is OK. Thank you for helping me figure it out and find the error! Thank you very much! The only thing that is still not clear to me is how the display of the timestamp works? Is there somewhere I can read more about this? During the check – I saw it, looking through the code of the page. But as soon as I left the admin panel, I don’t see it in the code. Is that how it should be? And yet, as far as I understand, without an active “time stamp”, the cache does not work correctly? Those. is it not only a debugging tool but also a required option?
Everything is fine. 🙂 You make good templates, but if you didn’t manage to take into account all the nuances with the selected font – nothing, let’s hope that I will somehow solve this problem in my favor.
Anyway. The template is cool, I will definitely recommend it to my readers.
While waiting for help from the community, I tried to set up links on a test site and this is what I got: from /old-page/ there is a 301 redirect to /new-page/ (without using third-party plugins; maybe the hosting provider settings help me with this ).
This reply was modified 3 years, 4 months ago by Andrew Bondar.
It’s good that you open this ticket – I have a similar problem. 🙂
WordPress version 6.0.2.
Apparently, some corrections are required so that the plugin again pleases us with its excellent work.
We are waiting for the reaction of the developers. 🙂
Thanks for the tip, I’ll try to find a solution to this problem.
If you don’t mind, I’ll return to the main topic of the conversation and ask the last question: now I have a theme without Cyrillic support – when a user opens the site, how are fonts processed? Which system (CMS/browser) decides which font will be used for a particular visitor?
Okay, I’ll try to find a solution to the problem.
Thanks for answers.
Can you explain why in the directory:
/wp-content/languages/themes/
There are language files in two sets:
baskerville-ru_RU.mo (dated 08/20/2022, – on this day I updated the theme)
baskerville-ru_RU.po (dated 08/20/2022, – on this day I updated the theme)
and
wp-themes-baskerville-ru.mo (from 01/30/2019)
wp-themes-baskerville-ru.po (from 01/30/2019)
?
About 150 kB more a lot?)
Sorry, but pushing your users to install 2 plugins is a lot worse than making a theme 150 kB heavier.
I would understand if there were no users of this language zone among your users, but they are, and I’m not the only one.
Will you change your mind?
This reply was modified 3 years, 9 months ago by Andrew Bondar.
This reply was modified 3 years, 9 months ago by Andrew Bondar.
+2 unnecessary plugins to solve the “problem”.
Sorry, but this option is illogical. (It’s easier to go back to version 2.1.4. and not know the troubles.)
A logical question: what dictated the decision – to exclude Cyrillic from the list of supported ones? Politics?
