Well the big issue I got is how can I run Odoo on my local host (WAMP). I have gotten the files from my company server however I need to test and migrate it so I am trying to run it on my local host however I have had no luck even accessing a single web page. I have copied and pasted the folder into the correct location. However if I try to access it it just takes me to a 404 error or a directory listing page (folder structure)
So just wondering if anyone knows how I can run odoo files from my server to my local host????
Just copying folder structure is not enough for proper migration. You should also have access to the Odoo database: it uses PostgreSQL, and you should either have access to your company database server or duplicate database. It's even more important than files in Odoo directory.
Moreover, for running Odoo on your local machine, you should not have WAMP installed - python with some modules and PostgreSQL is enough.
If you want "clean" install and then using some migration tools, you can install Odoo into your machine (I provided link for 9.0 version, for 8.0 you can use this link or choose corresponding version on the Odoo installation page) - this method will setup all necessary environment automatically, but you should manually upload your data to the fresh install.
Installation from sources is some more tricky, but still not very hard. You can find instructions in official website.
After this you can check directory structure and copy your custom addons, templates, design or content from existing directory structure to the fresh one. Don't forget about database - without it you won't have huge part of your data available on company server.
For running Odoo you should run odoo.py with your python from your Odoo directory (you should have python 2.7.x installed on your machine).
By default Odoo uses port 8069, i. e. for accessing it you should type in browser
localhost:8069
For more detailed instructions please refer to Odoo documentation.
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 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.
Trying to upgrade from 1.3.2.4 to 1.4.
I set up MAMP and created an empty database into which I imported the exported database from the online site (done via phpMyAdmin from the cpanel of the site).
Copied 1.4 files into htdocs and got the installation screens.
After entering the details for the imported database, the process crashed and I got a blank screen.
I've tried changing the base url string in the core_config_data table and redone the whole process but to no avail.
I've also tried setting up a clean install of 1.4 and using the database repair tool to perhaps bring the old database up to spec but that didn't work either.
I basically need a proper way to upgrade this site to the latest version (1.8.1) but I thought I'd start with 1.4 first. At the very least I'd like to have a database that can work in a fresh 1.8.1 install.
You need to find out what the error is before you can begin to fix it. The blank screen means that you are not getting those errors. It may be a simple timeout. What is in your php.ini for error reporting and timeouts?
With your 'MAMP' you can try a vanilla Magento install and see if that works. Try 1.3.2 with the demo data in the db first. Then point it at your copy of the live db and see if it still works or if it dies due to some module dependencies.
That should get you to the starting point. As for where you are now, check the apache log files to see if the error - maybe just a timeout - is in there.
On upgrade Magento does loads of stuff, as per the upgrade scripts with each module. This is database intensive stuff and by doing a dry run on a vanilla database you can see what you are up against.
Hope that helps.
I don't know how to install Joomla 1.7.3 and it's hard to know from joomla web page. Can anybody tell me how to install joomla 1.7.3 step-by-step.
Thank you
There's an old guide here, although it still mostly applies:
http://help.joomla.org/content/category/15/99/132/
In short: Create a database, Upload the Joomla files, follow the installer. In more detail:
Make sure you meet the system requirements:
http://www.joomla.org/technical-requirements.html
Create a MySQL database (note down the name, username, and password to access it)
Get the Joomla files from here:
http://www.joomla.org/download.html
Upload all the files from that package to your hosting
Browse to your site - the Joomla installer will automatically run. There's a guide for the steps here:
http://docs.joomla.org/Installer
Follow the instructions and fill in the boxes in the Joomla installer.
Once the installation is complete, delete the 'installation' folder (the installer will tell you to do this).
You now have Joomla :)
Have you checked this page? http://docs.joomla.org/Installation
It provides a step by step installation guide, I think it's quite easy to install Joomla. Generally talking, all you have to do is:
Download the latest Joomla version ( I guess you already did this )
Unzip the downloaded file, then copy it into your webroot ( if you have multiple sites, you should create a folder within your webroot dir and copy the files there )
Access via your browser your web dir, and installation process will start.
It's important that you check that your Apache user is able to read and write your Joomla files. If you're using virtual hosts, you should also create and configure the new virtual host.