Forums / General / Template override - Different behaviour in eZpublish 4

Template override - Different behaviour in eZpublish 4

Next topic

Author	Message
John Smith	Thursday 11 September 2008 5:25:41 am The main difference is very first line In 3.6.1 {let assigned_nodes=$node.object.current.node_assignments Which return an array with 1 element. In 3.8.12 {let assigned_nodes=$node.object.assigned_nodes which return an array with 2 elements.
John Smith	Tuesday 16 September 2008 9:52:03 am Anybody please? Doing upgrades next week on number of website. Hopefully this bug or problem is not going to cause major issues at a later stage. Please suggest.
André R.	Tuesday 16 September 2008 11:33:50 am I have no idea why you get this bug, but one of the changes to 3.8.x is that the ezcontentobject_tree table is used to figure out the node locations instead of the eznode_assignment table. So maybe you have (or get during the upgrade) a inconsistency in the ezcontentobject_tree table? Might be a hint to look at what data you have in that table on that specific object id ('contentobject_id') before and after the upgrade. If you can't find anything you could consider using support tickets for this, the ez network team is mostly more experienced with the upgrades, upgrade issues and debugging those. eZ Online Editor 5: http://projects.ez.no/ezoe \|\| eZJSCore (Ajax): http://projects.ez.no/ezjscore \|\| eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom
John Smith	Wednesday 17 September 2008 1:49:06 am hi Andre, Thankyou very much for kind help and response. This morning I checked the table "ezcontentobject_tree" after upgrading the software from 3.6.1 to 3.8.0, there are not even a single inconsistency. As far as my knowledge is concerned, it is the very first line in the locations.tpl with the following path: /design/admin/templates/locations.tpl In 3.6.1 the first line says: {let assigned_nodes=$node.object.current.node_assignments Which return an array with 1 element. Where as In 3.8.x {let assigned_nodes=$node.object.assigned_nodes Which return an array with 2 elements. To check , I copied the location.tpl from 3.6.1 to 3.8.x and it is returning me one location instead of two... Can you please also guide me regarding the ticketing system. How it works. I need to sort all this week, as we are going to upgrade next week to meet the deadline with your hosting provider. So it is very critical situation. It will be nightmare it something breaks after upgradation. I have already checked and tested the upgrade process and steps, it seems working expect this location duplication in the following: 1. Look and feel in the Design section getting two locations 2. Gobal settings in Setup section getting two locations:
John Smith	Friday 26 September 2008 12:59:00 am I think I am the only one who is doing something wrong. Nobody else got that problem. To check, yesterday I downloaded fresh/clean 3.6.1 from ez.no then ran the upgrade from 3.6.1 to 3.8.0, but the bad news is I am still gettting two locations as mentioned below.... 1. Look and feel in the Design section getting two locations >> Design / <site title>(Main) >> <site title> (unwanted) 2. Gobal settings in Setup section getting two locations: >> Setup / Common INI settings (Main) >> Common INI settings (unwanted) Steps which I followed: Changes to the ini files as mentioned in the documentation. 1. Backing up Client folder. 2. Deleting all folders/files in client folder. 3. Copying all the folders/files from folder - ezpublish 3.8.0 4. Copying design/example, var, settings/siteaccess, setting/override from the client backup folder. 5. Setting the owner and permissions on the client folder again. 6. Running the database update dbupdate-3.6.0-to-3.8.0.sql 7. Converting all tables to InnoDB. 8. Running update/common/scripts/updatemultilingual.php -s <siteaccess_admin> 9. Running update/common/scripts/updaterssimport.php -s <siteaccess_admin> 10. Running ./bin/shell/clearcache.sh --clear-all. Hope I havenot missed anything.