I updated Emmet to version 2.4.3 and can't seem to find the default snippets.json file. Previously I would just go to the package directory and it is at the root level, but now it's gone. Checked the DOCS and Emmet-Atom Github page but see no mention or update about the snippets.json missing. Has anyone come across this issue? Can anyone let me know where it is located on the updated version?
Related
I can't update any/all of the following packages in my solution:
I get the error:
I've tried reinstalling all packages via NuGet console but still get the same error.
I'm using VS 2022 64bit v 17.0.4. Migrating to PackageReference isn't allowed on this solution.
The only workaround for us was to clone the solution from the remote repository to a fresh local directory.
We tried emptying the NuGet cache, but without success. The problem is that the .dll-File was not present in the package directory (see file path from OP). Mixed backward and forward slashes are not a problem. Deleting/restoring packages did not solve the issue. Commands like Get-Package didn't work either.
We tried diffing the two folders, a) the freshly cloned working one and b) the old not working one, as we suspected that config files not under version control caused the issue. But without any success. We couldn't find any relevant difference. The binary .suo-File was not considered by us. Deleting the .suo-File and restoring packages didn't solve the issue either.
We gave up on that point because we have a workaround to deal with this issue.
I would dig for global VS/NuGet cache/setting files but we decided to not invest more time on that.
By referencing these Nuget Official Site and .Net Standard Implementation Support Chart, .Net 4.6.1 is compatible with NetStandard2.0 Applications.
Please check the version compatibility from the above references and try installing the required dependencies.
I had the same issue and as you wrote that copying repository to fresh local directory worked for you, I made some tests.
I have figured it out, that the problem is windows's path lengt limitation to 260 characters.
Maximum Path Length Limitation
My phpBB installation on Synology DSM 6.1 (latest version) fails after the upgrade from MariaDB5 to MariaDB10. I've already put a detailed failure description here: https://www.phpbb.com/community/viewtopic.php?f=556&t=2441286
I now tried to modify the official Synology package from https://archive.synology.com/download/Package/spk/phpBB/ according to the description on this site: https://amigotechnotes.wordpress.com/2014/05/17/how-to-create-a-spk-for-synology-dsm-to-distribute-your-lamp/
Actually, it didn't work...
I'm getting a "Package is invalid" or something like that in the Synology Package Station when installing from the generated SPK file.
Can anyone look at the repository https://github.com/SeppPenner/PhpBBFixMariaDB5Issue and check where the issue exactly is?
I finally found a solution: https://www.phpbb.com/community/viewtopic.php?f=556&t=2441286&p=14906311#p14906311
Install both database versions (MariaDB 5 and 10).
Import the whole mysql dump from before.
Add the same users (root) to both database versions.
Install phpBB on Synology package center with the passwords and a user for phpBB with some password.
I got an error: Database already exists" --> Dropped database for phpBB in MariaDB10.
Install was successful.
Uninstalled MariaDB5.
The board works again but posting is not possible. (There are some forum posts on this issue already and I will try to find a solution for this, too.)
I downloaded a Meteor Starter project called MeteorAdmin.
In the root of its directory tree, you find a packages directory that contains few packages (boostrap, comments, few others) and also, in the .meteor directory there's a file called packages that defines the dependencies of this project.
What is the difference between them? What I found interesting is that .meteor/packages contains bootstrap as well. In theory shouldn't that be enough so that bootstrap would get downloaded to the project?
The meteor packages file simply lists all of the apps dependencies as well as the load order of each (top to bottom). You can edit this file if you know what you are doing, but it's probably better to leave it alone until you are more familiar with Meteor.
The way you add packages is by typing meteor add <package-name> in your terminal and then it will be added to your project. Additionally, the name of the package will be added to the bottom of your packages file.
A meteor app can have local packages that are defined in the packages folder of the root directory. This project likely is implementing it's own bootstrap package and then added it with the meteor command I listed above. Once a local package is added to your project with the meteor add command it's package name will appear in the packages file just like packages from Atmosphere. I hope that answers your question... Let me know if you were looking for something more specific.
It may be a dumb question but I upgraded meteor.js to meteor 0.9 and now, when I add packages, I do not see /packages folder or smart.json file in the root of my project. How can I reach to the source code of the downloaded packages. Thank you.
The source code of the downloaded packages is in a semi compiled state, nothing like what you would find on github.
To access these have a look at ~/.meteor/packages. You would find them with the new notation e.g for iron:router you would see iron/router instead (depends on your OS if : is used instead)
I'm developing a couple of packages for plone 4.2. For some reason, when I install mypackage.blah through mypackage.policy, it loses access to its resourceDirectories, and its CSS and javascript are unavailable.
If I install mypackage.blah alone, it works fine. But I'm trying to install it using mypackage.policy, so I declared mypackage.blah as a dependency in setup.py and metadata.xml. When I install mypackage.policy, it install mypackage.blah, and its JS and CSS resources are registered, but portal_javascript they marked the files as "resource not found or innaccesible". It's as if it ignored the resourceDirectory directives.
What could be happening for resourceDirectory to be ignored?
Originally mypackage.policy used z3c.autoinclude, but I tried including mypackage.blah configuration directly in mypakcage.policy and even in buildout.cfg, and the problem persisted. There are no error traces in the log or console.
Any idea on how can I solve this problem?
Thanks in advance.
Did you upgrade collective.js.jqueryui? I did that and it REMOVED all other javascript!
I went into the ZMI->portal_CSS-> bundles (tab) and changed from 'jQueryUI' to 'default' in the 3 boxes. if it already is default, go to ZMI->portal_javacripts-> bundles (tab) and change 'jQueryUI' to 'default' in the 3 boxes.