View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006229 | OXID eShop (all versions) | 3.2. HTML, CSS, JavaScript | public | 2015-09-08 15:31 | 2015-09-11 10:02 |
| Reporter | nb | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | unable to reproduce |
| Status | closed | Resolution | unable to reproduce | ||
| Product Version | 4.9.4 / 5.2.4 | ||||
| Summary | 0006229: When "oxid_include_widget" is used in a template for an AJAX response it returns JSON instead of HTML | ||||
| Description | When "oxid_include_widget" is used in a template that generates content for an AJAX response, the widget is not rendered properly. Instead of HTML, the widget returns a JSON structure with HTML code in it. | ||||
| Steps To Reproduce | - include a widget using "oxid_include_widget" in a page that updates its content from an AJAX call, i.e. page/checkout/inc/basket.tpl - go to the basket and delete an item from it for the AJAX call to happen the place where the widget should be rendered shows a JSON structure like "{errors:[], content: "HTML code here"}" | ||||
| Tags | No tags attached. | ||||
| Theme | Not defined | ||||
| Browser | Not defined | ||||
| PHP Version | 5.4 | ||||
| Database Version | Not defined | ||||
| related to | 0005121 | resolved | vilma_liorensaityte | When using "oxid_include_widget" inside an AJAX template, it messes up the content received from the widget |
|
|
Reminder sent to: nb Hi, Thanks a lot for submitting this issue, but unfortunately we can not reproduce this issue. I added a widget include ([{oxid_include_widget nocookie=1 cl="oxwTagCloud" blShowBox="1" noscript=1 }]) to application/views/azure/tpl/page/details/inc/productmain.tpl, opened an article with variants and selected a variant. No problems. The template you mentioned (page/checkout/inc/basket.tpl) doesn't exist. Do you mean basketcontents.tpl in this folder? I checked the same in an older Version (5.0.6) and got the described problem as expected, because this was reported with issue 0005121. But this was fixed. So please add more detailed steps to reproduce or add the changed template file. Best regards |
|
|
Hi, the issue occurred when using the ROXID template set. The fix attached to 0005121 worked to resolve the issue for us. Best regards |
|
|
Closed because it is a problem with a third party theme. If you have information how to reproduce this in OXID, please reopen this issue. |
