| ... |
... |
@@ -340,25 +340,11 @@ |
| 340 |
340 |
} |
| 341 |
341 |
{{/code}} |
| 342 |
342 |
|
| 343 |
|
-= Frequently Asked Questions = |
|
343 |
+= Implementation Support = |
| 344 |
344 |
|
| 345 |
|
-== This is too abstract for me. Do you have code examples available? == |
|
345 |
+If you do not own a Partner Area based shop yet, but need something "in hand" to develop your implementation, you can rely on the **example shop 100488332** provided by us. The shop is available on the European platform (.net) only. You can use articleId=(% style="color: rgb(80,80,80);" %)999999999 to test the **legacy article mapping resource **in this shop. |
| 346 |
346 |
|
| 347 |
|
-Yes, there is an **example integration** of this API available [[here>>url:https://github.com/spreadshirt/shop-api-example-integration||shape="rect"]]. |
|
347 |
+Also, there is an **example integration** of this API available [[here>>url:https://github.com/spreadshirt/shop-api-example-integration||shape="rect"]]. |
| 348 |
348 |
It shows a draft of a shop system written in php that might be helpful to understand the (list-page -> detail-page -> add-to-basket) workflow. |
| 349 |
349 |
|
| 350 |
|
-== My account is still User Area based. How do I test my integration before I get migrated? == |
| 351 |
|
- |
| 352 |
|
-== (% style="color: rgb(23,43,77);font-size: 14.0px;letter-spacing: 0.0px;" %)If you do not own a Partner Area based shop yet, but need something "in hand" to develop your implementation, you can rely on the **example shop 100488332** provided by us. The shop is available on the European platform (.net) only. You can use articleId~=(% style="font-size: 14.0px;letter-spacing: 0.0px;color: rgb(80,80,80);" %)999999999 to test the **legacy article mapping resource **in this shop.(%%) == |
| 353 |
|
- |
| 354 |
|
-== Which parts of Spreadshirt's API are still valid and what exactly changed? == |
| 355 |
|
- |
| 356 |
|
-The good news is that the vast majority of the domain entities and their corresponding REST resources were not changed. They are still valid and work like they used to. However, **articles** and **articleCategories** became obsolete and will stop working once you are migrated. **Products** still exist, but they should not be worked with directly anymore when developing an online shop integration. Use **ideas** and **sellables** instead. as described in this document. |
| 357 |
|
- |
| 358 |
|
-== [[image:attach:venn.png]]I am using a non-official designer-tool integration. How can I enable editing of sellables for my customers? == |
| 359 |
|
- |
| 360 |
|
-The designer tool can be bootstrapped with a parameter named **sellableId**. This will only work in Sketchomat/Smartomat, but not in Tablomat. Alternatively, bootstrapping the tool with productType & design still works. |
| 361 |
|
- |
| 362 |
362 |
\\ |
| 363 |
|
- |
| 364 |
|
-\\ |