I just installed Apache 2.2.x in my windows 7 x64. everything seemed okey and I am getting the "It works!" page. However when I tried to edit the index.html in htdocs and I display localhost again it just says "It works!" it didnt show the modifications that I did on the file. Is this an indication of something wrong with my installation?
I believe to change the index.html in win7x64 , you need to run your editor as an administrator , as it is located in program files folder , and to change anything in program files folder or any folder under it you need to run the editor as admin
Double check that your browser isn't caching the default page. After you make a change to your index.html, clear your browser cache and try again.
If that still doesn't work, ensure you're not editing the wrong index.html file; the default site may be pointing to a different location than the one you're editing. (I'd guess the issue is the browser cache, however...)
Ctrl-F5 the page for hard refresh.
If same page is there:
A) you're editing the wrong index.html/php file.
B) you're making edits that don't change the output.
If you can't get it to work, I suggest you install a full WAMP package.
Related
I followed this tutorial http://www.appseconnect.com/how-to-install-magento-2-on-xampp-server-localhost/ to install Magento 2 on XAMPP (Windows).
But, after install magento, I open the project and admin on browser and when I see the firebug console there countless errors when trying to access js, css and fonts of the folder pub/static:
I tried this solution (and a few others I found on google) but not resolved.
Set the Magento 2 mode to 'Developer mode.
Clear everything on pub/static folder except .htaccess file.
Also clear all cache (var/cache/* , var/page_cache/* ,
var/generation/*)
Check folder permission of 'pub/static' folder.
Refresh the page on browser.
In 'Developer mode' required files will automatically create on
public/static folder if the folder have permission to create files.
I am having the most frustrating issue with VQmod. I moved my OpenCart store from a Godaddy VPS to Rackspace's Cloud Sites. The move went fine and everything works properly except the VQmod's on the admin panel. None of them load. No errors in the log files, no admin cache files in the cache dir, no php errors.
Things I have tried:
Cleared all cache Changed admin folder to 755
reinstalled VQmod tried both manually and using the installer with fresh index.php files
Removed all XML files and tried to load only one at a time
Cursed loudly at my computer repeatedly.
Please Help! OC version 1.5.6 VQmod 2.5.1
For those that want the solution to this, the issue was that the config.php files were both using relative paths instead of the full paths for OpenCart's various directories. They should always be full paths, or resolved with realpath() in the config.php files themselves
My case was a bit different. I checked the permissions, paths, all the regular stuff that comes to mind first. I even walked step by step through the manual installation guide.
The Opencart copy in question is shared across several environments using git. Long story short, the mods.cache and checked.cache were not added to .gitignore right away, and when I finally did that, I emptied both of them just to make sure Opencart will write new content based on my current environment. Turns out, since mods.cache was empty, Opencart believed there are no mods available.
Solution: delete both vqmod/mods.cache and vqmod/checked.cache.
Update: here are some similar issues:
https://github.com/vqmod/vqmod/issues/32
https://github.com/vqmod/vqmod/issues/3
The vqmod/vqmod/wiki/Troubleshooting guide, as of now, does not make it obvious the files should've been deleted, neither does the vqmod/vqmod/wiki/Installing-vQmod-on-OpenCart, and there doesn't seem to be any way to contirbute. vQmod fails silently, without producing any notifications, warnings, or simply detecting the issue and rebuilding the cache files. I've spent few hours trying to figure out what's wrong.
I got a copy of my project from work, and put it into the www folder of Wamp, in a different PC. However, when loading localhost, I am not able to see the folder in the list.
I attempted to create a few new folders, and they display correctly in localhost. Even if I rename this folder to something else, it still refuses to show up.
This is what my www directory looks like :
And this is what localhost shows me:
Update :
If I copy the files inside mainProject and paste them into either test1 or test2, that folder disappears from localhost as well.
Update 2:
Deleting/Removing the .htaccess file from mainProject makes the folder visible in localhost, but when I try to access it, it gives me file not found error for obvious reasons! Can add snippets from the .htaccess file if needed!
You should not put anything into the \wamp\www folder, this is where the WAMPServer homepage lives in a file called index.php
So it looks from you first sentence that you have overwritten this file with one of your own projects files.
The simple solution is to install WAMPServer onto another PC and restore the \wamp\www folder from there. Alternatively uninstall WAMPServer, delete the \wamp folder and all subfolders, re-install WampServer and then copy your project into a sub folder of the \wamp\www folder. The wamp homepage is not actually required, but it can make life easier.
Also check the wampserver.com/forum/en there is a document there called 'WAMPServer 2.5 The Homepage, Your Projects Menu and the need for Virtual Hosts ' describing how to setup Virtual Hosts which also provides a more buttet proof environment to run a project in.
ADDITIONAL INFO:
Ok now you have undone the damage you did, you now need to learn how to create a Virtual Hosts for each of the projects you want to run/develop.
You can undo the changes you made to Document Root, Directory and Virtual Host in the httpd.conf file, these can all be individually set from within a Virtual host definition.
See this post on the WampServer forum site
So, I'm running an apache server on linux. Sometimes, Firefox decides to not load the new version of a file after I edited it. For example, right now I have a .js file wich is loaded dynamicly. It had a bug, wich I corrected (I checked with Chromium), but when the file is loaded in Firefox, it still has the bug! When looking at the response header of the ajax request, I see the code of the file BEFORE it was changed. But that code doesn't exist anymore... I had this happen with CSS files too.
When I rename the file to something else, it loads the right stuff, but as soon as I rename it to the old name, it starts loading an old version of the file again!
I restarted apache2, but that didn't change anything.
I checked for file permissions too, no problem there as far as I could tell (I changed all files' permissions to rwxrwxrwx to be sure).
When accessing with an other browser, it works fine!
In previous cases, the next day or so, the problem would have vanished, but I can't always just stop for a day in what I'm doing...
This is caused by browser cache,
you can consider to use url with version parameter,
like http://yourdomain.com/js/some.js?v=$version,
and update the $version whenever you update a css/js
I had to reformat and reinstall XP a while ago which works just dandy.
My issue is that I never re-installed xampp until today (newest version). Going to "localhost/project" works fine. I can see the site but css and images aren't working. Localhost is reading my "/" path references inside the project folders as root "htdocs".
For those who will mention it: I removed the "/" in my php files and the links and reference to styles worked fine, but within the css files, any "../" reference failed.
I think there was a reason for the preceeding "/", but I have since forgotten.
Any have any ideas? None on my searches turn up anything useful.
did you copy your old xampp installation into the same path on your new XP? if not, you have to change the httpd.conf perhaps as apache uses some variables in there to calculate relative paths.
you could also try to use opera dragonfly or another debugger to see errors in your browser