Latest News: (loading..)
Issue information
-
#000292
-
1 - Low
-
Fixed
-
3.0.1
-
3.0.2
Issue Confirmations
-
Yes (0)No (0)
hi there,
while trying a coreUpdate, i get the following error in the log:
[error] [client ::1] PHP Fatal error: Cannot use osCommerce\\OM\\Core\\HttpRequest as HttpRequest because the name is already in use in /var/www/oscommerce/osCommerce/OM/Core/HttpRequest/Curl.php on line 11, referer: http://localhost/oscommerce/index.php?Admin&CoreUpdate
thank you!
bogdan
while trying a coreUpdate, i get the following error in the log:
[error] [client ::1] PHP Fatal error: Cannot use osCommerce\\OM\\Core\\HttpRequest as HttpRequest because the name is already in use in /var/www/oscommerce/osCommerce/OM/Core/HttpRequest/Curl.php on line 11, referer: http://localhost/oscommerce/index.php?Admin&CoreUpdate
thank you!
bogdan
By commenting out "use osCommerce\OM\Core\HttpRequest;"
in /var/www/oscommerce/osCommerce/OM/Core/HttpRequest/Curl.php line 11
I got rid of the error; however, not sure it works, as I was expecting some updates... but I might misundersood the statement that applications shall come through coreupdate as of april...
thank you,
b
in /var/www/oscommerce/osCommerce/OM/Core/HttpRequest/Curl.php line 11
I got rid of the error; however, not sure it works, as I was expecting some updates... but I might misundersood the statement that applications shall come through coreupdate as of april...
thank you,
b
Updating severity to: 1 - Low
Updating status to: Fixed
Issue fixed in: 3.0.2
Thanks for the report! This has been fixed with the following commit:
https://github.com/osCommerce/oscommerce/commit/85d1102061781589fd638a9b064b92d7a5f57c9e
Updating status to: Fixed
Issue fixed in: 3.0.2
Thanks for the report! This has been fixed with the following commit:
https://github.com/osCommerce/oscommerce/commit/85d1102061781589fd638a9b064b92d7a5f57c9e
Harald Ponce de Leon, on 02 August 2011, 18:57, said:
Updating severity to: 1 - Low
Updating status to: Fixed
Issue fixed in: 3.0.2
Thanks for the report! This has been fixed with the following commit:
https://github.com/o...64b92d7a5f57c9e
Updating status to: Fixed
Issue fixed in: 3.0.2
Thanks for the report! This has been fixed with the following commit:
https://github.com/o...64b92d7a5f57c9e
Hi Harald and bodistanciu!
The core update (from 3.0.1 to 3.0.2) will work after done the commit.
Thanks!
Gergely
0 user(s) are reading this issue
0 members, 0 guests, 0 anonymous users
















