I still feel bad about the fact that they removed this ability though. It was so handy.

I have not tried this way, but indexes should still work, for example, instead of named attributes: a) <xpath expr="//div[@class='page']/div[@id='informations']" use indexes: a)< xpath expr="//div[2]/div[5]", of course you'll need to use index numbers adapted to your case.

Agree, it was very handy

And not to forget that those indexes are risky. When somewhere along the line you add the same elements again the numbering will remove the incorrect items. So not very stable.

actuall i given the xpaths inside the base module of website_quote,website_sale,sale_stock. i want to create sale order , its fully customised . if i want to make it, entire page i need to replace , in this situation when i was trying to install the these base module arise the errors" particular xpath can't be located on sale order report" . Is there is any other solution to solve it rahter than create new one?

Temur,
excuse for interruption, but this xpath expression do works in odoo 9 too, as i have tried it in one of my template.. ah... that might be exception in my scenario..... but it did worked...

Logicious,
Please try looking for the path you are giving, does it really exist, you can take the help of HTML inspector for getting the right path, if its a pdf report, then first change the report type to HTML from settings -> Report -> Report, browse to your report and then change type to HTML for debugging, after wards you can make it back to pdf