Thread Details
  • State Suggested Answer
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 366 subscribers
  • Views 2078 views
  • Users 0 members are here
Forum Actions

trying to upgrade Sugarcrm Pro from v10.0.4 to v11.0.0. Failed opening URIScheme.php

Manson ho
I did

composer dump-autoload

composer install

before running CliUpgrader.php, but still getting this error


[Upgrader] - Add new OOTB scheduler job 'class::SugarJobProcessTimeAwareSchedules'

[Upgrader] - PHP: [2] include(/home/temp/code/sugarcrm11/sugarcrm/SugarPro/vendor/composer/../ezyang/
htmlpurifier/library/HTMLPurifier/URIScheme.php): failed to open stream: No such file or directory in
/home/temp/code/sugarcrm11/sugarcrm/SugarPro/vendor/composer/ClassLoader.php at 480

[Upgrader] - PHP: [2] include(): Failed opening '/home/temp/code/sugarcrm11/sugarcrm/SugarPro/vendor/
composer/../ezyang/htmlpurifier/library/HTMLPurifier/URIScheme.php' for inclusion (include_path='/home/
temp/code/sugarcrm11/sugarcrm/SugarPro:/home/temp/code/sugarcrm11/sugarcrm/SugarPro/vendor:.:/usr/share/php')
in /home/temp/code/sugarcrm11/sugarcrm/SugarPro/vendor/composer/ClassLoader.php at 480


Any ideas would be appreciated.
Thank you.
  • 0

    after copy all missing files in vendor and src, finally can make the upgrade to v11.0.0 success.

    But the problem is now all custom modular is gone, how can I fix it?



  • 0 in reply to Manson ho

    If you upgraded a copy of your SugarCRM with all your customizations in it, and your customizations were done following the upgrade safe rules, your custom modules should all still be there. I'm not sure why you would ever go back to the Module Loader after an Upgrade.

  • 0 in reply to Francesca Shiekh

    Hi Francesca,

    Thank you for your reply.

    Because it's my first time to do upgrade, so I am not sure if the custom module not showing in the module loader mean something go wrong on my upgrade.

    This is our custom module and our previous developer do the upgrade last year, all these custom module is still showing in the module loader.

    Anyway I can add these module back in the module loader?

    Thank you.

  • 0 in reply to Manson ho

    Just because you don't see the packages in module loader does not mean that the modules are not there. Check you instance to make sure they are there and you can use them.

    I never worried about the history of the packages not being there, and frankly never even checked to see if they disappear with an upgrade. I just check to see that the modules are there and I have my quality assurance people do a round of post-upgrade health checks that include customizations.

    If you need to see them back for some reason, you should contact support so they can help with your particular instance.

    Or maybe someone here else has a better suggestion.

  • 0 in reply to Francesca Shiekh

    Thank you Francesca.

  • 0 in reply to Manson ho

    Since this is a onpremise by the looks of it can you verify the contents of the upgrade_history table in the database? If the table is empty verify in a backup if something got deleted between upgrades.

  • 0 in reply to Jeroen Somhorst

    you are right, some record was deleted in upgrade_history table.
    I can manually insert back and it was loading in module loader now.
    Thank you.