› ›
CRITICAL SECURITY VERSION UPDATE:
https://github.com/daylightstudio/FUEL-CMS/releases/tag/1.4.13

toggle toolbar not working

EcotypeSEcotypeS
edited July 2015 in Installation
It does not toggle -- any ideas? The javascript all seems to be present and the generated code looks reasonable. I know that other javascript is working both in the application and in the dashboard. I have $config['admin_enabled'] = TRUE;

The developer console is not showing any errors.

Here is what it generated. Ideas?
<script src="/fuel/modules/fuel/assets/js/fuel/fuel_inline.min.js?c=" type="text/javascript" charset="utf-8"></script> <div class="__fuel__" id="__fuel_edit_bar__"> <form action="http://localhost/fuel/pages/ajax_page_edit" method="post" id="__fuel_edit_bar_form__"> <div class="buttonbar buttonbar_notop"> <ul> <li class="start round exposed"><a href="#" id="__fuel_page_toolbar_toggle__" class="ico ico_fuel" title="Toggle toolbar display"></a></li> <li class=""><a href="#" id="__fuel_page_edit_toggle__" class="ico ico_edit" title="Toggle editable areas"></a></li> <li class="txt"><a href="http://localhost/fuel/recent">Back to Admin</a></li> <li class="txt"><a href="http://localhost/fuel/logout/6347466e5a563979623356305a58493d" class="" title="Logout of FUEL admin">Logout</a></li> </ul> <div class="clear"></div> </div> </form> </div>

Comments

  • adminadmin
    edited 12:46PM
    Is the page you are on editable in the CMS? Also, have you tried logging back out then back in?
  • EcotypeSEcotypeS
    edited July 2015
    I've boiled it down to being a javascript problem. And for the moment, I've solved it by cutting out the offending javascript (which then causes my menu to fail).

    I load jquery 1.8.3, fuel is loading 1.7.1, is there any possibility that this is causing a conflict? I have an application in one page that requires 1.8.3 or higher. (I had no problem 0.93)
  • adminadmin
    edited 12:46PM
    It's possible. fuel/modules/fuel/views/_blocks/inline_edit_bar.php on lines 10-22 it does some checking for existing jquery and then determines if it needs to use the migrate plugin or not. I'd perhaps try commenting that out to see if it fixes your issue to help isolate the problem.
Sign In or Register to comment.