Posted by GiorgosK on October 5, 2009 at 12:08pm
2 followers
Jump to:
| Project: | Deployment |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
en/admin/settings/site-information
choose deployment plan and save
[other_language]/admin/settings/site-information
choose deployment plan and save
this setup is possible with i18n_variables enabled in settings.php
a standard practice (I believe) with multilingual sites
push the deployment plan, finishes with success (2 items)
only other_language settings have been successfully deployed
on the LIVE server
Looking at both admin/settings/site-information
on the test server the deployment plan
does not seem to have been saved ??!!!
Comments
#1
This might be more general than previously thought
Still on a multilingual site setup
on admin/build/themes/settings
saving to deployment plan "settings"
After saving the deployment plan STILL displays "" (is this default behaviour ?)
navigating to admin/build/deploy/list/1 (settings deployment plan)
I can see the system_theme_settings included
pushing the plan ends in success but the
"Display post information on" that was changed on the test server
does not propagate to the live server
would this be only on multilingual sites ?
EDIT
deployment of pathauto settings works as expected
admin/build/path/pathauto
#2
2 nodes one the translation of the other
when deployed they don't preserve their translation reference
both nodes get succesfully deployed but
one is not the translation of the other anymore ...
following warnings appeared at the end of the deployment (maybe related)
* warning: Invalid argument supplied for foreach() in sites\all\modules\deploy\modules\node_deploy\node_deploy.module on line 177.* warning: Invalid argument supplied for foreach() in sites\all\modules\deploy\modules\node_deploy\node_deploy.module on line 177.
#3
Currently I am not supporting translated nodes, although this is on my list to look into. I've been awya from the module for a while but I hope to pick up some development again soon and this is high on the list.
#4
So these are actually two separate bugs. The one about multi-lingual site settings (which is specific to the language-specific setup) and the one about nodes losing their tnid link on deployment. I am going to handle the system settings problem in this issue, and open a new issue for the problem with nodes - #642834: Translated node lose their relationships when deployed.
I hope to have patches available next week.
#5
Oops wrong title