Oledrion is a XOOPS-native eCommerce module developed by Hervet.

Voltan did some changes to it, and I have now updated it to XOOPS 2.5.x Admin GUI and tested on XOOPS 2.5.5 and PHP 5.3.10



Download: XOOPS SVN

Requirements:
- XOOPS 2.5.5
- ModuleAdmin
- PHP 5.2+

Changelog:

- Converted to XOOPS 2.5.5 Admin GUI (Mamba)
- fix: removed private lists form blocks other than "My lists" (Mamba)
- added language strings (Mamba)
- fix English translations (Mamba)
- several cosmetic changes (Mamba)
- added product properties (voltan)
- Updated Cache Lite (Mamba)
- Update PEAR.php (Mamba)
- Added "Total Savings" to Shopping Cart (Mamba)

TODO:
- selecting Product Option should be reflected in total Price
- Adding new Discount doesn't work

[EDIT] - it's now fixed.

This is a quite sophisticated/complex module, therefore I would appreciate help from the gurus in our community on the TODO items.

Thank you very much

nice & good job

I hope, you'll be able to test it.

There are still some inconsistencies with price calculations , most probably caused by my code changes, so I'll be cleaning them up in the next week or so, but please test as much as you can all the other areas, so we know what else needs to be changed/improved.

One thing that I am not sure is your usage for Cache_Lite.

Hervet has created his own PersistableObjectHandler and used there Cache_Lite.

The question I have is:

- was it because XOOPS didn't have yet its own "XoopsPersistableObjectHandler" when Hervet was developing Oledrion? Or was it because he wanted to make his PersistableObjectHandler better than our "XoopsPersistableObjectHandler"?

- is Cache_Lite comparable to XOOPS Cache in performance? Or is it better?

In other words: if I replace his PersistableObjectHandler with "XoopsPersistableObjectHandler" and remove Cache_Lite and instead use our standard XOOPS Cache mechanism, will I experience a significant performance drop, or will they be more or less the same?

If they are comparable in performance, then I would probably convert Oledrion to use the "XoopsPersistableObjectHandler", as it would help us keep all the modules consistent.

I've done it in another Hervet's module: Birthday, i.e. I converted it to "XoopsPersistableObjectHandler", as it helped to get rid of some PEAR errors (if user had already another PEAR installation) but since Birthday is not "transaction-oriented", even if there is a performance drop, it would be probably insignificant.

But Oledrion is a different story, since it is "transaction-oriented", so that's I wanted to ask experts on the forums for their views.

Nice work Voltan and Mamba, I'll try ro find some time for testing!

I downloaded and installed, error in the administration:

Error:
Fatal error: Cannot redeclare class oledrion_parameters in Z:\www\x255\modules\oledrion\class\oledrion_parameters.php on line 57

XOOPS 2.5.5
Server:
Versão do Xoops XOOPS 2.5.5
Versão do PHP 5.3.8
Versão do Mysql 5.5.17
API do Servidor apache2handler
OS WINNT
safe_mode Off
register_globals Off
magic_quotes_gpc On
allow_url_fopen On
fsockopen On
post_max_size 10M
max_input_time 60
output_buffering
max_execution_time 300
memory_limit 1024M
file_uploads On
upload_max_filesize 10M

Quote:
Can not replicate here on PHP 5.3.13.
Anybody else with the same problem?

Every time i change the file class/oledrion_parameters.php (with comment, space, etc ...) it works, but if he's reloading the page error.

This makes no sense, I know.

Hi Michael,

I had another error here...

Fatal error: Cannot redeclare _PEAR_call_destructors() (previously declared in C:\xampp\htdocs\x255\modules\oledrion\class\PEAR.php:737) in C:\xampp\php\PEAR\PEAR.php on line 806

XAMPP 1.7.7 on Win7Pro 64bits (blargh! )
Apache 2.2.21
MySQL 5.5.16
PHP 5.3.8

Quote:
I had the same issues in the Birthday module, and have removed the "Cache-Lite", and the issue is gone. I guess, there is a conflict between PEAR in the module, and your PEAR as part of your PHP installation.

You can try to comment out PEAR in your php.ini file, and it should work.

As I said in my earlier post, I am not sure about the performance impact of Cache_Lite. In the Birthday module it should have no impact, but I don't know about Oledrion, since it's more "transaction-oriented".

But if the performance is similar to Cache that we're using in XOOPS, then we could remove it, and then have no dependency on PEAR.

It worked!
Going to the tests ...