Just out of curiosity.
Even though my code is perfectly compiling yet I am getting a red line under sections that uses c# in the cshtml view.
Once I hover over it I get (The name *** does not exist in the current context)
Any Ideas?
Note: all references are added that's not the problem
I have that happen to me a few times already. Try to remove the reference in the project and add it again, that should fix it.
Related
I've got a cfdocument issue arising from a bug that's been there for at least 11 years, that causes pdf files created within a loop to lose colour after the first file.
There's a fix for this as detailed in the previous 11 year old link, and here, but that fix doesn't seem to work if you have a cfdocumentitem within it - like a header/footer. Using the fix with a header and footer I get the following error:
Routines cannot be declared more than once.
The routine _cffuncCFDOCUMENTITEM_cfpdf2ecfm9393969822 has been declared twice in different templates. ColdFusion cannot
determine the line of the template that caused this error. This is
often caused by an error in the exception handling subsystem.
If I remove the cfdocumentitem it's fine. The error says it been called by different templates, but it's only calling one template (but multiple times).
Anyone know of a fix for this?!
Currently I using OpenCart v2.3.0.2, after me purchased the theme template, I tried follow the documentation but stuck on here.
Before met this errors, I get some similar error, which is
/var/www/html/public_html/catalog/view/theme/logancee/template/extension/module/featured.tpl on line 2
at the end i solve this error by deactive and active the extension. Now I stuck on the footer.tpl, which is this error.
Notice: Undefined variable: registry in /var/www/html/public_html/catalog/view/theme/logancee/template/common/footer.tpl on line 2
Notice: Undefined variable: registry in /var/www/html/public_html/catalog/view/theme/logancee/template/common/cart.tpl on line 2
Notice: Undefined variable: registry in /var/www/html/public_html/catalog/view/theme/logancee/template/common/header.tpl on line 2
Please advice me if you face this kind of error before.
You can end notices in the settings by setting Display Errors to No. Or you can back-trace these errors and variables and fix them accordingly.
The theme you purchased is not prepared to handle some of the extensions, you have already installed.
I suggest you remove ALL extensions, modifications & vQmods that you have added and start adding them again by testing one by one to find out which one is giving you the error!
Also remove all your cached content & files before each step including your browser's cache.
I am using Flask-Admin to provide an admin interface for my web app, and so far everything has gone well. However, I am trying to make it so that the .TXT files can be edited right in the browser.
Reading the docs, I have incorporated the line:
editable_extensions = ('txt')
into my FileAdmin class. However, every time I check the box beside the file and press With Selected -> Edit, I get a "Permission Denied" error. On the contrary, the Rename feature works fine, and I can also click the file name to view the contents.
Does anyone have any idea how to solve this problem, or where I should start looking?
Note that I may very well be missing some required code, as the line above is all I have done with regards to the editing functionality.
EDIT: I have now managed to get:
Unexpected error while reading from filename.txt
This file cannot be edited for now.
Never mind, this was fixed in an update. For those curious as to what the issue was, the edit() function in fileadmin.py was opening the file as 'r', rather than 'rb'. This caused the error:
'str' object has no attribute 'decode'
which consequently produced in error in the very end.
I added a Resource Dictionary named ResourceDictionary1 to my silverlight project.
I also added a Silverlight Class Library to my project named OtherAssembly, then in this new assembly I added a new Resource Dictionary named ResourceDictionary2:
In my original project I'm trying to merge both dictionaries in MainPage.xaml:
<ResourceDictionary>
<ResourceDictionary.MergedDictionaries>
<ResourceDictionary Source="MyResourceDictionary1.xaml" />
<ResourceDictionary Source="/OtherAssembly;component/MyResourceDictionary2.xaml" />
</ResourceDictionary.MergedDictionaries>
When I run the project the line with OtherAssembly throws an exception, saying that there's an error assigning the property System.Windows.ResourceDictionary.Source in that line:
But at design time, the designer shows everything in order, it finds all the resources.
I don't know, It seems that the Pack Uri syntax is not well formed.
Anybody knows why I get this error message?
I found the answer.
I needed to add a reference to OtherAssembly, as the error is not detected until run time, it's hard to detect it.
This code:
<cfimage action="info" structName="imageInfo" source="#imagePath#">
is giving this error:
The attribute 'structName' is required for the tag. (Found:
[source, structname, action])
When I run this code in CFBuilder - everything is OK, but I must use CFEclipse.
What should I do (I use CF9)?
Thank you for your answers!
Of course this problem won't prevent you from running your application on ColdFusion. It is just an IDE warning that something is wrong.
You have a few options.
Try using a lowercase N in structName. i.e. structname. ColdFusion is not case-sensitive, but Java is, and CFEclipse is a Java application.
If that does not work, then it probably means that the dictionary file that drives the code assist is not correct. You can go earch forthose XML files and update them to include that attribute.
You can use CFBuilder. I know you said you can't, but I have to question why. You know there is a free version that is just as good as CFEclipse, right?
The problem is that there's a casing glitch in that file Peter mentions. There's one reference to "structName" to define the attribute itself, and another "structname" which is in the list defining which attributes are needed for action="info". If you make them both the same, then restart Eclipse, you should be OK (that's I've needed to do to make the error indicator go away).