I have a brand new installation of Magento CE 1.7.0.2 on my local machine, and cannot get any extensions to load. They install properly in the Magento Connect Manager and appear in the list as installed, but there is no effect in the admin interface.
I have successfully installed Magento and these extensions before, so I'm not a complete noob. The extensions I'm trying to get working are these (both theoretically compatible with 1.7):
http://www.magentocommerce.com/magento-connect/customer-experience/internationalization-localization/magento-community-modules-french-france-language-pack.html
http://www.magentocommerce.com/magento-connect/oscommerce-migration-tool.html
What should happen with these extensions is:
The admin interface should be in French (remains in English despite switching back and forth to French / other languages)
There should be a "oscommerce" menu item under System > Import/Export (not there)
What I've tried (many times and in every possible combination):
Logging out and back in
Flushing all caches
Deleting all cookies, exiting the browser, restarting apache, restarting the machine
Reinstalling/Uninstalling both extensions
Reinstalling Magento with a clean database and clean filesystem
I've followed the installation instructions to a tee. Magento is in developer mode ("SetEnv MAGE_IS_DEVELOPER_MODE 1" and "php_flag display_errors On" in .htaccess). There are no relevant errors in the logs and no PHP errors. The www user (under which runs the apache process) has full write permissions to the entire directory (also tried just /var, /app/etc and /)
Can someone please tell me what I'm doing wrong???
Do a chmod -R 777 on the root of your magento installation to test if the moduls start to work then.
Related
I am using CentOS 6.7 and I'm trying to get Magento installed on the server. All the software is the correct versions for Magento to run.
During set-up, I have followed Magento's instructions here:
http://devdocs.magento.com/guides/v2.0/install-gde/prereq/apache-user.html
The web host user and group is "nobody", so I used that in place of "apache". However, when I tried these:
http://devdocs.magento.com/guides/v2.0/install-gde/prereq/file-system-perms.html
The user I created for Magento is not permitted to run those commands.
I attempted installation anyway, it somewhat works, but new files created with Magento do not have the correct permissions. Running the Magento cleanup tool, it fixes the permissions for new files, but it would be an extremely slow process and magento is constantly creating new files.
Is there something I missed, or could there be something else causing these issues?
I tried to install Magento 2 on localhost using WAMP (php5.5, APACHE2.4.9 and MySQL5.6).
I added the required extension "intl" (by removing (;) in php.ini), but for some reason it didn't work - I had to copy the dll into the Apache bin folder.
I updated xdebug and had to create in php.ini an entry for xdebug.max_nesting_level = 50000;.
After all this I went to do the second phase of installation (database creation, etc...) and at the end it was successful. But upon trying to enter the Backend admin page, I get the error Page Not Found, and the Frontend was broken (no style).
So I installed the version with sample-date and the same thing happened, the only difference was the existence of the photos. I installed using the composer, and got the same error.
I think I did something wrong with the WAMP installation, but I'm not sure.
Another issue I encountered was on the themes in the installation with setup wizard: the app / design / frontend / magento folders are empty, while the github repository has two themes - why is that?
For broken styles and JS, please run php bin/magento setup:static-content:deploy. You might want to provide your specific language code as input; default is en_US
Re empty theme folder, there are several methods to deploy and install, based on your needs. The github version is meant for contributing devs, and hence there are themes present in the app/design/ folder. However, if you deployed via composer, or downloaded the zip file from magento.com, the app/design folder will be empty, since the themes are loaded via composer, from the vendor/magento folder.
I'm attempting to upgrade a Magento 1.7.0.2 website to 1.8.1.0 following the process given by Magento on their website: http://www.magentocommerce.com/knowledge-base/entry/ce18-upgrade-roadmap?icid=BLOG_magentoce1810release_upgradeinstructions
I follow this up to step 2b on the above link where it says:
Archive the file system.
This includes the media directory and subdirectories; all extensions and customizations; and all custom themes.
I understand how to make a zip of the media directory and theme directory files. However, I don't understand how to archive/move the extensions? We have about 10 extensions installed on the website we're upgrading; some were installed by copying zip files on to the webspace, whereas others were installed via Magento Connect.
The files for the extensions are all over the webspace (in line with Magento's huge directory structure) so I don't see how it's possible to identify all of these files and move them across.
Does anyone know what the best way of doing this is?
The steps on the Magento blog are a little odd. Does anybody really do it that way?
Surely the way to do it is:
0. clone your entire production system onto a new server - call it the back up
1. clone your entire production system onto another new server - call it the dev server
3. Via Magento Connect, upgrade the dev server to 1.8
4. Download all the Magento 1.8 files to your PC and then upload them all to the dev server just to be sure all the files are in place
5, Run lots of tests and iron out any problems
6. Either switch your store URL to point to the dev server or put your live store in maintenance mode while you repeat steps 1-6 on the live server; if it screws up see step 0.
Your point is correct : it is very hard to extract the modules which is why I say always build up from your current state rather than trying to build up form a fresh Magento 1.8.
The way I did it eventually was following steps similar to these:
http://www.magentocommerce.com/boards/viewthread/283184/
The point I was missing was the directories that needed manually moving to the "upgrade" version of the website (the "dev server" Malachy's post).
Steps were:
Install a clean copy of 1.8 on a dev server.
Make a copy of the live server (1.7) database on to the dev server.
Move these folders from the live server:
app/design/frontend/mytheme
app/etc/local.xml
app/etc/modules
app/code/community
app/code/local
js
skin/frontend/mytheme
media
Change app/etc/local.xml to reference the 1.7 database, but on the dev server.
Change the base_url (nonsecure & secure) settings in the config table of the DB.
Go to the URL of the dev website, wait for the upgrade scripts to run.
Test / fix - repeat as much as required.
Put the dev copy of the site live.
Caveat with this is that if your live site is getting orders frequently, you'll not get a copy of that as your database will become out-of-sync as soon as you copy it during step 2.
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.
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.