B2B Custumer module give migration error after install and restart module.
My Virtocommerce platform version is 2.13.35 community.
I hope some can help you to solve this error.
Thanks In Advance...
As you said, this module is obsolete and is no longer supported.
All the necessary b2b functionality is built into other modules in the new version platform.
Related
After doing a fresh install of the VC platform and VC storefront from source code, I chose to install the sample data. I am getting an error in the Smart Caching Module, which states Module platform version 2.13.28 is incompatible with current 2.13.26;
In my VC Platform solution, I can see the version is in fact set to 2.13.26 in my common assembly file - and in my Smart Caching Module the target version is in fact set to 2.13.28.
How can I roll back the Smart Caching Module to target the 2.13.26 version? Or is it easier to upgrade the platform to version 2.13.28?
Thanks
Yes, the easiest way to update your VC platform to the latest version. https://github.com/VirtoCommerce/vc-platform/releases
Is there a way to update a vc platform version from an azure setup? I can't update modules in the platform while it's version isn't the current one. I had storefront and platform installed in one web app. Any help is appreciated. Thanks!
unfortunately, this kind of deployment (both Platform and Storefront) on the same application, doesn't support updating platform through Azure deployment options.
To update platform you should repeat 4,5,6 steps from this article deployment-to-one-azure-application
Do you plan to release a new version of this module? I am trying to use, but there is something wrong. Maybe am I missing something?
My VirtoCommerce Core version is 2.4 and the module have Core 2.3 version dependency. After a sucessfull installation, the admin does not load properly.
If I remove the module from Platform/Modules folder, the admin load correctly again.
http://imgur.com/a/hk0sB#2
Thank you, in advance.
Yes, the module is now updated but haven't made it to the app store yet. Here is the link to the new version: Direct link to 2.4 version
http://virtocommerce.blob.core.windows.net/catalog/Altsoft.ShopifyImport_2.4.0.zip
I download the Mobile First Platform fix pack(6.3.0.0), It contain the 6.3.0.0-MFPF-Pattern-IF201503120508.zip, when it unzip this, I found it's for app-center and analytic console fix pack, but I am not able to find the repository.config or diskTrag.inf file to add InstallManager's repository.
Could anybody can tell me how to install this fixpack.
Thanks
Kumaresan
6.3.0.0-MFPF-Pattern-IF201503120508.zip is the Virtual application pattern installer. Here is the link to install MobielFirst Platform Application Pattern Type
But unless you are using the MobileFirst Platform Application Pattern Type, you do not need this.
To install the MobileFirst Platform Studio latest ifix, you need the 6.3.0.0-MFPF-StudioP2-IF201503120508.zip and the instructions are available here.
To install the MobileFirst Platform Server latest ifix, you need the 6.3.0.0-MFPF-Server-IF201503120508.zip and the instructions are available here.
If you want to install the fixpack in a production environment, please see instructions here.
Recently, I've wanted to deploy OpenERP and also, recently, I learned about Heroku.
I thought about how to deploy OpenERP on Heroku and it came to me that there's no python package for OpenERP.
So I thought about learning how to create python packages and then package up OpenERP for my personal use on GitHub or Launchpad (because OpenERP uses Launchpad and bazaar) and then, if it is useful, submit it to PyPI.
But, first, I'll check with the rest of the world. here for some advice.
Would you recommend me to take this route?
Would it be beneficial to the OpenERP community?
Would it be a wise method of deployment, through a python package?
What are the reasons that the official python packages on PyPI have been abandoned?
OpenERP already has packages and bundles for different O/Ses available. I would advise against creating one specifically for PyPI.
If you create one, please, please commit to maintaining it. If you don't, it too will be abandoned.