[Date Prev][Date Next][Thread Prev][Thread Next][Minivend by date
][Minivend by thread
]
Re: [mv] Search Results Problem
****** message to minivend-users from Ramsey French <rammjet@mindspring.com> ******
Betty,
Thanks for the suggestion. For testing purposes, I was using the existing
products.asc from the simple catalog.
Ramsey
On 1/11/00 12:33 PM, betty c at bc90007@yahoo.com wrote:
> ****** message to minivend-users from betty c <bc90007@yahoo.com>
> ******
>
> how are you entering your data?
> if thru minimate, the products.asc is not refresh -
> to force a refresh [tag export products]
>
> --- Ramsey French <rammjet@mindspring.com> wrote:
>> ****** message to minivend-users from Ramsey French
>> <rammjet@mindspring.com> ******
>>
>> OK. Now I am officially confused. Can someone please help me understand
>> why this doesn't work?
>>
>> In an attempt to get around my nested frames problem, I decided to try an
>> in-page search without frames for now. I lifted this example straight out
>> of minivend.html, put it in a page called x8.html and called it through my
>> mvend. This was my response (similar to my problems with frames):
>>
>> Sorry, no matches for .
>>
>>
>> This is the code in x8.html:
>>
>> <HEAD>
>> <TITLE>[L]Search Results[/L]</TITLE>
>> </HEAD>
>> <BODY MV="body 1">
>>
>> [search-region se=Americana
>> sf=category
>> sp=x8 <=== tried with and without this
>> ml=2
>> ]
>> [more-list][more][/more-list]
>> [search-list]
>> <A MV="page [item-code]" HREF="flypage.html">
>> [item-field title]<A>, by [item-field artist]
>> [/search-list]
>> [no-match]
>> Sorry, no matches for [value mv_searchspec].
>> [/no-match]
>> [/search-region]
>>
>> <!-- current page: @@MV_PAGE@@ -->
>> </body> </html>
>>
>> I appreciate all assistance.
>>
>> Ramsey French
>>
>>
>> On 1/10/00 9:34 PM, Ramsey French at rammjet@mindspring.com wrote:
>>>
>>> On 1/10/00 7:56 PM, Ryan Hertz at rhertz@gyb.baits.com wrote:
>>>
>>>>
>>>> Uh, perhaps the value is sent to the wrong frame.
>>>
>>> Thanks, but I have tested mv_search_match_count in the target frame and it
>>> prints the correct number and it prints it in the correct frame. But for
>>> some reason, it skips straight to the [no-match] section.
>>>
>>> I am running some test cases to see if I can get any more insight. But the
>>> docs say that [no-match] will be achieved if there are no matches, or other
>>> errors. I think I have the matches, so I am interested in what errors can
>>> cause it to skip to [no-match].
-
To unsubscribe from the list, DO NOT REPLY to this message. Instead, send
email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
Archive of past messages: http://www.minivend.com/minivend/minivend-list
