Ok, have found out that it’s probably cause by the pkupload-all handle. This handle seems to be a “fake handle”, because it’s not connected to any file, like the jquery handle, which triggers jquery-core and jquery-migrate at once.
Pkupload is a wordpress core module, which is used by RT Media. They enqueue the pkupload-all handle, but WPSSO actually cannot deal with it, without a real file behind it.
I will try to find a solution for this type of handles and release a bugfix version as soon as possible.
Hi,
I don’t understand what you mean by this:
WPSSO actually cannot deal with it, without a real file behind it.
Would you mind explaining a little more? 🙂
Never mind – I see that by “WPSSO” you don’t actually mean the “WPSSO” plugin. 😉
Thanks,
js.
-
This reply was modified 8 years, 2 months ago by
JS Morisset.
-
This reply was modified 8 years, 2 months ago by JS Morisset.
Thread Starter
dlx
(@deeluuxe)
Hi Hendrik!
Thanks for your answer! I´m no JavaScript Pro so I can only guess what the handle does.
But I can see the file …/wp-includes/js/plupload/plupload.full.min.js is being loaded in both cases. If there´s anything I can do to help just let me know!
Best regards,
Jan
Never mind – I see that by “WPSSO” you don’t actually mean the “WPSSO” plugin.
Sry for the confusion 😉 I was too lazy to write the full name of my plugin. But i don’t even know, that there’s a plugin with the same abbreviation 🙂
@dlx
I have looked into it and there are several plupload handles registered by wordpress for backward compatibility in case of plugins enqueuing the old handles. Here you can see a list of all handles, that are registered by wordpress. https://developer.wordpress.org/reference/functions/wp_enqueue_script/
The only one needed is plupload. If you enqueue any other plupload handle, it just forces the plupload handle into the queue. The problem here is, that the other handle, for example plupload-all or plupload-html5 remains also in the queue but without any src-value of a file. And that’s something my plugin obviously cannot handle right now.
I’m working on it and will release a new version soon. 🙂
Thread Starter
dlx
(@deeluuxe)
Hi Hendrik!
Version 0.4.1 works fine with BuddyPress now – thanks for the changes! I´ve installed WP Scripts & Styles Optimizer on the live version of my site now and it works fine. Still testing what scripts & styles can be disabled without brackig the site…
Is there any trick to save the settings e.x. for moving them from a dev to a live server?
Best regards,
Jan
Hi, glad to hear it works for you now.
Unfortunately, there is no import/export function yet. To move all settings to another server, you have to manually export the database table {wp_prefix}_script_optimizer from the old DB and import it into the new DB. (If the table already exists, delete it, before you import the new data)
This includes all files and their settings. After the import, you should see them in the backend. Then you can push the update button to update all the data in the database if anything is different on the new site.
Best Regards
Hendrik
