Hello Stack Overflow Community,
i want to use a multiple store infra structure and i decided to use Magento. i looked for a composer installation and i found one. So i installed Magento. the problem is that i used Magento 2 in version 0.74.0-beta16.
My question: Can use this version for production instead of Magento 1. The release plan (http://www.mag-tutorials.de/magento-2-release-plan/) says, that at the beginning 2016 Magento 2 to will be officially release. And the functionality is tested by Unit Tests, so the already existing functionality must be guranteed expect some special cases.
You cannot use Magento 2 in production at this time because payment doesn't work. The release is scheduled for November and you should be able to use it then.
Related
I'm following the official tutorial to update a theme from 7.0 to 7.2 https://help.liferay.com/hc/es/articles/360029316831-Running-the-Upgrade-Task-for-7-0-Themes, the process is successful but I need to update to liferay 7.4 and I can't find official documentation or information on how to continue from here, I try to deploy the war on my local server with 7.4 but it says which is not compatible with this version of Liferay. Can someone guide me?
There are 5 years between Liferay 7.0 and 7.4 - and a lot has changed in the frontend world. I'd suggest you either just create a new theme, or (better) check if just using a stylebook with a stock theme is sufficient. A stylebook should be a lot easier to migrate to future versions than a full theme.
I believe that it's technically possible to upgrade a theme, but wouldn't bother doing so. As you have an existing theme, it should be relatively quick to get to where you need to be - plus you'll have the opportunity to make those little adjustments that you likely had an eye on for the past couple of years.
I had two different Magento stores running on Magento 1.9 each on a separate installation. I have upgraded one to Magento 2 which is running fine. Is it possible to now upload/convert the old website (still on Magento 1.9) to this new Magento 2 installation as a separate store.
It's unlikely that this is possible to upload/convert in a simple way. If there are a lot of data (categories, products, cms blocks and pages, customers) you could try to use official migration tool or write a custom scripts by yourself.
Magento 2 is completely different to Magento 1, it is a complete rebuild of the platform; unfortunately there is no quick and easy way to convert your old M1 site to M2. There are 3 essential areas to cover:
Template
Functionality
Data
Your templates will need to be rebuilt as well as any custom or 3rd party modules, however there are a fair few extensions out there you can leverage. Finally, and the most volatile, is your data, I suggest using the official migration tool or use a data transfer service such as Cart 2 Cart to migrate the data from M1 to M2.
I know some people are using it (PyroCMS) but is CodeIgniter 3.0 complete and ready to be used in production?
I have been using CodeIgniter for many years and although I know it seems to be languishing at the moment it is just so easy to use.
UPDATE: The title of this question used to be "Is CodeIgniter 3 finished?". By this, I meant, is CodeIgniter complete and ready to use in production (not is it dead).
Update:
Version 3 completed on March 30, 2015. See CodeIgniter - Change Log
Original Reply:
No, it's not finished. When it is - you'll see the release announcement on the EllisLab website.
Contrary to what is said in the comments though, this doesn't depend on the issues pending on github and it's not dead either.
Codeigniter is now owned by the British Columbia Institute of Technology.
As of January 26, 2015, the Codeigniter 3.0rc release candidate, its documentation, and relevant changelogs are availble here.
Codeigniter 3.0.1 is now fully compeleted.
you can see changelog here:
http://www.codeigniter.com/userguide3/changelog.html
and Codeigniter 3.1 is in development!!!
Codeigniter has now released 3.0 Candidate version
http://www.codeigniter.com/download
CodeIgniter 3.x is the branch under active development.
A few issues remain to be resolved, and it will not be released until those are put to bed. Version 3 is almost ready for prime time, and many sites are actually using it in production already.
angularjs routing is enabled.
I noticed in the Magento Certified Developer Study Guide, under the Database section one of the items mentioned is "Write downgrade (rollback) scripts".
I've done some searching to see whether downgrade scripts are supported and it seems they are not. I found this thread from earlier this year in which it seems they concluded that downgrade scripts weren't supported at that time.
Also, did some searching on google and found this article discussing what appears to be some initial support for rollback scripts in the core.
I also searched under app/code/core/Mage for "rollback" and "downgrade" and pretty much most of what I found was code related to DB transaction rollbacks.
Why would the study guide be talking about this if it's not supported? I must be missing something.
Current versions of Magento have no implementation for rollback database migration scripts, where rollback means identifying that a module version number has decreased and running an appropriate script.
Remember through, you're looking at a study guide, not a manual.
While there's no support for formal rollbacks in the current version of Magento, as a Magento developer you may need to rollback database changes made in a previous module upgrade. I'd be ready for questions that describe that scenario, with answers that test your knowledge of existing Magento functionality.
It's here:
Mage_Core_Model_Resource_Setup::applyUpdates() Available, at least, from Magento 1.3.
I am pretty new to Virtuemart and now I do have to set up my first Webshop for a Customer.
As there is already a Virtuemart 2 Version I am now not shure which Version to take.
Well I think I am going to use VM1, because it is stable. But now I am asking myself:
What are the advantages/features of VM2?
Are there already Plugins out there for VM2? (Because I assume that
they'll need to be rewritten for VM2)
When can I expect a stable version of VM2?
Do you already have experience with VM2?
Advantages/features of VM2
For faster and more secure programming they use now more abstract classes.
Completly redesigned table layout.
Added hooks for plugins (own views, own customer number system, and so on,...), look in the wiki for more information ( http://dev.virtuemart.net/projects/virtuemart/wiki/Plugin_system )
Added registering while checkout
New backend design
Hardened against hackers
New js (jQuery to avoid Mootools incompatibility problems)
Customfields for the computer/pizza configurator
Real multicurrency, real currency format defined by currency
Prices displaying configurable by shoppergroups (also rounding)
Various sorting and searching options
Update system using Akeeba Release System (ARS, more information akeebabackup.com/software/akeeba-release-system.html)
Extensions for VM2
The extensions directory contain a lot of extensions for VM and some were updated for VM2 ( http://extensions.joomla.org/extensions/extension-specific/virtuemart-extensions )
Stable version of VM2
There is no clear data about this now. The current version at the moment is a release candidate which means a sable version is coming soon after sufficient users and developers test it and report the bugs.
Experience with VM2
I've used VM1 and migrated two websites for VM2 before. VM2 definitely worth the try, templates is way much better than the old table based ugly coded layout. Everything is perfect except if you are going to use Joomla 1.6 The modules does not work without glitches. Other that it's working with Joomla 1.5 perfectly.
Try Virtuemart 2 only if you are not planning to use any custom shipping module like canada post or UPS.
Or have enough knowledge to build it on your own.
VM2 performs shipping and payment system using plugin and trying hard to follow MVC structure of joomla.which is still under development.
Unless, VM2 is great and flexible.