View Issue Details

IDProjectCategoryView StatusLast Update
0005856OXID eShop (all versions)2.4. Administer productspublic2015-12-01 11:02
Reporterstephen 
PrioritynormalSeveritytweakReproducibilityrandom
Status acknowledgedResolutionopen 
PlatformAllOSAllOS VersionAll
Product Version4.8.7 / 5.1.7 
Target VersionFixed in Version 
Summary0005856: Incorrect sort order of reviews
DescriptionArticle reviews in eShop backend are not ordered by creation time. See screenshot.

The problem will only occur, if the database table oxreviews is defined as InnoDB. Not for MyIsam.

The problem comes from the following file:
application/controllers/admin/article_review.php

There is a method named:
_getReviewList

In that method there isn't an "order by" statement defined.

Proposed solution:

Find: $sSelect .= "and oxreviews.oxtext != '' ";
Add after: $sSelect .= "order by oxreviews.oxcreate";

Steps To Reproduce- Use a database in which the storage engine of the table oxreviews is defined as InnoDB.
- Write some reviews for a certain article
- Enter eShop backend
- Select the article
- Click on the tab "Reviews"
TagsReviews
ThemeAzure
BrowserAll
PHP VersionNot defined
MySQL VersionNot defined

Activities

stephen

2014-08-21 02:55

reporter  

sort_order.gif (12,287 bytes)
sort_order.gif (12,287 bytes)

stephen

2014-08-21 03:26

reporter  

sort_order_wrong.gif (12,258 bytes)
sort_order_wrong.gif (12,258 bytes)

stephen

2014-08-21 03:28

reporter   ~0010082

Please note: The first screenshot shows the sort order achieved with the proposed solution. The second screenshot shows the sort order as created in standard.

jurate.baseviciene

2014-08-21 12:13

reporter   ~0010083

Last edited: 2014-08-21 12:13

View 2 revisions

Reminder sent to: stephen

Hi,

 As we saw, you already submitted a complete solution for this issue. If you feel fancy, you'd also have the possibility to contribute your changes directly to our GitHub repository on https://github.com/OXID-eSales/oxideshop_ce/. Please leave a note there with the bug number you fixed so we can close this issue in the bug tracker."

Best regards
Jurate