i have a problem with installing and deinstalling a module in magento. after resinstalling a module, the previous configuration in the backend is still there.
I deinstalled the module via connect, checked the folders of the server for files that didnt got deleted but i couldnt find anything. No matter how many times i clear cache, delete cache manually from server, after reinstalling the module the configuration i have made in the backend keeps reappearing (the module in question asks for some pathes which i filled in when i first installed it).
So can anyone tell me where these data is stored so i can delete it as well?
The backend database contains some data in a few tables by default.
There are rows in core_config_data for each variable possibly defined for the module, you will have to search it for the keys related to module.
There could be tables created for the module which you will can easily find by the module prefix to tablename.
Also there is a table core_resource, which lists the modules recognized as installed by Magento, which means they are version number controlled.
Related
I was given a database backup (with filestore), the filestore folder and another folder with the installed modules on that database.
I am expected to restore that backup in Odoo 8 with no more data. So what I did is create the PostgreSQL role who owns the database tables and give it enough permissions (login, createdb, replication). Then I created an Odoo config file. Inside this, I set this new PostgreSQL role in db_user and its password in db_password. I added the path where I stored the filestore in data_dir, and the path of the folder with all the modules in addons_path.
As I was given no launcher file, I copied the OCB folder of other Odoo instance I have and used its odoo.py file to start Odoo.
The new instance seems to run well, but now I have just restored the database, and I get this error:
QWebException: "'HttpRequest' object has no attribute 'endpoint_arguments'" while evaluating
'website.get_alternate_languages(request.httprequest)'
I was googling a lot but I was not able to find anything about it, except for a non-answered question in other forum.
Does anyone know what is this about?
Changes related to this issue were introduced in Odoo on 29 February, 2016 (I mean the following changes: [FIX] website: alternate languages translated URL and [FIX] website: backport of as you can check for now these changes are available in the official Odoo 8.0 code base as well).
So most probably you have used outdated Odoo 8.0 server that do not contain above mentioned fixes. Please update to the latest official Odoo 8.0 and check if the issue still persists. Normally your issue should disappear after the update.
When you move backup databases and you want to restore them later on, make sure you mark the branch and commit point of the server files that you took the backup from. I have taken a look at my local v8 odoo and I can see that the endpoint_arguments variable is initialised upon the creation of a web request (openerp/http.py class WebRequest around line 192.)
You mention though that you are restoring the database on the v8 OCB Odoo. If you navigate their distribution and on commit:
https://github.com/OCA/OCB/commit/3913667396e17075528108ac1031939e6f479ced#diff-5e2f434047c379642786a87195c806f9
you will see that this variable was missing and they have added it. So make sure that you git pull the server file to get that commit.
The root of the issue is that you took a backup from a server that had different codebase than the one you are trying to restore the database to. (The qweb file was searching for a variable that is not there)
Hello I would like to ask how is it possible to migrate VM2 to VM3. I want to update my Joomla site from 2 to 3 and VM to be compatible. I found only that http://docs.virtuemart.net/tutorials/installation-migration-upgrade/198-upgrade-virtuemart-2-to-virtuemart-3.html please help I have many data on VM2 and I don't want to lose it.
this process should be careful, follow my procedures:
Go to official site installed VM Migrator plugin
before you should do all your backup sql in VM2 and VM3 sites
Also what I had done is add another Database called migration_vm2 in my server, and import vm2 sql, this could be avoid the problem and you could query one of table to compare
And for import the users and orders list and products you should use VM Migrator
There are some ways to achieve that. My pattern is mostly like this.
First attempt, update all Joomla components, install VirtueMart 3 via normal installer, install Joomla 3. If that fails:
Second attempt, use Daycounts Migrator and use a fresh J3/VM3 installation on the same server to transfer files and database with the migrator. If that fails:
Third attempt, compare the databases from first attempt or second attempt and export single db tables and import with the changed column names into VM 3 db.
Use a standard template like Protostar in the beginning, change to a new template only after everything else works.
This question is not answered in one answer here, I suggest the VirtueMart forum.
This worked for me. First download the newest VM package from the official site. Note that normally it is a compressed file with core component and AIO component zipped inside, so you will have to extract these first.
Second, in your Joomla 2.5 backend, check Extension Manager > Database tab and do a fix if necessary. Do not forget to do a backup of all your site using Akeeba or similar extensions. Keeping a backup of existing orders is good practice.
Finally, using the Extension Manager installer, upload and install the VM3 core and the AIO after that. Clear cache and check database fixes again if necessary.
Very important: clear your browser's cache to purge preloaded js files and so.
Check your VM3 frontend and backend, you should have all your items, registered shoppers, old orders and so. There can be some styling issues with new classes, also your shopper groups could be misconfigured, correct the prices to be shown... and thats it!
About the migration from J2.5 to J3, having VM3 installed has not been a problem for me so far. Always refresh your web browser cache after a migration in order to eliminate preloaded javascript files that are obsolete, otherwise you could have some problems trying to save menus, articles and so; just clear your cache again and thats it.
i want a live site to be on local host and without effecting any functionality of live magento site. i have tried many way of doing that but have not get any result from it.
steps i tried are :
1. taken database from magento live site by entering into cpanel(by ftp access) > phpmyadmin > exported all the files to my local machine and i imported all the data to my local phpmyadmin.
2.taken all neccessary files from cpanel > file manager > all files (for example p_html, .htpassword, .trash, access log, etc file and many more) and put it on my local machine and then i put the file in folder and kept it into C:\xampp\htdocs\ all file ( in folder ).
3 Replaced the path of live site with localhost:1234 in the all sql files where applicable taken in step one.
but still not working .
Any help will be appreciated....
Copy your LIVE Magento store to your Local computer:
Download the magento files using any ftp client.
Export the database from live server.
Put the downloaded Magento files in your localhost root folder.
Create a blank database(lets say it 'local-database') in your local computer and import the database backup that you exported from the live one.
Delete/Rename the file app/etc/local.xml
Re-install the Magento using the local-database.
After installation, go to Admin section and then
(i)Flush all cache. (ii)Re-Index all data. (iii)Flush all cache.
That's it. You are done.
N.B. If you have domain specific Modules installed, those modules will not work here.
Seems very simple right. Believe me, it is that simple.
If you face any problem in installing your Magento in localcomputer, here is a post that may come in handy: http://www.insync.co.in/how-to-install-magento-on-wamp-server-localhost-localcomputer/
Steps:
Download the files to the local project folder.
Create a new local DB and import the live database backup/dump.
Update app/etc/local.xml file with local DB parameters(Host name, DB
name, DB username, DB password)
Magento have the project URL saved in 2 places(secure URL and
unsecure URL) in the table core_config_data. We need to update
that in imported local DB to the local URL(9th and 10th record in
the table).
Delete the cache: Delete the contents in var folder(That folder
contains reports and logs too. I assume that you won't need it as
this is a separate installation)
The local copy will most probably work by now but there are possibilities that it would not. Things to do in this case:
If you are getting redirected to the live site, check the .htaccess
file for redirects(For various reasons there may be a redirect
defined in the file)
If you are getting forbidden error, this will come in handy(Usually occurs in linux systems)
There may still be some problems probably theme or module specific. In this case you will need to debug the project and find out what the problem is. Xdebug will come in handy in this situation for boosting the debug process :)
Subrata's solution will conflict with some of the Magento Modules installed and will not allow you to re-install Magento in local. I follow these steps and everything works fine.
Just give a permission (0777) after take a backup to that folder in your local PC
First of all you will have to change the secure and unsecure base_url in your database.
These can be found in the 'core_config_data' table.
Paths:
web/unsecure/base_url
web/secure/base_url
If you want to access your local version of Magento via localhost, you'll have to set localhost as your base_url.
After that you need to clear your cache folder.
EDIT:
To install and run Magento on your local PC using XAMPP, please follow these steps:
http://www.magentocommerce.com/wiki/1_-_installation_and_configuration/installing_on_windows_with_xampp_and_wamp
I have a Magento site running on a live e-commerce server.
I downloaded the whole site for offline use in a development environment. I changed the Base URL values in the database and edited the local.xml file but my local development site is still referring to the online store.
How do I correct this?
The usual problem, changing your base urls and local.xml is only a minor part of the equation.
Step 3 was missed on moving the website to the development server.
Moving stuff is actually pretty darn simple.
a. Tar the public_html directory on the old server
b. Reinstall on the development system.
a. Disable caching in Magento on the old server, dump the database and then reenable the Magento cache.
b. Create a mysql database, user and grant permissions on the development system. Load the database dump into the database on the development system.
Do the one thing that most people ignore, go set your file permissions and ownership.
Change your base URLs using either mysql command line or phpMyAdmin.
Go eliminate every subfolder in the var/ folder, Magento will recreate it.
Finally, go make changes to your local.xml file to change the database access credentials assigned to the new database and bring Magento up.
If you have complete ownership of the server, do the above steps with the Apache server down until you've loaded all the data and made the permissions and file corrections. This prevents accidentally starting Magento in an unprepared state which can cache Magento's configuration which is why you are having this problem.
If you do not have proper permissions on the var/ folder and subfolders, Magento will write your Magento temporary and cache to the system temp and you end up with Mage's magically redirected Magento which eternally points to the original website.
Also, if you copy local.xml to another file to save it, name it something like local.xml.sv0 otherwise if it ends in .xml, Magento autoload each .xml file in app/etc/ and try to merge it with the contents of your local.xml file.
NOTE: What happens when you don't properly set file/folder permissions before running Magento for the first time after a move.
I want to migrate the data from one Plone instance to another. I am new to Plone.
Any URLs or steps for migration are really appreciated.
When you want to move a complete instance, you need to copy over the same data as you would back up.
That means you'll need to copy over:
The Data.fs object storage file
The blobstorage directory
All your customizations and installed packages, beyond Plone.
See the Plone FAQ and Backing up (and restoring) a Plone instance.