Announcement

Collapse
No announcement yet.

Update to 8.2.0 failed

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • ChrisSka83
    commented on 's reply
    So this function was not from Ebla Link Pro.
    I have now installed the update and this ingenious function no longer exists.
    So it must have been directly from espoCRM.

  • espcrm
    commented on 's reply
    Thanks Big Boss Kharg!

  • Kharg
    commented on 's reply
    Will be updated soon

  • Kharg
    commented on 's reply
    update download all attachments to 1.2.0 as it supports Espo 8.0.0+

  • espcrm
    replied
    Originally posted by espcrm View Post

    So here I "fix" mine (THIS IS NOT RECOMMENDED SINCE I DON"T KNOW THE CONSEQUENCES YET)... I rename the ManualScheduled.php file without extension so it can't
    And looking at the screenshot, I think I found the culprit!

    Click image for larger version  Name:	image.png Views:	7 Size:	4.8 KB ID:	104339
    So what I did afterward was to uninstall this extension.
    Last edited by espcrm; 04-03-2024, 07:35 AM.

    Leave a comment:


  • espcrm
    replied
    Originally posted by espcrm View Post

    How did you fix it? I got a similar error

    Related thread: https://forum.espocrm.com/forum/inst...ause-error-500
    So here I "fix" mine (THIS IS NOT RECOMMENDED SINCE I DON"T KNOW THE CONSEQUENCES YET)... I rename the ManualScheduled.php file without extension so it can't run... I can list again but surely this is not how to fix it. I await more experience user to fix or perhaps v8.2.2 or extensions update to fix these error.

    For reference. Here is all the extension I'm currently using. One or more of these is extension is causing the error that used the "class" services that were removed in 8.2.0

    Click image for larger version

Name:	image.png
Views:	125
Size:	10.5 KB
ID:	104330
    Click image for larger version

Name:	image.png
Views:	102
Size:	114.2 KB
ID:	104331
    Click image for larger version

Name:	image.png
Views:	101
Size:	29.5 KB
ID:	104332

    Leave a comment:


  • espcrm
    commented on 's reply
    Kharg it shouldn't be Elba Link Pro, because I don't have it. From Elba all I have now is his Dark theme and DAV Integration.

  • espcrm
    replied
    Originally posted by ChrisSka83 View Post
    ok, somehow I've managed it now.
    Everything works. Top!

    But what I've just noticed is that an ingenious function has disappeared.
    If I want to enter a contact in the field of an entity, but it doesn't exist yet, I was always offered to create it directly until version 8.1.5.
    The window to create the contact always popped up.
    Unfortunately, this no longer happens.

    Have I removed it or do I have to reactivate it somewhere?​
    How did you fix it? I got a similar error

    Related thread: https://forum.espocrm.com/forum/inst...ause-error-500
    Last edited by espcrm; 04-03-2024, 06:38 AM.

    Leave a comment:


  • ChrisSka83
    commented on 's reply
    may be possible. I had to deactivate this as it was not compatible with 8.2.0.

  • Kharg
    commented on 's reply
    I think this is a feature of Ebla Link Pro?

  • ChrisSka83
    replied
    ok, somehow I've managed it now.
    Everything works. Top!

    But what I've just noticed is that an ingenious function has disappeared.
    If I want to enter a contact in the field of an entity, but it doesn't exist yet, I was always offered to create it directly until version 8.1.5.
    The window to create the contact always popped up.
    Unfortunately, this no longer happens.

    Have I removed it or do I have to reactivate it somewhere?​

    Leave a comment:


  • yuri
    replied
    The error message you get tells everything. The class you extend from is no more. You need to extend from Espo\Services\Record.

    Leave a comment:


  • item
    commented on 's reply
    go to application/Espo/Modules/ManualScheduledJob/Services/ManualScheduledJob.php

    and read 8.2v annoncement in forum

    this passage :
    Service classes from this directory and some classes from Espo\Services namespace have been removed. If you extend any of these classes in your customizations, extend from Espo\Services\Record instead.

  • ChrisSka83
    replied
    Then at least the standard entities should work, or am I wrong?
    #Contact, #Meeting, task etc.

    None of them work. In the backend I also can't get into
    #ScheduledJob or #Admin/extensions

    Leave a comment:


  • yuri
    commented on 's reply
    Reminding for whomever reading. Consider not to extend anything when possible.
Working...
X