Just thought I’d share my experience with installation of OXID_ESHOP_CE_4 on a WinXP machine (for local development only). If there is documentation that could have assisted me, please point me towards it. I searched the oxid-esales.com forums, wikis, manuals and then the web in general for help on the issues I came across, but without much luck.
Following online manual, installed OXID using setup pages provided in downloaded ZIP package. My WinXP machine is running Apache 2.2.16 and PHP 5.3.3. However, I could not pass the requirements page, always failing on just the “file/folder access” requirement. The provided note suggests that the requirement will fail if some chmod tests don’t pass. After checking that all files on the local server space have the correct access requirements, I assume this is the issue since WinXP doesn’t support chmod. To work around this, I hack the appropriate php file in the setup folder to force a ‘true’ condition to all requirements then re-run setup. This gets me past the requirements page but then a later install step fails trying to edit .htaccess. Apparently setup can’t write to this file even though it is writable on my file system. I notice it is ‘hidden’, and figure maybe this is messing something up (given incompatibility between WinXP and Unix file permission values). I remove ‘hidden’ from .htaccess and re-run setup, this time without issues. Am I the only person running into this or is OXID not intended to run an WinXP (home edition)?
After evaluating the shop, I decided to move it into the workspace of my webpage, which would require a change in location, both physically and a different URL. Couldn’t find any info on how to move the store location, nor any info on a manual install, so I simply changed the appropriate paths in .htaccess and config.inc.php. This, however, did not work, which the changes resulting in the php code failing and hence no shop displaying in the browser at the new location. Stepping through the code, line-by-line, I discovered (many hours later…) that OXID was caching file paths in the tmp folder under a oxpec_class_file_paths.php file, and this file still had all the old locations. Deleting this file got the shop running again. Maybe this should be a lesson moving forward? That is, always delete tmp files when porting software to new locations?
Well, this has proven to be much more effort than evaluating and moving around osCommerce, but, so far, looks worth it.
Again, if there is any documentation on the site that could have helped me, please point me towards it. Maybe it will still help moving forward.
#1: I think the real point was the hidden .htaccess file. No idea why it was actually marked as hidden as usually, Windows doesn’t interpret the dot-prefix, does it? All other files shall be treated like 0777 in a unix system. Take care simply moving your system to a productive nux web environment. Maybe Windows destroyed all file permissions!
#2: Yes, Smarty uses the /tmp/ folder for caching the output files. Every time you make a change during development, you ought to clear this folder. There’s a nice little module that might be helpful: http://www.oxid-esales.com/en/exchange/extensions/delete-tmp
Somebody should have told you before
By the way, did you find the manual and the tutorials? In case you are missing something: I will open up a new section on OXID forge where we can collect missing tutorials very soon. You’re welcome to help with writing if you feel fancy.
There is another maybe interesting thing for you: A prepared VMware appliance on a Linux basis with a pre-installed OXID eShop and all needed system requirements. It is highly recommended as in most cases, it will be very closed to your web server environment.
Ok. Thank you. I will check out the delete-tmp module as I’m finding myself deleting that folder quite often during developement. And, yes, windows does ruin all the file permission when uploading to a unix environment (prevented me from running the setup pages), but I was able to reset all these w/o too much trouble and proceed with setup as usual.
I have found the manuals and tutorials and, although useful, find much of the manual information doesn’t go into the details I’m after. I’m still in the process of exploring the tutorials, particularly the ones on module extensions. Most useful, I’ve finally stumbled upon the API documentation (http://docu.oxid-esales.com/CE/sourcecodedocumentation/), which seems to answer many of the questions I would have had.
Yes, I saw the VMWare download. I will explore this when I get around to updating my Linux box
Overall, quite impressed with the organization and structure of OXID.
Keine Ahnung was da schiefgeht, ich würde alles löschen (DB/Dateien), das zip nochmal entzippen, Browser neu aufmachen und nochmal starten. DB wird vom Setup angelegt und muss nicht vorher erstellt werden. Das Erstellen der Demodaten braucht normalerweise wenig Zeit, daran kann es m.E. nicht liegen.
[QUOTE=spurvis;42636]Just thought I’d share my experience with installation of OXID_ESHOP_CE_4 on a WinXP machine (for local development only).[/QUOTE]
Why bother to use WINXP after all?
It’s aboslute nonsense to waste your (and our) time with that!
Yes, if I had that option, I would not use WinXP. In fact, I would not use a Windows O/S at all. But sometimes, you’re stuck with what you’ve got. The post was intended to be informative to others who may find themselves in the same situation. One may be surprised to know how many people still use WinXP, especially in the business world. Most companies are much slower at upgrading than the average home user.
