Website turned white after update to 2.0.3.: Page 2 - Support Central

Website turned white after update to 2.0.3.

niobee78

saguaros First I updated from 2.0.1 to 2.1.0 and got a white page.. then I tried tu update step by step, hoping this would solve the issue... so I went from 2.0.1 to 2.0.2 without problem, but then from 2.0.2 to 2.0.3 it went white...
Will try what you suggested this afternoon, now I'm at work! Thank you!

saguaros

niobee78 Let me know if you still need help then.

niobee78

This message is visible to Moderators only

hidden content

saguaros

This message is visible to Moderators only

hidden content

niobee78

This message is visible to Moderators only

hidden content

saguaros

niobee78 It keeps redirecting. I put my IP in above reply.

niobee78

This message is visible to Moderators only

hidden content

saguaros

It still redirects to your live site.

niobee78

This message is visible to Moderators only

hidden content

saguaros

niobee78 Let me check and will get back to you.

niobee78

@saguaros any news? I see you made some tests, but an update of the template still brings back a white webpage... I suppose I will stick to v. 2.0.2 😅

niobee78

niobee78 up 👆

saguaros

I'm taking a backup of your site and debug in my local, pls wait.

niobee78

@saguaros any news?

vangogh

I attached the solution below. The file has been changed templates/ja_stark/html/layouts/chromes/T4Section.php. Beside that the issue has already fixed in the latest Ja Stark version 2.1.0.
Please check and let us know how it goes.

bugfix-ja-stark-v203.zip

1kB

Regards,

saguaros

Hi

Our developer is looking into this issue, will get back to you shortly.

niobee78

vangogh Thank you, will try this fix this evening!
How do I proceed? Do I need to update first and then apply the fix or vice versa? First the fix and then the update of the template?

niobee78

I have overwritten the file you sent me and then updated the site to 2.1.0 but this results in a white website.
Then I tried to overwrite again the file you sent as bugfix and this solved the issue!

So I suppose the right procedure is: update the template to 2.1.0 and THEN apply bugfix 😝

In any case, will try this on my production site too, just to check! but I think the problem is solved!!

Thank You!

niobee78

I confirm!! The PATCH is working! Thank you again so much for your effort.

« Previous Page