|
|
|
|
Tags: search function, raw HTML, MooTools, JavaScript, white screen |
The SOBI2 extended search function uses the MooTools framework. Sometimes, if the template also includes its own MooTools script and it is not the same version of the script as SOBI2 includes, it can cause conflicts and the search function stops working properly.
Note: Before you perform the following steps please ensure that the problem is really a conflict with another MooTools script. It is also possible that the in SOBI2 included mootools.js script conflicts with another script than the mootools script. Known problems are conflicts with moo.fx, prototype, etc. For this case we integrated in SOBI2 the possibility to switch off the inclusion of mootools.js. If you do that, you have to be sure that the script is already included in the template and, what is very important, that the script has to be included before the head output of components.
This means, if you have this code in your template file: <head> <?php if ( $my->id ) { initEditor(); } mosShowHead(); ...... // here can be some other code ?> <script type="text/javascript" src="<?php echo $mosConfig_live_site;?>/templates/<?php echo $mainframe->getTemplate(); ?>/js/mootools.js"></script> ..... it should look like that: <head> <script type="text/javascript" src="<?php echo $mosConfig_live_site;?>/templates/<?php echo $mainframe->getTemplate(); ?>/js/mootools.js"></script> <?php if ( $my->id ) { initEditor(); } mosShowHead(); ...... // here can be some other code ..... Note: The name of the mootools script file can be also similar. E.g. RocketTheme names this file something like mootools-release-X.YY.js If you switch the "use_own_mootools" key to "0" it is very important that the mootools framework is included before the components header output. |
Date added: 26.2.2008 |
|
| Hits: 1091 |
| Powered by Sigsiu.NET | ![]() |