vt7.0.1 Non-admin users pages do not load fully

All the list views do not load for non-admin users.

In layouts/v7/modules/Vtiger/ListViewContents.tpl $CURRENT_CV_MODEL is not set at line 68 and this causes the page to stop loading. I have not yet found out why that is not set.

@liam Can you elaborate this issue. i.e How you created this user etc..

Hi Satish,

Yes, this was an install of vTiger on Ubuntu 14.04, first installed as vTiger 6.5 and just upgraded to v7.0.1. Existing users with the same role and the same permissions (view/edit all) but with the Admin box ticked and unticked have different behaviour. I created a new user and a new role, with the view/edit all permissions and this user exhibited the same behaviour. The user works perfectly if the admin tickbox is enabled, otherwise when you go to any of the list views only the top part of the page loads (see image below). It looks like the problem is related to the filters (or lists as they are now called).

With admin privileges disabled:

With them enabled:

User settings screen (with an arrow pointing to the admin setting that is being enabled/disabled):

Role permissions (these remain unchanged between working and not working):

If you need any more information - I'm happy to help.

@liam Hi, Please check if the tables "vtiger_cv2rs" and "vtiger_cv2role" exist. It could happen that during the migration from vt6 to vt7 these tables are not created causing your issue. If that's the case then we should submit a bug report about that.

Hi @simonetravaglini , those tables are both missing - thanks for the quick diagnosis.

@satish.dvnk we had this problem with a customer also in a fresh installation

Running the following SQL commands to create the tables has solved the issue:

CREATE TABLE IF NOT EXISTS `vtiger_cv2role` (
`cvid` int(25) NOT NULL,
`roleid` varchar(50) NOT NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

CREATE TABLE IF NOT EXISTS `vtiger_cv2rs` (
`cvid` int(25) NOT NULL,
`rsid` varchar(255) NOT NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

This came from this support ticket

In the migration scripts the tables should be created as follows:

	if (!Vtiger_Utils::CheckTable('vtiger_cv2role')) {
		Vtiger_Utils::CreateTable('vtiger_cv2role',
				'(`cvid` int(25) NOT NULL,
				`roleid` varchar(255) NOT NULL,
				KEY `vtiger_cv2role_ibfk_1` (`cvid`),
				CONSTRAINT `vtiger_customview_ibfk_3` FOREIGN KEY (`cvid`) REFERENCES `vtiger_customview` (`cvid`) ON DELETE CASCADE,
				CONSTRAINT `vtiger_role_ibfk_1` FOREIGN KEY (`roleid`) REFERENCES `vtiger_role` (`roleid`) ON DELETE CASCADE)', true);
	}

	if (!Vtiger_Utils::CheckTable('vtiger_cv2rs')) {
		Vtiger_Utils::CreateTable('vtiger_cv2rs',
				'(`cvid` int(25) NOT NULL,
				`rsid` varchar(255) NOT NULL,
				KEY `vtiger_cv2role_ibfk_1` (`cvid`),
				CONSTRAINT `vtiger_customview_ibfk_4` FOREIGN KEY (`cvid`) REFERENCES `vtiger_customview` (`cvid`) ON DELETE CASCADE,
				CONSTRAINT `vtiger_rolesd_ibfk_1` FOREIGN KEY (`rsid`) REFERENCES `vtiger_role` (`roleid`) ON DELETE CASCADE)', true);
	}

I believe that the table creation is failing on applying the foreign keys.

We have run the migration again and this time it worked. So this was only a problem in the migration script, thanks for your help.

Status changed to closed

Just to add I get this error on a fresh install too.

@liam Is there a particular reason why you used MyISAM as engine and latin1 as charset in the table creation queries? I ask this because most tables in vtiger are defined as InnoDB and use utf8 as charset.

Hi @ruben.estrada,

I've just had a look at this - and we do use InnoDB and utf8 - those queries were copied from someone else's support ticket. The ones that I actually used are:

• vtiger_cv2role

CREATE TABLE vtiger_cv2role (`cvid` int(25) NOT NULL, `roleid` varchar(255) NOT NULL, KEY `vtiger_cv2role_ibfk_1` (`cvid`),
CONSTRAINT `vtiger_customview_ibfk_3` FOREIGN KEY (`cvid`) REFERENCES `vtiger_customview` (`cvid`) ON DELETE CASCADE,
CONSTRAINT `vtiger_role_ibfk_1` FOREIGN KEY (`roleid`) REFERENCES `vtiger_role` (`roleid`) ON DELETE CASCADE);

• vtiger_cv2rs

CREATE TABLE `vtiger_cv2rs` (`cvid` int(25) NOT NULL, `rsid` varchar(255) NOT NULL, KEY `vtiger_cv2role_ibfk_1` (`cvid`),
CONSTRAINT `vtiger_customview_ibfk_4` FOREIGN KEY (`cvid`) REFERENCES `vtiger_customview` (`cvid`) ON DELETE CASCADE,
CONSTRAINT `vtiger_rolesd_ibfk_1` FOREIGN KEY (`rsid`) REFERENCES `vtiger_role` (`roleid`) ON DELETE CASCADE);

• vtiger_report_sharerole

CREATE TABLE `vtiger_report_sharerole` (`reportid` int(25) NOT NULL, `roleid` varchar(255) NOT NULL, KEY `vtiger_report_sharerole_ibfk_1` (`reportid`), 
CONSTRAINT `vtiger_report_reportid_ibfk_3` FOREIGN KEY (`reportid`) REFERENCES `vtiger_report` (`reportid`) ON DELETE CASCADE, 
CONSTRAINT `vtiger_role_roleid_ibfk_1` FOREIGN KEY (`roleid`) REFERENCES `vtiger_role` (`roleid`) ON DELETE CASCADE);

• vtiger_report_sharers

CREATE TABLE `vtiger_report_sharers` (`reportid` int(25) NOT NULL, `rsid` varchar(255) NOT NULL, KEY `vtiger_report_sharers_ibfk_1` (`reportid`),
CONSTRAINT `vtiger_report_reportid_ibfk_4` FOREIGN KEY (`reportid`) REFERENCES `vtiger_report` (`reportid`) ON DELETE CASCADE,
CONSTRAINT `vtiger_rolesd_rsid_ibfk_1` FOREIGN KEY (`rsid`) REFERENCES `vtiger_role` (`roleid`) ON DELETE CASCADE);

@liam Thank you very much for your replay. Yes, I saw those same table definitions in the Vtiger forum but then started to wonder why those particular settings were used. Now I also wonder why this issue has been closed if this is still an ongoing issue with fresh Vtiger 7.0.1 installs. I'm not sure that bug has been fixed.

mentioned in issue #664 (closed)