|
|
Ok, I got further with the webextension, different error: { "context": [], "cause": { "details": { "code": 7002, "when": { "t_ms": 1776892399041 }, "hint": "Response invalid", "requestUrl": "http://localhost:9966/templates/paivana", "requestMethod": "GET", "httpStatusCode": 200, "response": "{\n \"template_contract\": {\n \"choices\": [\n {\n \"amount\": \"KUDOS:1\"\n }\n ],\n \"summary\": \"The summary\",\n \"template_type\": \"paivana\",\n \"website_regex\": \".*\"\n }\n}", "validationError": "expected number at (TalerMerchantApi.WalletTemplateDetails).template_contract.minimum_age but got undefined" } } } Will check if 'minimum_age' is a mandatory field... |
|
|
https://docs.taler.net/core/merchant/get-templates-TEMPLATE_ID.html#get-[-instances-$INSTANCE]-templates-$TEMPLATE_ID clearly states that minimum_age is an optional field. |
|
|
Sebastian: if you can help fix this quickly, that'd be welcome ;-). |
|
|
i will give it a try, i don't have a paivana setup but looks like a problem in taler-util |
|
|
I see that the template interface changed a lot, it won't take me much to sync them up. That may fix your problem |
|
|
69b9d14ed..5c3313e86 spec updated. all spa still doesn't support new template types that validation check is fixed |
|
|
i have a setup now, and I can work on this next issue image.png (31,848 bytes) |
|
|
since template_type is not yet supported is falling into the default |
|
|
TBH You don't need a template_type in the merchant side if you already have the ID |
|
|
this is what paivana generates taler://pay-template/merchant.taler/paivana?session_id=1777063148-8rXGN2Yep-5Bp24VsSD2R4hES9eYZI_LwmSqsvRcluo&fulfillment_url=https%3A%2F%2Fpaivana.taler%2F but then it fails because of paivana id curl 'https://merchant.taler/templates/paivana' \ --data-raw '{"template_type":"paivana","paivana_id":"1777063148-8rXGN2Yep-5Bp24VsSD2R4hES9eYZI_LwmSqsvRcluo","website":"https://paivana.taler/"}' HTTP/1.1 400 Bad Request { "code": 26, "hint": "A parameter in the request was malformed. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.", "detail": "paivana_id" } |
|
|
DEBUG Looking for by-id key RYPM9JXD of 'admin' in hashmap INFO PAIVANA session `1777063148-8rXGN2Yep-5Bp24VsSD2R4hES9eYZI_LwmSqsvRcluo' INFO PAIVANA after dash `8rXGN2Yep-5Bp24VsSD2R4hES9eYZI_LwmSqsvRcluo' INFO PAIVANA website `https://paivana.taler/' WARNING External protocol violation detected at ../src/backend/taler-merchant-httpd_post-templates-TEMPLATE_ID.c:537. INFO Generating HTTP response with status 400 and code 26 (paivana_id) INFO Request for `/templates/paivana' completed with HTTP status 400 (0) |
|
|
ah, my bad. I had changed it in paivana.git from SHA512 to SHA256 (to make the QR code more reasonable), but had failed to update it in the merchant backend. So this one should be fixed in a75ece57..6d58a48e. Can you please continue testing with this change? |
- Anonymous
