I have referenced Nancy.Viewengines.DotLiquid and DotLiquid but there is a bug in NancyFx response:
Nancy.RequestExecutionException: Oh noes! ---> Nancy.ViewEngines.ViewNotFoundException: Unable to locate view 'index'
Currently available view engine extensions: sshtml,html,htm
Locations inspected: views/Index/index-zh-CN,views/Index/index,Index/index-zh-CN,Index/index,views/index-zh-CN,views/index,index-zh-CN,index
this.ViewEngines.ToList() only has Nancy.ViewEngines.SuperSimpleViewEngine.SuperSimpleViewEngineWrapper.
How can I set the dotliquid engine for nancy?
Related
Recently I have installed last version of DNN (9.10.2) and last LTS version of 2sxc (12.8.1)
Everything is working as expected but after check DNN logs I found this error
DotNetNuke.Web.Mvc.Extensions.StartupExtensions - Unable to configure services for ToSic.Sxc, Version=12.8.1.26412, Culture=neutral, PublicKeyToken=null, see exception for details
- LoaderException: Could not load file or assembly 'Microsoft.AspNetCore.Http.Features, Version=1.1.1.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. The system cannot find the file specified.
System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module)
at System.Reflection.RuntimeModule.GetTypes()
at System.Reflection.Assembly.GetTypes()
at DotNetNuke.DependencyInjection.Extensions.TypeExtensions.SafeGetTypes(Assembly assembly, ILog logger)
As I said 2sxc is working without any problem but is generating in back those logs.
Maybe is needed to add or install some framework or component in server ?
ANY idea
I've developed a custom DNN module using the DNN web forms template found at christoc.com. The solution builds without error and the resulting install package installs without issue in my DNN 9.2 instance.
When I attempt to add the custom module to a page, I receive the above error. Chrome developer tools shows further information as follows:
POST http://localhost:81/API/internalservices/controlbar/AddModule 500
(Internal Server Error)
send # jquery.js?cdv=150:9566
ajax # jquery.js?cdv=150:9173
jQuery.ajax # jquery-migrate.js?cdv=150:191
request # ModuleService.js?cdv=150:30
addModule # ModuleDialog.js?cdv=150:214
_doAddModule # ModuleDialog.js?cdv=150:794
proxy # jquery.js?cdv=150:496
dispatch # jquery.js?cdv=150:5206
elemData.handle # jquery.js?cdv=150:5014
The standard DNN modules like HTML install onto the same page without issue. I just applied the 9.2 most recent upgrade package to the instance which is running the generic DNN skin.
It seems that there's an issue with JQuery but I'm unsure where the issue resides and how to remedy it. Any help and guidance would be much appreciated.
UPDATE:
I wanted to share a segment of the DNN Manifest file as this may be the root cause, but am unsure. Sample is as follows:
<moduleControl>
<controlKey>Product AccountLink</controlKey>
<controlSrc>DesktopModules/MyModuleName/P_View_AccountLink.ascx</controlSrc>
<supportsPartialRendering>False</supportsPartialRendering>
<controlTitle>AccountLink Content</controlTitle>
<controlType>View</controlType>
<iconFile />
<helpUrl />
<viewOrder>0</viewOrder>
<supportsPopUps>True</supportsPopUps>
</moduleControl>
UPDATE 2: I've learned that the View that's intended to be the first to be seen when the module is viewed on a page must have controlKey set to nothing in the DNN Manifest. After doing this, removing the module, reinstalling it, and attempting to place on the page, the following error was thrown:
AbsoluteURL:/Default.aspx
DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke
ExceptionGUID:5386839d-258e-4214-ae27-fb0bbae8837a
AssemblyVersion:
PortalId:-1
UserId:-1
TabId:-1
RawUrl:
Referrer:
UserAgent:
ExceptionHash:rtw8cf/KL7W//vxFceePqix1IGE=
Message:Value cannot be null. Parameter name: type
StackTrace:
at System.Activator.CreateInstance(Type type, Boolean nonPublic) at
System.Activator.CreateInstance(Type type) at
DotNetNuke.UI.Skins.Pane.IsVesionableModule(ModuleInfo moduleInfo) at
DotNetNuke.UI.Skins.Pane.InjectModule(ModuleInfo module) at
DotNetNuke.UI.Skins.Skin.InjectModule(Pane pane, ModuleInfo module)
InnerMessage:
InnerStackTrace:
Source:mscorlib
FileName:
FileLineNumber:0
FileColumnNumber:0
Method:
So at this point, the module still does not add properly to the page. I noted the following entry in the SQL Server DNN EventLog table:
<LogProperties>
<LogProperty>
<PropertyName>AbsoluteURL</PropertyName>
<PropertyValue>/Default.aspx</PropertyValue>
</LogProperty>
<LogProperty>
<PropertyName>DefaultDataProvider</PropertyName>
<PropertyValue>DotNetNuke.Data.SqlDataProvider,
DotNetNuke</PropertyValue>
</LogProperty>
<LogProperty>
<PropertyName>ExceptionGUID</PropertyName>
<PropertyValue>5386839d-258e-4214-ae27-fb0bbae8837a</PropertyValue>
</LogProperty>
</LogProperties>
I't been a while, but I believe I got a similar error with one of my modules once.
It could be added to a page on older installations without problems, and installing in DNN 9 was also fine. But adding it to a page in DNN 9 would not work.
The problem was a mismatch between what was listed in the .DNN file and the actual contents of the install package.
I think it was a moduleControls node in moduleDefinitions that did not exist anymore, or it was the other way around.
Anyway match all items in the DNN file with actual files and remove/add defenitions and reinstall the package.
I'm using Worklight 6.2 server edition and I can't deploy a working runtime (of other environments) on my server.
I'm using webpshere liberty profile v8.5.5 and when I deploy the runtime via GUI it says success and on server.xml I can see the new configuration for the app.
However when I go to the worklightconsole I don't see my runtime to upload the app.
On messages.log there is a error regarding JMX connection.
The quoted error is
Failed to obtain JMX connection to access an MBean. There might be a JMX configuration error: No JMX connector is configured
I'm refering this because I've seen some post on SO saying that these issues might be connected. However I have the restConnector-1.0 on my WLP features.
Reference: No runtime on my Worklight 6.2 Console after installing analytics
On messages.log there is some other things that I found interesting, like the correct start of the runtime I've deployed
[11/12/14 5:50:45:177 CST] 00000012 com.worklight.server.bundle.project.JeeProjectActivator I FWLST0002I: ========= Project /HelloWorld started. The project WAR file version is 6.2.0.00.20140922-2259,running on server version 6.2.0.00.20140613-0730. [project HelloWorld]
and two erros while starting my server
[11/12/14 5:50:49:911 CST] 00000012 SystemErr R 24 WorklightPU WARN [Scheduled Executor-thread-1] openjpa.Runtime - An error occurred while registering a ClassTransformer with PersistenceUnitInfo: name 'WorklightPU', root URL [file:/opt/IBM/WebSphere/Liberty/usr/shared/resources/worklight/lib/worklight-jee-library.jar]. The error has been consumed. To see it, set your openjpa.Runtime log level to TRACE. Load-time class transformation will not be available.
Second error:
java.lang.RuntimeException: Timeout while waiting for the management service to start up
I don't know what these are but I think it might be related to my problem and this errors eventually appear when I start my server.
Does anyone have any tips for troubleshooting this issue?
Thanks in advance.
This is a known issue from Websphere.
There is a APAR to fix that, a workaround is to restart the server with the --clean option to force a refresh onto the shared libraries.
http://www-01.ibm.com/support/docview.wss?uid=swg1PI17830
I'm attempting to use appcfg.py migrate_traffic, but I get a 500 error when using this with a module. The documentation states that a module can be specified:
The 'migrate_traffic' command gradually gradually sends an increasing fraction
of traffic your app's traffic from the current default version to another
version. Once all traffic has been migrated, the new version is set as the
default version.
app.yaml specifies the target application, version, and (optionally) module; use
the --application, --version and --module flags to override these values.
Can be thought of as an enhanced version of the 'set_default_version'
command.
If I try this with a module, I get the following error
Error 500: --- begin server output ---
Server Error (500)
A server error has occurred.
--- end server output ---
The source at https://code.google.com/p/googleappengine/source/browse/trunk/python/google/appengine/tools/appcfg.py?r=396 (MigrateTraffic) doesn't seem to use the module at all. Is this a bug in appcfg.py or a missing feature of app engine?
I filed a ticket with google support. The answer is that modules are not supported with migrate_traffic yet. No ETA on when they might be supported. I think the current version of appcfg.py doesn't mention modules as prominently in the help for migrate_traffic as well.
I am trying to install dotnetnuke in my system. For that i have unzipped dotnetnuke installable zip at C:\inetpub\wwwroot\DotNetNuke and created this directory as virtual in iis. Any other than this i have to do to successfully install ddn. How to create and attach database with it. Currently i am gettting below error.
Server Error
HTTP Error 500.19 - Internal Server Error
Description: The requested page cannot be accessed because the related configuration data for the page is invalid.
Error Code: 0x80070021
Notification: BeginRequest
Module: IIS Web Core
Requested URL: http://localhost:80/dotnetnuke
Physical Path: C:\inetpub\wwwroot\DotNetNuke
Logon User: Not yet determined
Logon Method: Not yet determined
Handler: Not yet determined
Config Error: This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".
Config File: \?\C:\inetpub\wwwroot\DotNetNuke\web.config
Config Source:
79:
80:
81:
More Information... This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.
Server Version Information: Internet Information Services 7.0.
Microsoft has a tool called Webmatrix which makes it very easy to install DotNetNuke (and other applications).