Error 'The "i18n" object does not exist in the current context'
|Assignee:||Dan Gillean||% Done:|
|Target version:||Release 2.4.0|
|Google Code Legacy ID:||Tested version:||2.3|
During AtoM install, if the admin restarts the server after installing PHP, but before running the web based AtoM setup, when AtoM setup is run it will fail after completing the "Configuring Search" page with the error 'The "i18n" object does not exist in the current context'. This affects 16.04 installs but I haven't tested anywhere else - I suspect it affects any OS where ticket 8887 is deployed.
This has been reported in the forums:
This appears to be triggered here:
...and is related to ticket #8887
The first message in this forum post contains the full trace for the error:
It was found that if a user encounters this error, they can work around by:
- restart fpm (sudo systemctl restart php7.0-fpm <-- in the case of Ubuntu 16.04)
- restart the install (dump and recreate db, delete and set up the atom application folder again)
- the install will now proceed cleanly.
If the user just tries again without restarting fpm, they will repeatedly run into the same error during install.
A coded fix has not been implemented yet and this is not directly related to Ubuntu 16.04.
#5 Updated by Steve Breker almost 3 years ago
Clear PHP opcode cache. This was added to correct issue where occasionally
during installation, the cache will contain the vendor skeleton .yml
files, which override the AtoM config files that should be written to the cache
folder during install. This prevents the i18n and Qubit helpers being
loaded (from apps/qubit/config/settings.yml) triggering the i18n errors
during the installation process.
#7 Updated by Steve Breker almost 3 years ago
- Status changed from New to QA/Review
- Assignee changed from Steve Breker to Nick Wilkinson
This will be difficult to test as the issue does not trigger in every case.
Testing should at least comprise of checking to ensure that the install process proceeds as expected.