Skip to content Skip to sidebar

Home › Support › English Support › [Escalated to 2nd Tier] Bug Report: 400 Bad Request due to double slash in OTGS Installer asset URL

[Escalated to 2nd Tier] Bug Report: 400 Bad Request due to double slash in OTGS Installer asset URL

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun Mon Tue Wed Thu Fri Sat
12:00 – 20:00 12:00 – 20:00 12:00 – 20:00 12:00 – 20:00 12:00 – 20:00 - -
- - - - - - -

Supporter timezone: Asia/Karachi (GMT+05:00)

Tagged: 

This topic contains 1 replies, has 0 voices.

Last updated by Noman 3 months, 1 week ago.

Assisted by: Noman.

Author Posts
January 14, 2026 at 12:44 pm #17729306

tomaszG-18

Hello WPML Team,

I am writing to report a small bug I encountered in the sitepress-multilingual-cms plugin regarding asset loading.

I noticed a 400 (Bad Request) error in my browser console related to an SVG file within the OTGS Installer vendor folder. The issue appears to be caused by a malformed URL containing a double slash (//).

The specific error: GET .../wp-content/plugins/sitepress-multilingual-cms/vendor/otgs/installer//res/img/icon-wpml-info-white.svg 400 (Bad Request)

Diagnosis: It seems to be a string concatenation issue in the code. The base path for the OTGS Installer likely has a trailing slash, and the code appends the relative path with another leading slash (e.g., /res/img/...), resulting in the invalid //res/ path.

Could you please pass this to your development team to fix in the next update? My server configuration rejects these URLs, so I assume others might face the same issue.

Thank you!
January 14, 2026 at 5:52 pm #17730779

Noman

I’ve escalated this to our 2nd tier support team. I’ll update you as soon as I hear back.

Thank you for reporting this and for the detailed explanation