Search found 193 matches
- 17 Apr 2024, 11:00
- Forum: Laravel package
- Topic: Product import takes too long
- Replies: 0
- Views: 156
Product import takes too long
Laravel framework version: 11.3.1 Aimeos Laravel version: 2023.10.8 PHP Version: 8.2.17 Environment: Linux aimeoscom/ai-elastic: 2023.04.* Hello, I am running an import of 122,000 products and the entire import process takes around 2 hours. Is it normal for the import process to take this long? What...
- 16 Apr 2024, 11:17
- Forum: Laravel package
- Topic: Custom.css changes arent working
- Replies: 4
- Views: 1037
Re: Custom.css changes arent working
Hello, Check the following: You are editing the CSS located at your-extension/themes/admin/jqadm/custom.css You have a manifest.php in the root of your extension with this config: 'custom' => [ 'admin/jqadm' => [ 'manifest.jsb2', ], ], You have a manifest.jsb2 in the root of your extension with this...
- 12 Apr 2024, 17:27
- Forum: Laravel package
- Topic: I don't understand the new product attributes layout
- Replies: 1
- Views: 1895
I don't understand the new product attributes layout
Laravel framework version: 11.3.1 Aimeos Laravel version: 2023.10.8 PHP Version: 8.2.17 Environment: Linux Hello, Please help me to understand why the new admin panel for attributes looks like this. When I add a new attribute type, there is a section for each attribute, where you can select the attr...
- 11 Apr 2024, 11:07
- Forum: Laravel package
- Topic: What is the difference between all the tables where user data used?
- Replies: 3
- Views: 4993
Re: What is the difference between all the tables where user data used?
Hello,
To add to the topic, I never understood why mshop_customer and mshop_customer_address are created if they are never used. It is a bit confusing when looking at the database structure, could they be removed in the future for less confusion?
Best regards
To add to the topic, I never understood why mshop_customer and mshop_customer_address are created if they are never used. It is a bit confusing when looking at the database structure, could they be removed in the future for less confusion?
Best regards
- 10 Apr 2024, 10:21
- Forum: Laravel package
- Topic: Integrity constraint violation when importing existing products, categories, etc.
- Replies: 11
- Views: 18020
Re: Integrity constraint violation when importing existing products, categories, etc.
Hello,
I updated Aimeos to 2023.10.8 and the properties import problem disappeared.
Best regards
I updated Aimeos to 2023.10.8 and the properties import problem disappeared.
Best regards
- 09 Apr 2024, 09:24
- Forum: Laravel package
- Topic: Integrity constraint violation when importing existing products, categories, etc.
- Replies: 11
- Views: 18020
Re: Integrity constraint violation when importing existing products, categories, etc.
And about checking if <lists> are mixed up with <property> tags? I don't think they are in this XML.
- 09 Apr 2024, 09:08
- Forum: Laravel package
- Topic: Integrity constraint violation when importing existing products, categories, etc.
- Replies: 11
- Views: 18020
- 08 Apr 2024, 13:16
- Forum: Laravel package
- Topic: Integrity constraint violation when importing existing products, categories, etc.
- Replies: 11
- Views: 18020
Re: Integrity constraint violation when importing existing products, categories, etc.
Hello, Thank you, this makes it clear about the category items. I am experiencing more integrity constraint violations when importing existing products. This time it seems to be coming from the product properties under the <property> tag. This is the error I get: Integrity constraint violation: 1062...
- 08 Apr 2024, 09:14
- Forum: Laravel package
- Topic: Integrity constraint violation when importing existing products, categories, etc.
- Replies: 11
- Views: 18020
Re: Integrity constraint violation when importing existing products, categories, etc.
Hello, 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 t...
- 08 Apr 2024, 08:41
- Forum: Laravel package
- Topic: How to set elastic search custom field type?
- Replies: 2
- Views: 6746
Re: How to set elastic search custom field type?
Thank you @nos3, works great <?php return [ 'base' => function( array $mappings ) { $map = [ 'base' => [ 'properties' => [ 'myfield' => [ 'type' => 'date', 'format' => 'yyyy-MM-dd HH:mm:ss' ] ] ] ]; return array_replace_recursive( $mappings, $map ); } ];