Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error in frontpage after removing statamic-one-click-content-translation #9

Open
Sennik opened this issue Aug 17, 2023 · 2 comments
Open
Labels
enhancement New feature or request

Comments

@Sennik
Copy link

Sennik commented Aug 17, 2023

After removing statamic-one-click-content-translation:

composer remove appswithlove/statamic-one-click-content-translation
rm -r public/vendor/statamic-one-click-content-translation

The website frontpage gives an 500 error while CP is working properly.

In the logs I find the following error:

Fieldtype [one_click_content_translation_inputs] not found {"userId":"05c1294e-021e-4816-8c38-48f27dc3aada","exception":"[object] (Statamic\\Exceptions\\FieldtypeNotFoundException(code: 0): Fieldtype [one_click_content_translation_inputs] not found at /var/www/vhosts/mywebsite.nl/staging/vendor/statamic/cms/src/Fields/FieldtypeRepository.php:19) 

Statamic 4.18.0

@OleksiiBrylin
Copy link
Contributor

You have to remove the one_click_content_translation_inputs field from your blueprints

@Sennik
Copy link
Author

Sennik commented Aug 17, 2023

Ok thanks. I cannot remember putting them there, is that automatically done by the add-on? If so why do I have to manually remove them?

@OleksiiBrylin OleksiiBrylin added the enhancement New feature or request label Aug 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants