It would be very nice to present the inflectional paradigms beside a hit. An example of how it could be done is this: http://sanit.oahpa.no/detail/sme/nob/guolli.html?no_compounds=true&lemma_match=true&e_node=6051707933484830156
Nice. Do you have REST call for getting paradigm?
I doubt that it exists, but I suspect Ryan knows more about it.
There is ;) http://sanit.oahpa.no/paradigm/sme/nob/guolli http://sanit.oahpa.no/paradigm/<lang>/<tag_language>/<lemma> It may need a little work, but try it out for a while and tell me what else you need from it and I can extend it a little.
I get CORS error: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access. The response had HTTP status code 404
(In reply to Tomi Pieski from comment #4) > I get CORS error: > > No 'Access-Control-Allow-Origin' header is present on the requested > resource. Origin 'http://localhost:3000' is therefore not allowed access. > The response had HTTP status code 404 Same result with a GET request? I can access this with cURL, so it should work. If it continues not to I can make some sort of jsonp parameter for this.
It is a GET request. You need to add 'Access-Control-Allow-Origin' * to the server response header, I think. What is the server? socket.io?
Here is the error I get: XMLHttpRequest cannot load http://sanit.oahpa.no/paradigm/sme/nob/iskan. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access.
This will be fixed from the server-side. I have no knowledge where this magical inflection paradigm generator is located. It actually could be possible to connect when the satni is deployed to gtweb, but it needs to be tested in that environment. I did some research, so if you have any of the following servers, here are instructions to fix this issue: Apache: To add the CORS authorization to the header using Apache, simply add the following line inside either the <Directory>, <Location>, <Files> or <VirtualHost> sections of your server config (usually located in a *.conf file, such as httpd.conf or apache.conf), or within a .htaccess file: Header set Access-Control-Allow-Origin "*" Tomcat, Jetty (java based servers): <filter> <filter-name>CorsFilter</filter-name> <filter-class>org.apache.catalina.filters.CorsFilter</filter-class> </filter> <filter-mapping> <filter-name>CorsFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> Nginx: The following Nginx configuration enables CORS, with support for preflight requests. # # Wide-open CORS config for nginx # location / { if ($request_method = 'OPTIONS') { add_header 'Access-Control-Allow-Origin' '*'; # # Om nom nom cookies # add_header 'Access-Control-Allow-Credentials' 'true'; add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS'; # # Custom headers and headers various browsers *should* be OK with but aren't # add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type'; # # Tell client that this pre-flight info is valid for 20 days # add_header 'Access-Control-Max-Age' 1728000; add_header 'Content-Type' 'text/plain charset=UTF-8'; add_header 'Content-Length' 0; return 204; } if ($request_method = 'POST') { add_header 'Access-Control-Allow-Origin' '*'; add_header 'Access-Control-Allow-Credentials' 'true'; add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS'; add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type'; } if ($request_method = 'GET') { add_header 'Access-Control-Allow-Origin' '*'; add_header 'Access-Control-Allow-Credentials' 'true'; add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS'; add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type'; } } Express.js: app.use(function(req, res, next) { res.header("Access-Control-Allow-Origin", "*"); res.header("Access-Control-Allow-Headers", "Origin, X-Requested-With, Content-Type, Accept"); next(); }); If you use CGI: print header( -type => 'text/turtle', -content_location => 'mydata.ttl', -access_control_allow_origin => '*', ); In python: print "Content-Type: text/turtle" print "Content-Location: mydata.ttl" print "Access-Control-Allow-Origin: *" Perl: Add the following to the builder enable 'CrossOrigin', origins => '*'; PHP (unless you have access to apache AND you still find yourself using PHP, but why??!!??): <?php header("Access-Control-Allow-Origin: *");
Moving satni.org bugs from the Dictionaries product to the satni.org product.
Any progress with this?
(In reply to Ryan Johnson from comment #3) > There is ;) > > http://sanit.oahpa.no/paradigm/sme/nob/guolli This links gives this error: 500 Whoops! There was some kind of error. argument 2 to map() must support iteration
Ryan, did you have time to look at the access problem Tomi had? When done, move this bug back to Tomi.
Flytta over til Børre, ingen respons frå Ryan på fire år.