Peter Westerlund

Thank you, that worked! ??

The problem was that I was using the wrong course actions block. There are two blocks (I dont know why) but it’s the one without the sensei green icon that should be used (for some reason).

Why is primary color getting the global primary variable? But not the secondary? Doesn’t make sense that you would be able to change the primary but not the secondary color.

I don’t want to use the method of overriding via theme files. I assumed it was possible to use the template option for a page since that dropdown was available.

Found the problem. Had padding top and bottom 60 px set in theme.json:

 "core/group": {
                "spacing": {
                    "padding": {
                        "top": "60px",
                        "right": "0px",
                        "bottom": "60px",
                        "left": "0px"
                    }
                },
                "border": {
                    "width": "1px 0 0 0"
                }
            }

Ok.

Another question: Does the plugin have a combine CSS-files feature for admin. Or is that just for front-end?

That it can exist slow queries that can’t be changed to be faster.

No one takes that long time but it’s just that there are so many and together it’s at least half a second or more I would guess.

This query is called 5 times and together takes 0,1 sec:

SELECT option_name, option_value
FROM subdoman0_options
WHERE autoload = 'yes'

It’s called from wp_load_alloptions()

Then this query is called 69 times:

SELECT?*
FROM?subdoman0_zbs_settings
WHERE?zbsset_key = 'secondaddresslabel'
ORDER?BY?ID?DESC
LIMIT?0,1

So you don’t agree with that sometimes it can exist queries that just are very big and slow that can’t be made faster?

well, yes, but I can see what parts are slow, I use Query Monitor. And Im trying to work with codes I codes myself now to at least get those fast first. Then I can worry about 3:rd party codes. But I have already a few plugins I coded myself.

I don’t mind use those functions everywhere if it helps. But we still have the problem of that time expiration. Should I just set like a month or something and manage the cache by the mentioned functions instead?

Then I don’t understand why we brought crawler up. I have only wanted help with wp-admin.

Okay, I thought Page Cache was for front-end caching. It caches the whole page to be loaded, the HTML. And is matched by the URL. And Page cache is what the crawler can pre-cache . It’s at least how I use Page Caching. And, we both agree that it’s nothing to be used for wp-admin.

Object Cache is used to prevent more DB-queries than necessary on a page load. It caches query results to be used later on the page again. BUT, the db-query needs to be run at least ONE time for the person entering the page. Because it’s the same time it’s cached.

Then there is Persistent Object Cache which is the same as Object cache just that the cached data can be stored longer than just for the page load. But still, NEEDS to be cached by a person entering the page at some point.

What have I missundrestod?

I don’t see how I would use the crawler for wp-admin to be honest.

So the answer is; That the site should be built to be quick without cache and not have any query that can take long time for a non-stressed server.

The cache should be only for helping when a server/database get stressed from a lot of hits. Not for slow queries from a non-stressed database. That is basically what you are saying.

While I would like to be able to pre-cache some query results that I know are slow always. It’s not affected by other plugins or anything. It’s my own queries but I can’t make them faster. I just wish I could pre-cache them or do half the job pre-cached or something. Get a cached table to filter from or anything. But I guess that’s not possible then. The answer for that is to upgrade the server, is what I read from your answer.

I guess we don’t get any further here.

For “pre-caching” or cache warmup use the built-in crawler to warmup the cache for the frontend.

Do you mean the built-in crawler in LiteSpeed Cache? Doesn’t that just crawl page visits? How do I “warm up” object cache? I need help with wp-admin. Not the “front-end” of the website.

If the object cache does not allow any improvement, then you most likely have inadequate hosting. However, the type and number of plugins installed contribute to the performance in WP Admin suffering, but that is just the architecture of WordPress and very often poorly programmed plugins.

I don’t really see why Object cache should be any solution to slow queries. It’s more a solution for a site that wouldn’t have problems if it just had fewer visitors. My problem is not a lot of visitors. The problem is a big database and slow queries. Then object caching with a time limit is not the solution. It mostly expires before next person visit the page anyway so all visits are in reality slow visits. Object cache should not be the main caching. At least not with a flush after expired time. But if I can use object cache without any time limit and with precache instead. Then it could work as the main caching.

The answer should not be to delete a lot of posts. There must be positble to have a pretty big database and still have a fast website. And there must be cache systems that don’t require visitors or admins to enter the site and wait long time for it to cache? Why isn’t there a precache system??

Makes sense. And maybe the object caching is actually working. It’s just so stupid that it clears after a few minutes. I will get a slow load next time. Need to find a way to use preload cache instead. But I can start another thread about that.