Can anybody help with this , I have cloned a production site to my local server for development and testing which seems to be working ok. I have created some new app/skin packages and applied and tested them.
But the checkout links are not working either from the cart or top-links or the mini sidebar cart , also the login link does not work.
The url's are
https://127.0.0.1/silkyliving/index.php/checkout/onepage/
https://127.0.0.1/silkyliving/index.php/customer/account/login/
I get "This webpage is not available
The connection to 127.0.0.1 was interrupted".message.
I've installed the default package and other packages to see if the fault lies in my package but it does it in any package.
So i think the fault is in the overal configuration/install.
I have also tested my local server with another install and that works ok so is not a server error.
To be honest i never checked the checkout functions when i cloned the production site so not sure where the fault is, the production site is working ok ?
Does anybody have any ideas ?
Thanks
Ledgemonkey
I have discovered the problem it was in >configuration >web - Use Secure URLs in Frontend was set to "yes" changed it to "no" and seems to be working ok now ? thanks
goto Magento root index.php
ini_set("memory_limit","512M");
// echo ini_get("memory_limit"); //for test
then all are solved.
Related
I'm a student working on a project to benefit other students, and I am currently facing a problem with reloading with any other url than the main path.
The webpage is written from scratch (more or less) in React with no backend, but I still hoped that it would work. I am using react-router to change sub-directories.
I have understood that there is a difference between server- and client-url's, and that this issue most likely is related to that. In the app's main directory "webpage.com" everything works fine untill the page is refreshed. If a sub-directory such as "webpage.com/link" is "called" directly, I recieve an error. You can go and try for yourself btw.
Does anyone know of a nice way to fix this? Do I need to implement something like Node.js to fix this? If so, how? I would prefer not to use a hot-fix such as redirecting all sub-directory calls (such as "/link" (an actual page) or "/kejrngo" (jibberish) ) to "/".
I've cloned your project locally and it seems you have a problem with the server. As you said yourself it seems that only open url for your page is http://ifistudenter.no where at the beginning all application is rendered. After you try to refresh the page you are looking for a path that isn't available on the server and that is the reason you get 404.
What seems to be a problem is React Router itself with Apache server:
Please look at this: https://www.malikbrowne.com/blog/using-react-router-with-apache hope it helps
I've been working on a web page for a while on Centos 6.3 server
Everything was fine, the page was accessible etc.
I was screwing around trying to get pchart working, i didnt do much with it except for adding a new folder in my /var/www/html; I also tried installing GD, dont think it worked.
Now everytime I go to my web-page url i get the apache test page.
It is now giving me You dont have permissions to access / on this server
Help please
/var/www directory is owned by the user "apache" and the group "apache", my case that had changed for some reason
I've just transferred a modx site for a client over to fasthosts - got the site setup working fine but when logging into the backend I'm getting Incorrect Username / Password.
I know that the credentials are correct.
Any ideas?
Using 1.0.4
I've heard of similar issues before when people migrate a site to a shared host. Does this solution help?
I've fixed it!
It seems to create all site content including paths and sessions within files on server... So obviously I'd ftp from old host to new host, put live expected to work which front end did because it doesn't use session data but then the backend had it's knickers in a twist
I setup a new installation with a db prefix test_ - once site was installed changed db parameters then cleared site cache, uploaded new template files etc.
Cheers
Shane
I have installed gitorious on my local server and when I try to run it
in my browser, I don't see the homepage. Instead I see this page.
http://gitorious.googlegroups.com/web/Screenshot.png?gsc=gBX1HyMAAADO...
Help?
RTM: http://gitorious.org/gitorious/pages/UbuntuInstallation
You need to create admin user etc. Configure it and it will work fine.
Basically i developed my app on a localhost wamp server with PHP 5. ON uploading to the actual host i notice that
The server is running php 4.4.9
Everytime i upload my .htaccess file, the server removes it completely.. seems to not be allowed
When i test out the set all i get is a 404 page not found
Any help on how to make it work on this PHP 4 server?
I did a test with CI 1.7.2, default installation.. works on my local server but when uploaded does not work, does this mean that the server does not support it?
I'm sure this isn't what you want to here, but get a new server. Here are the reasons why:
PHP 4 is no longer well supported. It's insecure.
If the server is removing .htaccess files, they are also unsupported on that server, giving you one more reason to move.
Code Igniter runs best with PHP 5 and with an .htaccess file.
The gist of this is you are going to have to hack your code back into the dark ages to get this to work, and then you will still have pretty URL issues and overall system instability. If you can make the switch, do.
If you cannot use .htaccess files with CodeIgniter, in system/application/config/config.php there is a configuration key called index_page. You need to set that to whatever page you have bootstrapping CodeIgniter (usually /index.php)
Then, make sure all your links that get routed through CI either target index.php/controller/action/params... or utilize the URL helper (with site_url or anchor) to automatically put in the index.php
Joe Mills is exactly right in his answer, though. CI works best with PHP 5 and .htaccess.
See CI URLs and CI URL Helper for documentation.
Well i found out how to fix several things
The issue with .htaccess would be to just not use modrewrite as such i put "query_string" option in my path variavable and this works.
The other issue, which was the major issue was that i was using Datamapper library which is a php 5 only library.