Iam trying to use
Umbraco.Web.Models.Mapping.TabsAndPropertiesResolver
method in umbraco custom section api however not able to include it.
using Umbraco.Web.Models.Mapping;
TabsAndPropertiesResolver.AddListView(display, "member", Services.DataTypeService, Services.TextService);
its showing me error message:
Error 61 'Umbraco.Web.Models.Mapping.TabsAndPropertiesResolver' is inaccessible due to its protection level D:\Umb\Site\Development\Membership\Controllers\MembershipAdminController.cs 163
any idea on assembly required for it?
Related
We have created the assetlinks.json file and placed it under the well-known folder in the root.After that when tried to validate the assetlinks.json file using Digital Asset Links API from google we are getting an exception.
{
"maxAge": "599.999999839s",
"debugString": "********************* ERRORS \n Error: deadline_exceeded: Timeout occurred while fetching Web statements from https://www..com./.well-known/assetlinks.json (which is equivalent to 'https://www..com/.well-known/assetlinks.json') using download from the web (ID 1).\n********** INFO MESSAGES ********************\n Info: No statements were found that match your query\n"
}
Can someone please help to understand what will be the root cause of this issue and how to resolve it
I'm trying to get Xamarin.Android to generate bindings for a library supplied as an AAR. JAR2XML is giving me a lot of "can't find type" errors, so I thought I'd try class-parse, but in addition to some library references I'm trying to track down, I'm getting a couple of these:
1> Error while processing '[Method] java.time.temporal.Temporal adjustInto(java.time.temporal.Temporal temporal, long newValue)' in '[Class] java.time.temporal.ChronoField': Type 'java.time.temporal.Temporal' was not found. (TaskId:69)
1> Error while processing '[Method] java.time.temporal.Temporal addTo(java.time.temporal.Temporal temporal, long amount)' in '[Class] java.time.temporal.ChronoUnit': Type 'java.time.temporal.Temporal' was not found. (TaskId:69)
Now, java.time.temporal.Temporal is a new type in JDK 1.8, so I'm wondering if maybe that's part of my problem here (ie. maybe the types that can't load are using other new-in-1.8 types). Running bin\javac -version in the path specified in Options-Xamarin-Android Settings says I'm using "1.8.0_172". My project is targeting "Android 8.1 (Oreo)" - ie. api level 27. Is there some other option I need to set to make sure I'm using 1.8?
I have a site with localization and using the 2sxc module but when i try to translate some of the content I get this error:
Had an error talking to the server (status 400).
Message: Bad Request
Detail: found languages in save which are not available in environment - used has 1 target has 1 used-list: 'en-ca'
Please make sure that it's enabled both on DNN and 2sxc (in the apps-management dialog)
If anyone familiar with contao,
I got a default contao error page when I try to create a news archive, I have check the log and nothing is wrong. Do I need add the news module first?
P.S I am newbie contao user, as a client only asked me to resolve this problem.
Last error log :
[12-Jan-2017 12:46:29 GMT] PHP Fatal error: Uncaught exception 'Exception' with message 'Query error: Unknown column 'master' in 'where clause' (SELECT id, title
FROM tl_news_archive
WHERE jumpTo IN (315) AND master=0
ORDER BY title)' thrown in /homepages/19/d124359810/htdocs/2016/system/modules/core/library/Contao/Database/Statement.php on line 295
I use 2 languages for the website with language extension.
I wonder if it has something to do with the language setting of main archive, because it somehow tells the error of unknown "master"
this is the screenshot of the interface when I tried to create a news archive.
Image : create new news archive
Your database is missing a column from the changelanguage extension. If you still have this extension installed, simply log into the Contao Install Tool and execute a database update.
I don't know what is causing this error. I was working on a custom module on my Magento store and didn't check the homepage of the store regularly. Out of the blue today I am getting this error on my homepage.
Fatal error: Maximum function nesting level of '100' reached, aborting! in C:\Program Files\EasyPHP-5.3.8.0\www\indieswebs\lib\Zend\Db\Adapter\Pdo\Mysql.php on line 1045
The funny thing is there is NO 1045 line number in this file! So I am guessing it's some sort of looping error. But I don't know what is causing it. Can anyone help me figure out what might be causing this particular error and how can I remove it?
Edit:I deleted the cache from the store and reloaded the homepage. The error has changed now. It says:
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 261904 bytes) in C:\Program Files\EasyPHP-5.3.8.0\www\indieswebs\lib\Zend\Db\Select.php on line 281
Does anyone know how to resolve this?
The error only come when you installed xdebug.
Use following setting in php.ini
xdebug.max_nesting_level = 200
I was able to resolve a related issue (that causes the same error message) by checking the files in [webroot]/app/etc/
It was happening (on enterprise edition) because
config.xml
enterprise.xml
were missing from that directory. Once I put them back, that fixed this problem.
I also read elsewhere that a malformed local.xml might cause this issue.
On enterprise edition, use something like:
<default_setup>
<connection>
<host><![CDATA[localhost]]></host>
<username><![CDATA[some_user]]></username>
<password><![CDATA[some_pass]]></password>
<dbname><![CDATA[database_name]]></dbname>
<active>1</active>
</connection>
</default_setup>
On CE, use something like:
<default_setup>
<connection>
<host><![CDATA[localhost]]></host>
<username><![CDATA[your_user]]></username>
<password><![CDATA[your_pass]]></password>
<dbname><![CDATA[your_db]]></dbname>
<initStatements><![CDATA[SET NAMES utf8]]></initStatements>
<model><![CDATA[mysql4]]></model>
<type><![CDATA[pdo_mysql]]></type>
<pdoType><![CDATA[]]></pdoType>
<active>1</active>
</connection>
</default_setup>
I got this in my Collection.php model, and the culprit turned out to be the call to parent::__construct(). Once I remmed it out the error went away. PS: Raising xdebug nesting level limit did not work.