Feature improvement to not hit server always for exclusion.

Hey Nabil,

I am assuming that you are talking about Sitewide Safelist. You can try the page/post option page to update safelists for individual pages. It should be in the sidebar of the edit page. image -> https://ibb.co/WfP5m4n

If you have 1000’s of pages you can use “Rule based Injection” to speed up the whole process.

Let me know if that helps.

Shakeeb

Yes, but this is not what i am requesting right now.

I want to not hit uucss server for forcing selector. because it may global selector for all pages.

Rule Based Injection not good always, because it missed the pattern, anyways i haven’t tested last two update, but i am doing comment because i don’t see any update related to it. and pattern related docs still not updated.

Anyways, pattern will not work for all single blog post, because it doesn’t contain always */blog/*,

Let me know if you have more ideas.

Thanks.

If you are adding a new safelist means API has to be re-process it in order to process the page with the new safelist rules.

The documentation is still in the making it will be live soon. You can set the pattern to / and it will handle all jobs which met by the type (condition).

Maybe we can add an additional CSS box where we will append that styles with the processed CSS files. That way you can use that CSS option add additional missing CSS rules instead of adding safelist rules. That way you don’t have to requeue all jobs.

Let me know your thoughts on this.

Thanks,
Shakeeb

Thanks, i followed your suggestion.

Updated Plugin, But I am still not happy with Rule Based Injection and always hitting to server one. if rule added, then there should be automatically applied css to all pattern at once. Rule Based injection introduced to improving Time in generating uucss. Now even with rule it’s go through old proccess queued>waiting>proccessing>succeed. I can see that after adding rule, file size matched with pattern rule with some missed.

> Rule Based Injection pattern matched should be applied on all pages at once after rules uucss generated. and steps should be rule-based>success
> About Re-Proccess Of Exclusion, This should be avoided from server and store in database somewhere, and fetch from database.

This way i think uucss will be faster, otherwise it’s slow like it was.

Let me know your thoughts.

Thanks,
Nabil Sikder.

Update: Looks like Rule Based Injection applied uucss on all pattern at once, but it’s not shows up in page if WProcket activated. so now if rules uucss generated it should clean up cache of WProcket. and if pattern matched it should stop hitting on uucss server(as all is same so no need to reproccess them) and step will be rule-based>success or success, right now i see it’s clearing cache one by one, but it should be all at once, so that user not confused about it.

I confirmed that uucss applied on all pattern at once by pressing clear cache of wprocket

Hey Nabil,

Good suggestion. It is page cache. We can clear the cache of all pattern matched results. This will be available in the upcoming versions.

Thank you for your feedback,
Shakeeb