How to solve Vtiger error : "Duplicate Profile Exists" while changing profile privileges - crm

While updating field level privileges for profile in Vtiger CRM configuration, I get an error message : Duplicate Profile Exists

Bymistake clicking on the duplicate button, It looks like view but it duplicates the error. The right way to go for edit is click on 3 dots and there is edit button.
UX design flaw.

Related

Cannot delete project

I am unable to delete a project from the Nest Device Access Console. When I click the delete icon and click delete, it processes and comes back with a pop-up that says "Could not delete project" with no other information. If I try to delete the OAuth Client ID, it processes and comes back with a pop-up that says "Could not update project data" with no other info.
Any advise would be helpful.
Resolved: this seemed to be just a temporary issue with the website.

Make a Custom Report created in Acumatica ERP visible in Self-Service Portal

After configuring Portal Site Map for a report I get Error#0. Please see details below.
Not seeing anything on this question - Can someone point me to the documentation on this. I've been told this has to be completed via a customization project - before heading down that path surely I'm not the first to want to expose a report.
Thank you.
Mark Mynatt
Error:
2/19/2019 10:13:15 PM Error:
Error: You don't have enough rights on 'QQ301000.rpx'.
The error message implies that the report is visible on the portal. That's a great start. If it isn't/weren't visible you would have to first add it to the portal files and then add it in the sitemap.
The error message suggests it is an Access Right problem that prevents access to the report. Make sure the report is visible in sitemap and then lookup screen Access Rights By Role (SM201025) to see if Portal User and Portal Admin have access right to the report. If it's Not Set, that could be your problem. Try giving higher access rights (delete is the most permissive right you can give):

Gravity Forms are giving me a 404 error

I have been trying to update a Gravity Form and it is giving me a 404 error everytime I try to update it. I have even tried to press update when making no changes, same error.
Does anybody know why a gravity form may give 404 errors on update?
Sounds like the form you are trying to update has left the building.
Have you tried building a new form or looking at your DB to see if the form information is accurate? Sometimes a server timeout will cause information to be dropped in the DB and you system won't know it to correct it.

500 - Internal server error with "resource you are looking for, and it cannot be displayed."

I have created a entry page and created fields for all those. Now am trying to entered fields into my database.
My values are save in database but after saving my CRM page shows error like
500 - Internal server error. There is a problem with the resource you are looking for, and it cannot be displayed.
I think this error may be because of not enabling parent path and authentication rights in IIS.
I enabled the allow parent path in IIs->ASP,iis->Asp->debugging properties->send errors to browser->true
How to resolve this error?
I figured out that in IIS7.
I had to go to the site in question, to 'Error Pages' --> "Edit Feature Settings" and select "Detailed errors". It's a little dialog box that pops up with three radio buttons.
This fixed it for me. Simply setting "Send Errors To Browser" to true, did not do the trick.
Hope this helps someone.

Drupal: displaying warnings

how can I disable warnings for my users in Drupal (and keep them on only for the administrator) ?
thanks
You can't do this yet in Drupal 6.
An issue has been created for this.
However, you can disable all on-screen warnings by going to Administer > Site configuration > Error reporting as stated on the Book page for Securing Information from Visitors. Errors will still be viewable by the roles given permission to do so by going to: Admin > Reports.
Go to Administer > Site configuration > Error reporting (admin/settings/error-reporting). There you have a dropdown list under 'Error reporting' with the two choices you have for the error logging, being:
* Write errors to the log.
* Write errors to the log and to the screen.
Choose this option --> Write errors to the log
And save
you can try the Better messages module. Some more details about this module (from its project page):
Better Messages is a very simple module that provides "Popup-like" Drupal messages.
Better Messages intends to let you control where and how you want to see your Drupal messages! Combine different animations and override better_messages.tpl.php to create your custom look.

Resources