We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 10702
    • 107 Posts
    Usually links in MODx are inserted by adding for example: <a href="[[~123]]">

    But now I want to link to a ssl-webpage like https://www.example-abcde.com/example.html

    Is this the correct syntax for this purpose?
    <a href="https//:[[~123]]>

    Or do I have to manage the problem in a different way?

    Thanks a lot in Advance!
    Gerdi
      • 28215
      • 4,149 Posts
      [[~123? &scheme=`https`]]
        shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
        • 10702
        • 107 Posts
        Thanks a lot!!!
          • 10702
          • 107 Posts
          And if I want to make a ssl-link in the wayfinder, do I have to add scheme=`https` in the "Link Attributes:" of the resource or how does it work?

            • 10702
            • 107 Posts
            Does anybody know how to put a single ssl-link between normal links in the wayfinder?

            Where do I have to add "scheme=`https`"? Do I have to put it in the "Link Attributes:" of the resource or anywhere else?

            I hope anybody knows this...

            Gerdi smiley
              • 10702
              • 107 Posts
              Meanwhile we tried different ways to encrypt a single page by using ssl (https) but nothing really worked.

              Therefore my question: How do others encrypt a single page? Is it maybe possible to change a configuration-field in the "page settings" of a resource?

              Would be great if anybody has experience making this work.

              Thanks a lot in advance!
              Gerdi smiley
                • 1343 ☆ A M B ☆
                • 2,213 Posts
                You could use a snippet to check if the page URL started with HTTPS and if not redirect them to the same page using HTTPS... It’s crude, but should do the trick. You could also look at some of the Evolution add-ons that accomplish this same task.

                AMDbuilder
                  Patrick | Server Wrangler
                  About Me: Website | Tweets |  MODX Hosting
                  • 10702
                  • 107 Posts
                  Hi AMDbuilder,
                  the consequence of such a solution is probably a high time delay. Do you think there is an other hopefully faster way to manage a ssl-encryption for single pages?
                    • 22303 MODX Staff
                    • 10,725 Posts
                    Quote from: Gerdi at Nov 08, 2010, 04:43 PM

                    Hi AMDbuilder,
                    the consequence of such a solution is probably a high time delay. Do you think there is an other hopefully faster way to manage a ssl-encryption for single pages?
                    High time delay? Not at all; the plugins or snippets designed for this are fairly efficient. You just need to adopt and test on Revolution most likely.

                    You can also manually force the generated links by using the scheme property on Resource link tags, e.g.
                    [[~12? &scheme=`https`]]

                    See http://rtfm.modx.com/display/revolution20/Resources#Resources-URLSchemesinResourceTags for more information.
                      • 12958
                      • 9 Posts
                      I tried the following: setting wayfinders property ’fullLink’ to "No", so that the generated links are relative. Then changed the alias of the concerned ressource (for example "test") into "https://www.domain.tld/test". Worked very well in one project, no redirect was necessary, wayfinder generated the desired link! BUT: I wanted to copy this solution to another website-project which also runs under revo where it doesn`t work huh The alias "https://www.domain.tld/test" is well produced by wayfinder and displayed in the address-field of the Browser, but produces an error-message: file doesn’t exist. When the alias is resetted to "test", I can *type in* the same address and the site is displayed properly. Also if the alias is set to another resource-alias (e.g. "https://www.domain.tld/anothersite") this link works well. I would be very glad if anyone has an idea what the reason for this behaviour might be?
                      Thanks,

                      Inka