i am looking into upgrading my magento community from 1.6.2 to 1.7.0.2.
First i will do this on my test server, but there are some errors during updating in magento connect, so i have to upload some files my self ...
but when i going to put these data into the live environment, can i just simply copy my data from the ftp to the live website?
Or are there also some new/changed settings in the database?
And if yes on the last question, which lines are changed?
I was able to successfully upgrade Magento from 1.6.1 to 1.7.using Connect Manager.
Here are the steps I had foung and followed
Go to yourdomain. com/magento/downloader/ (of course, make this
match your installation’s path.
Because I had installed Magento using tar.gz package provided with a skin I wanted to use, Magento Connect didn’t have all the
extensions listed for upgrading. I had to type
“connect20.magentocommerce.com/community/Mage_All_Latest” in the
“Install New Extensions / Paste extension key to install”
If you run into an error along the lines of “CONNECT ERROR: Package ‘Mage_All_Latest’ is invalid” repeated several times, once
for each package, it is because the files already exist, and you
have to remove a line of code in order for it to over-write data.
After everything has updated, you will probably have some errors. Make sure you clean the cache and session directories (delete
everything in /var/cache and /var/session)
If you receive a “500 Internal Server Error” it is more than likely because of file and folder permissions. It took .5 sec to
reset all of the permissions to what they needed to be.
If you receive a “Service Temporarily Unavailable The server is temporarily unable to service your request” error on a Magento
formatted header, it is probably because the store is set to offline
mode to prevent visitors from screwing up the installation process.
To fix this, delete the“maintenance.flag” file found in the root of
your magento installation directory.
Everything should be ready!
Avoid upload core library changes via ftp.
The fastest and more secure way is to patch your application using the diff files
patch -p0 -f < 1.6.2.0-1.7.0.0.diff
Then when you first visit your site Magento will automatically upgrade your db
best way to update is get a fresh mage zip 1.7.1 or whatever, and connect it to your current DB. When you go to index - the new install will update your DB to the latest MAge DB. This way you dont have to use connect etc. The mage zip has its own sql updates.
Make sure you put your current theme into the new install etc, and test it 1st on localhost etc.
Related
I am newbie in Composite, I already backup and download C1 websites (www.solve.sg), I also have installed (and working) Composite in localhost. So how to restore websites in localhost?.
I already used method to rename folder CompositesC1 to CompositesC1old, then extract and put extracted web in CompositeC1 folder at localhost but not working and gave me error.
Please help the right method how to read online backup websites and to read that at localhost
I dont know what Composite is, but you probably need to go back to your cPanel / backend of your webhost, dump the DB powering solve.sg and import that into your local instance.
Your hosting provider will probably have a tool called phpMyAdmin; go in there and find the 'Export' tab at the top of your DB and dump it out as a .sql file. You will then import that file into your local environment, probably also using phpMyAdmin.
You may also have to change around some of the settings files that show where your database is relative to your application.
I have a 2 questions regarding Weblogic.
I am using Weblogic 10.3.6.
Yesterday I deployed the war file.
Following are my 2 questions
1) When I restart the server the sys out logs at location
domains//servers//logs/Server-name.out
domains//servers//logs/Server-name.log
are not getting updated
Actually logs were getting updated initially but I cleared the log file by manually opening the log file and deleting its content.
Later I found on official oracle website that
"Oracle recommends that you do not modify log files by editing them manually. Modifying a file changes the timestamp and can confuse log file rotation. In addition, editing a file might lock it and prevent updates from WebLogic Server, as well as interfere with the Accessor"
I think my log files got locked due to above reason.
Is there any way I can do to get updates in log files.
I have restarted the server as well but the logs are not getting updated.
2) I have deployed my web application using packed war file. When I deploy using war file it is expected that the war file gets exploded at some temporarily location in weblogic server. War gets deployed successfully but when I checked the contents of
WEBLOGIC/bea10.3.6.0_BI/user_projects/domains/Managedserver_7011_7012/servers/Server-chanakya/tmp/_WL_user
It is blank.
I was expecting that war should get exploaded inside the _WL_user folder. But it is not happeining right now.
Please let me know what I can do with respect to above problems.
Thankx in advance.
First question:
Generally speaking the .out file is created during server start and not updated once the server reaches the RUNNING state. The .log file should be updated continually however. It is safe to delete both of these files and once the server is restarted they should be regenerated. If for some reason they are not, go to server name -> Logging tab -> Log file name and specify the full path and name for a new log file.
Second question:
If you chose nostage for your deployment, it will not be copied to your server and will live wherever the file originally was. stage mode should copy the file to tmp/_WL_user after starting out under a stage directory. You can remove your deployment from the weblogic admin console and also delete the tmp and cache folders and try the deployment again if you need to. It's also possible the deployment failed... check the Deployments link in the admin console to make sure it reached the Active state.
Last - welcome to Stack Overflow. In general you should ask one question at a time.
(edit: I'm leaving all the mistaken assumptions in just in case someone else makes the same mistakes)
I have an ancient Typo3 3.8.1 site on a remote server. I don't have access to that server, and the team in charge of maintaining the site doesn't know who to contact to get access to the server. I do have the admin rights on that site, though. (edit: no I don't. oops.)
This is what I see in the (not) admin menu:
I'm not sure if this version supports extensions, I can't find an extension manager anywhere. (because I'm not an admin)
I want to export the site so I can host it on a server on my own domain instead. The problem is the export file is too large, I can't download it. Will I destroy the directory structure if I export a bunch of pages at a time?
If you have admin access to the backend you can try to install Quixplorer - file manager. Using it you can try to zip folders in the main directory ie. (typo3, typo3conf, fileadmin etc) one by one and download them via browser.
It's important to download and remove typo3conf.zip from the server as soon as possible, cause it contains sensitive data.
Additionally you can also install PhpMyAdmin extension (search in repository) i you haven't other MySQL client.
Edit:
If you can't use Quixplorer the only way is... to write own extension and upload it via Extension Manager, there you'll need to try perform primitive file system operations like:
(PHP)
system('zip -R t3c.zip typo3conf/');
Sometimes the server allows more memory and execution_time that the T3D Export. So, if you can change PHP files on that server, try to change typo3/sysext/impexp/class.tx_impexp.php - search for ini_set and change that settings. If the server allows, you can then create bigger t3d-files.
And you could try some shell-extensions to get hands on that server:
http://typo3.org/extensions/repository/view/phpshell
http://typo3.org/extensions/repository/view/mw_shell
http://typo3.org/extensions/repository/view/shell
But to answer your initial question: you can crate a couple of T3D-files and import them again. Just force uid if you import them - and install all needed extensions first!
In our team, we use a common database server. When running the Orchard Setup, I point the connection string to an existing Orchard Database and got this error message:
Setup failed: The requested service 'Orchard.IWorkContextAccessor' has not been registered. To avoid this exception, either register a component to provide the service, check for service registration using IsRegistered(), or use the ResolveOptional() method to resolve an optional dependency.
The only way that can make setup successful for me is to point to an empty database. I attempted a workaround by doing so first, and then edit connection string in App_Data\Sites\Default\Settings.txt, but then I got the same error.
I had this problem as well, also tried copying the settings.txt file which did not work. This time I copied all the contents of the App_data directory over and it worked for me. Also, this latest time I was using the latest commit from codeplex.
I deleted cache.dat and restarted the website in IIS, this fixed it for me
I was given a dotnetnuke v4.9.5.5 database (sql-express about 300MB) and I am trying to get it up and running on a different server. I have tried:
Installing the 4.9 version and
loading the database into the app_data folder
loading the database through the SQL page under the host login (forwards to 404 page...)
installing the 5.x version and
loading the database into the app_data folder
loading the database through the SQL page under the host login (forwards to 404 page... again..)
All of which fail. I cannot find any support on this topic at all. What is the correct way to go about this?
EDIT: wrong info please close..
Here is a good blog on the topic HOW TO: Move a DotNetNuke installation .
The basics are:
Copy all the files and the database, the two are closely tied together.
Update the connection string in the web.config.
Update the portal alias' in the PortalAlias table.
If you don't have the rest of the site files, it may be very difficult. While the database will contain most of the site content, you may be missing some important pieces like skin files, module files, and content files.
So, the first thing you should do is see if you can get the files zipped up and sent to you. If so, it should be fairly easy to get the site up and running. You may have to update the ConnectionStrings in the web.config but otherwise it should run as it.
If you can't get the original files, you could try installing version 4.9.5 of DotNetNuke and replacing the supplied database with the database you were given. You'll need to post the error messages you get if it doesn't work out or consult someone with solid DotNetNuke experience.