Upgrading to 1.35 will be a bit fiddly.

The dlls need to be replaced - thats the easy part.

Rss macroscript needs replacing.

The hard part is the performance tweaks...

The macro scripts and masterpages need to be changed to use the  GetPosts and GetLanding methods in the NodeHelper. So anywhere you see DescendentsOrSelf("uBlogsyPost") you need to change that whole line to use GetPosts(). Similarly with AncestorsOrSelf("uBlogsyLanding"), and AncestorsOrSelf(1).Descendents("uBlogsyLanding")  

Good luck.

I did the upgrade from 1.32 to 1.33, 1.34 and 1.35 by just replacing the .dll's . I didn't get any errors. Now I upgraded to 1.36 and I do get an error when on a blogpost page.

I tried to change the script file 'uBlogsyListPosts.cshtml' by changing the line DescendentsOrSelf("uBlogsyPost") to GetPosts(), but if I try to save the file I get this error:

Error occured

c:\inetpub\webmove\macroScripts\634524909254446484_uBlogsyListPosts.cshtml(11): error CS1061: 'umbraco.MacroEngines.DynamicNode' does not contain a definition for 'GetPosts' and no extension method 'GetPosts' accepting a first argument of type 'umbraco.MacroEngines.DynamicNode' could be found (are you missing a using directive or an assembly reference?)

am I doing something wrong?

thanks for your help,

Anthony

I upgraded my Umbraco installation to 4.7.1 and now uBlogsy 1.36 runs fine :)

Hi Anthony,

I did a new Umbraco 4.7.1 install and did a fresh install on this instance of uBlogsy 1.36

Then I just did a plain copy and paste job of all Macroscript files to my existing website. This worked fine, except for on Macroscript file: uBlogsyListPosts.cshtml

On my homepage where I implemented the uBlogsyListPosts macro I get this error:

Error loading Razor Script uBlogsyListPosts.cshtml
Object reference not set to an instance of an object.

So I deleted the macro on my homepage an reinserted it, but the error remains

Do you have a clue what the problem could be?

Thanks for the help,

Anthony Candaele

Start with republishing your content tree.

If it keeps happening, you'll have to debug this in visual studio.

Also, debug by quickly taking out lines from the macro until it stops crashing, then take a look at the source.

is working on a reply...