See https://wikitech.wikimedia.org/wiki/News/Toolforge.org#Cross-Origin_Resource_Sharing_(CORS)_requests_broken for more information
As descripted in T234617 it is the plan to switch to toolforge.org and give each tool it's own subdomain.
I have in project WIWOSM a OpenStreetMap application (OpenLayers) , this project use data from project wp-world.
(The scripts are running in project osm,which seems in the moment not the problem.)
Original Script with Wikipedia data:
https://tools.wmflabs.org/wiwosm/osm-on-ol/kml-on-ol.php?lang=de&uselang=de¶ms=50.957777777778_N_13.94_E_region%3ADE-SN_type%3Acity(38320)&pagename=Pirna&language=de&title=Pirna&secure=1&zoom=11&lat=50.9604&lon=13.9484&layers=B00000000FTTTF
Error message from console:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://wp-world.toolforge.org/marks.php?.... (Reason: CORS request did not succeed)
Helppage from OpenLayers:
http://docs.openlayers.org/library/request.html
I my eyes the timeline for the hard end is much too short for volunteers. So I got the information about the move yesterday and have to work the next days.
What can I do?