Jack_mcs

To be clear, the paypal app addon has several modules in it, one of which is the Pro module and that allows taking cards on the site. Paypal may be less costly than authorize.net, depending on your host, the quantity of orders and whether you can get paypal to waive the monthly fee, which they will sometimes do.

You can download the authorize.net and paypal app addons here. Depending on the version of your shop and what version in on that site, they should work. You may also mention to your client that upgrading to V4 might be a better alternative. You can contact me if you want a quote or either of these.

@lampinoSome old addons can be found here. You can get updated versions here. The latter has a version that should work with your shop.

I apologize for missing that but I rarely look at subjects since so few apply to the actual subject, in my experience. It's the same thing. I don't know what parts of the code deal with the specials issue off the top of my head. So to do what you want, I would install the addon in a test shop, find the problem code, apply the change and test it. The end fix will probably just be a few lines of code. Finding that code and testing it could take hours. So doing what you want would not save you much in the final cost. I don't know how long that will take so I can't accurately quote it. If you want it done for $20 under the code of the Pro package, I will do that, though it doesn't sound like a good deal to me.

You're looking at it backwards. If i am coding an addon for a 2.2 shop, I would code it using php for that version - 5.3, maybe 5.4. To try to code it for some future version of php is just asking for problems. The parts you mention are compatible, but some other function may not be. So, I would need to create two versions: one for the intended shops and one for those like you, assuming I used code that was not compatible between the various versions. Since my imaginary addon is being written for free, why should I go to so much effort to cover cases where the shops code has been altered? Look at just about any old addon and the instructions will mention that the changes are for a stock shop. This is no different.

As you mentioned, that package is for oscommerce 2.2. That oscommerce version is not qualified to run on any version above php 5.4, if that. So if the code in the paypal package was coded with code that works for php 8x, it would probably fail since some php code is not backward compatible.

I didn't realize you had emailed me. I don't have an easy way of identifying usernames to email addresses so, unless mentioned, I treat each one separately. In the email you sent, you never mentioned the question was about Easy populate. If you look through my replies, you will see I was talking about the Image Interrogator addon, which is not related to EP at all. The image checker in EP works with subdirectories. The one in the Image Interrogator does not, at this time. I'm sorry but I am not interested in creating another version at this point due to my work load.

Sorry. That is sloppy documentation on my part. As you found previously, the free 3.6 version shows it is 3.4. I don't know how you would know this since you don't have the Pro version. But it works fine with images in sub-directories as long as that is how they are entered in the products table, which is how the addon for that feature works. If you are using some other method, I've no way to know if it will work or not. And, to be clear, the option is for checking products that have an image in its settings but the image cannot be found. This is another mistake in the docs. I plan to add a check for unused images but haven't done that yet.

The free version works correctly. It just doesn't have all of the options the Pro version does. Fairness runs both ways. The days of free addons has mostly passed. It takes a lot of time to write an addon and to keep them updated. In both V4 and Phoenix, there are some free addons, some of which are limited, but many more that have to be paid for. If paying for the developer's time is not something you wish to do, you are not forced to do that.

It's only available in the Pro version.

I am writing a new module using the new API. It is about 80% complete and will be completed before the XML method no longer works in June.

The menu option says Complete.

Does it work if you run a full report? I seem to recall there was a problem in the free version where it didn't work in custom mode, though I may not be remembering correctly.

Please try the latest version.

Yes, several times. Does the brredcrumb you have work as it should - showing the path of the clicks?