Welcome, Guest. Please login or register.
Did you miss your activation email?


Login with username, password and session length

Search

 
Advanced search

8043 Posts in 1856 Topics- by 2099 Members - Latest Member: roi
Calendar Script CommunityCustomizationHacks and Mods (Moderators: scott, DanO, Marty)advanced searching capability
Pages: 1 [2] 3 4   Go Down
Print
Author Topic: advanced searching capability  (Read 2694 times)
0 Members and 1 Guest are viewing this topic.
DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #15 on: January 17, 2003, 07:52:00 PM »

** it says the Search query must not be blank! **

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.

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

Logged
tw1000
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« Reply #16 on: January 17, 2003, 10:05:00 PM »

Thanks Dan! The file unzipped OK

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

Logged
beneath_the_ashes
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« Reply #17 on: January 18, 2003, 12:41:00 AM »

well the plugin definetely shows that it is enabled, but i wouldnt know where to start looking for something else using that same hook, but i would just assume the chances of it are low.

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?

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

Logged
DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #18 on: January 18, 2003, 12:37:00 PM »

** Where would i look? **

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.

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

Logged
beneath_the_ashes
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« Reply #19 on: January 18, 2003, 01:19:00 PM »

i searched the entire plugins directory, and SearchLink is the only one with that hook...also i re-uploaded a fresh download in ascii mode, and the same thing.  I thought it might have been the wysiwyg editor, but even when i search on feilds that done use it, it does the same thing...

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

Logged
DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #20 on: January 18, 2003, 02:40:00 PM »

** even when i search on feilds that done use it, it does the same thing **

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.

[This message has been edited by DanO (edited January 18, 2003).]

Logged
beneath_the_ashes
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« Reply #21 on: January 18, 2003, 06:55:00 PM »

sure...my calendar is @
http://www.darkvisionsmedia.com/cgi-bin/calendar/calendar.pl

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

[This message has been edited by beneath_the_ashes (edited January 18, 2003).]

Logged
tw1000
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« Reply #22 on: January 18, 2003, 08:29:00 PM »

I have installed the plug in and it works OK on an individual calendar.
Several issues have arisen, however, with several calendars created.
1. I have meta calendars installed, and if Meta is instlled above Search, then only a white screen apears when search is called.
2. If Search is above Meta then Meta and search appear to work with a few exceptions.
 a. Search works on only one calendar at a time.
 b.Search will not work on the calendar designated Meta( a search screen loads that reports no matches)
  c. if no calendar is specified, a search screen loads that reports no matches

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

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

Logged
DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #23 on: January 19, 2003, 12:43:00 PM »

** BTW - the search field is messed up because of the wysiwyg editor. **

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.

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

Logged
DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #24 on: January 19, 2003, 12:57:00 PM »

** I have meta calendars installed, and if Meta is installed above Search, then only a white screen apears when search is called. **

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.

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

Logged
DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #25 on: January 19, 2003, 05:05:00 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.

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

Logged
tw1000
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« Reply #26 on: January 19, 2003, 05:09:00 PM »

Thanks Dan, the Meta plugin works perfectly so far. I will try the new file later tonight. Thanks again for all the help!

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

Logged
tw1000
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« Reply #27 on: January 19, 2003, 07:13:00 PM »

Dan , you are amazing! Everything appears to be working OK, both meta and search are functioning. I have not thoroughly tested but so far so good!

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

Logged
DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #28 on: January 19, 2003, 07:58:00 PM »

ryan,

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.

[This message has been edited by DanO (edited January 19, 2003).]

Logged
beneath_the_ashes
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« Reply #29 on: January 20, 2003, 12:33:00 AM »

yes, the wysiwyg editor works fine...and that fix worked fine as well for the search page, but the searchlink path still doesnt work.

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

Logged
Pages: 1 [2] 3 4   Go Up
Print
Jump to: