CarolineElisa

The issue is in Firefox on a Mac, it works fine in Chrome

Thanks for your reply. We do not have a staging site, this is affecting our live site

It worked previously, we have had the plugin installed for some time. Not sure when it stopped working

I see the following errors in the console:

09:28:25.533 Cookie “tk_tc” has been rejected for invalid domain.

09:28:33.917 Cookie “__stripe_mid” has been rejected because it is in a cross-site context and its “SameSite” is “Lax” or “Strict”. checkout-template.html
?

• This reply was modified 4 days, 21 hours ago by CarolineElisa.

So it turns out the issue was due to a syntax error in another snippet

Thanks so much for your time @gripgrip!

Thanks @gripgrip

I meant to say taxonomy, not CPT. Oops! I have edited question

I tried the generator for creating a taxonomy and it also didn’t work

• This reply was modified 7 months, 3 weeks ago by CarolineElisa.

Thanks Peter

Yes, we only get the 500 error with Wordfence active

For now I must leave Wordfence deactivated so my client can edit the site. I will get back to debugging when he is done.

Thanks for your reply.

There is no way to correctly assign the instructor(s)? A web editor that edited a course should obviously not be listed as an instructor.

That is great news! Hopefully with the next release we will be able to convert all our images to WebP

Thank you, but we have hundreds of images and adding them all again is not feasible

So the bulk compress feature doesn’t work, is that right? That is what we used to compress many of our images

We have removed Cloudflare completely and cleared the WP-Optmize cache. Issue persists

But I did notice that when I right click > save the site logo, the file is WebP

Other images are not, even though they have all been compressed

Why might that be? Because I compressed the logo more recently?

We had other image compression plugins active before, could this be part of the problem?

We also use Wordfence and Cloudflare…

• This reply was modified 1 year, 8 months ago by CarolineElisa.

Both wp-optimize-redirection_possible and wp-optimize-rewrite_status are true

mime and headers are also enabled on the server

Could there be a problem writing to .htaccess? Or..?

Thanks for your reply.

mod_rewrite is active on the server (Apache)

What else could be the issue? A conflicting plugin?

https://www.sgtmartinho.com/

Thanks

Thanks for your reply.

I just tried to bulk compress the images again, after no attempts since yesterday, and after compressing 3 images it fails:

[2023-07-18 08:51:22 : INFO] - A total of 162 tasks of type smush found and will be processed in this iteration
[2023-07-18 08:51:22 : DEBUG] - Lock option (updraft_lock_smush, wp_options) already existed in the database
[2023-07-18 08:51:22 : INFO] - Lock (updraft_lock_smush, wp_options) could not be acquired (it is locked)
[2023-07-18 08:51:22 : INFO] - Failed to gain semaphore lock (smush) - another process is already processing the queue - aborting (if this is wrong - i.e. if the other process crashed without removing the lock, then another can be started after 1 minute
[2023-07-18 08:51:22 : INFO] - Cleaning up tasks of type (smush). A total of 165 tasks will be deleted.
[2023-07-18 08:51:23 : INFO] - Successfully optimized the image - .The file was compressed to N/A using WP-Optimize
[2023-07-18 08:51:23 : INFO] - Completed processing task with ID : 5385, and type 'smush'
[2023-07-18 08:51:23 : INFO] - The task with id : 5386, and type 'smush' seems to have been deleted from the database.
…..
[2023-07-18 08:51:23 : INFO] - The task with id : 5546, and type 'smush' seems to have been deleted from the database.
[2023-07-18 08:51:23 : INFO] - Lock option (updraft_lock_smush, wp_k5gxv6_options) released
[2023-07-18 08:51:23 : INFO] - Successfully processed the queue (smush). 165 tasks were processed out of 165.
[2023-07-18 08:51:23 : INFO] - Lock option (updraft_lock_smush, wp_k5gxv6_options) was deleted from the database

Is this simply due to limitations on the Smush.it server?

Look forward to trying out your compression service on the next release.

Thanks for your reply.

However adding classes to all email addresses on a website is not a practical solution.

The options to ‘Skip translation using CSS selector’ and ‘Skip translation of phrases’ would work if they were included in the plugin settings. As they are not, it seems the basic script should exclude emails (strings with @) by default.