Databases
StackOverflow2013
Postsdbo
POModify an existing Fulfillment unexpectedly returns 404 page
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POModify an existing Fulfillment unexpectedly returns 404 page
    primarykey
    data
    text
    <p>I am currently using sandeepshetty's shopify.php plugin on github <a href="https://github.com/sandeepshetty/shopify.php" rel="nofollow">https://github.com/sandeepshetty/shopify.php</a></p> <p>The plugin appears to work and the logic is fairly simple. I have tested it using the "<strong>Create a new Fulfillment</strong>", however I get an error message when using the "<strong>Modify an existing Fulfillment</strong>" API call.</p> <p>I submit the following string and I receive a 404 error</p> <pre><code>$orders = $shopify('PUT', "/admin/orders/160387514/fulfillments/791851111396.json", $fulfillment_put, $response_headers); </code></pre> <p>Where <strong>$fulfillment_put</strong> translates to the payload</p> <pre><code>{ "fulfillment": { "tracking_number": "987654321", "id": 255858046 } } </code></pre> <p>The following is a verbose dump from the PUT command. As can be seen above, I used the following format for the path. I did replace a few variables with either hidden or alt just as an fyi.</p> <p>/admin/orders/#{order_id}/fulfillments/#{product_id}.json</p> <pre><code>* About to connect() to alt.myshopify.com port 443 (#0) * Trying 204.93.213.40... * connected * Connected to alt.myshopify.com (204.93.213.40) port 443 (#0) * successfully set certificate verify locations: * CAfile: /usr/share/curl/curl-ca-bundle.crt CApath: none * SSL connection using RC4-SHA * Server certificate: * subject: /serialNumber=Hidden/C=CA/ST=Ontario/L=Ottawa/O=Jaded Pixel Technologies Inc./CN=*.myshopify.com * start date: 2010-05-10 22:23:08 GMT * expire date: 2015-08-12 19:17:14 GMT * subjectAltName: alt.myshopify.com matched * issuer: /C=US/O=Equifax/OU=Equifax Secure Certificate Authority * SSL certificate verify ok. * Server auth using Basic with user 'hidden for privacy' &gt; PUT /admin/orders/160387514/fulfillments/791851111396.json HTTP/1.1 Authorization: Basic hidden for privacy= User-Agent: HAC Host: alt.myshopify.com Accept: */* Content-Type: application/json; charset=utf-8 Content-Length: 62 &lt; HTTP/1.1 404 Not Found &lt; Server: nginx &lt; Date: Thu, 21 Mar 2013 21:39:06 GMT &lt; Content-Type: application/json; charset=utf-8 &lt; Transfer-Encoding: chunked &lt; Connection: keep-alive &lt; Vary: Accept-Encoding &lt; Status: 404 Not Found &lt; X-Shopify-Shop-Api-Call-Limit: 2/500 &lt; HTTP_X_SHOPIFY_SHOP_API_CALL_LIMIT: 2/500 &lt; X-Request-Id: 7ec529327cd022e973f22be4a9e86916 &lt; X-UA-Compatible: IE=Edge,chrome=1 &lt; Set-Cookie: _secure_session_id=hidden; path=/; secure; HttpOnly &lt; X-Runtime: 0.042757 &lt; * Connection #0 to host alt.myshopify.com left intact * Closing connection #0 </code></pre> <p>P.S. I would like to note that I used the following API documentation <a href="http://docs.shopify.com/api/fulfillment#create" rel="nofollow">http://docs.shopify.com/api/fulfillment#create</a></p> <p>It suggests that I use PUT /admin/orders/#{id}/fulfillments/#{id}.json</p> <p>However, #{id} is referenced in there twice, suggesting that I should use the Order ID twice in a row, but the documentation clearly shows the example of /admin/orders/450789469/fulfillments/255858046.json I would like more clarification on what the actual #{id}'s stand for and how to use them.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USipatenco
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload