We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 40088
    • 708 Posts
    Oops.

                            <form action="[[~[[+landing]]]]" method="[[+method]]">
                                <fieldset>
                                    <input type="text" name="[[+searchIndex]]" id="[[+searchIndex]]" value="[[+searchValue]]" />
                                    <input type="hidden" name="id" value="[[+landing]]" /> 
                                    <input type="submit" value="[[%sisea.search? &namespace=`sisea` &topic=`default`]]" id="searchButton" class="bttn" />
                                </fieldset>
                            </form>
      Todd
    • Ok, what happens if you use

      <form action="[[~50]]" method="[[+method]]">


      Just to see if it's something wrong in SimpleSearch itself, or if it's something wrong in your site's handling of the URL creation.

      Since you mentioned something about similar problems with Wayfinder, it's most likely something wrong with MODx URL processing.
        Studying MODX in the desert - http://sottwell.com
        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
        Join the Slack Community - http://modx.org
        • 40088
        • 708 Posts
        Quote from: sottwell at Sep 28, 2012, 05:44 AM
        Ok, what happens if you use

        <form action="[[~50]]" method="[[+method]]">

        Unfortunately no difference.
          Todd
        • Try making the action attribute be the actual URL to the landing page.

          action="http : //mysite.com/search-results.html"


          It's beginning to look like you have bigger issues than just SimpleSearch.
            Studying MODX in the desert - http://sottwell.com
            Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
            Join the Slack Community - http://modx.org
            • 40088
            • 708 Posts
            Quote from: sottwell at Sep 28, 2012, 08:20 AM
            Try making the action attribute be the actual URL to the landing page.

            action="http : //mysite.com/search-results.html"

            Oddly, that doesn't work either. Although the correct url is displayed the homepage is what shows, not the results page.


              Todd
            • That means the URL to your search-result page wasn't correct, you're getting the default "not found" page (your home page, resource #1).
                Studying MODX in the desert - http://sottwell.com
                Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                Join the Slack Community - http://modx.org
                • 40088
                • 708 Posts
                Quote from: sottwell at Sep 28, 2012, 04:42 PM
                That means the URL to your search-result page wasn't correct, you're getting the default "not found" page (your home page, resource #1).

                I left off the .html file extension and now it works. I am curious as to what the bigger problem is though because in addition to SS it's causing major issues when using Wayfinder in sub-directories.
                [ed. note: todd.b last edited this post 11 years, 7 months ago.]
                  Todd
                • It may have something to do with your "container_suffix" setting. If a resource is a container, it's given a different suffix (by default / rather than .html).
                    Studying MODX in the desert - http://sottwell.com
                    Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                    Join the Slack Community - http://modx.org
                    • 40088
                    • 708 Posts
                    Quote from: sottwell at Sep 28, 2012, 05:28 PM
                    It may have something to do with your "container_suffix" setting. If a resource is a container, it's given a different suffix (by default / rather than .html).

                    I'm guessing it's due to this:

                    Under System > Content Types I had removed .html under 'File Extension' because I didn't want my urls to have .html tacked on. I suppose if I enabled that again your example would have worked straight-away.

                    It seems that until I can suss out the real problem I'll have to use the hard-coded solution you offered. I'm more concerned about how this issue affects Wayfinder usage.

                    Thank you, Susan.
                      Todd