View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005996 | OXID eShop (all versions) | 1.03. Basket, checkout process | public | 2014-12-12 15:30 | 2015-01-08 07:48 |
Reporter | gerldental | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | sometimes |
Status | resolved | Resolution | unable to reproduce | ||
Product Version | 4.8.9 / 5.1.9 | ||||
Summary | 0005996: oxbasketitem->getIconUrl() returns standart link in SSL mode | ||||
Description | oxbasketitem->getIconUrl() returns standart link (http) in SSL mode | ||||
Steps To Reproduce | f.e.: in templates basketcontents.tpl ( line 61 ) <img src="[{$basketitem->getIconUrl()}]" alt="[{$basketitem->getTitle()|strip_tags}]"> on order class returns $basketitem->getIconUrl() a normal link, not htpps. thats causes an error in IE and warnings in other browsers. | ||||
Additional Information | seems to be something wrong in this function: 00390 public function getIconUrl() 00391 { 00392 // icon url must be (re)loaded in case icon is not set or shop was switched between ssl/nonssl 00393 if ($this->_sIconUrl === null || $this->_blSsl != $this->getConfig()->isSsl()) { 00394 $this->_sIconUrl = $this->getArticle()->getIconUrl(); 00395 } 00396 00397 return $this->_sIconUrl; 00398 } maybe $this->_blSsl has a wrong value? | ||||
Tags | No tags attached. | ||||
Theme | Azure | ||||
Browser | All | ||||
PHP Version | 5.3 | ||||
Database Version | 5.5 | ||||
|
Reminder sent to: gerldental Hi, Sorry we cant reproduce this behavior. Could you please provide to us more details? We got that oxbasketitem->getIconUrl() returns link in SSL mode not as standard link: <img src="https://testshops/OXID_ESHOP_EE_5.1.9/out/pictures/generated/product/1/87_87_75/rrd_passion_2010_1.jpg" alt="Kite RRD PASSION 2010 "> </a> Best regards, Jurate |
|
on the new hosting we had this problem in all of shops. Now, after few week we can't reproduce this problem too. Please close. |
|
Hi, Thank you very much for your an answer. We are very happy that this problem does not exist . We are close this behavior as unable to reproduce. Best regards, Jurate |