Paul Kevan
Paul Kevan
It seems like I am unable to reproduce this - tried both locally, and on `Simple`.
> I moved the code to compile and implemented downloads in JS instead of PHP. > > I had to use `downloads.wordpress.org` because `translate.wordpress.org` doesn't support CORS when requests come...
Adding CORS support is a request via systems, see: https://make.wordpress.org/systems/?s=cors
This is slightly complicated for a couple of reasons: - the indexes for search are all classified as `en` language, I believe you can create a language specific index, but...
This came up again recently, so started taking a look at it - it isn't super straightforward to rescind a restriction (exporting) based on a user type, and there are...
@dd32 the idea that came to mind was using `map_meta_cap` late, i.e. after the wp.org restrictions, and include a fixed set of users, which is also protected via a proxy...
Yes, the caps and code here covers the functionality within Jetpack. Thinking about this some more, i'll probably put this in the code within mu-plugins where the caps are restricted...
> I'm assuming it was for PII information or that it allowed access to the raw post_content of something that some were not allowed to access. Yes, plus probably exporting...
Unsure if this matters, but for the data we currently strip out manually, there isn't really any way to remove this.
Seems this isn't limited to just `Varia` themes - it is reproducible using a `Blockbase` child theme also - so it's unlikely solvable via the theme. Digging further, it seems...