How do I make sbt 0.11.3 use a new snapshot version of a plugin?
reload plugins
doesn't work.
reload plugins
clean
update
doesn't work.
Deleting the metadata files for the plugin in the ivy cache and restarting sbt doesn't work.
sbt ";reload plugins ;update ;reload return"
My mistake. The plugin wasn't being reloaded because the new snapshot hadn't been published for the version of sbt that I was using.
Related
I had some translations in my bundles, for example in src/Bundle/AppBundle/Resources/translations but when I moved it to app/Resources/AppBundle/translations in my Twig templates it shows that translations are missing. I've tried invalidating cache and restarting the IDE but it didn't help.
How can I fix this?
My PhpStorm version: 2017.2.1.
Symfony Documentation:
"Each time you create a new translation resource (or install a bundle that includes a translation resource), be sure to clear your cache so that Symfony can discover the new translation resources"
Phpstorm may be processing by reading the cache files.
Try clearing the Symfony cache.
bin/console cache:clear
Optimize Composer.
composer install --optimize-autoloader
this issue is fixed in PhpStorm Symfony Plugin via https://github.com/Haehnchen/idea-php-symfony2-plugin/issues/1010
Hi I am using a Ubuntu system. I am using a shell script to download wordpress from wget, update config and run it from nginx server.
Now I want to update this shell script so that when we install a fresh copy of WordPress, I get some plugins pre-installed.
So I installed wp-cli and ran the command
wp plugin install w3-total-cache --activate --allow-root
This command says the plugin has been activated successfully. But when I go to the site URL in the plugins section, it gives the following error
The plugin w3-total-cache/w3-total-cache.php has been deactivated due to an error: Plugin file does not exist.
This is true for any plugin that I try to install.
When I go to the plugins folder inside wp-content, I can see that plugin files exist. But still I get the error.
How to resolve this. Please help
You should try uploading the plugin by logging in to your wp-adm
Are you using the latest version of wp-cli?
Try: wp cli check-update
Today I am starting a new project and I am stuck on wordpress plugins installation
Downloading install package from
https://downloads.wordpress.org/plugin/types.1.8.11.zip…
Unpacking the package…
Installing the plugin…
The package could not be installed. No valid plugins were found.
Plugin install failed.`
I ve tried different plugins and all of them produce this error! any ideas?
you can use class-tgm-plugin-activation to install your plugin automatically at your theme
visit and download, https://github.com/TGMPA/TGM-Plugin-Activation
include at your functions
I managed to sucessfully install and activate it, right now. I used wp-cli, but that should not make much difference. I can recommend it though, as it is more verbose, which helps tracking down errors
What is the result of
ls -l .../path/to/wordpress/wp-content/plugins
Assuming you are on Linux/Unix. Do the other plugins have different permissions/users?
When running meteor from a git checkout, there are 2 packages available at path
<meteor-path>/packages/non-core
npm-bcrypt/
npm-node-aes-gcm/
How to use/enable these packages (best practise) on own project?
You can use the published versions of your packages already, because they're on Atmosphere:
meteor add npm-bcrypt
If you want to use specifically their git checkout versions, you need to create a packages subdirectory in your app's directory, and symlink there the paths to the packages.
Much easier than symlink is just setting the PACKAGE_DIRS env var. Have a look at https://forums.meteor.com/t/missing-non-core-packages-when-running-meteor-from-checkout/1140 for more details.
I'm using composer to update symfony bundles,
after updating all bundles, I'm getting some errors and I'd like to restore the previous versions, the problem is that on my composer the version are like 2.*, so I don't know which version there where before.
Is there any composer history/log file where can I see the previous versions of all my bundles?
Thank you
look at composer.lock.
After installing the dependencies, Composer writes the list of the exact versions it installed into a composer.lock file. This locks the project to those specific versions.
http://getcomposer.org/doc/01-basic-usage.md#composer-lock-the-lock-file
If you commit your composer.lock file (as you should), then if you have problems after an update you can just do git checkout composer.lock && composer install which will restore things to the way they were before.