I am trying to install umbraco packages such as Articulate (used for blogging) but every time I try and install a package I get redirected back to the package page. I have tried to install a local package but it still redirects back to packages.
I am running Windows 10 and VS 2015. I have tried Umbrco 7.5 and Umbraco 7.7 version.
Is there away to detect what the issue is in my umbraco installation if it not a known issue?
Thanks a lot
I have found that I can install the packages on another computer. I believe it to be the network I am on at work is the course of the issue. I worked on a computer that had more privileges and it worked. It might have been because not be able to write to a particular location.
I know in IIS I have to give security permissions to user IIS_IUSERS in the website folder. In order to get the website working.
Related
Sorry for being a noob at this.
I have installed ProcessMaker4 from the Bitnami image and am working towards having some packages and connectors.
From what I understand packages are separate instances (much like a microservice) that connect to ProcessMakerthrough connections (the bit you install in ProcessMaker).
Does anyone have a guide on how to install a connector and how to set up a package? There are apparently a lot of packages available to install, but I have found no guides or anything to install.
It does appear that they are part of the enterprise version of the software.
https://processmaker.gitbook.io/processmaker-release-notes/processmaker-4.1-release-notes/non-core-package-versions
I have WampServer Version 3.1.4 64bit installed on Windows 7 and it comes with PHP versions php5.6.38, php7.0.32, php7.1.22, and php7.2.10. I would like to use php5.6.x rather than php7.x.
So, when I switch from php7.2.10 to php5.6.38 from the server tray icon; it does not update the actual php version which is shown by phpinfo().
On localhost, it still says:
PHP Version: 7.2.10
However, it is updated on CLI side. This is tested with running this in the cmd:
php -v
The result is :
c:\wamp64\bin\apache\apache2.4.35\bin>php -v
PHP 5.6.38 (cli) (built: Sep 13 2018 12:45:08)
Copyright (c) 1997-2016 The PHP Group
Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies
After restarting WAMP services, and re opening the terminal, and restarting computer, it still not updated through phpinfo. It probably related the php version used by Apache service. How can I change this to 5.6.x
Any suggestions ?
Many thanks
Note : The issue is not related with changing php cli version as it was pointed here. I do not understand why some of them insist that this is potential duplication without reading the post carefully.
I have faced kind of similar issue, I have installed wampserver upgrades from https://wampserver.aviatechno.net/?lang=en. I needed php 7.3 and 7.4, after installing the php upgrades, those new versions were not being reflected in wampserver traymenu (left click on wamp icon->php-versions). After spending quite some time looking into this, finally could fix this by following steps :
Clearing logs (right click on wampserver icon -> tools -> empty logs)
[my php log file was 300+ MB].
Restarted wampserver and it was good to go.
I found solution from this thread http://forum.wampserver.com/read.php?2,159184
(TL:DR) Use left click -(instead of right click)- menu to change PHP versions.
(Long explanation)
Hi, this happened to me today. I was trying to change the php version from 7.2 to 5.6 to test something. However, Wampserver was not changing the web version of php. After much searching in the web and noticing in certain videos that some people were getting a different menu than me in the wamp server icon, I realised that there is a whole left click menu in wampserver in which you can change the php version and it does change the web version of php.
I understand that this can be a bit confusing for people who are used to using wampserver, but for someone who is using it for the first time, we are not used to having a left click menu in the bottom right icons. I hope this saves some time for others who have a similar issue than mine.
The wampmanager->Tools->Change PHP CLI Version menu only changes the version of PHP that will be used by wampmanager.exe to run all the PHP scripts that provide all the functionality of WAMPServer.
It has no effect on the version of PHP that will will be run from the command line in Windows.
If when you open a command windows and run the PHP interpreter >php.exe you actually get to the PHP interpreter, then you must have added one of the possible paths to one of WAMPServers PHP folders to the Window's PATH. You should never do this with WAMPServer, so if this is what you did, UNDO IT! This is for obvious reasons as you could have multiple versions of PHP available and want to run any one of them at any time as the CLI Version to test some code against multiple versions of PHP.
Instead create yourself a little batch/cmd file that accepts a php version as a parameter like in this answer I posted a while ago
With that you can set the PATH temporarily for the life of a command window ONLY. You can also make it include a PATH to the PEAR and/or COMPOSER folders at the same time, if you use either of these.
To check All VC Runtimes
There is a tool for checking if you have all the possible required VC Runtimes installed. Go to this page, the backup repo for WAMPServer, and download the little utility called Checks VC++ packages installed you will find it down near the bottom of the page. Download and run it, then throw it away, as it changes over time as new VC Runtimes become required.
My question, is there a way to configure the InstallShield setup and deployment project so that when I attempt to install the service it will uninstall the previously installed version of the service.
I've created a Windows Service and an InstallShield setup and deployment project to be able to install it onto my machine. The process of installing and uninstalling the service all works fine. When I go to update the service, at the moment, I need to stop the service, uninstall the service manually, and then run the installer. What I am trying to get to is a point where I can run the installer and it will uninstall the previous version of the service before installing the current version.
I have seen this process of running the install and having the previous versions uninstalled work. Through creating a test project using a windows form application. I was able to install the application. Then I: incremented the product version, created a new product code, added a new upgrade entry in the upgrade path area, and configured that upgrade entry setting the min and max version. After doing this, I rebuilt the setup project and ran the installer and the upgrade from version A to version B was complete.
The only difference I believe from the original test project (where I saw the process work) and my Windows Service project is that my test project was a Windows Forms application versus a Windows Service. In all the research I have been doing I have seen people ask similar questions, but I have not seen any real suggestions on what actions to take. So if anyone knows if this is possible or has any suggestions that I could try to accomplish this task they would be greatly appreciated.
I was able to resolve this issue, so it is possible. The setting I mentioned above are the correct settings needed to allow the service to update. This was just a case of human error that was causing my problems.
Quick background. My client uses Visual Studio 2010 for their website. It was ported onto a new machine, and I had to do some extensive work to get all of the 3rd party controls and add-ons to work. They then requested source control, so using their MSDN license I pulled down and installed TFS 2012 on their machine. Everything installed correctly, and seemed to work until I went to add the existing VS2010 project to TFS2012, and I got an error that when traced back, basically told me that I would not be able to use TFS 2012 and VS2010 together. I weighed the choices, updating the project to VS2012, or uninstalling TFS 2012 and installing TFS2010, and decided the TFS route was the way to go, as I did not want to screw around with all the add-ons again. TFS2012 uninstalled fine, and TFS2010 installed fine.
When I went to start configuring TFS2010, I got an error ([ Application Tier ] TF255297: The Web site found has bindings that conflict with the bindings chosen for the Web site for Team Foundation Server. You must manually resolve the conflict between the bindings.) basically telling me the binding were not removed for the TFS2012 install. I looked in IIS and there is nothing in there using port 8080.
So my question is, how do I find out where the bindings are in use. I tried the netstat commands, and did not find anything using port 8080. I am kind of dead in the water here, so any help that is offered would be greatly appreciated.
Background / History
I have a solution that contains an MVC4 project.
I downloaded a nuget package (specifically the dotLess package). This added a packages folder to my solution directory which includes dotless (it's still there).
I then removed the MVC4 project to start fresh and added a new project with the same name.
Normally, I would just reinstall the package. However, this seems to require the Nuget server and a connection to the internet. This is fine, except currently my development machine is without internet.
Question
Since I can see the folder with the package file in my solution's "packages" directory, is there any way I can add it to the project without having to round-trip via the internet?
Another option would be to setup a local nuget gallery for your offline access to the packages
http://www.codecapers.com/post/How-to-Set-Up-a-Local-NuGet-Gallery.aspx
Have you tried this from Scott Hanselman? http://www.hanselman.com/blog/HowToAccessNuGetWhenNuGetorgIsDownOrYoureOnAPlane.aspx
In brief he suggests that since NuGet caches stuff on your local hard drive, you should tell it to point there.
I used this when a proxy was preventing me from connecting to the internet and it worked nicely!
If I understand you correctly and you know the correct version number then you could try adding the following to packages.config and see if it's picked up correctly.
<package id="dotless" version="1.3.1.0" />
This is perhaps not an ideal answer but whenever I loose connection with a Nuget package in Visual Studio I usually turn to the Nuget Console and reinstall from there, after that all connections are restored. Which in your case would be something like:
PM> Install-Package dotless
Anyway, maybe I´m misunderstanding your issue ;)
Regards!