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.
Related
I have a laravel project running on Linux server without any issue. The files are in /public_html directory and "laravel" directory is out of public_html. It has mySQL 5.6 and PHP 7.1. The project works completely fine.
Now, we have decided to move this on windows server. I have setup same PHP and mySQL on new windows server. I have double checked and this is correct.
I have imported entire database to windows and files have been moved as below:
The files from /home/abcuser/public_html/ directory to
C:\HostingSpace\abc.com\wwwroot
The files from /home/abcuser/laravel directory to
C:\HostingSpace\abc.com\laravel
The IIS has site path as below:
C:\HostingSpace\abc.com\wwwroot
I set all required permissions to these directories and updated database connection in .env file.
I am now getting blank page with no error message. Do I still need to make any changes in code? Did anyone has experienced the same?
Finally got this fixed..
I had to enable some PHP extensions. What I did is:
Checked the list of disabled PHP extensions from IIS of concerned
site.
Checked whether the particular extension is enabled in oldserver where
it is working.
And Enabled it as needed.
I recently installed phpList in a folder of my current joomla install (on share server in bluehost). I had to manually install it, and I can access the admin page.
Joomla is installed at the root folder (html_public) and phpList in a folder within it (html_public/phpList).
As said, I can successfully access the admin page of phpList (www.my-site.com/phpList/lists/admin) and configure it.
The problem is: every time I click on "save" to save an updated configuration, then it re-directs me to a 404 - not found throw by joomla (as it redirects to http://www.my-site.com/lists/admin/?page=configure#item_confirmationmessage). My updated configuration is correctly saved, and I can easily go back to it pressing the "back" button in the browser. I notice that phpList is not redirecting to the correct folder html_public/phpList/lists but to an incorrect one: html_public/lists.
I think there has to be some tweak to do in joomla and/or phpList to correctly define the folder it should direct the confirmation message.
I'm fully aware of the alternative of installing phpList to a subdomain's root folder, but at this point I'd prefer (if possible) to fix what I actually have.
This is what I ended doing, if it's of help to people looking for solutions.
It seems phpList is somewhat picky about the folder it's installed to.
In order to avoid conflicts with the already existing Joomla install, I had to create a subdomain and then make a clean re-install of it to a folder called lists within that subdomain. Any other solution (for example installing it to lists within html_public of my main domain) didn't work well, producing errors similar to the one described in the question. So, step by step:
Create a subdomain to your site (mine was "lists.mysite.com")
Install phpList into a folder called lists within that subdomain's html_public folder. Make sure you follow the guide in phpList documentation
Configure and go.
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 am no expert in Joomla... :)
On my local station using XAMMP, my Joomla 1.5.22 site is running fine but when I upload it to our server online, my problem began, when I visit the frontpage it pulled out nothing but I can still access its backend. I tried to search all over the net, I did some suggested fix but still failed :(
Look for error log in the root folder of your Joomla install, that will give you a hint on why this is happenning.
Also, instead of copying the files and database manually use Akeeba Backup extension for backing up complete site (all files and database) in a single archive. Then use Akeeba Kickstart script for restoring. Akeeba Kickstart will automatically change all configurations needed to run your site on the new server. The extension and the script are free and the process is very simple, look for Youtube videos that show the backup / restore process step by step.
Good luck.
I just get my site back, I just learned that a depreciated module caused the problem, because our server has been upgraded, so I just disabled all my modules on site then single by single I enable it again and find the module that caused the problem, which I did, I'm now replacing that depreciated module with new extension so that the site will be working back.
-- Update --
Now my site is back, I just found out that GD library is not installed on PHP, that's why it shows blank page in the first place, PHEW!
thanks
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.