categoryId ignored for intent=browse searches in foursquare venues/search - api

As of a few days ago, foursquare venues/search with intent=browse seems to ignore categoryId. It definitely worked before that. If I change intent=checkin the category filtering is applied. Here's a sample query
https://api.foursquare.com/v2/venues/search?radius=1405&ll=37.769587%2C-122.420139&limit=30&intent=browse&client_id=CLIENTID&v=20120216&client_secret=CLIENTSECRET&categoryId=4d4b7105d754a06374d81259
note I'm doing a userless query. Perhaps related to the recent changes to allow multiple categoryId's?

This is a bug and the team is investigating a fix. Thanks for the report

Related

Some orders are duplicated in admin panel

I don't know how to start because this is my first time posting something on a forum.
So the problem is some clients are ordering some products, but when I go to the admin panel to see their orders, I get surprised because their orders are duplicated. any ideas ? or solutions ?
I use the latest version of persatshop 1.7.8.7
I searched the entire internet for some solutions, but no results.

JQL query that shows the tasks which have new comments on them

I work for a university and my group uses JIRA to maintain our technology helpdesk. We often send messages to customers and wait days to hear a response. I am looking for a filter that will show all the open tasks which are assigned to me and have a new comment from someone other than me. This way I don't have to look through all of my tasks, I can easily tell from this filter, whether any of my tickets now require a response from me.
So far I have this search:
assignee = currentUser() AND status != Done AND
updatedDate > startOfDay(-1d) AND updatedDate < endOfDay(-0d)
It doesn't look like Jira provides a way to access number of comments, last comment date, etc. The closest thing I could find in their reference was Comment which only checks the text of a comment.
Possible Alternatives
Add yourself as a watcher of the Jira issues and setup email notifications. This is what I do to manage my Jira issues. I setup a Jira folder in my email and an automated filter to move all Jira notifications into it. Then I just look through that folder multiple times per day. The downside is you'll keep more notifications than you actually need or care about.
Use Jira's REST API. If you or someone at your school has some programming knowledge, you could probably use the Jira API. Potential solution:
Use the search endpoint to get a list of issues. You can pass JQL to the API to filter the issues.
Use the get issue endpoint to get the details of each issue returned from the search. Within those details are all the comments on the issue, including the time the comment was posted.

Querying the API for orders with more complex search queries?

Is there a way to query the API to find a Shop's orders with more detailed query parameters? For example I would like to be able to find an order by entering the client's name or the date of the order.
The available URL query parameters don't allow anything like that.
I realize I could just request all the orders and then filter that data, but I would rather do it directly in the API instead of locally to avoid any overhead.
Edit: Actually I just realized that the only way to query for a specific order is to enter its internally used order ID that the shop owner has no knowledge of. It would be really neat if I could query the API instead by the order "name" which is shown as the order's ID to the shop owner and the order recipient. Any ideas?
I look at it like this. Let's say you're poor and cannot afford a data store for orders in your App, but you have API access and you want to provide a search for merchants.
You get 250 orders per call and 500 API calls with zero troubles, so that is 125,000 orders. The API provides you with 125,000 objects that you are free to query any way you want. Want to show the merchant just orders with last name Smith and a line item of dingo balls with a chaser of a cart note set to "no saturday delivery please"... you can do that. Has nothing to do with Shopify, just your code. I think it is pretty easy to query orders for anything of interest, your mileage may vary.
Me, I keep interesting aspects of orders in a data store in my Apps, and then provide merchants with search results that way... cuts down on API calls, and keeps interesting facets closer at hand.

Solr exclusion on stats.field?

One can tag specific filters and exclude those filters when faceting. This is generally needed when doing multi-select faceting.
Is something similar possible for the stats.field?
stats.field={!ex=foo}price // does not work
I have a price slider and I need the max price as if the price filter is not set.
Anyone concerned with this question/issue is suggested to go vote up this issue posted to the Apache Solr Jira site. (Free Apache account required.) If you are a Solr developer and wish to work on coding this feature enhancement, we salute you!
Yes.Use stats=true&stats.field=price

How to fetch, display Amazon Marketplace listings by item?

My question pretty much says it all: I'm looking for a way to display Amazon Marketplace listings based on an item lookup. Example: If I do a call to ItemLookup with an ASIN of 0590353403 (Harry Potter and the Sorcerer's Stone), I'm looking for a result set of perhaps the top ten new or used Marketplace listings, preferably with seller information attached.
I apologize if this is clearly documented somewhere, but I have been looking all through the Amazon API docs and on Google to no avail. StackOverflow doesn't seem to have any Related Questions that match what I'm asking, either.
Thanks in advance!
After some further research, it seems I've found what I was looking for. In order to get a listing of all sale offers -- not just those from Amazon itself -- you must specify the MerchantId parameter in your query to the web service. This parameter can take on a few different values: "Amazon" (default), "All," "Featured," or a specific Merchant ID.
To get all the offer information, including seller names and the like, you must also submit the parameter ResponseGroup with the value "OfferFull."
Hope this helps somebody else out down the line! :-)