Javascript error: Uncaught TypeError: Object #<Object> has no method 'datepicker'

+++ b/better_exposed_filters.jsundefined
@@ -83,7 +83,8 @@
+      if (Drupal.settings.better_exposed_filters.bef_datepicker && ¶

trailing whitespace!

It looks that tests are broken. We have no JS testing for now anyway

+++ b/better_exposed_filters.jsundefined
@@ -83,7 +83,8 @@
+        typeof Drupal.settings.better_exposed_filters.bef_dateformat !== 'undefined') {
         // Note: JavaScript does not treat "" as null

makes sense because this settings variable could be undefined

#6 works, thank you.

@maximpodorov we have 3 reviews and no JS testing, so back to rtbc

Indeed the patch works for me too

I can confirm that the patch in #6 applies and works fine!

Commited.

Thanks!

Currently, BEF won't show datepickers. Additional patch is needed.

One more check is needed. Please apply this patch and the patch from #1961486: Latest dev release + slider breaks views UI javascript since incorrect JavaScript breaks many things, including Rules UI.

@mikeker
Please apply this simple fix.

The underlying problem was that the BEF settings being set in the plugin had gotten out of sync with what was expected in BEF's JS code. An adapted version of your patch was committed along with a major revamping of the automated tests for this project.

Have to reopen the issue as it still persists in 7.x-3.0-beta4+6-dev. Same JS error is thrown when you use a BEF enabled view.

Very annoying side effect: a single view with BEF enabled makes VBO actions in Rules unusable as it breaks Rules' UI. Had to disable BEF because of that.

I am also having a datepicker issue. I am currently on 7.x-3.0-beta4 and cannot use my view with Ajax enabled otherwise I get the following error.

Uncaught TypeError: Cannot read property 'dateformat' of undefined.

Even though I am not using Dates at all.

I have this issue as well:
Uncaught TypeError: Cannot read property 'dateformat' of undefined.

I don't have anything that requires a date picker in my view...

Same error here. Strange to notice I couldn't go to the BEF settings in my views page display (although it worked on the master display) so it wasn't possible to re-save these settings.
Workaround for me was reverting to beta3. No problems then.

This patch adds datepicker library existence check.

Aplying the patch cleared up the error message about 'datepicker'.
Also it seems sensible to have this check in place anyway.

However, I get another error after applying the patch ( ' Uncaught TypeError: Cannot read property 'length' of undefined' ) I hoped this would be easily fixed by disabling 'jQuery update' module, and then the BEF settings worked as expected. Unfortunately this wasn't the case.

thanks for a valiant effort @maximpodorov !

Where do you get ' Uncaught TypeError: Cannot read property 'length' of undefined' error?

I've updated this patch to also fix the jQuery 'Uncaught TypeError: Cannot read property 'length' of undefined' error. Now AJAX stuff inside views should work properly

Patch from #27 @legittalon works for me (with beta 4). No more errors.
Updating status.

Why do you mix slider and datepicker? There is another issue related to slider: #1961486: Latest dev release + slider breaks views UI javascript.

Sorry bout the mix up @maximpodorov I just know the patch provided in #27 solved my problems (or at least seems to).

I tried the patch in #27 with no luck. I am having a similar problem when I try to load View Bulk Operations into Rules, when I go to create an Action Set, and click Add Action and choose the "Load a list of entity..." (either one of the 2 that show) the "please wait" toggle starts spinning then nothing happens.

Looking at the console log I see this:

Uncaught TypeError: Cannot read property 'dateformat' of undefined
Source is from VM788 line 198 typeof Drupal.settings.better_exposed_filters.datepicker_options.dateformat !== 'undefined') {

I tried updating BEF to latests dev branch, applied the patch in #27, but that didn't work.

Here is a simple workaround that can bring your filters back: just use the 7.x-3.0-beta3 version of better_exposed_filters.js. As a temporary hack, add it to template.php in your theme with hook_js_alter :

/**
 * Implements hook_js_alter().
 */
function YOUR_THEME_NAME_js_alter(&$javascript) {
  $bef_js_path = drupal_get_path('module', 'better_exposed_filters') . '/better_exposed_filters.js';
  if (isset($javascript[$bef_js_path])) {
    $javascript[$bef_js_path]['data'] = drupal_get_path('theme', 'YOUR_THEME_NAME') . '/js/better_exposed_filters.js';
  }
}

Hey Alex,

Thanks for your reply. I did was you said and swapped out the js file with the newest 7.3 beta, (and cleared caches), and I am still getting a spinning wheel that just stops and nothing happens. Console still says the dateformat is undefined.

UPDATE: Hold on, I just checked the Sources log, and it's still loading the modules JS instead of the one in my theme.

Hey Alex,

For the heck of it, to not waste time looking at why my version of the JS didn't load, I replaced the code in the current JS file with the new one and tried that. Still no change, same dateformat error. Am I missing a step? I am still using the latest Dev branch for the core module files. It's still having trouble with the following undefined:

// Check for and initialize datepickers
      if (Drupal.settings.better_exposed_filters.datepicker &&
        // This setting is undefined when "bef_datepicker" setting is array of
        // false values and as a result "ui.datepicker" library does not get
        // included.
        typeof Drupal.settings.better_exposed_filters.datepicker_options.dateformat !== 'undefined') {
        // Note: JavaScript does not treat "" as null
        if (Drupal.settings.better_exposed_filters.datepicker_options.dateformat) {
          $('.bef-datepicker').datepicker({
            dateFormat: Drupal.settings.better_exposed_filters.datepicker_options.dateformat
          });
        }

Fixed the usage of Drupal.settings.better_exposed_filters.

#36 works as expected.
thanks

#36 works on dev version for me too.
Thanks.

Thanks, everyone, for your patience on this issue.

The fix in #36 has been committed.