When I am on the translation page and click the 'Customize table' button, I get only a page of JSON data at /admin/settings/lingotek/manage/customize/config.

eg [{"command":"settings","settings":{"basePath":"\/","pathPrefix":"","ajaxPageState":{"theme"...

This feature has worked in the past and has allowed me to customize the display of the page.

Comments

robertdbailey’s picture

robertdbailey commented

Hi @calebtr, I have not been able to duplicate this issue. I've tested using both 7.x-6.02 and 7.x-7.x, and I've tested using the nodes tab, comments tab, and config tabs. Do you know when it stopped working?

calebtr’s picture

calebtr commented

Drat, I'll try to find the conflict.

calebtr’s picture

calebtr commented
Status: Active » Closed (cannot reproduce)

I'm not able to immediately find the conflict or resolve the issue. I'll update this issue if it is repeatable and re-open the issue if the conflict is with the lingotek module.

krlucas’s picture

krlucas commented
Version: 7.x-6.02 » 7.x-7.21
Status: Closed (cannot reproduce) » Active

I'm currently having this issue with the "Customize Table" button consistently with 7.x-7.21 on the following pages:
admin/settings/lingotek/manage/node
admin/settings/lingotek/manage/beans
admin/settings/lingotek/manage/config

The javascript console reports the following error when clicking the button:

Uncaught Error: Syntax error, unrecognized expression: <div id="ctools-modal"> <div class="ctools-modal-content"> <div class="modal-header"> <a class="close" href="#"><img src="https://XXXXXXX/sites/all/modules/contrib/lingotek/images/close.png" alt="Close window" title="Close window" /> </a> <span id="modal-title" class="modal-title"> </span> </div> <div id="modal-content" class="modal-content"> </div> </div> </div>
at Function.st.error (js_dbOM3t-2AldEgvm-dU4w8GGNUD61tjAVwnLcx860ueYsQ3_j8YpHr2_9JmPIpOUuAGwHzOTwQY3HNirUIDWdC0_syh9d…:4)
at ft (js_dbOM3t-2AldEgvm-dU4w8GGNUD61tjAVwnLcx860ueYsQ3_j8YpHr2_9JmPIpOUuAGwHzOTwQY3HNirUIDWdC0_syh9d…:4)
at wt (js_dbOM3t-2AldEgvm-dU4w8GGNUD61tjAVwnLcx860ueYsQ3_j8YpHr2_9JmPIpOUuAGwHzOTwQY3HNirUIDWdC0_syh9d…:4)
at Function.st [as find] (js_dbOM3t-2AldEgvm-dU4w8GGNUD61tjAVwnLcx860ueYsQ3_j8YpHr2_9JmPIpOUuAGwHzOTwQY3HNirUIDWdC0_syh9d…:4)
at init.find (js_dbOM3t-2AldEgvm-dU4w8GGNUD61tjAVwnLcx860ueYsQ3_j8YpHr2_9JmPIpOUuAGwHzOTwQY3HNirUIDWdC0_syh9d…:4)
at $.fn.init.init (js_dbOM3t-2AldEgvm-dU4w8GGNUD61tjAVwnLcx860ueYsQ3_j8YpHr2_9JmPIpOUuAGwHzOTwQY3HNirUIDWdC0_syh9d…:3)
at $.fn.init (js_dbOM3t-2AldEgvm-dU4w8GGNUD61tjAVwnLcx860ueYsQ3_j8YpHr2_9JmPIpOUuAGwHzOTwQY3HNirUIDWdC0_syh9d…:111)
at b (js_dbOM3t-2AldEgvm-dU4w8GGNUD61tjAVwnLcx860ueYsQ3_j8YpHr2_9JmPIpOUuAGwHzOTwQY3HNirUIDWdC0_syh9d…:3)
at Object.Drupal.CTools.Modal.show (js_O4FcDYLpXlUrWikBfaQ61OMxm_aRS2hUy3bKg4YxAukgfKCA1pxcRpSMCRsdBnaLwdVfuKQi35EvW5vQGifzQY_syh9d…:237)
at HTMLAnchorElement.Drupal.CTools.Modal.clickAjaxLink (js_O4FcDYLpXlUrWikBfaQ61OMxm_aRS2hUy3bKg4YxAukgfKCA1pxcRpSMCRsdBnaLwdVfuKQi35EvW5vQGifzQY_syh9d…:321)
krlucas’s picture

krlucas commented
Status: Active » Closed (works as designed)

I discovered the issue.

We had updated jQuery (using the jQuery update module) to 1.9. This breaks the cTools modal. Setting admin pages to use a different version fixed the issue.