In my local development installation of Intershop Commerce Management 7.9 the property "intershop.template.checkSource" is set to "true", but if I modify a template in Intershop Studio, the change does not become visible.
A look in SMC under "Monitoring > Cartridges > Loaded Cartridges" shows that my cartridges are still loaded from the server folder "share/system/cartridges".
What did I miss?
Just run a
gradlew enableHotCodeReloading
and then deploy the server again.
See
https://support.intershop.com/kb/index.php/Display/280E17
The enableHotCodeReloading task ensures that your locally built cartridges are monitored by the development server for changes. It does so by changing .gradle\gradle.properties
Related
I have installed a fresh Windows10, and downloaded the "dotnet-install.ps1" from Microsoft:
https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-install-script
And I ran it by:
powershell -Command "& '...\dotnet-install.ps1' -Channel 7.0 -Runtime windowsdesktop"
It returned success, and now if I rerun:
> .\dotnet-install.ps1 -Channel 7.0 -Runtime windowsdesktop
dotnet-install: Note that the intended use of this script is for Continuous Integration (CI) scenarios, where:
dotnet-install: - The SDK needs to be installed without user interaction and without admin rights.
dotnet-install: - The SDK installation doesn't need to persist across multiple CI runs.
dotnet-install: To set up a development environment or to run apps, use installers rather than this script. Visit https://dotnet.microsoft.com/download to get the installer.
dotnet-install: .NET Core Windows Desktop Runtime with version '7.0.2' is already installed.
dotnet-install: Adding to current process PATH: "C:\Users\daniel\AppData\Local\Microsoft\dotnet\". Note: This change will not be visible if PowerShell was run as a child process.
It says it's already installed.
However, when I try running my application:
Trying to run dotnet, but it's not found (neither from cmd, nor from powershell).
Tried rebooting the machine, then retry running this script, it keeps telling me it's installed, but I don't understand, what is going on.
I'm trying to configure my PhpStorm 2016.1 to run tests on remote machine. I have PHPUnit installed on dev machine (Windows Server 2012) and web server one (Ubuntu server). I can create "PHPUnit by HTTP" run configuration and then run this configuration. But I want to be able to run test of selected class. And when I open a context menu on a file I can choose "Run" and then temporary run configuration of "PHPUnit" type is created.
PhpStorm help states I have to expand "Create run configuration" context menu item and then choose run configuration type I want. However I have no "Create run configuration" menu item at all. And I could find no single mention of choosing run configuration type for selected file/class or setting default run configuration type.
I have no PHP installed on Dev machine, so running PHPUnit tests locally isn't an option at all. How can I set "PHPUnit by HTTP" as default or single option?
I'm trying to run the latest Asp.Net 5 samples (currently 1.0.0-rc1-update1) on my Ubuntu 14.04 VM guest using VirtualBox on Windows 10. The sample code is being run via shared host directory.
I have the active and default DNX set as the CoreCLR x64.
When I have run the dnu restore command against either of the 2 web projects, the restore completes but with an error message. For example, for the HelloWeb project:
Unable to locate Dependency helloweb >= 1.0.0
If I run then command dnx web for the web projects I get the error message:
Error: Unable to load application or execute command 'Microsoft.AspNet.Server.Kestrel'. Available commands: web.
I have a related question here as I am also trying to also get the same samples running on my Windows machine. As they are basic and also unmodified, so I can't understand why they are not working. To make things worse, I actually had them running on this VM yesterday in the same manner I am trying here and as far as I'm aware, nothing has changed other than I have restarted the VM in the meantime.
Can anyone suggest why the projects are referencing themselves in this way and how I can resolve it?
The issue was being caused because the source code was being shared and the project.lock.json file had been created by the dnu restore process on Windows. I created a separate set of code samples and the code restored then ran fine.
This doesn't explain why the message was appearing but I assume the message Unable to locate Dependency helloweb >= 1.0.0 is actually a red herring and possibly refers to the fact that it can't replace the lock file.
I haven't been able to install new plugins or updating plugins after upgrading to wordpress 4.3 on my Ubuntu Server 12.04.5 32bit machine. Usually I could just do it by clicking on the "update" link that's associated with a specific plugin. And it will update it successfully with less than a minute. But this time, it took so long and at the end, it threw out error "download failed, couldn't connect to host".
Then, I thought and guessed that it might be to do with the new wordpress 4.3. So I downgraded it back to previous version 4.2.4 and tried to update the plugin that needs updating. It also took so long and in the end, gave the same error message.
The strange thing is that I haven't made any changes to my Ubuntu server in terms of firewall at all.
My installed PHP version is 5.5.25 and apache is 2.4.12.
The permission of my wp-config.php is 644.
I don't know what else to look. Any help would be greatly appreciated.
Thank you in advance
did you install the correct .dll files in system directory? uninstall the program and try running a system repair and .dll file patcher
I'm trying to execute a web deploy script on a clean build Windows Server 2008 R2 machine and getting the following error:
ERROR: The system was unable to find the specified registry key or
value. msdeploy.exe is not found on
this machine. Please install Web
Deploy before execute the script.
The package was created in VS2010 and executes fine on my development box (as always!). If I import the package on the server through IIS everything works fine.
Web Deploy has been installed on the server through the Web Deployment Tool 2.1 via the Web P.I and I've verified the inclusion of msdeploy.exe. I'm running the script through the "IIS Extensions/Web Deploy Command Line" start menu item so I'm guessing that the correct paths should be set. I've also tried it as Administrator with the same error.
Any help greatly appreciated.
Copied from here:
There is an error with the way Microsoft’s Web Deploy 2.1 application creates command line packages from Visual Studio 2010.
If you create a package to publish and then try to run the msdeploy.exe command line publishing tool it on a production server running IIS then you may receive the following error:
ERROR: The system was unable to find the specified registry key or
value. msdeploy.exe is not found on this machine. Please install Web
Deploy before execute the script.
Assuming that you actually have installed Web Deploy from http://www.iis.net/download/WebDeploy then the error may be caused by an incorrect registry path variable in the .cmd file that Visual Studio creates.
Open up the .deploy.cmd file that is part of your deployment package in a text editor and look for the following code block:
if "%MSDeployPath%" == "" (
for /F "usebackq tokens=2*" %%i in
(`reg query "HKLM\SOFTWARE\Microsoft\IIS Extensions\MSDeploy\1" /v InstallPath`)
do (if "%%~dpj" == "%%j" (
set MSDeployPath=%%j
If you have installed Web Deploy 2.0 or higher, then the error is caused by the registry query to HKLM\SOFTWARE\Microsoft\IIS Extensions\MSDeploy\1. If you open up regedit on your production server you’ll find that the appropriate key is actually HKLM\SOFTWARE\Microsoft\IIS Extensions\MSDeploy\2.
Change the reference in the.deploy.cmd file and you’ll be able to successfully run the deployment package.
I have the same problem. Installed WebDeploy_2_10_amd64_en-US. Running the Deploy Command Line I get the same erorr. However, in IIS (version 7) I could use an option import application. With this option (right side of the window in the actions toolbar) I was able to import the application deployment package zip file. All settings were imported correctly except for the application pool. I only had to adjust that and everything was running fine.