Upgrade destroyed something

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • esforim
    replied
    You can grab all the version here or even track down the file changes from your version until the current version if you know how to use Git (I don't but have play with that function at one time, used GitKraken)

    EspoCRM – Open Source CRM Application. Contribute to espocrm/espocrm development by creating an account on GitHub.

    Leave a comment:


  • Fehu
    replied
    Yuri,

    Nothing on my end was renamed in regard to the program. Is there a version 5.8.2 file O can download and do a file compare?

    Thanks,
    Marcus

    Leave a comment:


  • yuri
    replied
    Ok. So my suspicion that it was caused by file renaming is wrong. 90% that the problem is not related with upgrading EspoCRM. I'd try to make a copy on another server just to test.

    Leave a comment:


  • Fehu
    replied
    Hi Yuri. It's 5.8.2

    Leave a comment:


  • yuri
    replied
    I looked through the thread and could not find what version are you actually have.

    Leave a comment:


  • Fehu
    replied
    I've tried any things to upgrade to 5.9 but it only displays the blue line when loading therefore, I always delete everything and restore the backups because I know they work. I have further isolated the issue, as far as I can tell.

    When I modify something in the Entity Manager (Leads, specifically) and add new fields to leads and then followup and add something to leads in the Layout Manager it causes the blue line issue. I used WinMerge to determine which files were different and then Code Compare everything points to the following: \custom\Espo\Custom\Resources\layouts\Lead\detail. json

    Thanks.
    Marcus

    Leave a comment:


  • tothewine
    commented on 's reply
    if $data is null wouldn't trigger this ? https://github.com/espocrm/espocrm/b...onfig.php#L209
    Last edited by tothewine; 06-26-2020, 04:10 PM.

  • yuri
    replied
    Assuming you have 5.9 version

    This invokes saving:
    https://github.com/espocrm/espocrm/b...onfig.php#L216

    https://github.com/espocrm/espocrm/b...nager.php#L200


    Not that $useRenaming param is set to true.

    Leave a comment:


  • yuri
    replied
    When you make a customization in the layout, it clears cache, clear cache makes a modification in config.php. Layout manager is not a culprit.

    So every time config.php is changing it's set to NULL due some reason.

    Leave a comment:


  • Maximus
    replied
    Hi there.

    > Does anybody have a list of files affected when a update is made in the Layout Manager.

    1. Download this upgrade package from here https://www.espocrm.com/download/upgrades/.
    2. Uzip the package.
    3. Investigate:
    - /files/application/Espo/Resources/metadata/
    - /files/application/Espo/Modules/Crm/Resources/metadata/

    Leave a comment:


  • Fehu
    replied
    I have determined the error happens when I modify the following: Customization > Layout Manager

    If I replace all files with a back up all is okay and the CRM is back online.

    Does anybody have a list of files affected when a update is made in the Layout Manager. In essence, I'm modifying the lead page only and it crashes the CRM

    Thoughts?

    Leave a comment:


  • Fehu
    commented on 's reply
    Hi tothewine. I'm not sure at the moment but will try that when it goes down this afternoon..

  • tothewine
    commented on 's reply
    what does it show if you click the "VM61:1" link? maybe it's outputting something when it shouldnt

  • Fehu
    replied
    I upgraded from the version I was running (5.8.2) through the various upgrade versions to the current version. I had to use UI upgrade. In maintenance mode it loaded on one browser but once I cleared the cache I got the think blue line again. Attached is the console view showing some errors.I upgraded from the version I was running (5.8.2) through the various upgrade versions to the current version. I had to use UI upgrade. In maintenance mode it loaded on one browser but once I cleared the cache I got the think blue line again. Attached is the error message from console.

    Thanks,
    Marcus

    Leave a comment:


  • yuri
    replied

    Leave a comment:

Working...