Why hello @jibe9191 Welcome to the community!
Usually that happens if the files doesn’t have the correct permissions. If what is happen is that you have a custom module, you save & deploy changes made to the edit/detail view that usually is because the system can’t update the files to accurately reflect your changes and thus shows what was there previously.
Ensure your files permissions and ownership of those files are correct first of all.
Make sure that www-data is your server’s user, you can quickly check by viewing the Scheduler’s admin page and that’ll show you the correct user to use.
Is SavedSearch your custom module name? Well, first off that doesn’t exist. Did you deployed your custom module via module builder? After which do a repair & rebuild (ensure the permissions are correct).
SavedSearch is not the name of my custom module. The name is Swap.
I initial created the module via the Module Builder and it was the same issue I then reinstalled a fresh SuitCRM 8 and deployed via the module loader from both export and publish package from a working SuitCRM Version 8.0.0-beta.3 and Version 7.12 did the repair & rebuild yet the same error.
My permission was based on the guideline in:
If i could followed similar guideline to get SuitCRM Version 8.0.0-beta.3 to work then what could be wrong?
Debugged graphql from netwoork tool and found some errors:
1- We were wrong using variable $mod_strings in vardefs.php of a module
2- We were using in view.detail.php of the module the deprectated constructor call parent:ViewDetail() and SuiteCRM8 didnt like that. We replaced it for parent::__constructor() and it worked fine
By the way, we found 2 compatibility issues with our SuiteCRM7 module within the vardef definition
We were using the property “popupHelp” in some fields to display a help tooltip in each field. In SuiteCRM 8 this tooltip doesn’t appear anymore.
We were difining this property to some of the fields:
We found in our side there is a code that isn’t compatible with SuiteCRM 8. You can find the code in any of the view.xxxx.php files inside the views folder of the module. For example, if your module is Swap, the folder would be: /modules/Swap/views/view.xxxx.php
Check for any code that look like parent:ViewDetail() and replace it by __constructor() . It could be ViewDetail() or ViewEdit() or ViewList().
I know it was mentioned before however, I’d like to confirm you ran a “Quick Repair and Rebuild” from the Repair Menu in Admin Panel after you made the changes?
When you run this command do you get any chances displayed in the blue section at the bottom?
When looking at the database via an application like PHPMyAdmin are you able to see the new field added to those records in the correct table?
I have the same problem with 8.1.2.
Today I updated to 8.1.3, but the problem continues.
I checked the files in the “custom” folder and the changes I made in EditView (in Studio) are in “editviewdefs.php”. When I edit the form the fields are the DetailView and not the EditView. The same with the creation form, the fields are the same as the DetailView.