News & Ankündigungen
Update 2026-01
We are working on new modules and solutions!
FAQ Module
FAQ / Troubleshooting – Module
Here we answer your questions about our modules!
How do I get my license?
Once we have installed the module and the license invoice has been settled, we activate the full license with the installation. If the license invoice has not yet been settled, activation occurs upon booking your payment of the invoice.
For self-installation, we need a brief notification including the module number and the system key visible in the header area of the modules sent to lizenzen@xycons.de; if the payment has been made, we will activate the license and you will receive a confirmation email. Activated licenses must then be adopted into your shop via the module's "Check activation" button. No license code will be sent; activation is done online.
For self-installation, we need a brief notification including the module number and the system key visible in the header area of the modules sent to lizenzen@xycons.de; if the payment has been made, we will activate the license and you will receive a confirmation email. Activated licenses must then be adopted into your shop via the module's "Check activation" button. No license code will be sent; activation is done online.
What is the module environment (module framework)?
We currently offer about 120 modules. All or almost all modules share commonalities. For example, all or almost all modules use certain routines and functions. Instead of repeatedly integrating these into each module, we have packed these reusable parts into a so-called "module environment," also called a "module framework." The module environment is thus the functional environment for all modules and contains processes, functions, and source code that the modules repeatedly need and are therefore centrally stored to save space.
You can and must download the module environment together with the module from us and install it at least once, preferably before installing the module. The module then automatically uses the function library provided in the module environment. Also update the module framework when you install an update for a module or a new module.
You can and must download the module environment together with the module from us and install it at least once, preferably before installing the module. The module then automatically uses the function library provided in the module environment. Also update the module framework when you install an update for a module or a new module.
My license is shown as invalid or cannot be loaded!
After a module or shop update, it can happen that the license cannot be loaded or is declared invalid. In this case, clear the entire content of the "Your license key" field in the affected module and save the field empty.
The module will then automatically retrieve the license key again; usually, this resolves the problem.
The module will then automatically retrieve the license key again; usually, this resolves the problem.
After installation, only a test license is shown, although I purchased the full version?
Full licenses for modules must be explicitly activated by us. Activation depends, among other things, on the license invoice being settled.
The same applies to service installations by us or when installing a paid upgrade version. If you have paid the full version or upgrade directly with an immediate payment method, a test license will initially be created during self-installation. Please refer to the point above "How do I get my license" regarding this.
The same applies to service installations by us or when installing a paid upgrade version. If you have paid the full version or upgrade directly with an immediate payment method, a test license will initially be created during self-installation. Please refer to the point above "How do I get my license" regarding this.
After a module update, a test license is shown?
If the module, module framework, or shop has been updated, the module checks the environment and may revert to a test license.
Clear the "Your license key" field in the affected module and save it empty.
The module will then fetch the current license information directly from our server.
If the module still shows a test license after this process, it may be that you updated to an upgrade version of the module, which should have been clearly indicated when downloading the new version.
Upgrade versions are paid and represent an extension of the previous license.
We usually provide updates free of charge, but if the effort to adapt to a new shop version exceeds certain limits, we offer these new versions as "upgrade" versions. You can purchase this subsequent version and license extension in our shop; prices are moderate and serve to refinance the effort we provide for necessary adaptations beyond certain limits to new shop versions. After purchasing the upgrade, we activate the license for the new shop version range.
Clear the "Your license key" field in the affected module and save it empty.
The module will then fetch the current license information directly from our server.
If the module still shows a test license after this process, it may be that you updated to an upgrade version of the module, which should have been clearly indicated when downloading the new version.
Upgrade versions are paid and represent an extension of the previous license.
We usually provide updates free of charge, but if the effort to adapt to a new shop version exceeds certain limits, we offer these new versions as "upgrade" versions. You can purchase this subsequent version and license extension in our shop; prices are moderate and serve to refinance the effort we provide for necessary adaptations beyond certain limits to new shop versions. After purchasing the upgrade, we activate the license for the new shop version range.
I want to test the trial version a little longer than the intended 14 days!
When you install a module from us, a 14-day trial version is initially available.
Usually, 2 weeks from installation should be enough to check and test the module. If you need to extend this period by a few days, please contact us with a short email including the module number and the shop key visible in the module header.
Usually, 2 weeks from installation should be enough to check and test the module. If you need to extend this period by a few days, please contact us with a short email including the module number and the shop key visible in the module header.
I receive an IonCube error message after installation
If you have installed or updated the module and/or the module environment, you may rarely see such or similar error messages with the following format and content:
The DATEINAME was encoded by the ionCube Encoder for … and cannot run under … or later.
Please ask the provider of the script to provide a version encoded with the ionCube Encoder for <...>
The cause here is an incorrect IonCube version. Check your PHP version and ensure via your host that the IonCube version matches the PHP version used. Use IonCube version 13.x.x or higher.
The DATEINAME was encoded by the ionCube Encoder for … and cannot run under … or later.
Please ask the provider of the script to provide a version encoded with the ionCube Encoder for <...>
The cause here is an incorrect IonCube version. Check your PHP version and ensure via your host that the IonCube version matches the PHP version used. Use IonCube version 13.x.x or higher.
No menu entry appears after installation
If you do not see a "Xycons-Module" menu entry in the backend after installation, proceed as follows:
Clear the caches explicitly in this order: module cache (2nd entry), text cache (7th entry), and then the page cache (1st entry).
The new menu should now appear. If not, there may be a fundamental problem in your shop.
If you - when it was still possible - deleted the English language, this indicates a fundamental problem. Such shops often have a favorites menu simply called "FAVS" that does not really work. The shop has a basic problem due to the missing language, which prevents and disrupts the addition of new menu entries.
Contact Gambio support and have the missing language restored, even if you do not use it. This problem occurs, among other things, when installing add-ons and modules, but your shop probably logs many error messages in the log files because the missing language also has effects here. The missing language problem also becomes clear when creating new admins; they cannot log into the admin area and receive a message indicating missing language data. Once the missing language and thus regular function are restored, the added menu entries will also appear correctly again.
Clear the caches explicitly in this order: module cache (2nd entry), text cache (7th entry), and then the page cache (1st entry).
The new menu should now appear. If not, there may be a fundamental problem in your shop.
If you - when it was still possible - deleted the English language, this indicates a fundamental problem. Such shops often have a favorites menu simply called "FAVS" that does not really work. The shop has a basic problem due to the missing language, which prevents and disrupts the addition of new menu entries.
Contact Gambio support and have the missing language restored, even if you do not use it. This problem occurs, among other things, when installing add-ons and modules, but your shop probably logs many error messages in the log files because the missing language also has effects here. The missing language problem also becomes clear when creating new admins; they cannot log into the admin area and receive a message indicating missing language data. Once the missing language and thus regular function are restored, the added menu entries will also appear correctly again.
I get an error message when clearing the module cache, sometimes also in the module setup
Rarely, a multi-line error message may appear in the shop backend starting as follows:
Fatal error: Uncaught Error: Class 'GXCoreLoaderSettings' not found in…
This is a problem of the shop itself. The "Clear cache for module information" option reloads all so-called class libraries of the shop and modules, and our modules also trigger this action in the background after updates to reload or initially include their own class libraries.
The error also occurs sporadically in shops without modules and add-ons. The problem is known to Gambio but is very hard to find, quite rare, and currently still open and present; it is not caused by the module or its presence. You can practically reproduce the error in any shop from version 3.14 by repeatedly clearing the mentioned cache; eventually, you will get the error message. The error is not critical. Once you get the error message, press "F5" once, twice, or more to reload the page – which triggers the cache clearing again – and then the issue disappears and it works again.
The problem only occurs in the backend when using this cache clearing option; ongoing operation or the frontend are not affected.
From shop version 4.2.x.x onwards, this problem should be fixed by Gambio and no longer occur.
Fatal error: Uncaught Error: Class 'GXCoreLoaderSettings' not found in…
This is a problem of the shop itself. The "Clear cache for module information" option reloads all so-called class libraries of the shop and modules, and our modules also trigger this action in the background after updates to reload or initially include their own class libraries.
The error also occurs sporadically in shops without modules and add-ons. The problem is known to Gambio but is very hard to find, quite rare, and currently still open and present; it is not caused by the module or its presence. You can practically reproduce the error in any shop from version 3.14 by repeatedly clearing the mentioned cache; eventually, you will get the error message. The error is not critical. Once you get the error message, press "F5" once, twice, or more to reload the page – which triggers the cache clearing again – and then the issue disappears and it works again.
The problem only occurs in the backend when using this cache clearing option; ongoing operation or the frontend are not affected.
From shop version 4.2.x.x onwards, this problem should be fixed by Gambio and no longer occur.
How do I learn about updates and where do I get updates for my modules?
You receive updates via your customer account with us at www.xycons.de. There you will also find downloads for all already licensed modules in the "Your Account" area. Basically, you also receive all updates, downloads, and information in our shop on the respective module page and on the TAB "Downloads," which appears when you are logged into your customer account.
Information about available updates and newer versions can also be found in the respective header area of the module setup in your shop under the link "Show Xycons updates": When you apply a new version or update, proceed as described for a regular installation. Updates released by us must be installed by yourself, but of course, we can also perform these as a commissioned installation for you.
Information about available updates and newer versions can also be found in the respective header area of the module setup in your shop under the link "Show Xycons updates": When you apply a new version or update, proceed as described for a regular installation. Updates released by us must be installed by yourself, but of course, we can also perform these as a commissioned installation for you.
What are upgrades?
Regular updates with corrections or new features for the respective module are provided free of charge to holders of a full license. Our modules must also be checked and usually adapted for compatibility with each new shop version to work and function with new versions of the shop. If this adaptation effort does not exceed certain limits, we provide free updates for download and self-installation. However, if certain effort limits are clearly exceeded to make the module compatible with a new shop version and to work again with the technical changes delivered by Gambio with the new shop version, we release so-called "upgrades." These are moderately priced and extend the usage scope of the respective module to the new shop version.
With upgrades, we involve you as a module user in the development costs that arise when the module should continue to work with new and significantly changed shop versions. The need for upgrades is rare but depends especially on the extent of changes Gambio makes in the shop itself for a new version and how much effort it takes us to adapt the modules. "Upgrades" can be purchased as needed on the respective module page in our shop to use the module again in the new shop version. You will find the upgrades as variants of the offered module directly where you also purchased and commissioned the first module license.
With upgrades, we involve you as a module user in the development costs that arise when the module should continue to work with new and significantly changed shop versions. The need for upgrades is rare but depends especially on the extent of changes Gambio makes in the shop itself for a new version and how much effort it takes us to adapt the modules. "Upgrades" can be purchased as needed on the respective module page in our shop to use the module again in the new shop version. You will find the upgrades as variants of the offered module directly where you also purchased and commissioned the first module license.
There are updates or upgrades for the module, does something need to be installed?
Yes! Suppose your module was installed when the shop had version 3.14.x.x. The module and the simultaneously installed module environment matched this version.
If you now update the shop to the next version, the installed modules in your shop do not change automatically. Not even if the module page now indicates a compatibility range like "3.14.x.x – 4.0.x.x" instead of just "3.14.x.x," because this range always refers only to the version you can currently download from us.
When your module was installed, this compatible subsequent version (e.g., for 4.0.x.x) did not yet exist, and the module installed with you is still in this state. You may therefore need to download the update / subsequent version from us and install the new module version immediately before or after the shop update so that it fits the new version range. Don't forget to also update the module environment accordingly; the same applies here!
With every module update or new module, also install the (new/appropriate) module environment, which is backward compatible with the respective predecessor.
If you now update the shop to the next version, the installed modules in your shop do not change automatically. Not even if the module page now indicates a compatibility range like "3.14.x.x – 4.0.x.x" instead of just "3.14.x.x," because this range always refers only to the version you can currently download from us.
When your module was installed, this compatible subsequent version (e.g., for 4.0.x.x) did not yet exist, and the module installed with you is still in this state. You may therefore need to download the update / subsequent version from us and install the new module version immediately before or after the shop update so that it fits the new version range. Don't forget to also update the module environment accordingly; the same applies here!
With every module update or new module, also install the (new/appropriate) module environment, which is backward compatible with the respective predecessor.
I installed a trial version. Do I need to reinstall anything for the full version?
No, if you want to license the trial version, you do not need to reinstall.
We can activate a full version from any trial version. Trial versions are actually full versions but are time-limited and otherwise have almost the full functionality. Only very few modules are functionally limited, e.g., in the number of runs or processable records, because trial versions are not intended to be quickly used, enjoyed, and then uninstalled.
We can activate a full version from any trial version. Trial versions are actually full versions but are time-limited and otherwise have almost the full functionality. Only very few modules are functionally limited, e.g., in the number of runs or processable records, because trial versions are not intended to be quickly used, enjoyed, and then uninstalled.
How do I get rid of info messages from modules whose test license has expired?
If you installed a module for testing or trying out and do not want to purchase the full license, the test period expires 14 days after installation, and the module can no longer be enabled or used. After expiration, the module reminds you with prominent backend info to purchase the full version.
If you do not intend to do so, you should remove the module according to the uninstallation instructions. This will also remove the messages.
If you do not intend to do so, you should remove the module according to the uninstallation instructions. This will also remove the messages.
Can I update to every new shop version and what should I consider?
Gambio releases two different types of updates:
Master updates and so-called feature updates.
We support the "master update versions" and only provide updates for these if applicable.
The basis is the versioning system introduced in 2015 here.
Master versions are defined as stabilized versions with no technical changes and include all changes from the immediately preceding feature version, which have been stabilized. You can recognize master updates by an even number in the second digit of the version number: 3.14.x.x was such a master version, as was 4.0.x.x – or simply by the name "master update." Service packs following master versions with further corrections are uncritical and appropriate; they change the third and fourth version digits.
Feature versions are more critical and are not explicitly supported by us. They may work but might not. In these versions, Gambio restructures the shop, introduces new technologies, removes processes and old technologies, and usually makes very significant and massive changes. These may be delivered in several time-staggered partial releases. The focus is on the changes themselves and on new features. Further changes in this feature cycle may be based on user feedback. You can recognize these versions by an odd second version digit: 3.15.x.x was a feature version, as was 4.1.x.x. These feature versions and the associated significant changes to the shop are also the reason why all add-ons and our modules must be completely rechecked, modified, and adapted to the changes coming from Gambio. You may know this issue from interfaces, modules, or your own modifications – in short, from everything not directly from Gambio.
With currently over 70 modules, providing updates for these feature versions would be impossible because the target is moving. While making adjustments, the next feature pack arrives, and the world turns again. Therefore, we only consider these feature update changes once Gambio announces the next master update, i.e., "closes the lid" and proceeds to correct reported problems and packages the master update, which includes all changes from the recent change cycle and will no longer change but only be corrected. At this point, we adapt our modules and develop the necessary updates or, in case of very massive changes, upgrades.
We need some time for this, so subsequent versions are not immediately available but after the release of a master update by Gambio. We therefore recommend focusing on master versions when using modules or add-ons and checking before updating whether corresponding new versions are available. If you use or update to a feature version and our modules no longer work, you can only remove them and wait for the version compatible with the following shop master version. Module versions that fit only pure feature versions of the shop are not provided by us.
Master updates and so-called feature updates.
We support the "master update versions" and only provide updates for these if applicable.
The basis is the versioning system introduced in 2015 here.
Master versions are defined as stabilized versions with no technical changes and include all changes from the immediately preceding feature version, which have been stabilized. You can recognize master updates by an even number in the second digit of the version number: 3.14.x.x was such a master version, as was 4.0.x.x – or simply by the name "master update." Service packs following master versions with further corrections are uncritical and appropriate; they change the third and fourth version digits.
Feature versions are more critical and are not explicitly supported by us. They may work but might not. In these versions, Gambio restructures the shop, introduces new technologies, removes processes and old technologies, and usually makes very significant and massive changes. These may be delivered in several time-staggered partial releases. The focus is on the changes themselves and on new features. Further changes in this feature cycle may be based on user feedback. You can recognize these versions by an odd second version digit: 3.15.x.x was a feature version, as was 4.1.x.x. These feature versions and the associated significant changes to the shop are also the reason why all add-ons and our modules must be completely rechecked, modified, and adapted to the changes coming from Gambio. You may know this issue from interfaces, modules, or your own modifications – in short, from everything not directly from Gambio.
With currently over 70 modules, providing updates for these feature versions would be impossible because the target is moving. While making adjustments, the next feature pack arrives, and the world turns again. Therefore, we only consider these feature update changes once Gambio announces the next master update, i.e., "closes the lid" and proceeds to correct reported problems and packages the master update, which includes all changes from the recent change cycle and will no longer change but only be corrected. At this point, we adapt our modules and develop the necessary updates or, in case of very massive changes, upgrades.
We need some time for this, so subsequent versions are not immediately available but after the release of a master update by Gambio. We therefore recommend focusing on master versions when using modules or add-ons and checking before updating whether corresponding new versions are available. If you use or update to a feature version and our modules no longer work, you can only remove them and wait for the version compatible with the following shop master version. Module versions that fit only pure feature versions of the shop are not provided by us.
I want to have the shop updated, but my service provider complains about the existing module!
If you use module(s) from us, they are secured via "IonCube" and only work on systems that have the server extension "IonCube."
Some service providers have a supposed problem when they create a copy of the shop on their own systems to test the effects of the update before applying it to the live shop. They may therefore refuse to perform the update or require clarification because they do not have a system with the free "IonCube" extension.
This can be easily solved by deleting the entire folder /GXModules/Xycons in the created copy and clearing the cache, as described in the documentation for removing all modules. After that, the copy also works on test systems without "IonCube."
Later in the live system – where IonCube is available for the module – this problem does not exist. After the shop update, the module and its module environment must also be updated. You can do this yourself using the downloads we offer, have your service provider do it, or contact us for an update.
Alternatively, you can contact us directly for upcoming shop updates to have all work done in one go; our test systems naturally all have "IonCube," and you get everything from one source. But always check BEFORE the update whether the modules are compatible with the new shop version or if updates are available.
Some service providers have a supposed problem when they create a copy of the shop on their own systems to test the effects of the update before applying it to the live shop. They may therefore refuse to perform the update or require clarification because they do not have a system with the free "IonCube" extension.
This can be easily solved by deleting the entire folder /GXModules/Xycons in the created copy and clearing the cache, as described in the documentation for removing all modules. After that, the copy also works on test systems without "IonCube."
Later in the live system – where IonCube is available for the module – this problem does not exist. After the shop update, the module and its module environment must also be updated. You can do this yourself using the downloads we offer, have your service provider do it, or contact us for an update.
Alternatively, you can contact us directly for upcoming shop updates to have all work done in one go; our test systems naturally all have "IonCube," and you get everything from one source. But always check BEFORE the update whether the modules are compatible with the new shop version or if updates are available.
I have a custom template/theme, does it fit?
Usually it fits, but not always. Our modules implement their frontend integration based on the standard templates "Honeygrid" and standard themes "Honeygrid" or "Malibu," and all adjustments are made accordingly. If you use a modified template or theme, displays may need to be modified or individually adjusted due to your modifications, as the inheritance of formatting elements may cause misalignment because they do not account for your explicit changes, which affect and change other elements on the page.
This coordination of your individual changes with the module elements is usually done by your supervisor who implemented the changed appearance for you, as he/she knows what was changed where. Alternatively, we can perform these tasks on request.
This coordination of your individual changes with the module elements is usually done by your supervisor who implemented the changed appearance for you, as he/she knows what was changed where. Alternatively, we can perform these tasks on request.
Old USERMODS are reported in the module that should no longer exist!
Our modules follow the implementation guidelines of Gambio.
Until shop version 3.8, it was basically possible to create so-called "USERMODS" for necessary template changes, i.e., files with the same name as the template file but extended by the suffix "-USERMOD"; these contained changed content based on the original file. The shop used this special file instead of the original file if it existed.
Since the introduction of the "GXModules" implementation concept with shop version 3.8, this old form of modification is deprecated and only works for compatibility reasons – and will soon be removed. Modifications are now made via so-called "BLOCK" changes. Each area in the template has its own name (BLOCK) and can be specifically modified by name via files located in the /GXModules folder hierarchy.
This means no changed copy of the entire file is needed anymore; instead, one of the many BLOCK sections of the original file is modified. This allows multiple independent changes to be made sequentially from different needs. Our modules have been implemented following this Gambio concept from the start. Old or still existing USERMODS still work but ultimately overwrite ALL regular changes made via BLOCK modifications. Even Gambio delivers such changes as BLOCK modifications via GXModules.
Our modules check the BLOCK changes necessary for the module in the template/theme and report old USERMODS that may still be found for these files because they may override the modification. These files will very likely cause problems because after the module has made its required BLOCK changes based on the original file, a USERMOD comes along and overwrites this and the original file with old content and a full copy that was created in a shop version and is probably outdated. This may cause the module not to display and possibly other effects because the USERMOD is based on an older shop version.
Please take care of these USERMODS and have them rewritten into BLOCKs so that changes can complement each other and you do not use full copies of old files in the system, which will soon no longer be supported. Contact us if needed to solve this issue.
Until shop version 3.8, it was basically possible to create so-called "USERMODS" for necessary template changes, i.e., files with the same name as the template file but extended by the suffix "-USERMOD"; these contained changed content based on the original file. The shop used this special file instead of the original file if it existed.
Since the introduction of the "GXModules" implementation concept with shop version 3.8, this old form of modification is deprecated and only works for compatibility reasons – and will soon be removed. Modifications are now made via so-called "BLOCK" changes. Each area in the template has its own name (BLOCK) and can be specifically modified by name via files located in the /GXModules folder hierarchy.
This means no changed copy of the entire file is needed anymore; instead, one of the many BLOCK sections of the original file is modified. This allows multiple independent changes to be made sequentially from different needs. Our modules have been implemented following this Gambio concept from the start. Old or still existing USERMODS still work but ultimately overwrite ALL regular changes made via BLOCK modifications. Even Gambio delivers such changes as BLOCK modifications via GXModules.
Our modules check the BLOCK changes necessary for the module in the template/theme and report old USERMODS that may still be found for these files because they may override the modification. These files will very likely cause problems because after the module has made its required BLOCK changes based on the original file, a USERMOD comes along and overwrites this and the original file with old content and a full copy that was created in a shop version and is probably outdated. This may cause the module not to display and possibly other effects because the USERMOD is based on an older shop version.
Please take care of these USERMODS and have them rewritten into BLOCKs so that changes can complement each other and you do not use full copies of old files in the system, which will soon no longer be supported. Contact us if needed to solve this issue.
Can I change the appearance or texts?
Basically yes, you can. Our modules implement according to Gambio's guidelines. You can change texts – as you already know from the shop itself – via "Adjust texts"; don't forget to clear the text cache after changes. You can also change elements and appearance in the frontend via any available options in the module setup. Furthermore, you can make extensive adjustments via the CSS formatting language; this requires HTML/CSS knowledge. You can store overriding and changing CSS definitions as your own CSS via the template or theme. We are happy to assist you upon request.
My host cannot – or will not – provide IonCube
In this case, unfortunately, you cannot use our modules.
Using "IonCube" is not rocket science and is practically the only way to effectively protect copyrighted works; therefore, this server extension is "state-of-the-art" and basically standard for commercial hosting.
Professional hosts and those not primarily focused on private individuals have no problems providing "IonCube." Providers like "all-inkl," "ESTUGO," and of course us always have IonCube available automatically.
Most other hosts allow activation of this server extension more or less easily via the web account control panel. The host is always the right contact for providing the "IonCube" server extension.
Some – fortunately few – hosts have a different view. Hosting customers of, e.g., 1und1, Strato, or world4you only get IonCube in regular and higher tariffs, not in tariffs intended for private individuals; however, shops are not hosted in these tariffs. Installing "IonCube" requires a small intervention on the server itself, so these hosts think your customer – i.e., you – could do it themselves. It's a bit absurd, but if you call support 10–20 times, you might get someone on the phone who knows what it's about and is hopefully kind enough to integrate and activate "IonCube" for you.
Using "IonCube" is not rocket science and is practically the only way to effectively protect copyrighted works; therefore, this server extension is "state-of-the-art" and basically standard for commercial hosting.
Professional hosts and those not primarily focused on private individuals have no problems providing "IonCube." Providers like "all-inkl," "ESTUGO," and of course us always have IonCube available automatically.
Most other hosts allow activation of this server extension more or less easily via the web account control panel. The host is always the right contact for providing the "IonCube" server extension.
Some – fortunately few – hosts have a different view. Hosting customers of, e.g., 1und1, Strato, or world4you only get IonCube in regular and higher tariffs, not in tariffs intended for private individuals; however, shops are not hosted in these tariffs. Installing "IonCube" requires a small intervention on the server itself, so these hosts think your customer – i.e., you – could do it themselves. It's a bit absurd, but if you call support 10–20 times, you might get someone on the phone who knows what it's about and is hopefully kind enough to integrate and activate "IonCube" for you.