Weave Code
At a glance
Frequently asked questions about Cnet Connector
- Is this package compatible with Akeneo PIM v5 or v6?
- No, this connector is designed for Akeneo PIM v1.6–v2.x (released in 2018) and will not work with modern versions (v5/v6). Akeneo v5+ uses Symfony 5/6, GraphQL APIs, and autoloaded bundles, making this package incompatible without a full rewrite. Consider Akeneo’s official API connectors or third-party solutions for newer versions.
- What Laravel or Symfony versions does this package support?
- This package is built for Akeneo PIM, which historically used Symfony 2/3 (not Laravel). It does not natively integrate with Laravel frameworks. If you need Laravel compatibility, you’d need to refactor it into a standalone Symfony service or microservice that communicates with Akeneo via its REST/GraphQL API.
- How do I install this connector in Akeneo PIM v2.x?
- Run `composer require akeneo/cnet-connector:2.0.*`, enable the `PimCnetConnectorBundle` in `app/AppKernel.php`, and register the `Brand` reference data in `config.yml`. Then update the database schema with `doctrine:schema:update` and regenerate assets using `yarn webpack`. Ensure `CustomEntityBundle` and `ExtendedAttributeTypeBundle` are also installed.
- Will this work with PHP 8.0+ or modern PHP versions?
- No, this package targets PHP 5.6–7.1 (Akeneo PIM v1.x/v2.x). PHP 8.0+ is incompatible due to deprecated Symfony 2/3 components and lack of modern PHP support. If you must use PHP 8+, you’ll need to rewrite the connector for Symfony 5/6 or isolate it in a microservice.
- Does this connector support Akeneo’s modern API (GraphQL/REST) or only CSV?
- This connector relies exclusively on CSV imports for CNET data, which is outdated. Modern Akeneo PIM (v5+) uses GraphQL or REST APIs for integrations. To migrate, you’d need to replace CSV logic with Akeneo’s API clients (`pim/api-client`) and batch processing via the job queue system (`pim:job:execute`).
- Are there alternatives for CNET integration with newer Akeneo versions?
- Yes, for Akeneo PIM v5+, use Akeneo’s official API connectors or third-party PIM integrations that support GraphQL/REST. CNET may also offer modern APIs or SDKs. Check the [Akeneo Marketplace](https://marketplace.akeneo.com/) or CNET’s developer documentation for updated solutions.
- How do I handle the abandoned `CustomEntityBundle` dependency?
- The `CustomEntityBundle` (last commit: 2019) is deprecated in favor of Akeneo’s native attribute system. Replace custom entities with standard Akeneo attributes or migrate to Akeneo’s `pim:installer:migration` system. If you must use custom entities, fork the bundle or implement a lightweight alternative.
- Can I use this connector in production with Akeneo PIM v2.x?
- Technically yes, but it’s risky. The package lacks active maintenance, relies on deprecated bundles, and may fail with large datasets due to CSV-based imports. Test thoroughly in staging, monitor performance, and consider isolating CNET logic in a microservice to reduce risk.
- How do I migrate from this connector to a modern Akeneo PIM (v5+)?
- A full rewrite is recommended. Replace CSV imports with Akeneo’s API clients, drop `CustomEntityBundle`, and use Symfony 5/6 bundles or microservices. Start by auditing CNET’s current API, mapping data to Akeneo’s native attributes, and leveraging Akeneo’s job queue for async processing. Budget 3–6 months for development.
- Does this package support batch processing or large CNET datasets?
- No, the connector uses direct CSV imports, which may fail at scale. For large datasets in Akeneo PIM v5+, use the job queue system (`pim:job:execute`) or implement batch processing via Akeneo’s API clients. Consider isolating CNET logic in a microservice to handle high volumes.
Weaver
How can I help you explore Laravel packages today?