What exact version of Umbraco are you using? And how did you do the deploy? Could you be missing any files? Sounds like the some of the partial views might be missing on the server - The <Macro:(.)> is typically shown when the macro has just been defined but no attached file exists.
Hmm, ok - Don't know that much about azure. But have you checked that all your partial view macros exists on the server?
In regards to the content - Have you tried using the "Republish Entire Content" option when right clicking the "CONTENT" node? It refreshes the umbraco.config file - But it will of course only work if the backoffice content is still right but it's the wrong content that is being showed on the frontend.
Sever issue with macros once deployed to IIS
Hi,
once my solution deployed on a new server using IIS, all my macros stoped working and render <Macro: (,)> instead.
My website as full permissision (full controle for IISUSR and regular Users), would anybody have a tip?
Hi Alex
What exact version of Umbraco are you using? And how did you do the deploy? Could you be missing any files? Sounds like the some of the partial views might be missing on the server - The
<Macro:(.)>is typically shown when the macro has just been defined but no attached file exists./Jan
In addition all the content nodes in my backend are not how they should be, more like they were weeks ago..
I am using Umbraco 7.1.9.
I just did a deploy from my azure environment:
Extract database -> Import database into sqlserver
And copy the build into IIS.
The files are physically there.
edit: sorry for the double post.
Hi Alex
Hmm, ok - Don't know that much about azure. But have you checked that all your partial view macros exists on the server?
In regards to the content - Have you tried using the "Republish Entire Content" option when right clicking the "CONTENT" node? It refreshes the umbraco.config file - But it will of course only work if the backoffice content is still right but it's the wrong content that is being showed on the frontend.
/Jan
I fixed it. One of my dev messed up the database connection string...
is working on a reply...