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.
Related
I copied the complete folder of my prestashop 1.7.3.0 on a new folder on my server with new database, install a new theme and maj prestashop in 1.7.7.0
The concern is that now that I have finished in the meantime I have had orders and customers.
I imported the products in excel redone the variations by hand.
How can I subsequently export customers and orders?
In excel import of my last clients it tells me that the password is required for the import?
What would be the best method even going on phpmyadmin to import the customers, addresses and orders that I miss on the new store?
Thanks for your feedback.
To align customers and addresses you can use Prestashop's built-in CSV import feature.
Regarding orders there is no standard way to do it,
you have to perform queries on the new database synchronizing the missing data of the old one, taking care to check the various tables of the site because there are several entities involved (and structure might change between PS versions too).
Also keep in mind that there may be third party modules on the old site that save data and therefore must be synchronized.
Other options: you'll put "catalog mode" on the live store for a few days until you've finished the work on the new one or use a paid data migration module that can perform incremental migrations.
while setting up a basic 1 x NGINX load-balancer in front of 2 backends, I ended up in what it is clear to me to be a bug: the cron of this Certified App cannot be edited:
As you can see, in this particular App the cron file is owned by root:root and doesn't have the extended attribute (the plus on the right of permissions) necessary for the file to be edited also by the logged in user (nginx in this case).
All other certified apps allow instead the main login user to have crontabs, even though I found the permissions of each file vary a lot.
I've stumbled on https://github.com/jelastic/jem/blob/master/etc/jelastic/export.conf and it seems the file to go for proposing a bugfix, but it's last update if Aug-2016, so I guess Jelastic had closed much of its source code.
How can we contribute to Certified App source code?
indeed it is a bug as cron file of nginx user isn't editable in a balancer template, by design in has to be.
As for exports.conf - this file left for backwards comparability, but no more used.
The problem will be definitely fixed in latest templates, as for existing containers - we would like to apply a patch to fix them, if you provide us more details about hosting service provider you are using - we will help with that.
As for contribution to certified templates, all the images are publicly available on Docker Hub, you can create your own version of template based on existing one if you build a docker image and in your Dockerfile you specify
"from jelastic/nginxbalancer" as a base, then you can do any modifications to the filesystem. Next step will be just to replace existing balancer with your custom one.
Anyway, let's start with fix of existing containers.
Many thanks for finding out the bug!
Our web developer picked OctoberCMS to develop our new website (his skill). Unfortunately before completion he rapidly left us due to health reasons and is no longer available. His Ubuntu environment has some problems and we need it on CentOS 7 anyway. The rest of us are OctoberCMS newbies, but want to learn it.
We built a CentOS 7 VM and installed OctoberCMS and want to move his work over.
We can not find any instructions on how to "export" the work he has done thus far and import it into our new OctoberCMS.
He is using 10 plugins and 3 he developed. (I don't know if that is relevant)
Is there an easy way to do this or at least instructions?
We have been googling, youtubing, IRC'ing for a week and still at a loss.
Any help would be most appreciated.
There really isn't anything special you need to know about moving an OctoberCMS install to a new server compared to moving over any other PHP application.
I am assuming you know how to do the basics of setting up a LAMP stack, such as setting up a virtual host for the domain you want to host the site on and setting up a MySQL database and user/password to access the database. There are of course many variants on how you could accomplish this such as using a management tool like Plesk or cPanel, or just configuring the services manually via the command line.
1) Ensure your new server is running at least roughly the same version of Apache, MySQL, and PHP.
2) Copy over the directory that contains all of the web files from the old server into the document root for your domain on the new server.
3) Do a database dump from the old server and copy it to the new server. If possible, use the same database name and username and password as the old server. This way you don't have to worry about updating the configuration of the website.
4) Pull up the site and troubleshoot any errors that come up. It is helpful if OctoberCMS debug mode is on.
Following the above method will ensure that you have the exact same setup on your new server that the old server had. This will copy over all of the plugins, data, etc.
There are of course many complexities that can come up during a switch over like this, but this should at least get you started and you can come back to StackOverflow with some more specific hurdles.
Hope that helps.
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.
Does anyone know about this problem: Any new fields I add work fine in the local back office, but when I use Webmatrix to publish to the server (discountASP.net) fields don't show up. I did a view source in the browser and they're just not there!
For example, #Umbraco.Field("comments")
Thanks!
Daniel
If you add new field, they are only added in the database. That means you would need to update the database on the production website. Webmatrix doesn't do this for you (by default).
There are a few ways to handle this scenario:
copy your database to the production server (i would advice against this, because you might overwrite content and media changes on the production server)
create the fields manually on the production server (easy solution)
use a commercial package like courrier (personally i believe it's a good solution, only if you have a content staging workflow)
use a free package like usync (http://our.umbraco.org/projects/developer-tools/usync)