C
Callya
·
Added a discussion
Travel Module - DB Error when opening travel entry

Hey @Jerome Mingo ,

I'm planning to use the Travael Module to let my users show where they travel to, but in the current version it is not usable because when I add a test entry it gets added the next page the Entry and there is a problem with an SQL query:

SELECT * FROM `bx_persons_data` INNER JOIN `sys_profiles` ON `sys_profiles`.`content_id`=`bx_persons_data`.`id` INNER JOIN `bx_persons_meta_locations` ON `bx_persons_meta_locations`.`object_id`=`bx_persons_data`.`id` INNER JOIN `sys_profiles` ON `sys_profiles`.`id`=ABS(`bx_persons_data`.`author`)WHERE 1 AND `bx_persons_meta_locations`.`country` ='DE' AND `bx_persons_meta_locations`.`city` ='Berlin' AND `sys_profiles`.`status` ='active' AND `sys_profiles`.`type` IN('bx_persons') AND `bx_persons_data`.`author` <>'3' AND `sys_profiles`.`status` ='active' AND 3 NOT IN (SELECT `content` FROM `aqb_black_lists_profiles` WHERE `initiator`=`mz_travel_entries`.`author`) AND 3 NOT IN (SELECT `content` FROM `aqb_black_lists_profiles` WHERE `initiator`=`mz_travel_entries`.`author`) LIMIT 0, 13

Error message is: "Not unique table/alias: 'sys_profiles'"

The same error occurs when you try to open the entry.

Used UNA Version is 14.0.0

Additional this module does not use the default Cover image when no cover image is uploaded by the user.

Please advise how to fix the issue with the entries.

Thank you

  • 95
  • 1
Comments

    • Most of its modules are not updated.. I wonder if he will respond...

      • Hello @Callya !

        This query has too many mentions of the Error message is: sys_profiles'. You'd better ask the vendor about it, but as dear PaveLS's mentioned the chances getting answers are too low...

        • C

          Yeah, I can read the SQL (many years of xp with MySQL, PostGreSQL, MS-SQL and IMS DB) but with una modules almost no xp. So I definitely need the help from @Jerome Mingo. I've contacted him already via dm

          • Hello @Callya If you know how to use SQL, have you seen this?? aqb_black_lists_profiles

            I assume the subquery was supposed to check if the current user is on the blacklist of the author of the record.

            You would have to temporarily disable the AQB Black list, but whether Jerome's patch for the Tavel module will be available is up to the stars. :)

            • C

              I've disabled the blacklist module. Does not help.

              In my opinion is the problem here:

              INNER JOIN `sys_profiles` ON 
  `sys_profiles` .`content_id`=`bx_persons_data`.`id` 
INNER JOIN `bx_persons_meta_locations` ON 
  `bx_persons_meta_locations`.`object_id`=`bx_persons_data`.`id` 
INNER JOIN `sys_profiles` ON 
  `sys_profiles`.`id`=ABS(`bx_persons_data`.`author`)

              The sys_profiles table is joined two times without defining an alias for them. This results in a "confusion" when then later in the WHERE clause (for example) 

              `sys_profiles`.`status` ='active'

              mentioned. The table is joined two times and the DB does not know from which joined table the data should be taken.

              Login or Join to comment.