Hi!
I'm using Reviews 2.3 on my site. On the modules start page it displays most popular and most recent reviews. However, most recent reviews are actually the oldest ones. Not the newest ones. How can this be fixed?
Watch
GitHub Core
Show your support for Zikula! Sign up at Github account and watch the Core project!
GitHub Modules
- rgasch created topic »Using PageUtil::addVar() to load script code« 11:48 AM
- michiel responded to »password problem« 10:01 AM
- mazdev responded to »Hide "Register new account" and change template to 3 col« 07:50 AM
- mesteele101 created topic »Zikula 1.3.3 - Site Search 1.5.2 - Unable to turn off plug-ins« 07:48 AM
- mesteele101 responded to »ERR (3): E_USER_ERROR: Smarty error: [in pagesvar:pagesitem2en line XXX]…« 25. May
- mazdev responded to »Pages 2.5.0 and updating - Page not found« 25. May
- mesteele101 responded to »Zikula 1.3.3 - Selecting a category in Pages not working« 25. May
Zikula Blog
- Anatomy of Open Source Projects on Mar 07
- Continuous Review on Mar 01
- Not Invented Here on Feb 24
- How to Contribute Your Code at Github on Jan 13
- 10 Steps to Coding-Nirvana: Tips for Successful Module Writing on Nov 12
- Submitting Bug Report Tickets That Get Results on Aug 17
- Cozi Tricks #1: Syntax Highlighting on Aug 07
Login
Reviews module's Recent reviews are actually the oldest ones
-
- Rank: Registered User
- Registered: Jun 03, 2004
- Last visit: Feb 25, 2010
- Posts: 22
-
- Rank: Team Member
- Registered: May 03, 2004
- Last visit: May 31, 2010
- Posts: 511
-
- Rank: Softmore
- Registered: Dec 23, 2003
- Last visit: May 05, 2010
- Posts: 351
This looks pretty nasty. The problem appears to be in the upgrade script that get's rid of pn_date and creates a column pn_cr_date
Look in pninit.php file:
Code
case '2.2':
// Move the creation date
$table = DBUtil::getLimitedTablename('reviews');
$sql = "UPDATE $table SET pn_cr_date = pn_date";
DBUtil::dropColumn('reviews', array('pn_date'));
In my DB that essentially zapped my pn_date column and left all pn_cr_date entries the same: 1970-01-01 00:00:00
I am wondering if simply restoring the table and renaming the pn_date will work.
This is not very good.
supa
--
Caribbean News
Online Shopping from USA, Canada, UK, France, Germany
On Facebook -
- Rank: Developer
- Registered: Jun 16, 2003
- Last visit: May 29, 2010
- Posts: 1966
I have never used review, but I'll guess that someone was converting it to categories. Categories has that pn_cr_date col. My guess is the col isn't yet created when that SQL is run and thus it doesn't actually move the data. -
- Rank: Softmore
- Registered: Dec 23, 2003
- Last visit: May 05, 2010
- Posts: 351
Any idea how it can be fixed? I have the old backup before 2.2 which has the right pn_date....Guess i can edit the DB directly and get past this.
supa
--
Caribbean News
Online Shopping from USA, Canada, UK, France, Germany
On Facebook
- Moderated by:
- Support
