-
Notifications
You must be signed in to change notification settings - Fork 15
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
i18n conflict #47
Comments
I could reproduce it. And it wasn't when enabling i18n_node, but when enabling i18n_string. |
PR for testing: #69 |
@mazzech Rename the file Your error messages seems to be different, though. At least at first sight. But let's verify that first. |
@mazzech Did you test this PR by any chance? https://github.com/backdrop-contrib/metatag/pull/69/files |
Oh, no I did not... thank you @laryn |
Hi Laryn, I did apply the patches manually... at least the module activation does not throw an error anymore! But clicking the settings shows an error in the log like Line 135 is about the i18n_string dependency, right? but when I got to the string settings page, I am not sure if I even can disable this sub module entierly, given the settings. @indigoxela do you know more about i18n_string module status? |
It's an alpha release. However, these bugs are in the metatag module and have to get fixed here. I can't help much, as I usually avoid to install metatag (and it's a pretty complicated module). |
The error message is odd... Some lines above the setting gets loaded: @mazzech could you inspect your config? You can export it via /admin/config/development/configuration/single/export. Choose "Configuration" and "Metatag settings". |
Thank you @indigoxela for checking... here's my export, hope this helps
|
The setting is clearly there... BUT... I just realized, that's a different file - metatag.admin.inc In that file the config isn't loaded and the "->get" is done in a wrong way. Two problems:
That should fix it. @laryn mind to give it a try in your PR? |
Good catch @indigoxela -- PR updated. |
@laryn your PR works for me using latest metatag release and i18n alpha release. |
Even with this patch I'm getting:
I need to look into this further, but I wasn't getting this error before applying the patch. |
I made the following changes to @laryn patch and it prevented the previous error. (I should note that on
|
I was testing a PR for i18n_node and when I enabled that module I got this fatal error:
I had to delete that file to get the site to load again.
The text was updated successfully, but these errors were encountered: