I've decided to add interactive maps to my website and Leaflet module seems to provide mobile-friendly maps. I followed the installation steps, everything was fine until the end. For some reason, I get Leaflet JavaScript library could not be detected error. I verified that the library is uploaded inside the correct directory; sites/all/libraries/leaflet/ but deleted and uploaded it again just in case. I spent over 2 hours to resolve it but I'd really like some help now!
Website address: http://www.kampuster.com/tr/home-inner-new
Turns out that there is an error in the code. I changed version control to the following and it worked.
'version' > 0
The version has to be added to the leaflet_libraries_info() hook.
There is an open issue in the Leaflet module issue queue here which outlines the problem
Related
I have been beating my head for the last 7 hours on this. Full disclosure, I am a PHP guy and not the strongest at ASP.net. So I am coming to you experts.
The issue is that when we run the code below it will product a valid PDF if we use the MSHtmlEngine function (which sets EngineType to MSHtml), but it won't work with the GeckoEngineOptions (which sets EngineType to Gekco). The problem is that the MSHtml won't generate the SVG graphics, so we need to run the Gecko method. When we run the Gecko method, it produces this error:
"ErrorMessage":"Failed to find ABCGeckoWP.exe."
However the file is in the output directory ("bin/"), as well as the project directory. The XULRunner38_0 also appears to be right as well in both the project and bin/.
I am including some screenshots in case it helps / show what has already been tried (sorry for the sizes being all over the place).
You might want to reinstall Abcpdf, from Nuget or reinstall the correct version on the server depending on how it's set up.
ABCGecko cannot function without the XULRunner38_0 folder in the same directory as ABCGeckoWP.exe.
On x64 Windows, even if ABCGeckoWP.exe is found only in %SystemRoot%\System32 (though it should be placed only in %SystemRoot%\SysWOW64 for being 32-bit), it never looks up XULRunner38_0 folder in %SystemRoot%\System32 (but in %SystemRoot%\SysWOW64) because of File System Redirection.
So maybe check the file location as stated above.
This error looks like the version of ABCPdf that you are using and the version installed on the server are not the same.
I would also recommend upgrading the version to the latest one and using the Chrome render engine.
I've been creating a small website using NextJS. I used formik and google-map-react to validate a form and show a basic map.
IE11 is "not cooperating" in using these libraries. I've tried changing the babel config and used the next-transpile-modules package to try and provide polyfills and transpiling of the node_modules packages without result.
Any push in the right direction will be greatly appreciated!
Kind regards
After further trial and error, I found the package google-map-react to be the problem. Removing the component that uses this package solved the formik/yup errors.
With regards to google-map-react, I removed this package and used the native google maps api package (#googlemaps/js-api-loader => see documentation for usage).
To get nextjs to transpile both packages from the node_modules, the next-transpile-modules package was added and used within next.config.js.
In the end all I had to do was edit my babel.config.json file, the next.config.js and package.json file.
Below are images of what they look like now.
babel.config.json
next.config.js
add this line to package.json
Keep in mind that #babel/core, #babel/preset-env, core-js need to be installed.
I hope this solution is helpful to anybody experiencing the same problems. I also changed the title since formik wasn't the problem.
In VSCode, in settings.json for one of my extensions is a line
"extends": "C:/Users/snarl/.vscode/extensions/stylelint-config-wordpress",
But that line is dimmed compared to the rest of the text in the file, as if disabled, or path not found (screenshot). Is that indicating some kind of error I need to resolve? That folder does indeed exist at that location (screenshot).
Motivation For My Question
I ask because this is a line of code I manually added to settings.json, as part of installation instructions for a particular extension. I'm currently using the stylelint extension to help notify me of errors while I type. I am now trying to install a separate extension--stylelint-config-wordpress--which is a set of rules to be used with stylelint. But that new ruleset doesn't seem to be working properly. So I am now trying to troubleshoot why the new rules are not working properly. The settings.json file I edited is part of the stylelint-config-wordpress extension.
Of Note
I am running Windows 10.
When I initially installed stylelint, I installed it globally. I can confirm it was installed properly and linting errors in my code, as expected.
In the GitHub repo for stylelint-config-wordpress, there is one issue related to this (see here). I posted there and received some initial replies. But nothing worked, and I've not heard back since.
After opening an issue in the relevant GitHub repo, I was able to understand the answer to my question.
Short Answer: The code I was adding was incorrect. I was adding:
extends": "C:/Users/snarl/.vscode/extensions/stylelint-config-wordpress",
when I should have been adding something more along the lines of this:
"stylelint.config": {
"extends": "C:/Users/snarl/index.js"
},
Long Answer: If anyone is really curious about how to get this ruleset working in VSCode, you can read this issue.
Upgraded to the latest 0.6.0 of meteor and Collection API is not define, meteor does not start correctly any more:
ReferenceError: CollectionAPI is not defined
I copy pasted collectionapi to app "packages" folder, but still does not run. Is there anything else I have to do, to use Collection API with latest meteor 0.6.0?
meteor add collectionapi - says: collectionapi: already using
Thanks in advance for any kind of information and help!
I'm not sure copying and pasting packages is a good idea. Have you tried reinstalling it with meteor remove collectionapi and then adding it again?
Update: I seem to be getting the same problem with one of my packages, chartjs. It's now giving a similar error to yours, saying ReferenceError: Chart is not defined. Previously Chart was scoped to the window, so it could be accessed in my client JS files. It must be due to the scoping changes in 0.6.0, but I'm not sure yet how to resolve it - probably the package itself needs updating.
Update 2: Yup, akshat was dead right, the JS file at the heart of the chartjs package needed the var Chart changing to just Chart so it would be scoped to the window object. Have sent a pull request to the package.
Yes, thanks for answers. Fix is also available for download in CollectionAPI github:
https://github.com/crazytoad/meteor-collectionapi/pull/12
I need to get the source code for this, but unfortunately, I can't find links to it on jquerytools.org. The forum on that site is also down. Does anyone know where I can get this source or unminify it?
Thanks,
Rob
Have you tried going on http://jquerytools.org/download/? (I mean appending '/download/' to the url you posted)
EDIT: However you can download the source from Git, got to the link and click "clone" or "zip".
EDIT: No, it's the 1.2.7 version, as you can see in the "tag" link they tagged the 1.2.7 version about 7 months ago, this is the version you need as far as I can read in your question, if you are not convinced than I suggest you this link (that is the link near "Tagging version 1.2.7" in the github project's tag page):
https://github.com/jquerytools/jquerytools/zipball/v1.2.7
clicking on the link above you will start to download jquerytools v1.2.7 in a .zip file
It has become very difficult to find the source code for jQueryTools, and since the original CDN provided by the author has now disappeared a lot of sites that were calling the toolset from the CDN in question have stopped working.
There is a useful resource at https://cdnjs.com/libraries/jquery-tools/1.2.7 that provides CDN/download links for all version of jQueryTools back to v1.2.0, which although it is not a source repository, can at least help some people with legacy sites still running to keep them running whilst they find an alternate solution or replace the website.