- Details
- Written by: Max Milbers
- Category: Latest News
- Hits: 16272
Some people from the community have been saying for years, that we should make a paid version for better funding of the project. I was unsure that this would be a way forward. However, the last year has had me re-evaluate the completely "free to use" model and whether such a strategy is sustainable or good for the future of VirtueMart.
One clear issue is that, while I am busy with updating and testing the core, third party developers work to quickly update their extensions and earn revenue immediately on release of the core. Unfortuantely the majority of my ISTRAXX extensions are not able to be updated for compatibility until after the core is released which results in customers being negatively impacted by the delay, a major loss in user installations and significant loss in revenue for my business.
Additionally, in order to make this current business model economically viable, I have to direct significant efforts to bespoke customer projects, effectively further reducing the time available for core developement. This was a major factor in the speed in which the latest version of VirtueMart could be delivered. - Joomla 4 compatibility along with PHP 8.0 support required significant core changes.
We also have our wide user community offering a lot of suggestions, solutions and fixes. A tiny feature, for example, for which 3 community members donate their 30 minutes, has to be discussed, tested and eventually a core solution must be optimised by myself to ensure a compatible and long term resolution.
Many of you will wonder why these tasks fall on me alone and why this work has not beeen distributed to supportive interested parties. Such a distributed and loosely managed approach was used in the past with VirtueMart and it eventually led to a codebase that was a mish mash of confused, personal style, bespoke, often hard coded and short term "solutions" that rendered VirtueMart too unweildy for people to maintain or develop in a cohesive and coherent manner. Today a key part of my role is that of VirtueMart Product Manager, taking ideas and features forward and ensuring code compatibility and flexibility such that it is suitable for multiple ecommerce use cases now and in the future, with the additional workload of creating releases and associated documentation - weeks and months of time is being expended.
Over the many years core VirtueMart has helped secure significant revenues for: customers selling products, agencies selling compatible plugins and agencies building strong revenue generating customer bases throught the use of VitueMart. Unfortunately only a tiny fraction of these businesses and customers have made any contribution to the ongoing work of the VirtueMart business, even when it was obvious how such a contribution could be made. This is not a unique situation, but it is one that is misaligned and unsustainable. VirtueMart clearly needs a better funding model. On analysing the sold memberships over the last years, I have found that less then 1% of virtuemart shops are members, incredible but true!
The new approach is that the core code will still be free in the SVN, but the new installer or package will only be available with a membership on extensions.virtuemart.net.
I have added a small manual showing how to update VirtueMart by the SVN directly https://docs.virtuemart.net/tutorials/installation-migration-upgrade/246-how-to-update-virtuemart-from-svn.html.
Users willing to expend the time and effort to learn how to do this update and implement it via SVN should understand, in a very small way, how much effort one tiny aspect of VirtueMart takes to maintain.
There will be still an older VirtueMart version on VirtueMart.net. This will be updated less frequently than it is currently.
These slightly outdated versions will be good enough to start with VirtueMart, but the convenience to update to the latest VirtueMart version with one click will not be offered unless you support the project with at least a Bronze membership.
You can still install the latest version via our SVN, but for the small price of a basic membership you will save a lot of time and effort as you will be able to update VirtueMart to the latest version with the click of a button.
- Details
- Written by: Max Milbers
- Category: Latest News
- Hits: 6240
Dear VirtueMart users,
a Joomla 4 update is fixing a serious vulnerability today at 4pm UTC.
Please be advised to update Joomla 4 as soon as the update is available.
In a similar case Joomla 3 sites were getting hacked hours after the update was available.
The vulnerability is reported to exist only in Joomla 4 not Joomla 3.
Find the security report here:
https://www.joomla.org/announcements/release-news/5877-joomla-4-2-8-important-security-announcement-patch-available-soon.html
Please update and stay safe
The VirtueMart Team
- Details
- Written by: Joerg Kiekebusch
- Category: Latest News
- Hits: 10497
Improved compatibility with Joomla 4.2 and PHP 8.1 plus category tree loading speeded up by factor 10
This version took longer than expected, as the team faced several compatibility issues this time. Joomla 4.2 caused more problems than Joomla 4.0 did back then. Suddenly, the 'add to cart' function didn't work anymore, opening shipping/payment methods caused a loop, saving with timestamp failed and so on.
In addition, the changes and removed functions/methods/modes in PHP 8.1 caused further trouble. For example, this caused searches with special characters to not work.
When we were about ready, a customer with more than 8000 categories (in 5 levels) tested the new version with a
- Details
- Written by: Max Milbers
- Category: Latest News
- Hits: 9619
The Paybox payment system of Verifone is extending more international. It has very interesting payment concepts. They support already more than 50.000 shops and do more than 140 Million transactions per year.
Equip your e-commerce site with a secure and recognised payment solution!
From a basic need to a more complex processing, Verifone secures your e-commerce flows by giving you access to over 30 payment methods.
15 years of experience with a wide range of customers
Paybox accompanies you in your daily life with a secure, modular and turnkey payment solution that meets all your needs.
With each transaction, you benefit from the advantages of a cross-channel, multi-bank, multi-payment means, multi-currency platform equipped with fraud management and reporting tools to facilitate the daily management of your business.
6 good reasons to choose Paybox
| For you ... | For your customers... |
| Your bank account is credited every night. Paybox does not collect your transactions |
Pay with the payment method they prefer |
| A choice of payment methods appropriate to your your business and your customers |
Convenient debit at the time of shipment, in installments, by subscription or in 1 click |
| A flexibility of collections, reporting, refunds refunds to satisfy your customers and build loyalty |
Quick refund in case of return on the payment method used |
Paybox is already integrated in our AIO installer, just update your installation, or use our full package to install Paybox with VirtueMart and Joomla!
4.0.6 release notes
This release is for two critical bugs. The security feature for orderUpdate was too secure and blocked updating orders of guests. The other problem was in vRequest which uses the data of the router better now.
- Details
- Written by: Max Milbers
- Category: Latest News
- Hits: 7785
croatian coast, Copyright Max Milbers
VirtueMart 4.0.4 contains various bug fixes and improvements. Especially it solves some problems reported to us after the release of the previous version of VirtueMart when it is used along with Joomla 4.1.x.
Fixes and changes and enhancements included in this version are:
Joomla 4
- Fixed saving the sorting of items in j4
- Fixed chosen update for j4, needs another trigger
- New jQuery for j3 (j4 one)
- Updated xmls so they should work for j3 and j4
- Added a missing j4 adjustment to the vmloaderpluginupdate plugin
Developer new technics
- vmJsApi new method to push JHtml execution in a queque like we do with our js already. The queque is executed with writeJS
- sku, gtin, mpn only shown for is_input customs
- updateStatusForOneOrder is only executed if there is a given virtuemart_order_id and if the entry already exists
- vmplugin function storePluginInternalData converts the decimals, too
- Updated state published in the product model, for listing we now use list.published and some other minors in product model
Templater
- New classes for Multivariant dropdowns
- Horme3 removed $app->isAdmin
- Just some better use of existing functions "loadPopUpLib"
Fixes
- Enhanced router using static functions and values (all static) and remanaged it for better debugging
- Fixed initialisation of language in router, if language was not loaded the first time with loadConfig
- The debug of the router was sometimes called without loading the config and failed
- Changed key field_type_searchable_published from unique to key and minors
- GUI, changed maximum input for order status
- Replaced all %1s and %1d to %1$s and %1$d in EN and DE language files due %1s and %1d causing problems
- Found big error which lead to wrong inserts/updates, if the same entry was stored within the same call again.
- Fix for vmView, added parameter for construct and added setting of VmView::$bs in getVmSubLayoutPath
- Replaced deprecated FILTER_SANITIZE_STRING against FILTER_SANITIZE_FULL_SPECIAL_CHARS
Enhancements
- Added a new option in vmloaderpluginupdate to load config with or without language
- Categories do not load anylonger the parents for the breadcrumbs in the Backend for faster listing
- Some work on the languages. If a language is selected, which exists in joomla but not in the vm config, it should show the joomla language and only the vm content stored in tables like product description should use the fallback.
- JPEG images create thumbs with JPG
- Enhanced handling of storing a new custom proto type if type is plugin but no plugin set
- Enhanced vmecho for better measuring time. It sums up the time needed for a particular function, but not the time between calls to the function
