posted January 07, 2003 05:11 PM           

Also...i notice the search results are sorted alphabetically....is there a way to make them show up chronologically?

posted January 07, 2003 06:04 PM            

I think that will only be possible if you can make a dynamic link too. The search works from between 2 dates, you would have to have those dates change in the link to keep the results up to date.

You could link directly to the ssi.html template as that is basically what it does (ie. show upcoming events).

Dan O.

posted January 08, 2003 03:32 AM           

and also for sorting chronologically...

posted January 08, 2003 03:27 PM            

Doesn't do much for upcoming events. I would think linking to the ssi.html template would be a better idea, you can modify its design to display any way you like. Plus the search results do not always show recurring events which the SSI template does.

** do you know what the url string format is? **

calendar.pl?view=Search&end_month=2&start_date=8&calendar=default&start_year=2003&start_month=1&end_date=8&template=default.html&command=search&end_year=2003&FIELD_descrip tion=Search_Term

It will vary depending on what field you are searching on though.

** and also for sorting chronologically... **

All search results I've seen are by date. Maybe the template I'm using has been modified but don't remember?

If you find the code in the default.html template file following:

<% IF SEARCH RESULTS EXIST %>

Add

<% @$SEARCH_RESULTS = sort {$a->{schedule}->{start} <=> $b->{schedule}->{start} } @$SEARCH_RESULTS; %>

right before:

<TABLE BORDER="1" CELLPADDING="1" CELLSPACING="0">

That might do it.

Dan O.

posted January 08, 2003 08:50 PM            

Glad to hear it.

Dan O.

posted January 14, 2003 04:03 PM            

You can find it and other plug-ins at the www.much2.com web site.

Dan O.

posted January 16, 2003 07:41 PM            

What do you want to know?

Dan O.

posted January 16, 2003 11:53 PM            

Or do i just use the URL string from the search page and add something to it? Im not sure how to interact with the plugin...

ryan

posted January 17, 2003 03:48 PM            

** Where do i find the URL i use **

From that file:

You can now link to the calendar's search results page using a link URL like the following:

calendar.pl?view=Search&command=search&FIELD_title=search+text&duration=14&calendar=default

** do i structure it myself and pass specfic variables to it? **

You can. From that file:

quote:

---

The calendar=default is optional and can point to the specific calendar to be searched.

duration=14 is optional but will set the duration in days from present for the calendar to display results from. If not supplied, a default of 7 days will be used.

You can search specific event fields using FIELD_title=search+text where "title" is the
event field to be searched and "search+text" is the text to be searched for.
NOTE: to separate multiple search terms use a "+" or "%20" (without the quotes) between the terms. Eg FIELD_title=search+text or FIELD_title=search%20text

Alternately, you can search all event fields using SEARCH_ALL=search+text

If no search term is supplied, all results that fall within the duration requested will be returned.

---

** Im not sure how to interact with the plugin... **

All you need to do (besides enabling the plug-in) is call the calendar using a URL with the wanted query string elements in it. All that has to be included is:
calendar.pl?view=Search&command=search

That will display all events from the current time forward 7 days.

Let me know if you have any other questions.

Dan O.

posted January 17, 2003 05:47 PM            

