Double Slashes (//) and Uneditable URLs in Page Settings – Causing Issues in Translated Projects

Hi RapidWeaver Elements team,

First of all, thank you for a great product – I really appreciate the flexibility and Tailwind-based workflow.

I wanted to report a couple of issues I’ve encountered recently, which are significantly affecting my workflow when building multilingual websites.

  1. Double Slashes (//) in URL Paths
    RW Elements now seems to automatically insert a double slash (//) when linking to internal pages. For example, instead of /Sound-systems-for-lighting-tracks/, it becomes //Sound-systems-for-lighting-tracks/. This behavior was not present before – it didn’t add the extra slash initially, but started happening after a recent update. I want to clarify that I have not manually added any extra slashes, and it appears even on the main page. It might be related to the feature that auto-fills URLs. The issue becomes much more time-consuming when duplicating the project to create translated versions (e.g., /se/, /dk/), since every instance has to be corrected manually.
  2. Broken URL Paths When Using Subfolders
    When setting a publishing path like se for the Swedish version, I sometimes end up with broken or malformed URLs in the page settings. In many cases, the field is grayed out and can’t be edited. This results in unexpected folder structures when publishing and creates inconsistencies that impact internal linking and SEO.

These issues are creating a lot of extra work in what was previously a very smooth workflow. I’d really appreciate it if you could look into this or suggest a workaround to avoid these problems.

I noticed this specifically because I’m now in the final step of setting up hreflang tags on each page under Edit Extra Code – and that’s when I began seeing the inconsistent URLs and double slashes across the project.

Thanks again for a great product – I really enjoy using RW Elements and hope this helps improve things further.

Best regards,
Henrik

Elements 1.0.9 (23745 ) - #4 by dan - @dan don’t forget to remove the / in your sample below the web adress or people will get confused

1 Like

Hi, this only happens if you add the trainling / at the web sites address in the general settings and/or the publishing settings.

1 Like