After updating to Revo 2.1.3-pl (probably from 2.1.1) there is a problem in our MODx-Installation concerning symlinks:
On Site 1 we have a symlink with a own template. This symlink reads and processes the content of Site 2. It used to work perfectly in an earlier version of MODx Revolution but now the TVs of Site 2 (which were read in the symlink-template of site 1) were not processed correctly in the symlink-page anymore. Instead of reading the value of the TVs it is now read the default value of the TV no matter of the individual value of the TV.
Does anybody know if this is a bug or if there is anything we have to change in our settings to make it work again?
Letti
[ed. note: lettis last edited this post 14 years, 11 months ago.]
-
MODX Staff
- 10,725 Posts
Letti:
Is this a multi-context configuration or two separate sites? I assume the former since you can't forward to Resources in external sites.
Are you sure the Symlink does not have a value set for the Template Variable in question? The behavior is for the values from the Symlink to override those of the target Resource if not empty, unless you disable the setting .
Is it possible this is related to a parsing issue, e.g. calling something non-cacheable in a particular spot?
I think this should be the solution. The TV in the symlink-resource is not empty what should explain our problems. I will change this. Thanks a lot!!
on active page, the field "class_key" is overwritten as all other variables??
I write this code on template: [[!getResourceField? &id=`[[*id]]` &field=`class_key`]]
and the output is: "modDocument" although the page in question is modSymLink.
can anyone help me?
Thanks in advance.
Matteo
-
MODX Staff
- 10,725 Posts
This is not a bug. See the forward_merge_excludes System Setting which defines the fields of the modSymLink which are NOT merged over the ones from the modSymLink's target. Though you could edit this to remove class_key, then your target Resource would also be processed as a modSymLink, looking for somewhere else to forward to. And likely without success, so I would not recommend removing class_key from this list.
Why do you need this information on the modSymLink's target Resource BTW?
Because if the page is a symlink, so it is duplicated on the site, I have to insert a link rel = "canonical" to indicate to Google that the page is duplicated.
Thankyou, is a good solution, but having already created several symlinks and I want to avoid editing each page
