How I can change the .dev extension with .test to be able to continue developing usin chrome?
-
As per the latest chrome update which made any local site end with .dev extension force it to redirect to https so they give error and can't view them in chrome, How I can change the .dev extension with .test to be able to continue developing usin chrome? I changed the .dev to .test from the preference - general but it didn't work for me. @leokhoa
-
@waul : What do you mean it doesn't work for you? Any images?
By the way, why don't you use Vivaldi (https://vivaldi.com) - It's chrome-based and far better than Chrome.
-
Hola @waul,
You just have to change the TLD from preferences, and press reload.
When the servics restart, Laragon application will generate new sites-enabled configuration file, and change the host file for you.
If the browser redirect you to google search, you should add http:// to your url bar, example: http://myapplication.test.
-
Typing
http://is waste of time. That's why we should go with.dev
-
@leokhoa, it's only once (except, you delete the cache or set the browser setting, you have to do it again). But i guess i will try Vivaldi, since it's chrome-based.
But, why it's better than chrome?
-
@rizaldywirawan : It's fast & friendly. It also have many unique features. It is created by former founder of Opera with long-term mission. Just try it.
If you have any doubt, just check other references:
https://www.howtogeek.com/250683/the-best-features-of-vivaldi-a-new-customizable-web-browser-for-power-users/
https://www.hongkiat.com/blog/cool-vivaldi-browser-features/
-
@leokhoa I mean after changing to .test from .dev and typing for example "dilon.test " in chrome it redirect to "https://dilon.dev" and in firefox also redirect to "dilon.dev" the old url and it give error "We’re having trouble finding that site." or "This site can’t be reached", although the hosts file was changed to .test and also the http-vhosts.conf was changed to .test
-
@waul : How about another clean browers or Incognito mode to avoid cache issue?
If you have the same result, I believe somewhere in your code using.dev
-
Halo @waul
try to remove the cache, or open it in Mozilla Firefox
-
This issue is De facto issue in my locality and mostly with chrome. And it is a pain to leave chrome b'cos of extensions.
It does not work when you change .dev to anything.
What i did is switch my dev browser to firefox
-
@leokhoa I did that already with the same result
-
@rizaldywirawan I did that also in Mozilla Firefox and deleted all caches from chrome and firefox and also used Incognito mode
all these results are the same not working
-
@Jo3e Yes exactly the same with me
-
@waul, @Jo3e : Can you guys check your code?
or delete all the generated Virtual Host files in Menu > Apache > sites-enabled?
-
@leokhoa what do you mean by checking my code?
and I don't have that path in laragon
I attached here 2 pics for the menu under appache and the other for the place where I changed .dev to .test before and didn't work for me.
If I change it in a wrong way or I need to change any other files to make the old websites with .dev work with the new .test, Please tell me
-
@waul : Oh man, you use a very old version of Laragon - nearly 2 years ago
You should consider to upgrade to Laragon 2.2.2 with is compitable with 1.0.8:
Download it here: https://laragon.org/download.html - Select the "Full + Apache" package.- First, stop Laragon, then copy
C:\laragontoC:\laragon-1.0 - Install Laragon 2.2.2 over
C:\laragon
I
- First, stop Laragon, then copy
-
@leokhoa I tried to upgrade before but it made problems as I am using windows7
If I failed to upgrade can I restore the old one from "laragon-1.0" folder?
and if there is any approach to do this "delete all the generated Virtual Host files in Menu > Apache > sites-enabled?" with this old version of laragon, can you tell me ?
-
Hola @waul, maybe i can help.
Let's give it a shot!
First, open C:\laragon\etc\apache2\sites-enabled (if your laragon installed at Local Disk C)
Second, open sites-enabled, and try delete except your .domain.conf and 00-default.conf.
Third, reload.
Fourth, open the browser.
Let's see what's the result.
-
@rizaldywirawan : He is using Laragon 1.0.8
@waul : Laragon 2.2.2 works well with Windows 7. If the upgrade fails, you can go back to Laragon 1.0.8 without any issue as Laragon is portable.
If you are afraid to upgrade, no problem as the http-vhosts.conf now contains no.devtext but.test
I guess 99.99% the issue is in your code. Try searching.devthe whole C:\laragon to figure out.
-
@leokhoa "I guess 99.99% the issue is in your code" what code do you mean? this situation occur for every site in my local host. Say that I have 50 sites in my local host in what site you want me to search for".dev" or you mean something in the database
Sorry, I can't get you in ths point
1094 points