TMM Technology

@loyukfai Maybe you could check action scheduler for that day, and then I could tell for sure. But these were only suggestions.

So I suppose if there were other tasks that ran that night, but not CW, then it’s something with priorities, and some higher prio tasks were running for the whole night. But I would like you to verify it, and if so, I can add a setting to tweak prios.

• This reply was modified 1 year, 3 months ago by TMM Technology.
• This reply was modified 1 year, 3 months ago by TMM Technology.

@ucdguy Hi. You’re the second person requesting this feature ??

Yes, we will prioritize it, and when ready, I will notify you in this thread.

Stay tuned! And we will also ship several User-Agents support with it.

ETA: This month – mid of the next month (too many projects…).

@loyukfai Strange indeed. We are using the Action Scheduler’s interval feature, and we don’t have fine-grained control over the interval execution, as it has an enqueue and priorities mechanism built-in within (executing tasks with higher priorities first).

I see 2 potential reasons why this issue might happen for you:

1. Some other tasks were running with the higher priority and the enqueue became available only at 12:06 (if this is the case, you will find many tasks in Tools -> Scheduled Actions for that night)
2. Or maybe the site did not get any visitors during the night (in this case, you will find no or just a few tasks for that night).

I suppose that is #2 and your site simply get no / not enough visitors that night.

You can try setting up a server-side CRON job to visit your site every hour, I think that will help. If it does not help, then I can add a setting to the plugin to set the higher task priorities for the warming intervals.

Here’s how to setup a CRON job, if needed: https://chat.openai.com/share/34509d2e-1ab4-4aeb-8f6f-dae53ba5b9d3

@snipsnip And regarding the warming with “Cloudflare Super Page Cache” being enabled – yes, the plugin will create the cache for it of course. It creates cache for all plugins we tested.

@snipsnip It should preload the cache when you edit the post manually (i.e. edit and click on the “Update” button).

No, it will not trigger the warm when the scheduled sale is becoming active. But I can add such a logic to the plugin of course.

You can also list more scenarios when you would like the posts to be warmed, if you have something else in mind.

But of course warming without flushing the previous cache will not bring any benefits, as the previous cache will be present.

So I see 2 things to do:

1. Warm posts when the sale date arrives;
2. Add an integration for “Cloudflare Super Page Cache” plugin to flush the cache of that page when it’s edited or the sale date arrives.

As for now, you can use a warming interval, and that should be relatively ok to mitigate this.

And thank you very much for the features suggestion! I will respond to this topic when it’s ready.

TL;DR: No data is sent to the server, the images resizing is done by the browser of the person that is uploading the image, then the minimized image is uploaded to the WordPress server.

It works by replacing those WordPress scripts:

• /wp-includes/js/plupload/plupload.js?ver=2.1.9 – replaces with either [plugin_dir]/libs/plupload-2.1.9/js/plupload.min.js?ver=2.1.9 (default) or [plugin_dir]/libs/plupload-2.3.9/js/plupload.min.js?ver=2.3.9
• /wp-includes/js/plupload/moxie.js?ver=1.3.5 – replaces with either [plugin_dir]/libs/plupload-2.1.9/js/moxie.min.js?ver=1.3.5 (default) or [plugin_dir]/libs/plupload-2.3.9/js/moxie.min.js?ver=1.5.7

The scripts shipped with the plugin are:

