|
|
Rank: Newbie
Joined: 5/7/2008
Posts: 10
Location: co.us
|
I have a weird problem. I just converted some reports I had to be ascx controls and put them in Umbraco. All is fine with the first version of each one. Then I tried to create new content pages and put the same macros on them but with a different parameter value and Umbraco chokes. When I add the macro the editor shows my content coming in fine. As soon as I save the page, the frame goes blank and I can't access any tabs and the editor is gone. When I try to view the page from my site, I just have a blank where the content should be. The first versions are still working fine, but any macro I try to add now causes this behavior, including one that does not have any parameters.
I have tried re-publishing the site and restarting the web service and site and the problem is still there. Any time I navigate to one of these problem pages the editor frame is blank and I can't get to any of the tabs including Properties.
Anyone else run into this? Any ideas on how to troubleshoot?
Thanks for any suggestions you may have!
~chuck
|
|
Rank: Enthusiast
Joined: 5/13/2008
Posts: 45
Location: VA, USA
|
I ran across this a few weeks ago and ended up getting rid of the in-editor macro and doing something else entirely. The only way for me to get the node to redisplay correctly was to delete and re-add the node because clicking on the node in the content tree pulled up a blank pane on the right side as well. I don't think I was using a user control at the time, but it's been a while and I'm fuzzy on the details now.
|
|
Rank: Newbie
Joined: 5/7/2008
Posts: 10
Location: co.us
|
Hmmm... More info but I still don't understand. I tacked ?umbdebugshowtrace=true on the end of the URL. The only thing that stands out in red is "No macro with alias '' found." So I checked the source after adding the macro (and before saving where the problem occurs) and there surely is an alias at that point. The stack trace seems to indicate it is there as well, but it contradicts itself right after. See bold section below.
template Begining of parsing rutine... 0.0131421520714063 0.000056
umbTemplate Outputting item: <?UMBRACO_GETITEM field="bodyText"/> 0.013352781387955 0.000211
item Start parsing 'bodyText' 0.0133837108802985 0.000031
item Done parsing 'bodyText' 0.013409101585017 0.000025
template Begining of parsing rutine... 0.0134615872368002 0.000052
umbTemplate Outputting item: <?UMBRACO_MACRO umb_eventid="223" macroalias="CareerFairOrgsbyJobFunction" /> 0.013671274207581 0.000210
macro No macro with alias '' found 0.0145183954343491 0.000847
template Begining of parsing rutine... 0.0146158204530564 0.000097
umbTemplate Outputting item: <?UMBRACO_GETITEM field="postContentInclude"/> 0.0148292091384625 0.000213
item Start parsing 'postContentInclude' 0.0148675646162053 0.000038
item Done parsing 'postContentInclude' 0.0148934590749115 0.000026
template Begining of parsing rutine... 0.0149530398885798 0.000060
aspx.page End Init 0.0153223667486565 0.000369
aspx.page Begin InitComplete 0.0153453414392255 0.000023
|
|
Rank: Addict
Joined: 7/19/2006
Posts: 789
Location: Århus, Denmark
|
I have sometimes seen the tabs getting messed up because an error message has been written out in the html source of the editor page, but is not visible. But it has messed up the div's. Try and do a "View source" on the editor pages that are giving you problems and see if there are any .Net exception messages.
|
|
Rank: Newbie
Joined: 5/7/2008
Posts: 10
Location: co.us
|
Thanks for the tip. I did not see any error messages in the html source.
|
|
Rank: Newbie
Joined: 5/7/2008
Posts: 10
Location: co.us
|
OK. Problem averted, but not solved. After browsing the forum quite a bit I found somewhat related posts mentioning problems with macros and firefox. Switched to IE and re-created the pages and all are working now. Not sure what FF would be doing differently. Not going to waste any more time with it.
|
|
Rank: Enthusiast
Joined: 5/13/2008
Posts: 45
Location: VA, USA
|
Now that you mention it, I think that may have been the way I fixed it as well. I was using v3.0.3 at the time and I know there were a lot of FF fixes in v3.0.5 so it may be a non issue now unless you are using v3.0.5. I haven't had the problem in any recent sites.
|
|
|
Guest |