Author Topic: Possible Conflict with VirtueMart Extended Search Plugin  (Read 17163 times)

dirtymonkey

  • Beginner
  • *
  • Posts: 14
  • Can you get square eyes?
    • Rocket IT Support
Possible Conflict with VirtueMart Extended Search Plugin
« on: June 16, 2008, 16:18:33 pm »
I think I've found a conflict between Joomla Search Plugins.

With both plugins enabled the returned search results page is blank. The Search Administration page in Joomla is also blank.

J! v1.5.3
VM v1.1.0
PHP: 5.2.3

VirtueMart Extended Search Plugin - vmxsearch.plugin_1.1.0.j15.zip
Keyword Density Content Search - KD_Content_Search_J1-5RC3_v1-1.zip
http://joomla.pietrogallo.it/index.php?option=com_content&task=view&id=23&Itemid=3

Unfortunately no debug info is given so I don't know which one's at fault.

DM.
Rocket IT Support - RocketITSupport.com | Custom Joomla Design/Development/Content Management/Marketing and SEO | Speshitpilling in Quality Joomla Solutions, Remote Webmaster Services, Support and Consultancy.

federiki

  • Beginner
  • *
  • Posts: 1
Re: Possible Conflict with VirtueMart Extended Search Plugin
« Reply #1 on: June 17, 2008, 14:33:13 pm »
I think I've found a conflict between Joomla Search Plugins.
With both plugins enabled the returned search results page is blank. The Search Administration page in Joomla is also blank.
J! v1.5.3
VM v1.1.0
PHP: 5.2.3
VirtueMart Extended Search Plugin - vmxsearch.plugin_1.1.0.j15.zip
Keyword Density Content Search - KD_Content_Search_J1-5RC3_v1-1.zip
http://joomla.pietrogallo.it/index.php?option=com_content&task=view&id=23&Itemid=3
Unfortunately no debug info is given so I don't know which one's at fault.
DM.

I have a problem too:
When the plugin ist activated, the search component does not work any more...
clicking search in the backend the page shows this:
....\components\com_virtuemart\virtuemart_parser.php on line 80

jaychou

  • Beginner
  • *
  • Posts: 1
Re: Possible Conflict with VirtueMart Extended Search Plugin
« Reply #2 on: June 20, 2008, 06:56:55 am »
I think I've found a conflict between Joomla Search Plugins.
With both plugins enabled the returned search results page is blank. The Search Administration page in Joomla is also blank.
J! v1.5.3
VM v1.1.0
PHP: 5.2.3
VirtueMart Extended Search Plugin - vmxsearch.plugin_1.1.0.j15.zip
Keyword Density Content Search - KD_Content_Search_J1-5RC3_v1-1.zip
http://joomla.pietrogallo.it/index.php?option=com_content&task=view&id=23&Itemid=3
Unfortunately no debug info is given so I don't know which one's at fault.
DM.
I have a problem too:
When the plugin ist activated, the search component does not work any more...
clicking search in the backend the page shows this:
....\components\com_virtuemart\virtuemart_parser.php on line 80

I fix this with this
"
      if( vmIsJoomla( '1.5' ) ) {
          $menu = & JMenu::getInstance('site');
          $menuparams = & $menu->getParams( $Itemid );
         //$menuparams = $mainframe->getParams();
      } else {
"
works fine

korvax

  • Beginner
  • *
  • Posts: 1
Re: Possible Conflict with VirtueMart Extended Search Plugin
« Reply #3 on: June 20, 2009, 17:29:31 pm »
Got the same problem and fixed it.
This problem occurs because the virtuemart search plugin and the keyword density plugin use a function with the same name.

To fix this change the function name in the keyword density plugin
pg_keydenseSort to pg_keydenseSort2

/plugins/search/keydensity_content.php at line 272 to 276

Code: [Select]
pg_keydenseSort2($results,'count','DESC');
return $results;
}

function pg_keydenseSort2(&$data, $key, $order)


schijfenmuis

  • Beginner
  • *
  • Posts: 1
Re: Possible Conflict with VirtueMart Extended Search Plugin
« Reply #4 on: July 22, 2009, 03:28:20 am »
I had the same problem in mambo 4.6.3 with VirtMart 1.1.3.
I just unpublished de vmxsearch.searchbot and every other searchmodules seems to function perfect.
I tried it with:  if( vmIsJoomla( '1.5' ) ) {
          $menu = & JMenu::getInstance('site');
          $menuparams = & $menu->getParams( $Itemid );
         //$menuparams = $mainframe->getParams();
      } else {

But no change at all.