You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am expecting that when using AspireUdate with rewrite it should goto AspireCloud with proxy to ts.worg and ps.w.org and later be served by AspireCloud.
Same when updating themes or adding new plugin/theme
Yah right now I'm just getting metadata mirroring to work so that our results line up with .org, so all assets and download links are still pointing to .org. Mirroring the data files themselves and rewriting metadata to point at it is the next step.
When there is plugins to be updated. today it get the plugin picture from:
https://ps.w.org/advanced-custom-fields/assets/icon.svg?rev=3167679
https://ps.w.org/limit-login-attempts-reloaded/assets/icon-256x256.png?rev=2456910
I am expecting that when using AspireUdate with rewrite it should goto AspireCloud with proxy to ts.worg and ps.w.org and later be served by AspireCloud.
Same when updating themes or adding new plugin/theme
Same for themes.
example: https://ts.w.org/wp-content/themes/generatepress/screenshot.png?ver=3.5.1?ver=3.5.1
The text was updated successfully, but these errors were encountered: