UmbrellaWeb

@qtwrk shall i generate the report with the cnd setting enabled (images dont work) OR with it disabled (images do work)???

are you referring to LiteSpeed Cache -> CCDN -> Use CDN Mapping ?

Yes thats correct. CDN is turned on but mapping is not setup or configured….

@qtwrk implemented the code that you gave which seems to work BUT still getting the notification popups even though we dismissed them. Happening on all the sites using the old version even after being dismissed…

@qtwrk many thanks for the super quick response.

On another note, concerning that this i second (from what i can tell) vulnerabilitiy in the last year of the cache plugin never had this issue with other cache plugins we used in the past. hoping this is not going to be a regular occurence….

@qtwrk done: Ticket Created #875185

may I know how many pages your site has ? and how huge is the JS dir ?

the site has just under 500 pages. If each JS file generated is around 1.5MB then that would be less than 1GB of space.

Acutually the JS folder is 40GB in size!

I feel you might look into wrong direction

I am looking in the direction as specified in your official docs: https://docs.litespeedtech.com/lscache/lscwp/ts-optimize/#disk-space-filling-fast so once we could NOT see a difference in the generated html on the frontend… we then manually checked the differences between 2 files in the JS folder…

I can see at least a facebook pixel inline script , as well as some elementor inline JS

Well as you should have seen in the report (maybe not?) those (and a few others) are added to the Page Optimisation > Tuning > JS Ecludes list which are:

ivory-ajax-search.js
eventID
pys-js-extra
pysOptions
pixelyoursite

So, no to your answer UNLESS these have been added to the wrong section? they are not the cause of the issue AND it doesnt explain my initial findings does it?

As you can clearly see the ONLY difference when inspecting is: "DOMContentLiteSpeedLoaded" and "DOMContentLoaded"

Hope that clearly explains it? If not more than happy to explain or dig based on what you advise…

@miss-newyork 100% agree. latest update is ‘pants’

Only way we could get round this is to use an older version via a DB backup at least that way we can get the sytling sorted (somewhat!)

without restoring a DB backup it does not restore any of the addon products. Seems like once you upgrade to a latest version of this plugin there is NO backwards compatibility! Very poor… Sourcing an alternative solution now TBH

Hi There,

Great that the new version of seopress has been released.

As stated before we still have a few sites that use 6.7.2 to retain bulitin GA3 functionality. Do you have a hook/snippet that we can use to implement the fixed matomo for this version? or can we upload the included motomo file from the latest version to the one we use?

@jfarthing84 thanks for the update.

Tested and looks like it not compatiable with seopress plugin (only other plugin being used) no settings in seopress to control TML pages robots but seems that its setting to noindex (or TML sees it and noindexes it!) either way not workable ??

@ivansosa thank you for the update and code.

That works to get the grid 2 only 2 columns in the row. Albeit lacks any gap styling even though its set as: gap:10px in sites code…

Where are the settings to control all this in the plugin settings? seems arkward to have to rely on code snippets to achive this OR is that a premium function???

Hi Carlos,

So whilst waiting and trying to figure out whats going wrong we setup a totaly default setup of latest versions of WP + WOO and your plugin using the default twenty twenty 3 theme. You can see here: https://1devsites-com.stackstaging.com/tests/cor/index.php/product/wordpress-pennant/

As you can see on this one its setting 1 addon per row/per block (where as the issue site its doing as 2!)

NOW no where in the plugin settings is there an option to set amount of options to show in 1 row ie. 1,2,3 etc. That does NOT exit. Plugin is broken and does not work ??

Hi Carlos,

Thanks for the update. How can I send you that link privatly???

Thank you for the update.

Cureently using v6.7.2 on a lot of sites so we can retain the GA3 funtionality (I know the arguments but clients not ready to FULLY move) so when you provide a fix in the update please can you kindly ensure we are able to apply to that version (which ever way is best) Thank you.

sure, initially it was highlighted via search console We then ran a screaming frog crawl and it was highlighted in that. You can also see it via a w3c validator html test which show that error on any site really which will include the noscript tag in the header

@qtwrk done:

Report number: XFUBISCS

Report date: 01/25/2023 10:13:57

@easyootstrap prob due to the plugin updates on the 16th dec 2022. IF you need an urgent fix, roll back to 2.0.8 that should fix things for now (maybe also roll back child plugin to 2.3?) at least until you can get a permenat fix sorted.