This is my first attempt at using Magento to develop a site. I have to admit the learning curve has been steep, but i have been able to navigate most of the challenges thus far. Here at the final hurdle, however, i have stumbled.
I am using Magento 126.96.36.199 on this server:
Apache version 2.2.22
PHP version 5.3.10
MySQL version 5.1.65-cll
Magento is located in a folder named magento one directory down, eg. http://www.mydomain.co.za/magento
Problem: No images are displayed on the page AND i cannot access the backend. It looks like the paths to the stylesheets are wrong when viewing the source, but that doesn’t exaplin not being able to access the backend. EDIT*** I just found something interesting. When trying to access the backend i type domain.co.za/magento/index.php/admin but on the 404 it says magentoindex.php/admin/dashboard, which suggestes that there is definitely something wrong with the paths. This has given me a glimmer of hope! I have been able to access the backend by manually adding the missing ‘/’. There is also no styling in there, just plain HTML.
Attempts to solve:
Changed the url’s in database (http://stackoverflow.com/questions/1762090/how-do-i-transfer-a-local-magento-install-onto-my-live-server)
Changed app/etc/local.xml to use correct database
Changed .htaccess to include this line: RewriteBase /magento/ (but i removed it again)
Deleted the appropriate cahce folder
Tried the suggestion given here (http://www.kudoswebsolutions.com/web-design-blog/magento-deployment-tips)
Now, i am stuck. I have worked my way through error upon error (no fault of Magento, just the learning curve) and i am tired… :-( If someone can please give me some advice as to what to try next, it would be greatly appreciated!
** EDIT: I found this http://www.magentocommerce.com/boards/viewthread/234373/ that is exactly the problem i am having. The one difference being that i did have magento in a folder on the dev system and it is in a dev fodler right now. Clearly there is something happening here. The other thread never solved the issued, just found a work around. Is it possible that we have run into a bug? Something is stripping that slash out and it isn’t any of the usual suspects… *dum dum dum*