• Minified (leads to the faster page loading).
• Have a modification of the plupload.min.js script that allows the client-size images resize (https://www.plupload.com/docs/v2/Image-Resizing-on-Client-Side) by passing the value to resize.width from the plugin setting (default is 2560).

The client-side resize is helpful in that way that it offloads the images resize processing from the server to the clients that are uploading those images, reduces the bandwidth usage and increases image upload speed (due to the less data to transfer).

The plugin has only a few settings at the moment, which can be seen under “Media” -> “Resize before upload”.

@cptkoolbeenz So just send to me the console error you’re getting, and I’m pretty sure I will be able to fix this ASAP.

Looking forward for your reply! Thanks.

@bsfherman Yes, we are developing our own plugin, but it’s not published yet.

I managed to fix this by calling it after ‘init’ hook, so I suppose you can close this topic actually.

But I it shouldn’t get broken anyway on the early call, as I’m, plainly speaking, just utilizing WC function at the time it should be able to work, and it doesn’t.

So prob someone else will encounter this issue in the future anyway, so I would recommend to fix this. The steps:

• Add somewhere to functions.php or a custom plugin  wc_get_default_product_rows_per_page() call (which has to be called before ‘init’ hook).
• Install & activate Astra theme from the scratch.
• You will get the error, as in the image I attached.

I suppose Astra finishes its init on ‘init’ hook.

@cptkoolbeenz By the way, I watched your GIF more closely, and I see that the console errors counter at the top right corner of DevTools is increasing, which means you’re probably getting some errors after submitting the deletion.

Just click on it, expand the error (the GIF attached), and send a screenshot to me.

But I still would recommend to do the “wpCacheWarmer” search as I proposed in my previous message, as it could give me more info. And also would recommend to try the deletion from the Chrome Guest Profile.

@cptkoolbeenz Wow, that is interesting that no request is being sent for you.

Can you please check for console errors (Console tab, left to Network) after the Logs delete submission.

So I suppose that you either will get a console error with some error description, or that the script was not even loaded for you.

If you see no console errors after you click on the popup, then let’s check if the script was loaded for you.

Steps

• Open DevTools
• Click on DevTools at any place (to focus on DevTools and make the below shortcut to go to them, instead of the page)
• Press CTRL + SHIFT + F (it will redirect you to the DevTools Search tab)
• Type “wpCacheWarmer” in there and press ENTER; there should be 3 results returned:

If you got less than 3 results, send a screenshot to me; and also try deleting the logs from the Chrome Guest Profile (as I would assume some browser extensions are interfering with plugin JS), and report to me if that helps:

@cptkoolbeenz I will add an option to disable the logging in the future.

Maybe you could give the site access so I could look why logs deletion doesn’t work (our email is [email protected])?

Or I can give an instruction and you can try yourself:

• Go to logs tab.
• Open browser DevTools (Right click on the page -> Inspect) and open Network tab, then select Fetch / XHR subtab.
• Click “Delete all logs” button.
• See which request is sent, and which data is returned by the server.

Here is the video example attached: https://youtu.be/JOsMSfvqzkM

I just want to see if the request is being sent in the first place, and if you get some response, which is not a error.

If the request was not even sent, you can look up for the error description in the Console tab (the first one, left to Network).

Hey guys @caranibieros @hargums

Thanks for the great assistance to @cuongpham259 I think we managed to fix this bug. Please try updating the plugin to the latest version and let me to know if that helps.

Thank you for your feedback!

A small remark: for some sitemaps, depth 2 is necessary. For example, Yoast and “XML Sitemap & Google News” have 2 layers of nesting, which means the min depth to warm the pages should be 2.

I have added this note to the settings page during yesterday’s update, so hopefully it will be easier to use for non-technical people now.

@mbv Sure, we will make a guide!

The plugin is a bit technical, so it just visits your site pages. It makes a tree of links from the entry point of the specified depth;uses specified user agent, cookies; URL params etc (if needed).

For the basic use only entry points and depth will be enough. Also you can enable “Add sitemaps of entry points as entry points” checkbox on “Entry points” tab if you have a sitemap on your site, and you can also check the “Add all public posts (of any type) and taxonomies of this site as entry points” checkbox. That will get the list of the pages from WP and visit the pages directly without creating the tree (should work faster). You can enable both checkboxes actually, shouldn’t be redundant (it visits a page only once).

But can be hard to understand for non-technical person for sure.

I have made a video of the basic example of how to use the plugin (by default, just clicking one button should be enough, and waiting a few minutes before it starts): https://youtu.be/f7H2MTCsQBM

Please let me know if it does not work for you, I’m always here to help and assist you, if you still any questions or something does not work.

@cptkoolbeenz Sure.

How would you like it to work? So let’s say you enter 3 user-agents (Desktop, Tablet, Mobile) – then you would like every page to be visited for 3 times (once per UA)?