kwstas778

Thank you, the issue is resolved!

Ah thank you, I just needed to remove the -js affix there at the end. It works now! I’ll go ahead and mark it as solved.

Hello @alinclamba. I contacted the WP Booking Calendar team and they responded to me, which are the js files / scripts that should be excluded from the Concatenate feature. You can see the discussion here https://www.ads-software.com/support/topic/booking-calendar-is-not-visible-on-my-page/#new-topic-0

So what should I write in the Exclude JS Strings: field to exclude the above scripts?

Edit: I tried putting in the ids like this wpbc-global-vars-js, wpbc-popper-js, ... but it didn’t work.

• This reply was modified 11 months, 2 weeks ago by kwstas778.

I asked over Jetpack Boost forums and there is a way to mark certain Javascript files so that they don’t get affected. Here is the conversation https://www.ads-software.com/support/topic/boost-is-missbehaving-with-wp-booking-calendar/#new-topic-0

Can you tell me which files I should exclude?

In the Jetpack Boost Concatenate JS feature there’s a field called “Exclude JS Strings:” I assume that’s the one where I need to put in the excluded scripts. It already has some values “jquery, jquery-core, underscore, backbone”. I’m wondering what’s the syntax here.

For example I have a script function defined by function my_scripts() in my files which I call with wp_enqueue_script. How would I exclude that specific my_scripts script from the Concatenate feature? Just add my_scripts in the field so it becomes “jquery, jquery-core, underscore, backbone, my_scripts” ?

• This reply was modified 11 months, 2 weeks ago by kwstas778.

I’m bumping in the hopes of a helpful response.

1. I will be asking of Jetpack Boost forums for a way to exclude the booking URL from their stuff
2. That second part is my own customization, as I don’t want people to send me spam applications with infinite text. I don’t think it’s causing any problems, right?

I identified the problematic addon to be Jetpack Boost. I will be asking in their forum as well for any solutions, as the Defer Non-Essential JavaScript, Concatenate JS and Concatenate CSS seem to break the Calendar. If you have any ideas on your part of how to fix this, it would be welcome.

• This reply was modified 11 months, 3 weeks ago by kwstas778.

Any further clarification on this?

Alright thanks for the fast replies. I was in the process of going through the ckecklist that Bruce suggested but then I saw an update on the post, reloaded the page and saw it was edited out.

So to summarize and see if I understood this correctly.

1. The cache-checker website, checks only for browser cache, located on each client’s machine locally and has nothing to do with out server side caching.
2. Preload is one of the two types of server side caching you are offering with your plugin. It’s different from the other type of caching, in the sense that it preloads absolutely all pages from the website and it disables garbage collection so they don’t get deleted. The other type, generates the server cache when users visit the website, keeps them for a certain amount of time and garbage collection disposes of the old files. That is done so that for big sites with big traffic, there’s less space taken by the cache and only where needed.
3. Preload mode by default caches everything except the homepage.
4. What I did, preload button + load the homepage from a browser, effectively creates cache that includes everything + homepage and since it’s preload mode, it never gets deleted.
5. Refresh preloaded cache files every?X?minutes, means that every X minutes the plugin will perform a new preload and after it finishes will delete the old files. My website is very small with infrequent changes. If I manually do a preload every time I change something, the I don’t need at all to automatically refresh my preloaded cache files using the plugin.

Are those statements / assumptions correct?

As additional info. When I preload I get a result of 21 cached pages in the “Contents” tab of the plugin, with (85.89KB) space taken as shown. At this point, my wp-content > cache > supercache folder has 2.35 MB size.

If I load my homepage in a browser, the number of cached pages on the “Contents” tabs shows as 22, in the list my homepage is included but still displays (85.89KB) as the size. Meanwhile, the wp-content > cache > supercache folder now has 2.47 MB size. Which means something got cached there.

The question still remains, why do I need to open the page on a web browser (without logged in user), why pressing the “Preload Cache Now” button doesn’t preload that certain homepage and why the displayed size in “Contents” tab is not changing.