does Custom Pages option include normal posts? like articles and blog

The plugin does not work with WP Fastest Cache
When I use WP Fastest Cache in combination with the plugin, the first time you delete the cache, the plugin you can delete the CSS, the second time to download, the CSS is added. Your settings do not work

https://docs.flyingpress.com/en/article/lazy-render-elements-up666e/

Flyingpress has this awesome lazyrender html feature which really cleans up the DOM and reduces page weight. Hoping you can implement something similar.

Hello again,

I continue to enjoy your plugin, but I have opened up my site’s log file to find a huge number of PHP warnings from this line:

[16-Mar-2024 14:09:33 UTC] PHP Warning: Undefined array key “opm_control_media_files” in /home/…/public_html/wp-content/plugins/optimize-more/includes/classes/Parser.php on line 148

I notice another user posted about this about a month ago and reported it went away for him but not yet for me.

Any ideas as to what may be causing this, or whether this is a bug in the plugin that needs to be fixed?

I can’t find any optimization plugin capable of inlining font files, could you add that as a feature?

Hi, tried on Firefox and Chrome, both I wasn’t able to import the settings. Also using a folder as name is not working at least on JS/CSS load upon interaction , tried as well with: *, such as /folder-name/*

Last some ideas that could be useful: add an option to use wildcards, and separate lazy loading only for iframes and for images, in my case I ‘d really use iframes lazy loading but not for images since I’m using html attributes already to define them.

Thank you for this, though I cant get it to work for more than one line. Also after saving changes I get the 404 custom theme error. in addition I’m getting these errors:

Warning	Constant HDOM_TYPE_ELEMENT already defined	

    wp-content/plugins/optimize-more/vendor/ori-dom-parser.php:30

	1	Plugin: optimize-more
Warning	Constant HDOM_TYPE_COMMENT already defined	

    wp-content/plugins/optimize-more/vendor/ori-dom-parser.php:31

	1	Plugin: optimize-more
Warning	Constant HDOM_TYPE_TEXT already defined	

    wp-content/plugins/optimize-more/vendor/ori-dom-parser.php:32

	1	Plugin: optimize-more
Warning	Constant HDOM_TYPE_ENDTAG already defined	

    wp-content/plugins/optimize-more/vendor/ori-dom-parser.php:33

	1	Plugin: optimize-more
Warning	Constant HDOM_TYPE_ROOT already defined	

    wp-content/plugins/optimize-more/vendor/ori-dom-parser.php:34

	1	Plugin: optimize-more
Warning	Constant HDOM_TYPE_UNKNOWN already defined	

    wp-content/plugins/optimize-more/vendor/ori-dom-parser.php:35

	1	Plugin: optimize-more
Warning	Constant HDOM_QUOTE_DOUBLE already defined	

    wp-content/plugins/optimize-more/vendor/ori-dom-parser.php:36

	1	Plugin: optimize-more
Warning	Constant HDOM_QUOTE_SINGLE already defined	

    wp-content/plugins/optimize-more/vendor/ori-dom-parser.php:37

	1	Plugin: optimize-more
Warning	Constant HDOM_QUOTE_NO already defined	

    wp-content/plugins/optimize-more/vendor/ori-dom-parser.php:38

	1	Plugin: optimize-more
Warning	Constant HDOM_INFO_BEGIN already defined	

    wp-content/plugins/optimize-more/vendor/ori-dom-parser.php:39

	1	Plugin: optimize-more
Warning	Constant HDOM_INFO_END already defined	

    wp-content/plugins/optimize-more/vendor/ori-dom-parser.php:40

	1	Plugin: optimize-more
Warning	Constant HDOM_INFO_QUOTE already defined	

    wp-content/plugins/optimize-more/vendor/ori-dom-parser.php:41

	1	Plugin: optimize-more
Warning	Constant HDOM_INFO_SPACE already defined	

    wp-content/plugins/optimize-more/vendor/ori-dom-parser.php:42

	1	Plugin: optimize-more
Warning	Constant HDOM_INFO_TEXT already defined	

    wp-content/plugins/optimize-more/vendor/ori-dom-parser.php:43

	1	Plugin: optimize-more
Warning	Constant HDOM_INFO_INNER already defined	

    wp-content/plugins/optimize-more/vendor/ori-dom-parser.php:44

	1	Plugin: optimize-more
Warning	Constant HDOM_INFO_OUTER already defined	

    wp-content/plugins/optimize-more/vendor/ori-dom-parser.php:45

	1	Plugin: optimize-more
Warning	Constant HDOM_INFO_ENDSPACE already defined	

    wp-content/plugins/optimize-more/vendor/ori-dom-parser.php:46

	1	Plugin: optimize-more
Warning	Constant HDOM_SMARTY_AS_TEXT already defined	
wp-content/plugins/optimize-more/vendor/ori-dom-parser.php:55

• This topic was modified 9 months, 1 week ago by snippet24.

After updating to the latest version 2.0.2 one of my sites started to show warnings (both when logged in or just when visiting the site):

Warning: Undefined array key "opm_control_media_files" in .../wp-content/plugins/optimize-more/includes/classes/Parser.php on line 148

Please advise !

jQuery migrate is loading also is the option is active. No works…

Hi

Thanks for making this awesome plugin. I have too many lines in php error log like this:

PHP Warning:  strpos(): Empty needle in /home/xxx/public_html/wp-content/plugins/optimize-more/includes/functions/async-css.php on line 7

Is it possible to prevent this? The plugin works but makes the the error log file really big

Thank you for a fantastic plugin. Some time ago suddenly it stopped working, no style sheets were loading (except all right on my own pc). I had cache from the beginning, but as I mentioned, problem started later, perhaps after woocommerce plugin upgrade, not sure. I did not notice straight away because on my screen everything was ok.

I disabled cache, changed theme, but nothing helps. I have Storefront now. When I disable OM plugin, css loads fine. I am on Siteground. Can you please advise?

Hello,

Optimize More is an awesome plugin, but I have observed an unexpected behaviour when using new lines in forms placeholder text (e.g. Forminator Textarea field), i.e. they are shown properly when logged into WP, but it becomes a continuous text (no new lines) when loading the page without logging in.

If either Remove CSS or Remove JS are just enabled in Optimize More (no any further settings):

Then Forminator’s Textarea loses new lines, but ordinary text keeps its new lines:

Same can be observed with other than Forminator forms, so it seems to be some issue with Optimize More and forms’ placeholder text, please advise !

Hello,

Async doesn’t work in subdirectory. Is there any way to solve this issue?

Thanks for the great plugin. it’s very helpful.

Hi!

I put for example in remove css / js fields in a entire plugin like

/my-plugin/

But Homepage no remove anything.

i try to put only one css or js file and do nothing

I thing the Home page option no works.

Thanks!

Hello! I have been loving this plugin since it came out. Just here to present a PHP warning as an FYI with PHP8.2:

[05-Feb-2023 22:58:30 UTC] PHP Warning:  Undefined variable $om_custom_pages in /home4/goseongg/public_html/wp-content/plugins/optimize-more/includes/functions/async-css.php on line 109

Thanks!

Hi, remove css doesnt work in Blog page and archives.
I also put an id but nothing.

thx fo the awesome plugin

How does it work in a wpms installation? If it is network enabled, will it open a central dashboard for global settings? tks! ??