Magento Connect is not working after migration - magento

I have a problem with Magento after move it from local to live server: Magento connect is not working properly. I will explain it:
I have access to Magento connect, but the extensions are not working.
I have tried to delete the pear.ini file but didn't work. I have tried to delete the app/etc/local.xml file, copying the following files from a clean installation: clear, pear, peardev and pecl, and then running the installation process again, but nothing happened.
Is there a way to get my downloaded extensions working wihtout do a clean install?
Greets to all and I aplogize for my English.

Moving a Magento installation can be difficult. Here is the procedure that I have used many times with great success.

Make sure that your /download folder and the /pear folder are owner and group writeable and that the apache or other http user have write access via the group permissions.

Check the file permissions match the webserver's user and delete downloader/pearlib/pear.ini. When you hit the page, it will regenerate the file with the correct paths.

In order to get the extensions working I needed to copy all files manually. I don't know why, but I have tried everything and it was the only solution that worked for me.

Related

Joomla installation permission errors

So I have been given the task of upgrading one of our companies' old websites that is based on 1.5 to something newer (because a second site of ours on the same version just got hacked).
I know some php and some other web stuff, but I'd never used Joomla.
I have setup a lamp server on a local VM (ubuntu) for me to test it all out on, then upload the upgraded version as is suggested. My problem now is that I know the permissions are not correct because when I tried installing Akeeba Backup, it kept throwing errors such as "could not copy to /var/www/components and /var/www/administrator etc. I went in and chmod'd those 2 (and then the rest of www because of more errors) to 757 (from 755 for the most part) - which i know at that point might as well be 777. Then when I've tried to use Kickstart to restore from the JPA file I have, it just right away throws an error "could not create j_backup/ folder".
I know this slackening of all permissions on the root folder is wrong, but it was the only way to get it to 'work', which it's not even now, so my question is what did I do wrong in the setup and how do i fix it? I'm not great with Linux, but I'm thinking I have to make PHP owner of www? is that right? or terrible practice?
The other issue I see now is that I just installed the latest php and everything and I see Akeepa says not to use php 5.4... not sure how much of a problem that's going to be....
Some direction would be great because I'm more than a little lost.
Thanks!
This is certainly a headache. Most often, as you stated, the issue is the ownership of the files on your server. Files uploaded via FTP will be owned by your FTP user and may not be editable by the Apache/PHP user. Similarly, files created by installing extensions in Joomla! will be owned by the Apache/PHP user and your FTP user will not be able to modify them. Here is an article discussing the problem with a couple of possible solutions:
http://docs.joomla.org/Why_can%27t_you_install_any_extensions%3F#File_ownership_advice_from_ianmac
In the past, I have used an Apache Module called suPHP (http://www.suphp.org/Home.html) to solve this problem and keep it from reoccurring. suPHP executes PHP scripts with the permissions of their owners.
As for file permissions other than ownership, please refer to the Joomla! documentation for the correct settings: http://docs.joomla.org/Verifying_permissions. One quick way to handle this (if you can install extensions after correcting the ownership issue) is to use the AdminTools extension (http://extensions.joomla.org/extensions/access-a-security/site-security/site-protection/14087). One of its tools ‘fixes’ the file permissions on your server by resetting them to the Joomla! default.
Good luck!

Joomla administrator redirects to public site

I have a Joomla site running on a windows machine. The site was at 1.6 when some update requests came in. I decided to update the site, but the automated process didn't work, so I started FTPing the files up there manually.
I followed the instructions for the manual upgrade at http://docs.joomla.org/Upgrading_1.6.5_to_1.7 once I got the site to 1.6.5, but my problems had already started before that.
Now when I go to mysite.com/administrator most images are not there and when I try to log in I get kicked up to my site root rather than the /administrator folder. I took the opportunity to look at the code and none of the image src attributes or the form action attributes include "/administrator".
Soooo I need a little advice as to why this is happening. I would rather not have to restore from my backup and start over at 1.6. I was kinda hoping for this to be my first Joomla 3 site. Thanks in advance.
You said that you had trouble with updating Joomla via the admin panel, however did you check if the folders were writable? Site -> System Information -> Directory Permissions Always check this page once you have installed Joomla as it is the reason why a lot of people are unable to install updates or normal extensions.
You then mentioned that you had to upload the files manually via the FTP, however this is not requires. All that is required it to upload the update.zip to the foot of your Joomla site and unzip it.
As for a proper answer, May I suggest that you first update to the Latest version of the 1.6 series (1.6.6), then you download a fresh copy of Joomla 1.6.6, unzip the "administrator" folder, zip that folder, upload via the FTP to your Joomla root folder, then extract it. This will override all the default administrator files.
In the end I had this client move their Joomla install off Windows and onto a Linux machine. Things were just getting worse with the install and I threw in the towel. Thanks to Lodder for trying to help.
This can happen if you are using the JSecure plugin. It requires a token in the URL to enter the admin panel, for example:
http://www.yoursite.com/administrator?token
Explanation:
http://forum.joomla.org/viewtopic.php?p=2198164
I was able to fix this by removing the value that I had in the $live_site variable in the configuration.php file. I am also running this on a Windows server.

Joomla blank after changing server, admin panel good

I did a cPanel move of a Joomla 1.5 website and a PHPBB3 forum from one server to another, and when the DNS changes kicked in all I see is a blank page. The administrator panel works without any problems whatsoever. cPanel works. Website and forum (which is separate from the website) are both blank.
I have then manually downloaded and then uploaded all files (didn't move the databases manually), and some files wouldn't upload because of 555 file permissions. I changed the permissions to 777 temporarily to overwrite the file with the manually uploaded one. So all files are now the same as they were on the old server.
Even when I turn the Site Debugging on, the screen is blank.
There is no hidden index.html or default.html file which could be causing the problem.
The entire account was moved with cPanel so it's the same on the old server and the new server. The hosting provider reports no problems. The DNS changes kicked in two days ago.
PHP is working, as this link works: http://oklade.net/findpath.php
In configuration.php, there is nothing specifically pointing to the old site.
var $dbtype = 'WeboMySql';
var $host = 'localhost';
All roads in these cases generally lead to configuration.php Check spelling and punctuation for mistakes. Also, enable one of the default Joomla Templates to be sure that whatever template you're using isn't also using old values.
Problem is solved.
The configuration.php file was to blame, as everyone suggested, but there was no possible way to change it manually and get it right, I had to make the system determine its own configuration.
I installed a fresh version of Joomla in a separate folder, and a fresh version of PHPBB3 in a separate folder.
Then I took the configuration.php and config.php files for those two things and put them in the existing folders of the website which didn't work.
Changed the minor details such as database prefixes (as I couldn't have entered the existing ones while installing), and that's it. Now it works.
So this might be a good workaround for anyone facing the same problem. Install a dummy version of Joomla and use the generated configuration.php file for the old, non-functioning website.
Before starting to debug the server, turn debug-mode on (in the admin CP)
First thing I would try is to delete the cache by running: rm –rf /var/www/html/<your website directory>/var/cache/*
The next thing I would try is to switch to another template - make sure that the template is not the issue.
Also, make sure to check the apache access log - just in case. also, you can check .htaccess for stuff like 301 redirect rules or any other problematic configuration (same applies for httpd.conf and configuration.php)
Good luck!

magento var folder

A while back I was deleting Magento's cache in the var folder. I may be wrong but I think I made a mistake and instead of deleting everything in var/cache deleted everything in var accidentally. Magento seems to be running fine though. Have I got problems that I cant see, can anyone tell me?
Magento 1.6.
It should be fine, the files in there are supposed to be temporary. Just make sure that you recreate the .htaccess file that was in there as it blocks the public from being able to see your log files if you have logging enabled. The .htaccess file just contains these lines:
Order deny,allow
Deny from all
As long as the permissions are properly set on var/ , Magento will recreate the needed subfolders. You may need to create the import and export folders, watch for any other folders that may have been created by third party module installs, they should be recreated if the module programmer did their homework.
I've had situations where I actually had to delete all the folders in var/ so the web server could recreate them with the proper ownership (running as nobody).
In the future in case you're interested in emptying your cache:
Simply delete everything from the /var/cache directory and then reload your website in your browser.
To clear all sessions, you can also delete everything from the /var/session folder within your Magento installation directory.

install joomla on strato.de

I am creating a website based on Joomla! for my german friend who has a hosting in strato.de
I encountered many problems with installing Joomla on this hosting. After uploading Joomla 1.5.23 files on their server and trying to install Joomla, I got anerror:
Warning: file_put_contents(.../configuration.php) [function.file-put-contents]:
failed to open stream:
Permission denied in /.../installation/installer/models/model.php on line 850
After this, I created manually configuration.php and filled it with database data (passwords etc).
Joomla seemed to be installed, but when I tried to install any extension, I can't do it since it shows only errors like:
Cound not create directory
Component install: failed to create directory
Of course I tried to change directory permissions to 777 but it didn't help, always the same problem and no availability to install any component. The php info shows it's a SunOs on the server and i think something is wrong with owner of the files.
I also tried to install Joomla via strato own installator, but it gives the same errors.
I contacted strato de help office, but they answer was "we do not offer any technical / scripting support for either of the 3rd party CMS's".
Could someone help me please with that?
Has anyone succeed with installing Joomla and components on this hosting?
I would appreciate any help.
First, you should never set the permissions to anything to 777, that's a big security risk.
Next, chances are that the server is not configured properly to run Joomla without any problems. Joomla works a lot better when PHP is run in CGI mode rather than when it is run as an Apache module. Most likely the server you are on is running PHP as an Apache module, which causes a lot of issues.
You can get around a lot of the issues by turning on the FTP layer, but there are some things to check first -
Make sure that both the log and tmp directories exist in the root.
Check the directory permissions by logging in to the admin then Help > System Info > Directory Permissions (you should see the tmp and log directories here as well). Files should be 644, directories should be 755.
Turn on the FTP layer by going to Site > Global Configuration > Server > FTP Settings
If it still gives you errors, I would suggest moving to a better hosting company. Rochen Host has a data center in the UK and they handle all of the official Joomla websites. I use them and they are great. Everything works without any issues.

Resources