Timeline error with UNA 13.1.0-B1
I installed UNA 13.1.0-B1 on a live site and now there are random people receiving database query errors when viewing pages with a timeline.
Long story short, my UNA site is unusable now 😂
here is the error from sys_db.log
Sep 01 06:33:49 [8612] / Database query error
Error: Unknown column 'bx_timeline_events.owner_id' in 'where clause'
Query: (SELECT `te`.*
FROM `bx_timeline_events` AS `te`
LEFT JOIN `bx_timeline_handlers` ON `te`.`type`=`bx_timeline_handlers`.`alert_unit` AND `te`.`action`=`bx_timeline_handlers`.`alert_action` INNER JOIN `sys_profiles` AS `tpoo` ON ABS(`te`.`object_owner_id`)=`tpoo`.`id` AND `tpoo`.`status`='active'
WHERE 1 AND `bx_timeline_events`.`owner_id` NOT IN (9966) AND `bx_timeline_events`.`object_owner_id` NOT IN (9966)AND `te`.`active`='1' AND `te`.`status`='active' AND IF(`te`.`system`='0' AND (`te`.`object_owner_id`=8612), 1, `te`.`status_admin`='active') AND `bx_timeline_handlers`.`id` NOT IN (44,4) AND IF(`te`.`system`='0' AND `te`.`object_id` = 8612, 1, `te`.`date` <= UNIX_TIMESTAMP()) AND ((`te`.`owner_id` = 8612) OR (`te`.`owner_id` = '0' AND IF(`te`.`system`='0', `te`.`object_id` = 8612, 1))) ORDER BY `te`.`sticked` DESC, `te`.`reacted` DESC, `te`.`id` DESC LIMIT 0, 6) UNION (SELECT `te`.*
FROM `bx_timeline_events` AS `te`
LEFT JOIN `bx_timeline_handlers` ON `te`.`type`=`bx_timeline_handlers`.`alert_unit` AND `te`.`action`=`bx_timeline_handlers`.`alert_action` INNER JOIN `sys_profiles` AS `tpoo` ON ABS(`te`.`object_owner_id`)=`tpoo`.`id` AND `tpoo`.`status`='active' INNER JOIN `sys_profiles_conn_subscriptions` AS `c` ON `c`.`content` = `te`.`owner_id` AND `c`.`initiator` = 8612
WHERE 1 AND `bx_timeline_events`.`owner_id` NOT IN (9966) AND `bx_timeline_events`.`object_owner_id` NOT IN (9966)AND `te`.`active`='1' AND `te`.`status`='active' AND IF(`te`.`system`='0' AND (`te`.`object_owner_id`=8612), 1, `te`.`status_admin`='active') AND `bx_timeline_handlers`.`id` NOT IN (44,4) AND IF(`te`.`system`='0' AND `te`.`object_id` = 8612, 1, `te`.`date` <= UNIX_TIMESTAMP()) AND `te`.`type`<>'bx_channels' ORDER BY `te`.`sticked` DESC, `te`.`reacted` DESC, `te`.`id` DESC LIMIT 0, 6) UNION (SELECT `te`.*
FROM `bx_timeline_events` AS `te`
LEFT JOIN `bx_timeline_handlers` ON `te`.`type`=`bx_timeline_handlers`.`alert_unit` AND `te`.`action`=`bx_timeline_handlers`.`alert_action` INNER JOIN `sys_profiles` AS `tpoo` ON ABS(`te`.`object_owner_id`)=`tpoo`.`id` AND `tpoo`.`status`='active' INNER JOIN `sys_profiles_conn_subscriptions` AS `cc` ON `te`.`system` = 0 AND `te`.`object_privacy_view` > 0 AND `cc`.`content` = `te`.`object_owner_id` AND `cc`.`initiator` = 8612
WHERE 1 AND `bx_timeline_events`.`owner_id` NOT IN (9966) AND `bx_timeline_events`.`object_owner_id` NOT IN (9966)AND `te`.`active`='1' AND `te`.`status`='active' AND IF(`te`.`system`='0' AND (`te`.`object_owner_id`=8612), 1, `te`.`status_admin`='active') AND `bx_timeline_handlers`.`id` NOT IN (44,4) AND IF(`te`.`system`='0' AND `te`.`object_id` = 8612, 1, `te`.`date` <= UNIX_TIMESTAMP()) AND 1 ORDER BY `te`.`sticked` DESC, `te`.`reacted` DESC, `te`.`id` DESC LIMIT 0, 6) UNION (SELECT `te`.*
FROM `bx_timeline_events` AS `te`
LEFT JOIN `bx_timeline_handlers` ON `te`.`type`=`bx_timeline_handlers`.`alert_unit` AND `te`.`action`=`bx_timeline_handlers`.`alert_action` INNER JOIN `sys_profiles` AS `tpoo` ON ABS(`te`.`object_owner_id`)=`tpoo`.`id` AND `tpoo`.`status`='active'
WHERE 1 AND `bx_timeline_events`.`owner_id` NOT IN (9966) AND `bx_timeline_events`.`object_owner_id` NOT IN (9966)AND `te`.`active`='1' AND `te`.`status`='active' AND IF(`te`.`system`='0' AND (`te`.`object_owner_id`=8612), 1, `te`.`status_admin`='active') AND `bx_timeline_handlers`.`id` NOT IN (44,4) AND IF(`te`.`system`='0' AND `te`.`object_id` = 8612, 1, `te`.`date` <= UNIX_TIMESTAMP()) AND `te`.`promoted` <> '0' ORDER BY `te`.`sticked` DESC, `te`.`reacted` DESC, `te`.`id` DESC LIMIT 0, 6) ORDER BY `sticked` DESC, `reacted` DESC, `id` DESC LIMIT 0, 6
Account ID: 4306
-
We have exactly the same problem, at this time there does not appear to be a solution @Alex T⚜️ @Andrey Yasko @LeonidS our site has been down for 4 days now.
-
The site seemed fine after update to 13.1.0-B1 as long as I was logged in as admin. After logging out I get a nasty database error: Had to screenshot it because it wouldn't paste here as text
-
The only way I found back in was to call (siteURL)/studio/dashboard.php which brings up a login page where I can log back in as admin.
-
Once in Studio you can disable to the timeline on your homepage a personal pages. The "manage all" view of the timeline still works so it's not a DB error and you can view the individual posts. You can't post an "update" but you can share a normal post. In the "Persons" module the "User Posts" view still works. I assume it will work under "Organizations"
-
I disabled the timeline block - which means I disabled the main focus point of my site - lol.
-
Hello @BIG Marketing Solutions LLC !
That's weird because the `promoted` field was added there long ago. Try to fix it by running the following query:
ALTER TABLE `bx_timeline_events` ADD `promoted` int(11) NOT NULL default '0';
-
Leonid: Thanks for the reply and suggestion. I figured it was the weekend over there already and didn't want to leave the site broken so restored to v 12 again. I would have to go through the whole upgrade process through all the Intermediate and RC versions in order to try the fix you suggest. How confident are you that it would work?
-
Hello @Zandra !
It's a similar situation like @BIG Marketing Solutions LLC have because this table had the `owner_id` field from the start. Could you please check that field in this table?
-
owner_id field dose exist and is populated.
-
`owner_id` field does exist and is populated.
-
I get a SQL error running that command:
SQL Error [1064] [42000]: (conn=1740) You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'ALTER TABLE `bx_timeline_events` ADD `promoted` int(11) NOT NULL default '0'' at line 1
-
table 'bx_timeline_events' already has the row 'promoted' which is apparently populated by a 0 by default or 10 digits such as "1681045440".
Is the field supposed to have 11 digits or just 'allow' 11 digits? Do you still recommend this fix?
-
-
@BIG Marketing Solutions LLC @InPage @Zandra could you please specify your Timeline module version ?
-
13.0.12
-
Hi @Alex T⚜️ 13.0.12 @LeonidS has additional information and access to the servers
-
The Admin view "timeline-manage" is fully functional, it is the other "public facing" views of the DB that do not work.
-
@BIG Marketing Solutions LLC @InPage @Zandra could you please provide access to your site Studio ? and steps how to reproduce the problem ?
-
Sent you the information in messenger
-
I spent some time with @Alex T⚜️ running through the problem. The timeline error only appears to be an issue for accounts that are associated with "multiple profiles" This means that your average user with a single profile will be able to view your site just fine. My advice is that you reenable your timelines for the general public and wait for an update from Alex.
-
A big thank you to @Alex T⚜️ and @LeonidS for their help identifying this problem.
-
Zandra: Can you restore to a backup until they get this fixed?
-
The problem is in Black Lists module from @AQB Soft - it's not compatible with latest changes in Timeline module. I hope @AQB Soft will update their module very soon, for a while you can try to deactivate this module (don't uninstall, just deactivate).
-
@Alex T⚜️ thank you for all your help today. @AQB Soft kindly let us know when your Black Lists module has been updated.
-
Unfortunately no - we use a replica standby server as a ‘backup’ - I been too lazy to setup veeam to backup the replica vm itself. So that’s my bad 😂
-
Yep, disabling the blacklist mod seemed to have resolved the issue.
-
@Alex T⚜️ According to our storefront downloaded page:
- Title: Timeline
- Vendor: UNA Inc
- Version: 13.0.12
It is only the home page that is broken - and only for visitors (non logged in users) or logged in users with incomplete registrations (not verified according to our custom verification solution provided by UNA). If a user is admin or completely verified and configured standard user, then the site works.
Also note: Antispam module won't update: error message is:
- Check module hash: Can't apply upgrade because too many files(17%) were modified in Antispam module
All customization was done by UNA. No third party modules or apps.
@BIG Marketing Solutions LLC @InPage @Zandra could you please specify your Timeline module version ?
-
Sorry to hear this isn't easy for you.
-
Glad to you were able to get to the bottom of your issue!
Yep, disabling the blacklist mod seemed to have resolved the issue.
-
Meh, I’m going to treat this as a lesson learned. Already ordered a couple large SSDs to toss in my home server so I can effectively snapshot the replica VM that runs UNA.
-
There are two types of people... those who have backups and those with no hair. lol
Meh, I’m going to treat this as a lesson learned. Already ordered a couple large SSDs to toss in my home server so I can effectively snapshot the replica VM that runs UNA.
-
@Andrey Yasko @Alex T⚜️ We were assured that we could safely upgrade our custom UNA site to stable 13. Now we are having multiple problems with database errors, and antispam module won't upgrade due to too many modifications. Errors are on home page when not logged in, or with logged in user who is not verified according to custom verification code written by UNA. Errors are on site and with hundreds of database error emails a day. We need your help in order to demonstrate the site to potential investors. Email has been sent detailing problems. You have login credentials on file. Please fix.
The site seemed fine after update to 13.1.0-B1 as long as I was logged in as admin. After logging out I get a nasty database error: Had to screenshot it because it wouldn't paste here as text
-
@AQB Soft kindly let us know when your Black Lists module has been updated.
Hello. The bug fixing update was released. We are sorry for inconvenience.
-
Thank you. That was nice and fast. The update appears to work perfectly.
-
Thanks for getting that fixed! We appreciate you!
