ruedacal / razor-mediator-4-tridion

Automatically exported from code.google.com/p/razor-mediator-4-tridion
0 stars 0 forks source link

Unable to save existing (v1.2) tbb's with version 1.3 #4

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Upgrade to razor mediator 1.3 from 1.2
2. Make a change in existing tbb
3. Save the tbb, error will occur, most likely about some functions not in the 
scope of the tbb.

We import some of our (helper) tbb's in the Tridion config like:
<add 
import="/webdav/20%20Developer%20-%20Templates/Building%20Blocks/System/Libs/Raz
or/Helpers/RTBB_Constants.cshtml" />
<add 
import="/webdav/20%20Developer%20-%20Templates/Building%20Blocks/System/Libs/Raz
or/Helpers/RTBB_Helpers.cshtml" />

Running the code (publishing) works fine after the upgrade, but as soon as you 
want to change the tbb code and save it gives an error about functions not 
being in scope.

Removing the following line from the config that is set by the install of 1.3, 
solves this problem:
<importSettings includeConfigWhereUsed="true" includeImportWhereUsed="true" 
replaceRelativePaths="false" />

However I assume this is needed for the new 1.3 features like (from changelog):
Added Where Used functionality for imported TBBs.
Added configurative settings to control Where Used functionality, and ability 
to replace relative paths with full paths if desired.

Apart from the question if this new feature is handy for me, is this an actual 
bug? It only seems to give the error if you import the tbb's in the config.

Original issue reported on code.google.com by rwars...@gmail.com on 30 Oct 2012 at 2:41

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Version 1.31 should solve these issues, the installer should be release within 
the next couple of days.

Those config values are needed if you would like the Where Used functionality 
to work correctly. :)

Original comment by alex@tahzoo.com on 4 Dec 2012 at 2:13

GoogleCodeExporter commented 8 years ago
Version 1.3.1 should solve these issues.  Thanks to Robert for testing the 
fixes.

Original comment by alex@tahzoo.com on 21 Dec 2012 at 3:13