I have installed magento-1.6.1.0 on my wamp local server. And I am getting this error after installation
Illegal scheme supplied, only alphanumeric characters are permitted
How to overcome this problem??
have your base url with full URI Schema : http://your.url or https://your.url and note that you cant use http://localhost as cookies wont work so name your host something else like local.host or whatever suits you best
There is a patch which seems to address this issue in Magento 1.6.1.0 for development purposes, at least to allow me to do some basic testing using a local installation. The patch and instructions are available from http://www.danneh.org/2011/11/bug-magento-1-6-1-0-affecting-development-sites-base_url/
I have tried this on a local installation I'm using for some experiments: both the patch and instructions worked first time on my Macbook (I stopped and restarted the web server after applying the patch and clearing the cache folder, then refreshed the start page in my web browser).
FWIW: I've also added another hostname because of the earlier answer to this question - the site loads correctly for both http://localhost/magento/ and http://myotherhostname/magento/
PS: I've made various changes to the default installation and I'm not planning to use it for production purposes.
I had the similar issue.In error report i was getting following.
a:5:{i:0;s:67:"Illegal scheme supplied, only alphanumeric characters are permitted";i:1;s:669:"#0 D:\wamp\www\mymagento\app\code\core\Mage\Core\Model\Store.php(726): Zend_Uri::factory('localhost/tevet...')
#1 D:\wamp\www\mymagento\app\code\core\Mage\Core\Controller\Varien\Front.php(313): Mage_Core_Model_Store->isCurrentlySecure()
#2 D:\wamp\www\mymagento\app\code\core\Mage\Core\Controller\Varien\Front.php(161): Mage_Core_Controller_Varien_Front->_checkBaseUrl(Object(Mage_Core_Controller_Request_Http))
#3 D:\wamp\www\mymagento\app\code\core\Mage\Core\Model\App.php(354): Mage_Core_Controller_Varien_Front->dispatch()
#4 D:\wamp\www\mymagento\app\Mage.php(683): Mage_Core_Model_App->run(Array)
#5 D:\wamp\www\mymagento\index.php(87): Mage::run('', 'store')
#6 {main}";s:3:"url";s:10:"/mymagento/";s:11:"script_name";s:19:"/mymagento/index.php";s:4:"skin";s:4:"demo";}
url which I had provided in core_config_data table in database was like following
web/unsecure/base_url localhost/mymagento/
web/secure/base_url localhost/mymagento/
When I changed the urls to following
web/unsecure/base_url http://localhost/mymagento/
web/secure/base_url http://localhost/mymagento/
problem got solved.
This is probably a bug in Magento 1.6.1.0, see here:
http://www.magentocommerce.com/bug-tracking/issue?issue=12530
with topic:
http://www.magentocommerce.com/boards/viewthread/263751/#t357355
I was receiving this error because I didn't have http:// in my base url
Have same problem on Wamp and XAMPP., nearly give up.
Finally find the solution, Magento 1.6 can not work properly with WAMP 2.1 and XMAPP 1.7, I guess it caused by Mysql version, not sure.
but after I change WAMP to 2.0 i, everything is fine. Magento 1.6 is running well.
Download WAMP2.0i : http://sourceforge.net/projects/wampserver/files/WampServer%202/WampServer%202.0/WampServer2.0i.exe/download
I failed to install it on Chrome, but success on firefox.
Good Luck.
Install Magento with Firefox, I also got the problem on IE. After installation with Forefox, it worked fine.
http://www.danneh.org/2011/11/bug-magento-1-6-1-0-affecting-development-sites-base_url/
This fixed my problem. MAMP and magento 1.9.0.
I downloaded the tar file, and delete all cookies in chrome, then delete all files under var/cache. Be sure you have more than 1 GB of space on your disk when you refresh the page and go to localhost/magento/
PS: in my core_config_data table, I have http://localhost/magento/ as my base_url (change 2 rows) don't use https, because I couldn't solve the problem (takes a lot of time) with SSL configuration on MAMP.
Related
after manually updating from Joomla 3.51 to Joomla 3.6 my website works without any problems, but when I try to reach my administraton zone i get anerror "An error has occurred. 0 The file Cache Storage is not supported on this platform. " anyone had this problem before?
Check that tmp and cache directories are writable by the server.
I had the same issue after update to Joomla 3.6
In configuration.php, replace $cache_handler with $cachelite.
This is actually a known issue, and I could've sworn I have answered this particular question myself. The Joomla developers state that this is should be the expected behavior when there is an issue with the cache adapter (most likely this issue is a permission issue on the cache folder or the administrator/folder - they are not writable by Apache).
We have discussed the issue at length here - and it has sparked a Twitter discussion on whether this is a feature or a bug. The Joomla development team insists it is a feature that was added for stability reasons (see their reply here) - despite the fact that the previous behavior did not cause the whole Joomla website to crash (the current behavior does).
The fix is typically simple and it almost always consists of making both the cache and the administrator/cache folder as writable by Apache.
The following setting should fix your issue.
(1) Go to your Files and find the configuration.php
(2) Open Configuration.php and locate public $cache_handler = 'file';
(3) change public $cache_handler = 'file'; to public $cachelite = 'file';
(4) Save the file.
i have a serious problem in Magento Admin Backend. After login its shows a BLANK Page. i used the same files and database in different server, there it was working fine but when i have transferred files into LIVE then Admin issues came. Please help me over this as i got frustrated from last some dayz. If you need any more dertails then plz ask but i need to resolve this soon. Link: http://studywings.com/index.php/admin/
Magento ver: 1.7
flush your magento root /var/cache folder and /var/session folders, It may have previous server session that may cause problems.
Otherwise disable all third party modules and try again. I think this will help
I had the Same problem,
i have also debug the any errors occured, i tried index.php file
ini_set('display_errors', 1);
error_reporting(E_ALL);
$_SERVER['MAGE_IS_DEVELOPER_MODE'] = true;
pleced above code in index.php file. after that i have tried admin login.
showing the errors are session related, header already send errors.
i have to add the code in root/index.php file in top add the following line.
ob_start();
after that tried the login its worked.
Cheers..!
Is url changes to this after click login button or not?
http://yourdomain.com/index.php/admin/index/index/key/(key value)/
if url changes but not not show the dashboard page then go to
app/code/core/Mage/Core/Model/Session/Abstract/Varien.php
make copy of this file
Find the code for setting session cookie parameters these started on line 77
Comment out the final three lines and be sure to remove the comma after $this->getCookie()->getPath(). You should end up with this:
// set session cookie params
session_set_cookie_params(
$this->getCookie()->getLifetime(),
$this->getCookie()->getPath()
// $this->getCookie()->getDomain(),
// $this->getCookie()->isSecure(),
// $this->getCookie()->getHttponly()
also line 104 comment out :
//call_user_func_array('session_set_cookie_params', $cookieParams);
If there is no change in url after click login then try to uncomment display error and see error_log file of your server
I think this problem is due to file permissions. As you added files from one server to another, permissions might be get changed.. Try to give the permissions to all the files. Check this http://www.mage-shop.com/forum/threads/3-Magento-Admin-Backend-Blank-Page-Error
There are a number of things that can cause it, but it's most common after migrating to a new server, last time it happened to me it was an excessively low php memory_limit setting on the new server - the Admin part of the site uses a lot more resources per user than the frontend.
In general when having this issue:
Flush out your cache by emptying var/cache
Clear out sessions by emptying var/sessions
Check the magento error logs/reports for an error code in var\logs and var/reports
Turn on magento error logs in mysql if logging isn't already on! (look in core_config_data for WHERE path like 'dev/log/active'
Check if your php configuration is displaying errors
Check your apache/php error logs for more clues - memory errors will show up here for example
Try this solution
It sounds like you want to enable Developer mode. Add this to your .htaccess file:
SetEnv MAGE_IS_DEVELOPER_MODE "true"
You may also want to enable display errors in index.php:
ini_set('display_errors', 1);
The best way I have found to debug is with X-Debug in a local environment. You can also use log files to help debug in a production environment, if your unable to run X-Debug in the environment.
I've got a more detailed posting here:
http://www.molotovbliss.com/debugging-tips-and-tricks-with-magento-commerce
Consider also installing XDebug
Hope this helps you!
Just to complete the other answers....
I am upgrading a magento install, and got the same problem, in the end I had another folder inside of var/
magento/var/minifycache
Only worked after clear deleting the files inside of this folder.
I had the same problem after uninstalling an extension. I thought that clearing cache would be enough, and I did without success... later speaking with the technical team, they commented me that it did not work because I hace memcache installed, and needed to be done the cleaning via system - backend (that i coudl not see...)
I just move my Magento store to my localhost environment for testing use, I also using Git to maintain code, but after I move all the files to my local environment, I can't login my admin page, but I can still see my frontend pages, and the git, the database, seems works well.
When I type a wrong admin/password to my admin page, it still gives me "Invalid password".
But when I enter the right one, it just refresh the page and stay at the login page, nothing happens.
Does anyone has met this problem before? Has any ideas?
Thanks in advance!
Although this question is old, all the above answers did not work for me until I did one additional thing.
Follow the very helpful answers already posted (summary):
Change your base_url to http://127.0.0.1/ for secure and unsecure path.
delete files in var/session and var/cache
alter your Varien.php file accordingly - depending on your version of Magento.
And then:
Finally, use http://127.0.0.1/your/site/folder/name/index.php/admin
It was the lack of the index.php/admin ( instead of using http://127.0.0.1/site/admin ).
I hope this helps someone else.
Recently started using Magento for a project and came across this issue. I was left frustrated by the fact there are at least ten or more different workarounds suggested on the net and it took a bunch of trial and error to find one that did the job. Seemingly some workarounds work for some versions and not for others. No one explained why or how the problem occurs and the most popular solutions involve hacking the code base or using a different url, which shouldn't be necessary.
The cleanest solution I found for Community Edition 1.9.1.1 was editing two config values in the database:
update core_config_data set value = NULL where path = "web/cookie/cookie_path";
update core_config_data set value = 0 where path = "web/cookie/cookie_httponly";
The cookie path is actually NULL by default on a fresh installation but it must either be NULL or empty string.
The behavior arises because some browsers including Chrome have issues creating cookies with a localhost domain, this means that when Magento calls session_start() the session identifier cookie never gets created and as a result information can not be passed from page to page. The login procedure is actually successful but the next request doesn't know about it, hence why you get redirected back to the login screen. There are no errors because Magento doesn't account for this edge case as a possibility.
If you do not provide a domain value when creating a cookie on localhost then the browser has no problem with it. Unfortunately just setting web/cookie/cookie_path to NULL is insufficient, because Magento's configuration class resolves this as an empty string which is enough for a real domain to be set later in the code:
if (isset($cookieParams['domain'])) {
$cookieParams['domain'] = $cookie->getDomain();
}
This method eventually uses the current HTTP host to resolve a real domain for the cookie, and the browser therefore wants nothing to do with it. However if we disable web/cookie/cookie_httponly then Magento will not perform this additional step, $cookieParams['domain'] is unset and no domain gets passed as a session parameter, thus allowing the session cookie to be created and things to function as they should.
Note that any time you modify the database configuration you must delete the contents of /var/cache/ for the changes to be reflected.
If like me you don't want to have to comment out code, or even make configuration changes, then I created an extension which overrides the getDomain() method shown above and returns null if we are on localhost, this should be somewhat more future proof and result in no collateral damage.
http://www.mediafire.com/download/q39p4k95s5tlght/LocalCookie.zip
Try deleting the contents of the cache folder /var/cache. Clear your browser cookies and try. Also, if you have copied down the database from your server, you may need to manually change the base urls (secure and non secure) as well as the cookie domain in the core_config_data table. Do this manually if you need to. e.g. web/unsecure/base_url with production value of http://www.mywebsite.com/ becomes "http://localhost/"
When ever I have had this it's because of this or cache. Ensure the cache folder is ignored in git hub if it's not already.
1.you need remove the cache
rm -rf var/cache/* var/session/*
2.change the domain form core_config_data
update core_config_data set value="http://127.0.0.1/" where path="web/unsecure/base_url";
update core_config_data set value="http://127.0.0.1/" where path="web/secure/base_url";
do these steps :
1: go through: xampp\htdocs\magento\app\code\core\Mage\Core\Model\Session\Abstract**
2: open **Varien.php file
3: make comment line number from 87 to 104 save it and try to login...
Had the same issue, but the fix was changing DB values:
UPDATE `core_config_data` SET `value` = 'http://127.0.0.1/example/' WHERE `path` = 'web/unsecure/base_url';
UPDATE `core_config_data` SET `value` = 'http://127.0.0.1/example/' WHERE `path` = 'web/secure/base_url';
Then in browser http://127.0.0.1/example/admin
Same problem! I fix my problem after remove/replace static domain in core_config_data Table
web/secure/base_url
web/secure/base_link_url
web/secure/base_skin_url
web/secure/base_media_url
For me, running it on IIS (I know, not officially supported):
Although other suggestions kind of worked I found the best solution was to enter a new A record for me domain like
127.0.0.1 local.example.com
Then in IIS add the binding
local.example.com
to my site and it worked perfectly.
I found there were errors when actually trying to login to the customer account more than admin but believe it still applies.
In my store have magento community edition - 7.1.
I try to install extension using magento store, but I got an error like this for all type of extensions
community/Dropifi_Dropificontactwidget: Could not resolve host: connect20.magentocommerce.com; Host not found
I placed this key for install magento
http://connect20.magentocommerce.com/community/Dropifi_Dropificontactwidget
http://connect20.magento-commerce.com/community/Dropifi_Dropificontactwidget
Help me to get a result for this issue.
Thanks
I had the same problem ("CONNECT ERROR: Unsupported resource type") while upgrading a 1.6 magento on PHP 5.5.
The unpack function (http://php.net/manual/en/function.unpack.php) has changed.
In downloader/lib/Mage/Archive/Tar.php, the line
const FORMAT_PARSE_HEADER = 'a100name/a8mode/a8uid/a8gid/a12size/a12mtime/a8checksum/a1type/a100symlink/a6magic/a2version/a32uname/a32gname/a8devmajor/a8devminor/a155prefix/a12closer';
must be replaced by:
const FORMAT_PARSE_HEADER = 'Z100name/Z8mode/Z8uid/Z8gid/Z12size/Z12mtime/Z8checksum/Z1type/Z100symlink/Z6magic/Z2version/Z32uname/Z32gname/Z8devmajor/Z8devminor/Z155prefix/Z12closer';
This was not an issue specific to you. Today, the Magento Connect server experienced an outage which prevented any of the community extension keys from working.
The Connect server appears to be online now, so try again and it should work.
Source: https://twitter.com/magento/status/384805097315659776
Helpful Note:
You can download extension packages directly by using the following tool:
http://freegento.com/ddl-magento-extension.php
Just paste in your Magento extension keys and Submit. A downloadable link will appear for you to obtain the package.
i have got this error then try following steps
first you can disable all cache
second after install extension then clear all cache and logout and login
My Magento web site home page has a redirect loop error. When I try to open it it goes to my old server url and gives the error:
The webpage resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.
When I try to go into admin it takes to me old server admin url without any error.
I down loaded the fresh data base and connected my store to that it works fine but when i connect it my old data base it give same error.
Please advise me.
This isn't an ideal solution, but I was having issues with Magento 1.9.x.
The setup was: Nginx Proxy & SSL Terminator => Apache Webserver
No matter what I did enabling SSL caused a redirection loop. I narrowed the issue down to Magento rather than the Nginx configurations.
It was like Magento didn't know it was receiving a secure connection from Nginx even though the correct headers were set.
The dirty solution was to add some code to the very bottom of index.php within the magento root directory (ie. /var/www/magento) just before the Mage::run... line, like so:
if( isset($_SERVER['HTTP_X_FORWARDED_PROTO']) ) {
$_SERVER['HTTPS'] = 'on';
$_SERVER['SERVER_PORT'] = 443;
}
Mage::run($mageRunCode, $mageRunType);
Wrong permissions can also cause this to happen. So in addition to truncating the var/cache and var/session folders, go ahead and make sure that you have the proper permissions on the app, skin, and includes directories, sub-directories and files. I believe the suggested permission setting is 644. You can do this with a proper FTP client such as FireZilla.
Go to table core_config_data
Update these value to be your localhost url(or whatever url you are providing while installation):
web/secure/base_url //(new url)
web/unsecure/base_url // (new url)
Empty the var folder.
I got it fixed.
I manually deleted my cache i was unable to login in my amdin and it get fixed
My issue was Cloudflare, put it in Development mode and it worked. It was cache related.
Issue: ERR_TOO_MANY_REDIRECTS - redirected you too many times
This issue is related cookie domain name.
For ex: if you already installed Magento 2 in www.example.com, and now you change magento base path to sub domain path like www.subdomain.example.com means, then you need to update your cookie domain entry inside of core_config_data table. You cannot access magento 2 backend so you can use following query to check record exist else use insert query.
SELECT * FROM `core_config_data` WHERE `path` REGEXP 'cookie_domain'
if record exit then update subdomain.example.com to the value column.
else
INSERT INTO `core_config_data` (`scope`, `scope_id`, `path`, `value`) VALUES ('default', 0, 'web/cookie/cookie_domain', 'subdomain.example.com');
Then flush cache using command php bin/magento cache:flush
Refresh magento 2 admin, now you can access admin. try this. thanks.
Note: if you are not using cookie domain, then don't configure this settings, if you configuration wrong then also you can face this error, so to fix that error update value to default configuration.
I had the same issue and after reloading and reloading my page I noticed that the error message responded to www.mydomain.tld and sometimes to mydomain.tld. I'm using Plesk on the server and I remembered that I set the Domain to always be called without www. I just changed that to none in the hosting settings of the domain. Lucky me, that solved that issue. Hope that helps someone else.