vtigercrm | vtiger CRM -

If you have no custom code of your own, I would suggest the following steps -

1. Backup your code and database for 6.5
2. Uninstall your vtiger 5.4 version
3. Install XAMPP with PHP7.1 support. Moving away from the standard vtiger installer will let you upgrade to future versions of PHP/apache without this hassle.
4. Import your database to this new XAMPP and setup the code (you will need to change the config.inc.php)

If everything goes fine, you should have your 6.5 version back working normally and you should be able to upgrade to vtiger 7.

Some pointers -

1. The new XAMPP installation will have different PHP/mysql settings
2. Check the Mysql UTF-8 support when creating db
3. Don't panic if you see lot of notice/warnings, it just means your php.ini is not configured properly yet

I did a quick bit of Googling and found these 2 projects which may be interesting:

• ngx-permissions
• Akita

I am not affiliated with either.

That said, there is a bigger question you want to ask yourself: is there any logic to the roles and permissions? In other words, do you want to have to manually assign permissions to roles / users or could you possibly write a policy that would determine what users can do based on attributes?

If so, you need to look into Attribute-Based Access Control (abac) which will simplify your authorization management. Rather than creating hundreds of roles and thousands of permissions which you then need to manually assign to users (and do the governance thereof - i.e. recertify, remove...), you could just create policies along the lines of:

• An assistant can create a report if...

The language to write these policies is called ALFA, the abbreviated language for authorization. It's a standard by OASIS. It gets converted to XACML which you can then feed to an authorization service e.g. AuthZForce (open source) or Axiomatics (commercial).

I hope this helps a little.

Did you change the path in the config.inc.php folder?

From your shared nginx log, there is so many bot service request are come to the EC2 instance. The bot service are trying to crawl your web site like "YandexBot/3.0" may use the EC2 instance bandwidth heavily.

error is generating because of invalid "error_reporting" variable in php.ini

as you may know , the required value of error_reporting for installing vtigercrm is "E_WARNING & ~E_NOTICE & ~E_DEPRECATED & ~E_STRICT"

so if current value is E_All or something else , In php.ini set "error_reporting" as below

error_reporting = E_WARNING & ~E_NOTICE & ~E_DEPRECATED & ~E_STRICT

There are three solution, A) Make dynamic content in your code B) Clear Smarty Cache in your code C) Disable caching in vTiger

If option A works, it is most effective

one is to put a little footer or header in your code that changes the content to let smarty clear cache itself( for example put Date() or a number.

Second solution is to look for SMARTY to clear cache:

So I see at least a few potential issues, and have some questions. First, some background --

Iterators in QuickBooks work just like a database cursor. Part of that means that you can't have two iterators open at once - you have to finish with one iterator before you start and/or continue another iterator. So if you do this, you'll get the error you're seeing:

1. Start iterator #1
2. Fetch some data from iterator #1
3. Start iterator #2
4. Try to fetch some data from iterator #1 again

That will fail because starting the second iterator has closed/killed the first iterator. This is probably what's happening to you.

What is this?

$extra['iteratorID'] = $saved_iterator_id; // From Table

That looks like an undefined variable to me. Did you check your PHP error logs?

Why are you saving this to a table, and what table are you saving it to? Where in the code are you pulling it back out of the table? I don't see any code that gets it from the table.

After lot of research i found out that i needed to update vtiger_ws_referencetype table for making the relation. Here is the query for the same. In my case custommodulename will be replaced by Leaves.