General error after upgrade to last 1.7.50.8

Hi all, yesterday I got a strange error after upgrading. My all site is not working anymore giving this error on each page.
Twig \ Error \ RuntimeError
An exception has been thrown during the rendering of a template ("copy(/var/www/grav/vendor/getgrav/image/Gregwar/Image/images/error.jpg): Failed to open stream: No such file or directory").

so first I though I was missing something and retry. Then I also update all plugins. Then I removed all plugins and theme (mundata). I also controlled dir & files rights
Nothing more.
So I thought options in items.fr.md or default.md were broken and took one, make it the most simple, only one title.
Nothing more again.
Then I tried (a bit of luck) to remove all images from the directory where the .md resided, thinking of the error message.
And it works !:thinking:
So at this time, pages work only if I don’t insert any pictures. Very annoying.:grimacing:
I search for this Gregwar stuff and did not found any directory with this name. Is something missing with this version ?
Any idea on how to improve that kind of bug ?

Thanks a lot for any help :melting_face:

@Francois, Andy (aka rhuk) is making lots of changes to 1.7 and seems to go 2 steps foreward and 1 step backward…

Unfortunately, most issues are not being logged on the Grav repo, but reported on Discord. Hence, it’s hard to find if your issue is a known issue.

Your issue seems to be a Grav core (or its libraries) related, which should be reported at the Grav repo. Andy doesn’t visit this forum, but lives on Discord and Github.

woh… thanks a lot for the answer. I posted on GIT and I will try to rollback today.
you mention discord, what’s the group name please ? I can’t find it…

1 Like

I finally rolled back to v1.7.42.3 and it’s OK.

A note today from Andy (the lead developer):

:police_car_light: FYI, i’ve removed ALL the 1.7.50.x releases until I can get a handle on the safe-upgrade issues that we’ve been having. This was intended to be a better upgrade system for Grav, but it’s actually been a nightmare, and is causing more issues than it solves. The next version will be a 1.7.51 release with these issues sorted :crossed_fingers:

1 Like