Hi I've been facing an issue on my website avcpetstore.com
-theme used in this is (Porto ecommerce theme)
I've tried the following steps already.
disabling all plugins (doesn't workout)
disabling current theme and activation other 2 themes (doesn't workout)
Php memory limit increased already - permalinks setup multiple times (did't workout)
all other things in terms of debug did't workout. console showing
Browser's console showing this error
Unable to fix malformed JSON
checkout.min.js?ver=7.0.0:1 ---------- Unable to fix malformed JSON
Probably in your checkout page file while copy-paste code you miss clicked and remover or added symbol like '<' so you should review code from end to start looking for unintended content. Also you could try disabling (commenting) all the hooks to that file one by one, maybe there is mistake in them.
Also you can try using the default woocommerce template file to see if it start working again and trying adding your custom code on top of your fresh default file.
Related
Recently, the forward search on Lyx all of sudden stop working and the customized layout also stop working...
So, I try to reconfigure by clicking Tools - Reconfigure, but it says "The system reconfiguration has failed. Default textclass is used but LyX may not be able to work properly. Please reconfigure again if needed."
If I select customized document class then it says "Due to some error in it, the layout file: artticletheorem could not loaded. A default textclass with default layouts will be used. Lyx will not be able to produce correct output." I don't know what happened... It used to work well with no issue.
In addition, I would be very much appreciated if someone let me know how to use .cls file in lyx. It looks like I need .layout file, but how can I convert it? Also, I have .bst file for the reference style, but I have no idea how to use it in Lyx...
I installed Magento 2 - Luma theme using XAMPP.
When I try to change one heading for example, from Admin Panel - everything is working.It displays changed heading in the front end correctly.
When I try do the same from core code - it's not working.
I save everything in core core when change something. Delete cache.Change browsers - none of these working.
If you really want to reflect the changes in css/html on run time, you have to change in pub/static/front end/magento/theme/css contents, then you can check the result on front end, if you are doing the changes in code folder you have to clean/flush the cache, still you are not seeing the result, just run the deployment command. everything will be working fine.
You have to to use Flush JavaScript/CSS Cache
and Flush Static Files Cache
I'm trying Azure Functions for the first time and have been able to build and publish "Release" versions without any issue.
I want to step through the code and so need to create and publish a "Debug" version but when I try and build I get the following errors with the same code:
CS0579 Duplicate 'System.Reflection.AssemblyCompanyAttribute' attribute
CS0579 Duplicate 'System.Reflection.AssemblyConfigurationAttribute' attribute
CS0579 Duplicate 'System.Reflection.AssemblyFileVersionAttribute' attribute
CS0579 Duplicate 'System.Reflection.AssemblyInformationalVersionAttribute' attribute
CS0579 Duplicate 'System.Reflection.AssemblyProductAttribute' attribute
CS0579 Duplicate 'System.Reflection.AssemblyTitleAttribute' attribute
CS0579 Duplicate 'System.Reflection.AssemblyVersionAttribute' attribute
From researching this error the main suggestion has been to remove them from the AssemblyInfo.cs file but rebuilds just put them back in again and the "Release" version is happy with these settings being there.
What am I missing so I can create a "Debug" version of the code?
Thanks
According to your description about CS0579 Duplicate error ,I suppose some temporary *.cs files generated during compilation got accidentally added to the project. The files were from the obj\Debug directory, you could try to delete these files to solve problem. For more details, you could refer to this SO thread.
In my case, some temporary *.cs files generated during compilation got accidentally added to the project.
The files were from the obj\Debug directory, so they definitely shouldn't have been added to the solution. A *.cs wildcard went a little crazy and added them incorrectly.
If it doesn't work, there are also other solutions you could have a try. Such as right click project name>choose Edit FunctionName.csproj. Edit the csproj and turn the generation of the attributes causing the issues off. More solutions you could refer to this article.
Resolution
I found this issue on GitHub where there were a couple of options to resolve this issue which I am going to cover here plus a third option I tried not mention in the issue.
I have managed to now get the Debug to build by following one of Janley's link and adding 4 extra lines into the .csproj file:
<GenerateAssemblyConfigurationAttribute>false</GenerateAssemblyConfigurationAttribute>
<GenerateAssemblyCompanyAttribute>false</GenerateAssemblyCompanyAttribute>
<GenerateAssemblyProductAttribute>false</GenerateAssemblyProductAttribute>
<GenerateAssemblyFileVersionAttribute>false</GenerateAssemblyFileVersionAttribute>
<GenerateAssemblyInformationalVersionAttribute>false</GenerateAssemblyInformationalVersionAttribute>
<GenerateAssemblyTitleAttribute>false</GenerateAssemblyTitleAttribute>
<GenerateAssemblyVersionAttribute>false</GenerateAssemblyVersionAttribute>
I created first plugin for sublime text 3 with name relative:
import sublime, sublime_plugin
class ExampleCommand(sublime_plugin.TextCommand):
def run(self, edit):
self.view.insert(edit, 0, "Hello, World!")
Then save it to path
/pathToSublime3/Packages/relative/relative.py
Then try to test it in command window (cntrl + `):
view.run_command('example')
I expected to see Hello, World! in the beginning of current opened file, but fail. What I do wrong?
If your experience was like mine, you may have copied several super basic plugins to try to find one that worked. I think the failure of the others was affecting the Hello World one. For what it's worth, here are the things I did that seem to have worked.
I'm using ST3 on Win7, so maybe there are differences in plugin development between that and ST2.
Note that as I tried many different permutations of these, I don't exactly know which ones are the real fix. But if these get you working, then maybe you can start making incremental changes and see when it breaks.
Moved all *.py files that were my plugins into "Packages" folder. (I read many posts that said that plugin files in the "Packages\User" or "Packages\NameOfPlugin" folder should be read, but I haven't tried them yet. I put it in "Packages" to make sure that finding the files wasn't a problem.)
Restart Sublime after every change. (The docs say you don't have to, but if you have errors in your plugins, it seems that the auto-reload feature doesn't work. Which kinda makes sense. Once I got the errors out of all my plugins, the auto-reload feature started working correctly.)
A few of the simple/tutorial plugins I copied off the web (even some from sublimetext.com!) referenced/imported "sublimePlugin" which errorred on my ST3 Win7 instance. Apparently the correct library to import is "sublime_plugin". The two places this is used, in basic plugins, are 1) at the very top in the import section, as well as 2) in the class line, which I'll illustrate below...
# didn't work for me...
class ExampleCommand(sublimePlugin.TextCommand):
# DID work for me...
class ExampleCommand(sublime_plugin.TextCommand):
'Ctrl+N' create a new file, then try it again. Don't run it in the old file.
All I need is close sublime text 3 and open it again. Now Hello World works fine
The console doesn't open with Ctrl + ` For Sublime Text 2, but this example is written in the v2 documentation.
Using that command opens up a popup starting with # which is to open another file.
The console opens by doing Ctrl + F1. After that, you can write that code in there, and the text will be added into your current view (in any view, in fact).
Be sure to read the "Where to Store Plugins", I made the mistake of creating a folder (package) when the hello_world.py is simply a plugin. Also keep in mind from the documentation window commands and text commands, cause in this case since it is a text command you must execute it in the "view" that you want it to place the text (which can't be the plugin definition file that you created.
Hope that helps anyone in the future as that was a few things I came across
I downloaded the ArticleComments.php from the homepage, and have copied it to my extensions directory.
I add this line to the end of my LocalSettings.php :
require_once( "extensions/ArticleComments.php" );
But when I do, it knocks my wiki over until I disable it!
The PHP error log says:
Fatal error: Call to a member function addMessage() on a non-object in /opt/bitnami/apps/mediawiki/htdocs/extensions/ArticleComments.php on line 277
where line 277 reads:
$wgMessageCache->addMessage('article-comments-name-string', 'Name');
Any ideas? This is a common extension, and I just don't know why I can't get it to work? Can anyone link me to the correct file / download in case my PHP file is corrupt in some way? Any info would be useful, I'm tearing my hair out!
Apparently, the version of the ArticleComments extension available from the "official homepage" (0.4.3) is pretty badly outdated, and doesn't work with MediaWiki 1.16 or later. There's a more up-to-date version (0.6) available in the Wikimedia SVN repository which fixes a number of incompatibilities and, according to the change log, a few security issues as well.
(The specific reason for the crash you got is that the global $wgMessageCache object, which the old version uses to define its interface message, was removed in MW 1.18. However, looking at the change log, there seem to be several other incompatibilities as well.)
The mediawiki.org page for the ArticleComments extension is currently really confusing: it contains links to the up-to-date version in the infobox, but everything else on the page links to the old version. I really should contact the maintainers of the extension and try to get it straightened out.