(osCommerce 2.2rc1 + CK-ERP 0.25.1) connector failure

[C K Wu]

Hi, folks,

I am afraid I made a major blunder with the osCommerce connector. The
current osCommerce connector embedded within CK-ERP v.0.25.1 will fail
within an osCommerce environment. Please consider CK-ERP to be
non-operational within osCommerce for the moment. I'll try to produce
a new release as soon as the updated connector is fully tested.

I apologize for any inconvenience caused, especially to the osCommerce
folks.

Best Regards,
CK

[C K Wu]

Hi, folks,

I forgot to mention one important detail about the new connector.

The barebone installation of osCommerce 2.2rc1 does not include a
facility, function or concept resembling administrator group, so I have
decided to suppress the group feature within the osCommerce connector.
Hence, within an (osCommerce 2.2rc1 + CK-ERP v.0.25.1) environment, the
read-only group feature does not work, although execution of the
associated scripts would not lead to script failure either. In effect,
there is no read-only group within an (osCommerce 2.2rc1 + CK-ERP
v.0.25.1) environment.

Best Regards,
CK

C K Wu wrote:
> Hi, folks,
>
> Please find attached an updated and re-tested connector.inc.php for
> the osCommerce connector.
>
> Just download this file and overwrite the existing file located at
> ..../ck-api/osc22/connector.inc.php within an (osCommerce 2.2rc1 +
> CK-ERP v.0.25.1) environment. This should solve the connector failure
> problem.
>
> Since the rectification is centered around a single file, I'll put it
> up as a post v.0.25.1 release patch, instead of issuing a new release.
>
> Best Regards,
> CK

[C K Wu]

Hi, folks,

Please find attached an updated and re-tested connector.inc.php for the
osCommerce connector.

Just download this file and overwrite the existing file located at
..../ck-api/osc22/connector.inc.php within an (osCommerce 2.2rc1 +
CK-ERP v.0.25.1) environment. This should solve the connector failure
problem.

Since the rectification is centered around a single file, I'll put it up
as a post v.0.25.1 release patch, instead of issuing a new release.

Best Regards,
CK