[Gelöst] URGENT: 502 bad gateway since latest update
This support ticket is created vor 6 Jahren, 2 Monaten. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Heute stehen keine Supporter zur Arbeit im Werkzeugsatz-Forum zur Verfügung. Sie können gern Tickets erstellen, die wir bearbeiten werden, sobald wir online sind. Vielen Dank für Ihr Verständnis.
I get on specific pages a 502 bad request, on some pages, where views are inserted. My hoster says disabling views plugin solves this issue and so it is.
Can you please solve this problem as soon as possible?
Thank you for contacting Toolset support. I tried to login to your site but it says “401 Authorization Required” (security username and password needed).
I have logged in to your site and visited number of pages but I can not see any issue in them. Could you please provide me page/view link where I can see that issue.
Thanks for the link, Now I can see the 502 issue. To further debug this issue I need to request you please provide temporary access (WP-Admin and FTP Login info) to your site (preferably staging site), so that I can look into your setup and check the issue.
Your next answer will be private which means only you and I have access to it.
=== Please backup your database and website ===
✙ I would additionally need your permission to de-activate and re-activate Plugins and the Theme, and to change configurations on the site. This is also a reason the backup is really important.
I have thoroughly debugged this issue, when I remove resize='proportional' attribute from the Specialist Image field, all seems to be working fine and the design still looks the same on the frontend, please check and confirm: versteckter Link
Basically its not a bug, it looks some sort of conflict either on server side or with the data in the database for the terms, which happens only in this particular site. Because I tried to reproduce this same issue in my test site and the resize='proportional' attribute works fine for me.