Magento 2 stable was released in November 2015 and from that moment onwards, the market is slowly crossing over from Magento 1 to Magento 2. With MageBridge being focused mainly on Joomla administrators that are not Magento 2 developers, our conclusion is that it will only be worth migrating to Magento 2 if the majority of the Magento 1 extensions is already available for Magento 2. Estimations range that this majority will be migrated towards the end of 2017.
Definitely, we will convert some of the code of MageBridge to be compatible with Magento 2. But if little Magento 2 extensions are actually available, little benefit will you get when trying to integrate Magento 2 into Joomla. We can't be 100% certain that all MageBridge functionality of Magento 1 will also be available under Magento 2. The first MageBridge functionality we will work is remote authentication and user synchronization, the last thing that will be worked on (if at all) is visual integration. We will update this FAQ when things are progressing.
Please note that Magento 2 is not Magento 1. Magento 2 will require a complete migration to start with and it will also require the presence of a senior developer to help you with customization and maintenance. This makes Magento 2 a high-fetch for an average Joomla administrator. Make sure to consider your options.
PHP 5.3 has been declared obsolete since August 2014 - it really is outdated and should not be used. All our extensions are tested and built for PHP 5.6 and higher. Performance wise, we recommend Magento shops to run on PHP 7.
Some code might still work under PHP 5.5 and earlier. One of the changes we have made is to use the <?= tag in PHTML templates. Contrary to what some believe, this is not a bad practice: The short echo tag <?= is not part of the short open tags, it is part of the PSR-1 standard, part of the Magento coding standard, considered a best practice by many PHP developers and actually enabled all the time in PHP 5.4 or higher. Under PHP 5.3 though, it is part of the PHP setting short_open_tag which should, therefore, be enabled.
We are currently working on implementing various features that definitely will require PHP 5.4 - traits, short array syntax. So we recommend you to work on upgrading PHP instead of hacking our code to make it work on outdated PHP environments. Additionally, our Magento 2.2 code will only work under PHP 7.
Yes. But this question is one that we believe that you as a merchant or developer should answer in a more proactive way. Magento 184.108.40.206 has brought many changes into the core, thus requiring extensions to be made compatible with this new version, if that was not the case already. There has been a community effort to list which extensions are compatible with Magento 220.127.116.11 and which not. Yireo was the first extension provider to be on this list, and also the first to have all its extensions listed as compatible.
The list is here: https://docs.google.com/spreadsheets/d/1LHJL6D6xm3vD349DJsDF88FBI_6PZvx_u3FioC_1-rg/. Instead of resorting to our own FAQ, we recommend you use this spreadsheet at all times, because this way you are not dependent on the answers of extension providers, but you can again take control of your shop.
Yes. Please note that Magento 18.104.22.168 brought in major changes, that were breaking backwards compatibility. Magento 22.214.171.124 does not.
We will announce news on specific Magento versions as they are released. However, do not simply take the word of extension developers (like us) for granted. When they say that their extension is compatible with Magento version 1.x.x.x, naturally they are refering to the core. You are not running just the core. You are running additional extensions and a custom theme. If you want to know if a certain extension can be upgraded safely, do not do this directly on your production site, but setup a testing site and test things there until you (and not somebody else) know for sure that this works.
If you are asking this for a paid extension, that you have purchased in the past, the question is impossible to answer. We don't maintain old versions of extensions to be compatible with future Magento versions. In short, if you want to make sure your Yireo extension (with an outdated version) works with a modern Magento version, the solution is to upgrade. Our subscriptions offers automatic discounts on renewals, plus they are low priced. Upgrading is a bargain.
MageBridge is fully open-source. Note that MageBridge uses dual-licensing, because it has extensions in either Joomla! or Magento: For Joomla!, the GNU/GPL is applied. For Magento, the OSL is applie. We offer Subversion-access to all sources.
In general, every Magento extension that works under Magento also works in MageBridge. Note that MageBridge is not a different platform, but it is a Magento storefront wrapped inside the Joomla! CMS. Any Magento extension works in MageBridge, just like it would in Magento standalone. However, the bridging brings along some specific problems, if the Magento extension is badly coded.
For instance, MageBridge makes heavy use of the difference between the Base URL, the Base Skin URL and other Base URLs. If a Magento extension is not following standards, this might lead to 404 errors. The developer of this Magento extension should fix these bugs.
Also, many Magento extensions make use of ProtoType and Scriptaculous (actually Magento itself does as well), which does not work together with MooTools (used by a lot of Joomla! extensions). MageBridge is not able to solve this conflict, but gives you all the tools to avoid such a conflict.
This depends on what you want. All the MageBridge PHP-sources are made available under the GNU/GPL and are available for free on our Subversion server. However, you will need to construct your own packages from source and if you're not a PHP-developer, this is not ment for you. If you want to receive MageBridge packages and support, you are required to purchase a support-subscription.
You can use MageBridge for free by checking out the Subversion-sources - this is ment for developers, and allows developers to use MageBridge without any costs. If you want our support, you will need to purchase a support subscription.
Magento Go is a platform of Magento that should not be compared to Magento Community, Magento Professional or Magento Enterprise. It only supports a limited set of third party extensions, and does not support extensions that offer dramatic changes like MageBridge does. Please refer to the Magento Go FAQ for information on what kind of extensions you can actually use.
Yes, you can. A valid MageBridge Support Subscription gives you the right for support and to receive easy updates for all MageBridge extensions using the MageBridge update-servers. This means that you can download or upgrade the MageBridge extensions until the subscription expires. After this, you can still use the software but updates will not be available anymore through the MageBridge update-servers. Also, the download-folders of MageBridge on our site will become unavailable to you. Nothing stops working on your site. Note that you can also still receive updates by checking out the free sources from Subversion.
Yes, it is. Magento Enterprise Edition uses the same code-base as Magento Community Edition plus some extra additional Enterprise-modules. We fully support the usage of Magento Enterprise Edition. Please note that you can only manually install MageBridge in Magento Enterprise (through a file-patch) because the downloader-application is not available in Magento Enterprise.
You can use MageBridge on an unlimited number of domains. However, if you want us to support a domain and/or if you want to receive updates from our MageBridge update-server, you will need a valid MageBridge support subscription.
The MageBridge Standard subscription allows you to receive support and updates for 2 hosts; the MageBridge Enterprise subscription allows you to receive support and updates for 6 hosts. You can still copy sources to cover more domains, but you will be unable to use the MageBridge Update Manager for that.
Please check the MageBridge System Requirements for details.
All source code of MageBridge are distributed under an open source license and can be changed without problems. Please note that all of our source code includes our copyright, and the used open source licenses (GNU/GPL OSL) forbid the removal of this copyright.
Yes and no: It depends if we are talking about the same thing. Within Magento the multi-site mechanism is implemented through three different store-types: Websites, Store Groups (also simply called Stores) and Store Views.
MageBridge itself only allows you to configure one Magento Website in one Joomla! website - this makes sense, because this is the way the multisite-architecture was ment. In most cases this is just fine. For multi-lingual content, MageBridge supports Joomla! core multilinguality, Joom!Fish and others out-of-the-box and allows them to connect to different Store Views.
Yes, you can, you even have to. As soon as you have purchased a MageBridge Support Subscription, you need to configure the domains within your Yireo Account settings under Software Subscriptions. Our documentation guides you through this process. Afterwards, you can always modify the domains as you as fit. We only monitor these changes to prevent abuse - common-sense changes are allowed, 10 changes a day are not.
No, MageBridge is not being sold as a product, so therefor there is no option for reselling either. What Yireo offers, is MageBridge Support Subscriptions that give either you or your custome our support and updates.
See the MageBridge Refund Policy for more details.
For various Joomla! templates, we have developed special CSS-modifications that allow you to easily integrate MageBridge with that template. Every month we try to release new template-patches for popular templates of RocketTheme and YOOtheme. All template-patches are listed on the MageBridge templates-patches page. If a template is not listed there, we have not developed a patch for it.
These template-patches are not a requirement to use MageBridge. When you built a custom Joomla! site, you probably will need to modify CSS-code somehow, and not having MageBridge template-patch for your specific template, simply means that you will need to modify your own CSS-code to your own needs. With the base MageBridge CSS-code you have a good start anyway.
If your support subscription expires, renewing your subscription is optional. You can purchase a new MageBridge Support Subscription on the Plans & Pricing page.
Setting up a MageBridge-based website requires a good knowledge of Joomla!, Magento and MageBridge. Currently, Yireo does not act as an implementation parter - we don't build any entire sites. We do offer some precisely defined services, which might be of help, though.
On this site, you can find various patches for popular templates from RocketTheme, YOOtheme and JoomlArt. We offer these patches as a kickstart to get you going with template-design. If you choose a Joomla! template, most likely that template has never heard of the concept of MageBridge, unless the template is listing MageBridge as a supported extension. Therefor you will need extra styling to add the look & feel of the choosen Joomla! template to MageBridge. With our template-patches some of this work is already done. Ofcourse, no Joomla! website could ever be built without proper webdesign, and the same applies to MageBridge.
A demo of the template-patches can be found here: templates.magebridge.com
No, it doesn't. MageBridge doesn't modify the core of either Joomla! or Magento. Most features are implemented by using the available APIs and event-systems.
A warning has to be issued regarding the Magento-extension. Magento allows core-classes to be overridden by third-party-classes, and MageBridge uses this trick to fetch data needed from Magento which could normally not be fetched. For instance, the breadcrumb-class only allows for fetching HTML, not the data-array that lies underneath. The MageBridge override adds a method to the class that does fetch this data-array. Note that these modifications are not core-hacks, but adaptions of the override-technology offered by Magento.
Multi-currency is totally independant from the multi-site mechanism, and is configured per store. Because one Magento store is brought to one Joomla! site, this just works - just like many other Magento features.