Jump to:
| Project: | Pathauto |
| Version: | 6.x-1.x-dev |
| Component: | I18n stuff |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed (duplicate) |
| Issue tags: | gaerg |
Issue Summary
I have Pathauto enabled to create path aliases for different content types, which it does very well, however, after I edit and save a node that has been previously aliased (i.e. in the node's url path settings area the automatic alias check box is checked and you can see but not edit the alias that has been created by pathauto) the node's URL Path Settings field is cleared and the node's url is back to it original "clean url" as if no pathauto configurations have been set. If I run pathauto's bulk generate, the url alias for the node is created for the node as expected and remains until I go and edit/save the node gain and the path once again is deleted on node save.
Screenshot 1 is of my pathauto configurations
Screenshot 2 is of my pathauto node path settings
Screenshot 3 is of the node's url path settings after pathauto bulk updates have been run and prior to the node being edit is saved.
Screenshot 4 is of the node's url path settings after the node that was being edited has been saved.
I have used pathauto in the past with no troubles, the only difference in this site is that it is an Ubercart site that is using SSL but I don't think that should make a difference. Any help would be appreciated. Thanks
| Attachment | Size | Status | Test result | Operations |
|---|---|---|---|---|
| pathauto_config.jpg | 258.74 KB | Ignored: Check issue status. | None | None |
| pathauto_config_node_paths.jpg | 176.01 KB | Ignored: Check issue status. | None | None |
| pathauto_before_node_edit-save.jpg | 56.73 KB | Ignored: Check issue status. | None | None |
| pathauto_after_node_edit-save.jpg | 50.96 KB | Ignored: Check issue status. | None | None |
Comments
#1
Anybody have any ideas on what the issue might be?
#2
I have the same issue. I tried fixing it with triggers. Maybe you can do that for the time being. I couldn't find a way to do it properly though..
Or you can try this http://drupal.org/node/313411#comment-1801782.
I hope this is resolved soon.
#3
This should be fixed with the latest code. Please re-open this issue if you can re-confirm with the latest module code.
#4
Automatically closed -- issue fixed for 2 weeks with no activity.
#5
I have same problem that still exists on last DEV version : 6.x-1.x-dev (2010-Mar-14)
Alias is well generated for new nodes.
For existing nodes which have already an alias, this alias is erased.
I must run bulk generation to recover lost aliases.
#6
I found how to reproduce.
I have node ID=1 in French and its translation node ID=2 in English.
Both are synchronized on particular fields. If I save one node it synchronizes the other one on those fields.
If I edit ID=2 then it loses its alias.
Node ID=1 is synchronized but it keeps its alias.
If I edit ID=1 then it keeps its alias.
Node ID=2 is synchronized and it retrieves its alias.
So problem is when you edit a node which ID is not the "translation set node ID".
#7
Issue confirmed, same problem here.
#8
I am having the same problem - does anyone have a solution for this? I am in the process of setting up a trigger action as it only seems to be affecting my home pages which have the same dst value for each language. The other pages in the site have avoided this problem by adding a language code to the url alias dst which seems to have avoided the problem.
Thank you
#9
It seems like this is a content translation issue.
There are several of these in the queue (both Pathauto and core). As far as I can tell it's not working very well right now.
#10
I have the same problem as #6 with Pathauto 1.3, but only if the node and its translation have the same alias (for example, fr/mission and en/mission).
Edit: I just traced what is happening, and it is related to #269877: path_set_alias() doesn't account for same alias in different languages : after a node update, all identical aliases of a node are tagged with the same language. Let's hope there is a fix for that soon :-/
#11
I'm seeing the same error described in the original issue report. I have found no way thus far to translate a node from one language to another without the original node loosing it's path settings. Fixing the source node will break the translated node and vice versa.
I tried out the patch that pfournier posted on the thread referenced above. See: #269877-193: path_set_alias() doesn't account for same alias in different languages
Not sure if that issue is the cause here or not, but figured it was worth a shot. No luck thus far.
In my case, I have custom paths defined for most of my pages ("Automatic alias" unchecked). These get lost the second I add a translated node. Addings (or editing) a translated node, whether I allow it to be auto aliased or not, causes my source node to loose it's path settings.
Anyone else have any updates on this?
#12
subscribe
#13
subscribe
I have a same issue.
#14
subscribe
#15
Pretty sure this is a duplicate of #358722: Node aliases lost/changed when using i18n synchronize translations
#16
For me this seems to be caused by synchronization, as mentioned in #358722: Node aliases lost/changed when using i18n synchronize translations. I disabled "Synchronize translations" from modules and node aliases seems to work now.
#17
I think if you aply patches in #269877: path_set_alias() doesn't account for same alias in different languages and #358722: Node aliases lost/changed when using i18n synchronize translations, you will completely fix the problem.
Disabling i18nsync also fixes the problem, but you will loose functionnality and may still loose aliases if you update you aliases manually.
#18
+1