1,415
edits
Changes
Added error "Not unique table/alias" to the VtigerCRM error page
::: The INSERT clause should consist of the following data: (1st available identifier, '<module_name>', 'include/Webservices/VtigerModuleOperation.php', 'VtigerModuleOperation', 1) .
::: The INSERT clause should consist of the following data: (1st available identifier, '<module_name>', 'include/Webservices/VtigerModuleOperation.php', 'VtigerModuleOperation', 1) .
:: '''Solution 2:''' Rewrite the module creation code inserting a call to function '''$'''<module>'''->initWebservice();''' in the line following the '''$'''<module>'''->save();''' instruction. The function will populate table '''vtiger_ws_entity''' with the proper data.
:: '''Solution 2:''' Rewrite the module creation code inserting a call to function '''$'''<module>'''->initWebservice();''' in the line following the '''$'''<module>'''->save();''' instruction. The function will populate table '''vtiger_ws_entity''' with the proper data.
----
----
:::: '''php''' ''-f'' ./ResetPassword.php
:::: '''php''' ''-f'' ./ResetPassword.php
:::* Once done remove the script.
:::* Once done remove the script.
----
== Error "Not unique table/alias" ==
This error appears while '''creating a report mixing standard modules and custom ones'''. Suppose you want to relate standard module "Contacts" to custom one "Policy", the returned error is:
Report generation failed!
Not unique table/alias: 'vtiger_accountRelPolicy'
Where Policy is my custom module.
: ''Tentative bug diagnosis:'' This is a documented bug in VtigerCRM code resulting in non unique alias generation for table names. The resulting SQL string cannot retrieve any data from the related tables.
:: '''Solution:''' A bug related discussion can be found in the [https://forums.vtiger.com/viewtopic.php?t=26517 VtigerCRM forum] where a [https://forums.vtiger.com/download/file.php?id=3397&sid=c23b4e86e5afee8fd29e995ca9402084 patch] is provided.
:::* Download the patch.
:::* Copy the patch in the '''data''' sub-directory of your VtigerCRM installation tree where the '''CRMEntity.php''' file is located.
:::* Optionally rename the patch file in CRMEntity.patch. I did it only for the sake of clarity.
:::* Apply the patch running the '''patch''' command:
root@vms140v32:/var/www/htdocs/vtigercrm521_pro/data# '''patch''' ''-p0 -i'' CRMEntity.patch
patching file CRMEntity.php
Hunk #1 succeeded at 1890 (offset 18 lines).
patching file CRMEntity.php
Hunk #1 succeeded at 1953 (offset 18 lines).
:::* The patch command will automatically create a back-up copy of file CRMEntity.php: '''CRMEntity.php.orig'''.
:: The issue should be solved.
----
== Error "You are not permitted to execute this Operation" ==
Any action taken against the custom module fails returning error "You are not permitted to execute this Operation" to screen. The issue is related to the new custom module and does not affect the standard software behavior.
: ''Tentative bug diagnosis:'' Php scripts are affected by a lack of permissions.
:: '''Solution:''' Check for the script user and group to be the '''same which run the Web Server''' otherwise reassign user and group. If the user / group change were not decisive, temporarily assign permission '''755''' the the scripts in order to perform further checks. Please recover previous permissions at check completion. Granting higher than required permissions is a bad option when dealing with production environments connected to the Internet and could result in a security risk. The practice should be avoided for hosts other than development and test ones.
: ''Tentative bug diagnosis:'' The unique identifier for the related entity consists of multiple fields, but only some are flagged as "Required".
:: '''Solution:''' Update file <entity>.php setting '''$required_fields''' value equal to the parameter list passed to '''Vtlib''' function '''setEntityIdentifier''' in the module creation code.
----
----