I just uploaded a fresh copy making sure the upload was in binary (just in case it wasn't the last time). Let me know if you are successful now.

Dan O.

posted January 17, 2003 06:32 PM            

but even with the info i have now, its not displaying anything, just a blank screen.
i am using:

calendar.pl?view=Search&command=search&calendar=default&duration=365&FIELD_description=beneath+the+ashes

and if i take of the search terms completely, the page comes up, ,but it says the Search query must not be blank!

does anything look wrong? it seems like its not running through your plugin...

posted January 17, 2003 07:52 PM            

If it says that, either the SearchLink plug-in is not activated in the administration section or you have another plug-in installed that is using the display_before_search script hook. In the latter case, you'll have to see if there's a conflict elsewhere.

Dan O.

posted January 18, 2003 12:41 AM            

I even moved the plugin to the very top og the list, and disabled all the other plugins, and i get the same thing.

Where would i look?

posted January 18, 2003 12:37 PM            

You could look in each of the directories that is off the plugins directory to see if any contain a file named "display_before_search.pl" but moving that plugin to the top should have over ruled others if present. So that may not be the cause.

It could possibly be that the file is corrupted and the script is not even attempting to execute its code at all. Maybe try downloading a fresh version, unzipping it locally then reuploading it making sure it is done in ascii mode.

Dan O.

posted January 18, 2003 02:40 PM            

That plug-in replaces the original search routine so all searches will (try to) use it if the plug-in is enabled.

I don't know what else to tell you, it works fine on my system and I can't see why it wouldn't on any other. Can you provide the URL to your calendar?

Also, maybe tw1000 will post if he was able to utilize the plug-in successfully or not?

Dan O.

posted January 18, 2003 06:55 PM            

BTW - the search field is messed up because of the wysiwyg editor. Also trying to get fixed...
------------------

the exact link i am using to search is: http://www.darkvisionsmedia.com/cgi-bin/calendar/calendar.pl?view=Search&command=search&calendar=default&duration=365&FIELD_description=beneath+the+ashes

Its a different outcome if you take off the field description var like:
http://www.darkvisionsmedia.com/cgi-bin/calendar/calendar.pl?view=Search&command=search&calendar=default&duration=365

Thanks much
ryan

posted January 18, 2003 08:29 PM            

Is it possible to work around the Meta/Search issue?

posted January 19, 2003 12:43 PM            

That may be the whole problem. If I get a chance in the next couple of days I'll see if I can find if anything in that hack could effect the Search Link plug-in.

Have you been able to get the wysiwyg editor to work at all?

Dan O.

posted January 19, 2003 12:57 PM            

Those plug-ins won't work together because they both use the same CalendarScript hook (display_before_search).

** Is it possible to work around the Meta/Search issue? **

It will require the two different display_before_search.pl files to be combined. I'll see if I can do that and make it available for download, it probably won't be until the middle of next week. I'll post a note here when it's ready.

BTW. How does the Meta Calendar mod work for you otherwise?

Dan O.

posted January 19, 2003 05:05 PM            

quote:

---

It will require the two different display_before_search.pl files to be combined. I'll see if I can do that and make it available for download.

---

tw1000, it didn't take as much time as I thought, just some copying and pasting. A replacement display_before_search.pl is now available for download from www.much2.com and is located with the original Meta Calendar's plug-in link.

Let me know how it works.

Dan O.

posted January 19, 2003 07:58 PM            

I haven't yet figured out what's going on on your calendar but in the mean time you can correct the "Invalid input type: 'wysiwyg'!" by doing the following.

Go to the modified DBFileUtil.inc used for the 'wysiwyg' display and change one line towards the end of it. In the sub GetSearchFieldInput find the line following
# Define input field based on type
which is:

if (($type =~ /^text(?!area)/) | | ($type =~ /^password/) | | ($type =~ /^textarea/)) {

and change it to:

if (($type =~ /^text(?!area)/) | | ($type =~ /^password/) | | ($type =~ /^textarea/) | | ($type =~ /^wysiwyg/)) {

See if that makes any difference. Be sure to make a backup of the original!

Dan O.

BTW. This forum inserts a space between each | | in the code above so those spaces will have to be removed before pasting the code into that file.

posted January 20, 2003 04:28 PM            

The link from List is:
calendar.pl?view=Search&calendar=default&style=List

The Link fron Grid is:

/calendar.pl?style=Grid&selected_datestring=20030120&calendar=default&view=Search&datestring=20030120&style=Grid

Is there a way to have the Grid view link take the user back to the default grid you or to the previous grid?

posted January 20, 2003 09:21 PM            

As there is only one view available for the search results, those links don't have much to do. It works the same on the demo calendar from te search view.

I have no idea why each of those links have different length URLs on your calendar. On my calendar they're both exactly the same except the &style=List or &style=Grid at the end.

Here are examples of mine after using a Search Link:

calendar.pl?calendar=move&view=Search&duration=14&style=Grid
calendar.pl?calendar=move&view=Search&duration=14&style=List

Here are examples after a regular search:

calendar.pl?duration=14&end_year=2003&start_date=20&fromTemplate=&start_month=1&end_date=22&calendar=move&view=Search&end_month=1&start_year=2003&style=Grid

calendar.pl?duration=14&end_year=2003&start_date=20&fromTemplate=&start_month=1&end_date=22&calendar=move&view=Search&end_month=1&start_year=2003&style=List

Are you sure you looked at them from the same screen and not one before a search and one after? Or more likely, one from before a search and one after moving to the search view page from viewing the Day view of 20030120?

** Is there a way to have the Grid view link take the user back to the default grid **

Sure if you want to code the page that way. But unless you use some if/else statements, it will work the same from all the calendar views.

** or to the previous grid? **

You mean the calendar view they were at before moving to the Search View in the first place? Doubtful, or at least I can't think of an easy way to accomplish it. It wouldn't be done through the plug-in.

Dan O.

posted January 21, 2003 01:23 PM            

You can remove those options altogether on the search view by editing the default.html template file and putting their code inside an if $view eq "search" (or "Search", I forget which) conditional.

Dan O.

posted January 21, 2003 07:03 PM            

I don't see anything in that hack that should effect the Search Link plug-in.
It looks like the script is not processing the Search Link's display_before_search.pl
file and I have no idea why that would be.

I have had that happen with other plug-in files but that was caused by an error in the
script (which could include it being uploaded incorrectly). It works on my system
so I'm fairly sure an error in the coding isn't causing it.

I don't know what else to suggest. Sorry.

What are you using to upload that plug-in's files? Maybe you could try uploading the zip
file in binary mode and unzipping it on the server?

Dan O.

posted January 28, 2003 01:30 PM            

What are you using to upload that plug-in's files? Maybe you could try uploading the zip file in binary mode and unzipping it on the server?

Dan O.

posted January 29, 2003 05:24 AM            

But here is the code for the Search View section in default.html...im not sure if this code matters at all, but i am pretty lost.

<textarea name="ta" cols="50" rows="25"><% } elsif ($VIEW eq "Search") { %><font size="1"> </font></font>
<FORM NAME="mainform" ACTION="<%= $CGI_URL %>" METHOD="POST">
<font size="1" face="Verdana">
<INPUT TYPE="hidden" NAME="QUERY_STRING" VALUE="<%=$QUERY_STRING%>">
<INPUT TYPE="hidden" NAME="fromTemplate" VALUE="<%=$thisTemplate%>">
<INPUT TYPE="hidden" NAME="command" VALUE="search">
<INPUT TYPE="hidden" NAME="view" VALUE="Search">
</font>
<TABLE BORDER="0">
<% if ($userMessage ne "") { %><font face="Verdana" size="1"> </font>
<TR>
<TD></TD>
<TD ALIGN="left" VALIGN="top">
<FONT COLOR="red">
<%= $userMessage %><font face="Verdana" size="1"> </font>
</FONT>
</TD>
</TR>
<% } %><font size="1">
<%
$fieldnames = &main: BGetSearchFields($db);
foreach $field (@$fieldnames) {
%> </font>
<TR>
<TD ALIGN="RIGHT"><SPAN CLASS="text"><B><%= $db->{'properties'}->{$field}->{'name'} | | $field %><font face="Verdana" size="1">
</font><font face="Verdana" size="1">: </font> </B></SPAN>
</TD>
<TD><%= &main::GetSearchFieldInput($db->{'properties'}->{$field},$field,$search_params) %></TD>
</TR>
<% } %><font size="1"> </font>
<TR>
<TD ALIGN="RIGHT"><font face="Verdana" size="2"><SPAN CLASS="text"><B>
Between:</B></SPAN></font><span class="text"><b><font face="Verdana" size="2"><br>
And:</font></b></span><font face="Verdana" size="2"><SPAN CLASS="text"><B> </B></SPAN>
</font></TD>
<TD>
<p align="left">
<font size="1" face="Verdana">
<SELECT NAME="start_month" style="font-family: Verdana; font-size: 10pt"><%= &HTML::monthNameOptions($in{start_month} | | $TODAY_MONTH) %></SELECT>
<SELECT NAME="start_date" style="font-family: Verdana; font-size: 10pt"><%= &HTML::dateOptions($in{start_date} | | $TODAY_DATE) %></SELECT>
<SELECT NAME="start_year" style="font-family: Verdana; font-size: 10pt"><%= &HTML::yearOptions($in{start_year} | | $TODAY_YEAR) %></SELECT><br>
<SELECT NAME="end_month" style="font-family: Verdana; font-size: 10pt"><%= &HTML::monthNameOptions($in{end_month} | | $TODAY_MONTH) %></SELECT>
<SELECT NAME="end_date" style="font-family: Verdana; font-size: 10pt"><%= &HTML::dateOptions($in{end_date} | | $TODAY_DATE) %></SELECT>
<SELECT NAME="end_year" style="font-family: Verdana; font-size: 10pt"><%= &HTML::yearOptions($in{end_year} | | ($TODAY_YEAR+1)) %></SELECT>
</font>
</TD>
</TR>
<TR>
<TD ALIGN="CENTER" COLSPAN="2">
<font face="Verdana">
<font size="1">
<INPUT CLASS="button" TYPE="submit" VALUE="Search"> </font>
</TD>
</TR>
<% IF SEARCH RESULT %><font size="1"> </font>
<TR>
<TD COLSPAN="2" ALIGN="center">
<SPAN CLASS="text">
<font face="Verdana" size="1">
<u><B>Search Results</B></u><BR>
<% IF SEARCH RESULTS EXIST %>
No Matches
<% ELSE %> </font>
<% @$SEARCH_RESULTS = sort {$a->{schedule}->{start} <=> $b->{schedule}->{start} } @$SEARCH_RESULTS; %>
<TABLE BORDER="1" CELLPADDING="5" CELLSPACING="0" width="100%" style="border-collapse: collapse">
<TR>
<TH><font face="Verdana" size="1"><SPAN CLASS="text">Date</SPAN></font></TH>
<TH><font face="Verdana" size="1"><SPAN CLASS="text">Title</SPAN></font></TH>
<TH><font face="Verdana" size="1"><SPAN CLASS="text">Description</SPAN></TH>
<TH><SPAN CLASS="text"><font face="Verdana" size="1">Location</font></TH>
<TH><SPAN CLASS="text"><font face="Verdana" size="1">Price</font></TH>
<TH><SPAN CLASS="text"><font face="Verdana" size="1">Time</font></TH>
</TR>
<% FOREACH SEARCH RESULT %><font size="1"> </font>
<TR>
<TD valign="top">
<SPAN CLASS="text">
<% IF NEXT OCCURRENCE EXISTS %><font face="Verdana" size="2">
<%=$MONTH_NAMES->[$EVENT->{schedule}->{nextoccurrence}->{month}-1]%>
</font> <%=$EVENT->{schedule}->{nextoccurrence}->{date}%><font face="Verdana" size="2">, <%=$EVENT->{schedule}->{nextoccurrence}->{year}%>
<% ELSE %>
None
<% /IF %> </font>
</SPAN>
</TD>
<TD valign="top"><font face="Verdana" size="1"><A HREF="<%=$CGI_URL_QUERYSTRING%>view=Event&event_id=<%= EVENT FIELD(id) %>&datestring=<%=$DAY->{datestring}%>" STYLE="text-decoration:underline;" CLASS="text"><%= EVENT FIELD(title) %></A></font></TD>
<TD valign="top"><font face="Verdana" size="1"><SPAN CLASS="text"><%= EVENT FIELD(description) %></SPAN></font></TD>
<TD valign="top"><font face="Verdana" size="1"><SPAN CLASS="text"><%= EVENT FIELD(location) %></SPAN></font></TD>
<TD valign="top"><font face="Verdana" size="1"><SPAN CLASS="text"><%= EVENT FIELD(price) %></SPAN></font></TD>
<TD valign="top"><font face="Verdana" size="1"><SPAN CLASS="text"><%= &Date::formatTime($EVENT->{schedule}->{start_time}, $Config->get("time_format")); %></SPAN></font></TD>
</TR>
<% /FOREACH %><font size="1"> </font>
</TABLE>
<% /IF %><font size="1"> </font>
</SPAN>
</TD>
</TR>
<% /IF %><font size="1"> </font>
</TABLE>
</FORM>

<% } %><font size="1"> </font></textarea>

posted January 29, 2003 09:07 PM            

You require shell access. If you don't have it you'd have to ask your host's support if they will do it for you.

** im not sure if this code matters at all **

No it doesn't. The code that would be important if it had an error or were corrupted would be the
display_before_search.pl from the plugin. And posting its code here would not likely help to determine if it
was corrupted or not.

Dan O.

------------------