Debugging Episerver Find - episerver

My Episerver Find content indexing job gets quite a few errors when I run it from the editor page, but I don't get any information about which pages/blocks/properties are causing the issue - it just says "see log for more information".
We are already logging everything Episerver and I have tried adding
<logger name="EPiServer.Find">
<appender-ref ref="RollingLogFileAppender" />
<level value="All" />
</logger>
How can I debug the content indexing job?

Related

unable to logoff from the site

I have came across a strange issue regarding a logoff a user from site with my specific theme.
When I press the logoff link, then page is refreshed, but user is still logged in. When I changed the site skin to the default provided by the DNN, then there is no problem.
In completly diffrent site that I created with my custom theme, this links works also. I have disabled the javascript thinking that, maybe some js script mess something but result is the same.
I don't know where to start looking for this issue. Any suggestions?
Disabling javascript is a problem. The "logoff" link uses javascript.
GO back to your custom skin with javascript enabled, and use the developer tools to open the Console window. You should see information there that will help identify the problem.
Try messing with the order and priority of the javascript files in the .ASCX skin control. For example, if you have:
<dnn:DnnJsInclude runat="server" FilePath="jquery.one.js" PathNameAlias="SkinPath" />
<dnn:DnnJsInclude runat="server" FilePath="jquery.two.js" PathNameAlias="SkinPath" />
Try switching them around, or alternatively try changing their priorities, like so:
<dnn:DnnJsInclude runat="server" FilePath="jquery.two.js" PathNameAlias="SkinPath" Priority="100" />
<dnn:DnnJsInclude runat="server" FilePath="jquery.one.js" PathNameAlias="SkinPath" Priority="150" />
Sometimes there is a conflict in the order in which the libraries are loaded, even if it doesn't show up in the console.
You can read more about this in the Client Resource Management API
Finally, try comparing the several skins .ASCX files to each other, to see if something is missing in this particular one.

BrowserLink VS2013 not connecting

my issue is, BrowserLink never connects to my Browser in "Browser Link Dashboard"
i'm using Visual Studio 2013 Prem Update 5 on a Win10 machine
project is a MVC 5 application
Browser is IE11.212.10586.0
BL is activated in the dropdown of the refreshbutton
From here, when i run my app on IISExpress, the BL Dashboard says no connection
but in the HTML i can find the script-Tags
images, i'm not rated enaugh to implement in post
at least, i checked the web and found some web.config parts i should try, but that not resolved my issue
1# <compilation debug="true" targetFramework="4.5" />
2# <add name="Browser Link for HTML" path="*.html" verb="*"
type="System.Web.StaticFileHandler, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
resourceType="File" preCondition="integratedMode" />
so i need to change, save, refresh my page all the time - someone tipps for me what could be wrong?
Many thanks
UPDATE 2016-06-23
The TrafficFiddle by IE10 does not contain a GET Request with BL in URL
He does:
Get HTML File
Load scripts and stuff by "bundle.cs"
load image
Additional: Some weired things happen with DOM Explorer.
There is only html>Head! no body is listed or BL scripts, when i use "inspect element" the full DOM do appear
DOM displayed initial by browser - weired
I would guess the browser would stop add stuff into DOM because of any script issue in head - but when i look with inspect at the "real DOM" there's just the body after the printed DOM - sry not enaugh rep to show a 3rd link :(
You can try looking at a network trace in Fiddler or your browser tools. Since the script tag has been inserted, there should be two requests that have "browserLink" in the URL. The first one gets the Browser Link script, and the second one establishes the SignalR connection. If either of those is failing or missing, the failure could provide a hint why Browser Link is failing to connect.

Solr Default Query in Admin UI does not work

I am changing the default query for the UI in solrconfig.xml but it does not change the default query in the Admin UI. It says legacy config but I don't know where else I should change it to refresh the admin UI. I have reloaded the collection and restarted Solr.
<!-- Legacy config for the admin interface -->
<admin>
<defaultQuery>*:*</defaultQuery>
</admin>
Any ideas?
You can change this by editing the query.html file in the /tpl directory of the webapp.
<textarea name="q" id="q" title="The query string.">*:*</textarea>

How to show in link Google's universal navigation in multi-language?

As you see below, I set multi-language in Google's universal navigation for my app, but it does not work! it is always displayed in Japanese.
<Extension id="navlink" type="link">
<Name>ใƒ†ใ‚นใƒˆ</Name>
<Name language="en">Test</Name>
<Url>https://test.appspot.com/domain/${DOMAIN_NAME}</Url>
<Scope ref="calendarAPI"/>
</Extension>
Could you show me any idea?
This is a known issue with Google Apps Marketplace. We are hoping to address this next year.

dotnetnuke and dotimage problem

I created a module for dotnetnuke that uses Atalasoft's dotImage viewer. dotImage uses and iframe for "ajax" rendering. My module works great on the home page but in any other page the module loads the whole home page in the dotImage iframe.
Has anybody worked with both dotnetnuke and dotImage?
Any tips?
I am from Atalasoft. You should open a support case with us so that we can help you.
In any case, the usual reason for a page showing up in a frame is that there was an exception thrown while generating the contents of the frame -- what you are seeing is the custom 500 page for DotNetNuke.
Probably the easiest way to see what's going on is to temporarily turn off custom error pages in your web.config -- then the problem will show up in the frame and you can fix it. At this point it could be a lot of things (file permissions, not having a license installed correctly, etc) -- so getting the exception is key to solving this.
You turn off custom errors this way:
Look for section like this in your web.config:
<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
<error statusCode="403" redirect="NoAccess.htm" />
<error statusCode="404" redirect="FileNotFound.htm" />
</customErrors>
Make sure that it is uncommented and then change mode in the customErrors node to "Off"

Resources