Not able to get orders between dates #36

Activity

1. xsalefter commented on Mar 18, 2021

   

   xsalefter

   on Mar 18, 2021

   More actions

   I get the same problem as well. Calling the woo-commerce endpoint via CURL is fine, for example:

   curl "https://www.mysite.com/wp-json/wc/v2/orders?after=2021-01-01T00:00:00.000Z&before=2021-01-20T00:00:00.000Z" -u key:secret;
   

   Furthermore, using this parameters is working like a charm as well:

   // params.put("after",  "2021-02-01T00:00:00.000Z");
           // params.put("before", "2021-02-13T00:00:00:000Z");
           params.put("context", "view");
           params.put("per_page", "20");
           params.put("page", "1");
           params.put("status", "any");
           params.put("orderby", "title");

   Only when we uncomment one of before or after, then we get the exception described in this issue. Maybe there's little things that missing here.

   @omandryk (sorry for mentioned you here), but do you have any idea what's going on?
2. xsalefter

   added a commit that references this issue on Mar 18, 2021

   fix issue omandryk#36 by adding COLON in SpecialSymbol and apply in O…

   ...

   5bc4f55
3. kiranuw commented on Mar 22, 2021

   

   kiranuw

   on Mar 22, 2021

   Author

   More actions

   Issue Fixed. Got the solution we need to encode the dates.

   String wcFormattedDate=startDate+"T00:00:00";
   			Map<String, String> params = new HashMap<>();
   			params.put("per_page", "10");
   			params.put("after", percentEncode(wcFormattedDate));
   
   	public String percentEncode(String s) {
   		final String UTF_8 = "UTF-8";
   
   		try {
   			return URLEncoder.encode(s, UTF_8)
   					// OAuth encodes some characters differently:
   					.replace(SpecialSymbol.PLUS.getPlain(), SpecialSymbol.PLUS.getEncoded())
   					.replace(SpecialSymbol.STAR.getPlain(), SpecialSymbol.STAR.getEncoded())
   					.replace(SpecialSymbol.TILDE.getEncoded(), SpecialSymbol.TILDE.getPlain());
   		} catch (UnsupportedEncodingException e) {
   			throw new RuntimeException(e.getMessage(), e);
   		}
   	}
   
   
   
4. kiranuw

   closed this as completedon Mar 22, 2021
5. xsalefter commented on Mar 22, 2021

   

   xsalefter

   on Mar 22, 2021

   More actions

   @kiranuw I think this issue should not closed yet, as currently there's PR from me about this issue.