Search found 7880 matches
- 11 Apr 2024, 07:06
- Forum: Help
- Topic: [Planing Stage] feasibility stage question.
- Replies: 2
- Views: 9340
Re: [Planing Stage] feasibility stage question.
- is possible (in easy way) to deploy different front for different location (based on geolocation) - domain, view/theme, currency and pay gateways, etc You can have different domains, themes, currencies and payment gateways for different locations but you need the complex B2B/marketplace extension...
- 09 Apr 2024, 09:18
- Forum: Laravel package
- Topic: Integrity constraint violation when importing existing products, categories, etc.
- Replies: 11
- Views: 30004
Re: Integrity constraint violation when importing existing products, categories, etc.
We only use 2023.10 LTS as 2023.04 isn't supported any more.
- 08 Apr 2024, 19:06
- Forum: Laravel package
- Topic: Integrity constraint violation when importing existing products, categories, etc.
- Replies: 11
- Views: 30004
Re: Integrity constraint violation when importing existing products, categories, etc.
We can't reproduce the problem with the product property update with your file. According to the error message, the property was tried to be imported as referenced item in mshop_product_list. Did you mixed up <lists> with <property> tags?
- 08 Apr 2024, 10:17
- Forum: Laravel package
- Topic: Integrity constraint violation when importing existing products, categories, etc.
- Replies: 11
- Views: 30004
Re: Integrity constraint violation when importing existing products, categories, etc.
Fixing the capitalization worked for the root catalog item, but the error occurs for the children as well Does this mean that the children also have to have ref="" parameter matching the catalog.code ? Adding this parameter to the child <catalogitem> tags seems to work, so I think the doc...
- 08 Apr 2024, 09:20
- Forum: TYPO3 extension
- Topic: Template: You are here: Back
- Replies: 5
- Views: 14796
Re: Template: You are here: Back
It's a link but there may be an overlay of another element depending on your CSS:
https://github.com/aimeos/ai-client-htm ... hp#L68-L70
You can check that in the browser console.
https://github.com/aimeos/ai-client-htm ... hp#L68-L70
You can check that in the browser console.
- 07 Apr 2024, 13:13
- Forum: Help
- Topic: FR: BE - Category - Product listing - label not id
- Replies: 2
- Views: 10609
Re: FR: BE - Category - Product listing - label not id
Agreed but the sub-panel must be completely rewritten for that because it also doesn't work with e.g. ElasticSearch too. It's on our list of todos.
- 07 Apr 2024, 11:54
- Forum: Help
- Topic: About Laravel CMS
- Replies: 2
- Views: 10903
Re: About Laravel CMS
The Laravel CMS package is still work in progress. The APIs are all fully functional but the backend lacks managing content types other than texts.
- 07 Apr 2024, 11:53
- Forum: Help
- Topic: JsonApi: Stock level mixed with f_catid when fetching products
- Replies: 2
- Views: 11271
Re: JsonApi: Stock level mixed with f_catid when fetching products
The f_catid parameter doesn't filter by product.instock property so there must be something else: - https://github.com/aimeos/ai-client-jsonapi/blob/master/src/Client/JsonApi/Product/Standard.php#L373 - https://github.com/aimeos/ai-controller-frontend/blob/master/src/Controller/Frontend/Product/Stan...
- 07 Apr 2024, 11:45
- Forum: Laravel package
- Topic: Integrity constraint violation when importing existing products, categories, etc.
- Replies: 11
- Views: 30004
Re: Integrity constraint violation when importing existing products, categories, etc.
<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <catalog> <catalogitem ref="home"> <catalog.code><![CDATA[Home]]></catalog.code> <catalog.label><![CDATA[Home]]></catalog.label> <catalog.status><![CDATA[1]]></catalog.status> </catalogitem> </catalog> &...
- 04 Apr 2024, 13:40
- Forum: Laravel package
- Topic: Integrity constraint violation when importing existing products, categories, etc.
- Replies: 11
- Views: 30004
Re: Integrity constraint violation when importing existing products, categories, etc.
Can you provide a minimal XML which reproduces the problem?