Due to numerous issues that would cause many of my custom modules to break, I have not yet chosen to make my BundlePlus module compatible with Magento’s “stable” 1.4.2 release.
So until I see the need and I have enough time to evaluate all of the changes from 1.4.1.x to 1.4.2.x, my module with not be “fully” compatible with the 1.4.2 releases. I certainly entertain other developers to review the changes in 1.4.2 and contribute back. Sorry if you are displeased with this news. Sometimes, it’s hard to keep up with the evolution of Magento’s APIs.
As it is, it looks like the 1.5.0 branch will soon be making its way into “stable” status. All these changes that are quickly occurring do not exactly encourage developers to invest a lot of time into a particular branch that is just going to get broken again.
Looks like I will have to entertain the idea of downgrading to Magento 1.4.1. Thanks for the reply /
For those following this thread and/or the development of the KAbel_BundlePlus module: I certainly have a vested interest in keeping my module (and my Magento installations) up to date.
If you feel compelled and/or willing to contribute back in the form of a small donation or code, I welcome you to PM me.
In the spirit of ensuring this post doesn’t conflict with the forum rules, it should not be interpreted as a “solicitation” but rather a statement that there are ways that you can help with development.
@balexandre: Thanks for using my Bundle Module. Normally, there would certainly be a code update out for 188.8.131.52. However, looking at the extremely long list of outstanding, verified bugs that were again introduced in the 1.5 branch I am delaying my upgrades once again. v184.108.40.206 remain to be the most “stable” release in my opinion.
It is unfortunate that the Magento Team focuses so much on putting out “seemingly” unnecessary new features and service (it’s what happens when the VC’s demand return-on-investment). These new features take away from the core platform and usually result in MAJOR regressions once released. Suffice it to say, they are keeping me in business by continually adding complexity to the code base.
Ranting aside, I did get a copy of Tuxi’s proposed Type.php file for the 1.5 branch. I have skimmed through it, and while there may be a few things I’d adjust for coding standards/readability/optimization, it appears that it should bring expected functionality to the module. However, because Tuxi has adapted the PHP class name for his/her own module setup, it probably can’t just be dropped over my current distribution. If you are comfortable with your coding skills, you may review the file for yourself at https://docs.google.com/leaf?id=0B3vwOF6cNaa6OGI5Y2Q2YjQtMmQ4MS00Yzc0LWJkNDQtZTkwMzU0OTNiZjUw&hl;=en
Now to the real issue, looking at your report and the debugging steps you took, it would appear that you don’t quite have things installed correctly. That fatal error will only occur if the overridden Type.php is not being used. Please check your install locations and that the following is true when you run Magento:
Just wanted to say Thank You for this modification and let everyone know out there that this does work with EE 1.9.1. I was wondering if you had intended on wrapping this up as a normal module modification? Looking at the structure I tend to forget things like the Adminhtml changes that need ot happen especially when I upgrade. If this was all in one self contained module I have a feeling it would be easier to install and easier to maintain. Just a thought.
Hi Greg. I completely agree with you that the installation is a little cumbersome. For all intents and purposes, it is a self-contained module, however it does require some manual interaction to overcome some limitation of installing unobtrusive modules.
If you are referring to the Magento Connect module distribution channels, I choose not to distribute through there. Magento Connect is simply a wrapper around a PEAR/Pyrus server AND requires administrators to give the web application FULL write access to itself. I do not agree with this kind of deployment, so I don’t use it. Because I’m familiar with the code-base, I choose security over simplicity.
Well folks, the time of putting off the upgrade to the 1.5 branch is over. There will be a new release of my module posted tomorrow that will bring all functionality to 1.5 and fix certain issues with using the new “edit from cart” feature.
== Release Details ==
This release of the module KAbel_BundlePlus (0.2.1) brings the “user-defined” qty feature to checkbox bundle option selections for the 1.7 Magento branch. It is now supported to be installed through Magento Connect.
Version 0.2.2 brings support for admin created orders to use the composite product configuration to specify the option qty.
Version 0.2.3 fixes a couple of bugs when rendering selections on the frontend for certain configurations.
== Install Notes ==
The 0.2.1 version introduced support to be installed via Magento Connect. However, it can also be installed though normal file system access.
Previous versions can (and should) be safely removed, as usual, files have been reorganized.
Please note that this new version is NOT backwards compatible with previous versions, however, you may download an older version to make things work with the 1.4 or 1.5 branch. All previous download links still point to the old 1.4 version.
What is \’mucip more information about this problem, I really cannot provide you a possible solution. By this module, the Sales/Quote., so this is not written in the php file that is created by another module installed or due to errors, probably a Magento cache issue.
fantomas82: “composite bundle” products? Do you mean bundle products with “configurable” product options. If so, then no, it is beyond the scope of this module to provide support for a new product type as the storage system for such a product would require significant code changes.
[EDIT]: Ah, I should have looked before posting. You must mean the new functionality in the Admin Panel to Create orders with composite (configurable, grouped, and bundled) products. New answer, yes. It can be assumed that this is a logic feature that is yet to be covered by this module. I’m not quite sure what priority it will be for me (or others), but I will certainly add it to my list of things to look into.
i did some research and coding in this issue myself, because i need this functionality asap.
I thought that i could share what i have done to save your or maybe someone else’s time.
Note that this code is not tested thoroughly nor is the feature complete.
The files that need to be manipulated and overrided: