truxton

(2):
If js rendering code is added to lang-php.js, any <script></script> part will be rendered by lang-js rendering code using different css marks. However, even pure lang-php can render most js codes perfectly. Since I know little about js and php, I still can’t find some js code that can only be rendered correctly using lang-javascript.js. So I think adding js rendering to lang-php is optional, although I will add it to provide best compatibility, with only extra 4kb resource size.

Hi,
(1) Considering a post with only one prismatic block(using prismJS), and its language is not set. Then plugin-toolbar.js won’t enqueue, and there won’t be a [copy] button. If there’s another prismatic block(with certain language) in the same post, then plugin-toolbar.js will enqueue, and all prismJS blocks are rendered with [copy] buttons: the former no-language code block will also be processed and rendered by plugin-toolbar.js.

Hi,
(1) I just force-enqueue plugin-toolbar.js regardless of language settings, and found that prismJS provides ‘plain text’ mode in toolbar (if no language is selected, ‘plain text’ will be shown in toolbar’s language). Thus I suggest adding plugin-toolbar.js everywhere, to provide plain-text support in prismJS.
(2) Currently I use https://github.com/WordPress/WordPress’s several pure php files to test two different rendering js files, then using a diff checker to compare rendered html. For now all pure php files are rendered the same.

Hi,
I’m sorry that I misjudged the plugin that went wrong.

Hi,

I downgraded my imagick from 3.7.0 to 3.6.0 and the problem was solved. Thanks for your help!

My configuration:
use imagemagick 7.1.0 with libwebp 1.22; latest imagick; uncheck ‘Keep images metadata stored in EXIF or XMP formats’; php exif is disabled.

A more detailed operation:
1. I have an image with IPTCDigest exif in my computer, I copy it and paste it in my wordpress’s editor
2. The image is uploaded in my wordpress’s directory with such exif information.
3. the original image’s webp conversion failed.
3.5 however, I can convert the problematic image to webp with imagemagick’s convert command directly (or with libwebp’s cwebp command)
4. if I remove all the exif information from the image and upload it again, all operations go well without error.

Hi,

This time, the optimization button exists and the tables are re-generated. thank you!

Hi,

I drop these tables:

wp_yoast_indexable
wp_yoast_indexable_hierarchy
wp_yoast_migrations
wp_yoast_primary_term
wp_yoast_seo_links

And after re-activating(even delete and re-install) yoast SEO, all these five tables did not re-generate. In yoast->tools, I do not have a button to optimize data because the plugin show me that “SEO data optimization complete”. Although these tables do not exist, the html <header> still shows that yoast seo works normally.

Hi,

yes, .svg.webp.crashed files do not appear in 4.0.3; I switched to 4.0.2 and the file appears again. Thank you!

Hi,

I deactivated all the plugins except this plugin and SVG support, and the problem still occurs.

Hi,

After testing on different versions, I found that .svg.webp.crashed files begin to appear starting from V3.2.3 (versions under V3.2.3 work fine).

Hi,

Yes, 4.0.2 is causing the problem.

Hi,

I tried these:
1: downgrading imagemagick version from 7.10 to 7.0.x, and imagick from 3.6.0 to 3.5.7
2: downgrading this plugin from 4.0.2 to 3.2.4

Still does’t work. So I tried webp converter 3.0.0, found that it does not generate .svg.webp.crashed files.

Since there are many versions between 3.0.0 to 3.2.4, I don’t know which version is the nearest version that causes this problem.

Thank you so much for your help and hook API. I create a hook function to capture every saving snippet’s data and insert it into another MySQL table so that I can easily backtrack code snippets’ revisions whenever I encounter troubles. Actually, I hope this can be a future feature of this plugin because sometimes it’s common to wrongly modify snippets (or unsuccessfully add new functions), and we need to restore the older snippets. Of course, this will lead to extra disk space (like WordPress’s post revisions), but I think it’s worth it.

• This reply was modified 2 years, 11 months ago by truxton.