We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 23085
    • 9 Posts
    We have a problem with the weblogin when we use friendly urls. Without friendly urls the form action looks like this:
    <form method="post" name="loginfrm" action="/index.php?id=2">

    This is wrong on itself because there should not be a GET argument in a form action, this does only ask for troubles.

    With friendly urls the action looks like this:
    <form method="post" name="loginfrm" action="/blog.html?query=blog.html">

    The ID is obviously gone but login is no longer possible because MODx does not know the ID and it seems to be necessary for the login process.

    One thing: we have the MODx/vBulletin integration installed, that allows logins in both areas. Could that be the cause for the login problem? If not, does nobody but us have problems with logins and friendly urls?

    Since we have the login only on one page, it could be hardcoded. I tried to add a hidden field with the ID in the weblogin chunk but it didn’t help. And I tried to include the ID into the alias name of this page. Didn’t work.


    Any solution or hint how I could fix this?

      • 20413
      • 2,877 Posts
      This is different from page to page. It’s referring to the form where you are...

      $tpl = str_replace("[+action+]",preserveUrl($modx->documentIdentifier,"",$ref),$tpl);

      http://svn.modxcms.com/svn/tattoo/tattoo/releases/1.0.3/assets/snippets/weblogin/weblogin.inc.php

      You can use [~[*id*]~] instead (in the form). But if your url-vars decide another template etc. action placeholder
      do a good job.
        @hawproductions | http://mrhaw.com/

        Infograph: MODX Advanced Install in 7 steps:
        http://forums.modx.com/thread/96954/infograph-modx-advanced-install-in-7-steps

        Recap: Portland, OR (PDX) MODX CMS Meetup, Oct 6, 2015. US Bancorp Tower
        http://mrhaw.com/modx_portland_oregon_pdx_modx_cms_meetup_oct_2015_us_bancorp_tower
        • 23085
        • 9 Posts
        Quote from: mrhaw at Apr 02, 2010, 09:22 PM

        You can use [~[*id*]~] instead (in the form). But if your url-vars decide another template etc. action placeholder do a good job.
        Thanks, I think the [~[*id*]~] will do it in our case.
        I’m coming closer.