What's Included in Service?
Our Technical Process
Certified TYPO3 Agency
Pricing Plans
| Particulars | Basic | Standard | Premium |
|---|---|---|---|
| Complexity of TYPO3 Instance | Low | Medium | High |
| Installe TYPO3 Version | LTS | LTS/ELTS | All |
| No. of Community TYPO3 Extensions | 5 | 10 | 20+ |
| No. of Custom TYPO3 Extensions | 5 | 10 | 20+ |
| Assign a Dedicated Technical Manager | Yes | Yes | Yes |
| Free Consultation Service | Yes | Yes | Yes |
| Emergency Backup & Restore | Yes | Yes | Yes |
| Reaction & Response Time | 5 business days | 3 business days | 2 business days |
| Support Time (After Delivery) | 10 business days | 20 business days | 30 business days |
| Hours Package | 10 hours | 10 hours | 10 hours |
| Hours Package | €40/H | €50/H | €60/H |
Happy Customers
Frequently Ask Quastions
Composer packages for TYPO3 are available on Packagist.org from version 6.2.0 onwards, making migrations feasible for various TYPO3 versions.
Composer is a PHP program essential for managing dependencies. Detailed instructions for downloading and installing Composer are available on getcomposer.org
Changing this setup is crucial if your project's root folder mirrors your web root folder. Composer adds a 'vendor/' folder to the project root, potentially posing security risks if the project root matches the web root. A suggested structure involves a separate web root folder like 'public/'.
Ensure that your project's TYPO3 Core and installed extensions are straightforward. Any manual changes to these files might be overwritten during migration.
Initially, specific files such as 'public/index.php', 'public/typo3/', and extensions inside 'public/typo3conf/ext/' need deletion. Additionally, configurations like 'composer.json' creation are essential for proceeding.
With Composer, you can include necessary packages using the 'composer require' command followed by the package name and version specification.
Extensions not found on Packagist can be installed from version control systems like GitHub or GitLab. The process involves defining the repository in 'composer.json' and specifying the extension for installation.
After migration, specific files like site configuration and translations should be moved to new locations, adhering to the updated project structure.
Both 'composer.json' and 'composer.lock' files should be added to the version control system. This ensures consistency among team members by tracking exact package versions.
Team members should always run 'composer install' to ensure consistent package versions among collaborators. This command installs packages according to the 'composer.lock' specifications.
How can I ensure the integrity of my TYPO3 project's code during migration?
Our migration process ensures that your TYPO3 Core and installed extensions remain intact. We take precautions to safeguard any customizations or manual changes to your project's files.
The migration involves deleting specific files, configuring Composer, adding required packages, installing TYPO3 Core and extensions, and adjusting file locations. Our team will handle each step efficiently.
Yes, we ensure your project's extensions are seamlessly integrated into the Composer-based setup. Any necessary adjustments or compatibility checks will be performed during the migration process.
