Error 'The "i18n" object does not exist in the current context'
|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 over 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 over 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.
#17 Updated by Dan Gillean 4 months ago
Note for future troubleshooting: this has come up again for a user in the forum upgrading from 2.5.2 to 2.5.3. The suggestions on this ticket did not resolve the issue. See the thread for more details and eventual (we hope) resolution:
#18 Updated by Dan Gillean 4 months ago
- File settings-yml-wiped-to-0b-during-web-installer-run.png added
- Status changed from Verified to New
- Assignee deleted (
- Priority changed from Medium to High
- Target version deleted (
Going to re-open this issue as it seems to be recurring.
In terms of resolving it, see especially the last user post in this thread: https://groups.google.com/d/msg/ica-atom-users/_fXHZuID6Vg/Gb2xqQ7rBgAJ
Before running the web installer it [the settings.yml file] has the same configuration at the tmpl. By the time it reaches the Search settings page, the settings.yml file becomes a zero-length file. Somewhere in between starting the web installer and Search settings page, the file is being wiped!!!
I replaced the settings.yml file using the template in the same directory and checked that the correct permissions were applied. Then I continued from the point above. The web installer completed without fault and the upgrade appears to be complete. I have ported the old data across and I'm done.
See the attached CLI image for further context.
See also: internal issue #11572
#21 Updated by José Raddaoui Marín about 1 month ago
- Status changed from New to QA/Review
- Assignee set to Dan Gillean
Tested in Ubuntu 18.04 following the install docs, with 2.5.3 and 2.5.4. Tried with various browsers at the same time, with different cache engines, with existing config files and clean AtoM folders, with two installations on the same machine and restarting processes and clearing cache in the process. In any case, I couldn't make the settings.yml file to lose its contents.
I can only hope the fixes from #13051 improve the situation in 2.5.4 and later versions.