We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 25663 MODX Staff
    • 12,272 Posts
    Actually, it makes sense to comment that one out because a TV formatter will never be present without at least one of the other items. We’ll need to let someone who knows definitively though make the final call.
      Ryan Thrash, MODX Co-Founder
      Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
      • 22303 MODX Staff
      • 10,725 Posts
      Actually, that last instance for TVs is the only one that would affect the front-end of the web site. And it may be required in order for a TV with a widget which depends on resources in the MEDIA_PATH folder to render in the front-end; I’m just not sure what those dependencies are off hand. It may affect QuickEdit as well, but Adam could tell us better...
        • 32241
        • 1,495 Posts
        The last call will be made from Adam then wink
          Wendy Novianto
          [font=Verdana]PT DJAMOER Technology Media
          [font=Verdana]Xituz Media
          • 1764
          • 680 Posts
          I’m pretty sure it’s not being used by QE for anything and a quick grep confirmed that.

          The only places it seems to be really used is in /manager/media/scripts/modx.js to include /manager/scripts/bin/webelm.js which seems to be Raymonds baby. So I’d say, ask Raymond grin

          I’m not even sure what webelm is for honestly. It appears to be a sort of a javascript toolkit.
            • 15914
            • 145 Posts
            I hope I haven’t picked at a thread which just unravels everything else. undecided
              Kunal Kapoor
              Technical Director
              Limesharp Internet Limited - Effective, Functional, Standards Compliant

              IRC Nick: KingKoopa
              Skype ID: KingKoopa16
              • 1764
              • 680 Posts
              If your are using the weblogin snippet you may have noticed that it doesn’t give any errors when you login with the wrong username or password (or any other errors like blocked accounts). There is a very simple fix for this.

              Edit /assets/snippets/weblogin/weblogin.inc.php.
              Find the line with the code below (it should be line 91)
              $output = ob_get_contents();

              and change it to
              $output .= ob_get_contents();


              This will prevent the error output from being overwritten and should give you a javascript alert with the appropriate error.
                • 25663 MODX Staff
                • 12,272 Posts
                One more for webuser logins. When using the password resetter (forget your password? link), it will in fact update the password, but not unblock a user if they’ve goofed more than the allowed number of times. The fix committe for 0.9.2 is as follows. In assets/snippets/weblogin/weblogin.processor.inc.php, change:

                			// activate new password
                			$newpwd = md5($newpwd);
                			$sql="UPDATE $dbase.".$table_prefix."web_users 
                				  SET password = '".$newpwd."', cachepwd='' 
                				  WHERE id=".$row['id'];
                			$ds = $modx->dbQuery($sql);
                
                			// invoke OnWebChangePassword event
                			if(!$ds) 
                				$modx->invokeEvent("OnWebChangePassword",
                								array(
                									"userid"		=> $id,
                									"username"		=> $username,
                									"userpassword"	=> $newpwd
                								));
                			
                			if(!$ds) $output = webLoginAlert("Error while activating password.");


                To:
                			// activate new password
                			$newpwd = md5($newpwd);
                			$sql="UPDATE $dbase.".$table_prefix."web_users 
                				  SET password = '".$newpwd."', cachepwd='' 
                				  WHERE id=".$row['id'];
                			$ds = $modx->dbQuery($sql);
                
                			// unblock user
                			$sql="UPDATE $dbase.".$table_prefix."web_user_attributes 
                				  SET blockeduntil = '0' 
                				  WHERE internalKey=".$row['id'];
                			$ds2 = $modx->dbQuery($sql);
                
                			// invoke OnWebChangePassword event
                			if(!$ds || !$ds2) 
                				$modx->invokeEvent("OnWebChangePassword",
                								array(
                									"userid"		=> $id,
                									"username"		=> $username,
                									"userpassword"	=> $newpwd
                								));
                			
                			if(!$ds || !$ds2) $output = webLoginAlert("Error while activating password.");
                  Ryan Thrash, MODX Co-Founder
                  Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                  • 15914
                  • 145 Posts
                  I’d just thought I’d throw this post in for WebSignup (so it can generate random password upon registration so people can verify their web user’s email addresses.)

                  http://modxcms.com/forums/index.php/topic,3050.0.html
                    Kunal Kapoor
                    Technical Director
                    Limesharp Internet Limited - Effective, Functional, Standards Compliant

                    IRC Nick: KingKoopa
                    Skype ID: KingKoopa16
                    • 27855
                    • 21 Posts
                    Hello,

                    I was looking for a solution to a problem I’m having and it looks like someone else had the exact same problem (quoted below). It says "solved" but I haven’t been able to find a solution. Does anyone know how this problem was fixed?

                    I updated from 0.9.0 to 0.9.1 and after updating my links are messed up:

                    If I click on a link from "Home" I’m okay. But once I click on another link that is "deeper" my links in the menu change.

                    For example, what used to be http://languagelearner.com/eslarticles.htm now changes to http://languagelearner.com/eslarticles/eslarticles.htm .

                    If I type in the URLs by hand, there’s no problem...the documents are still there. It’s just that the menu links have changed and added the additional folder instead of base index.

                    I’m using a chunk that someone set up for me so that the menu items show up on the left-hand side

                    <div class="sidenav">[[DropMenu? &menuName=`LeftColNav` &removeNewLines=`true` &startDoc=`0` &levelLimit=`2` &hereClass=`activeLink` ?startDoc=1 &topnavClass=`sidenav`]]</div>


                    and then a snippet that goes with it.

                    <ul class="sidenav">
                    
                    <li><a href="#">Link here</a></li>
                    <li><a href="#">Another link</a></li>
                    <li><a href="#">A third link</a></li>
                    </ul>


                    Any help would be appreciated.

                    Sincerely,

                    Sam




                    Quote from: banzai at Dec 25, 2005, 08:28 AM

                    Using friendly URL with alias path, links in Drop menu and Newslisting seems relative:

                    example:

                    1) from document www.root.com/news/article.html - home page link in DropMenu points to www.root.com/news/index.html (instead www.root.com/index.html)

                    2) from document www.root.com/news/article.html - DropMenu link to document in other folder, points to www.root.com/news/otherforlder/document.html (instead www.root.com/otherforlder/document.html)

                    sorry for my bad english sad
                      • 22303 MODX Staff
                      • 10,725 Posts
                      Hello snowflip, it looks like you are using the friendly alias paths option, and in 0.9.1 we removed a forced fix for this from the core, making it necessary for you to add this to your templates if you structured your site in such a way as to require absolute links to get back to the root of the site. Try adding the following to the top of your HEAD element in your template( s ) and see if that solves the problem:

                      <base href="[(site_url)]" />


                      Let me know if that doesn’t help.