Drupal users who recently upgraded from 6.x.2.10 to 6.x.2.16 noticed that the Views which were using Exposed filters stopped working correctly. The reason for the error was that the Exposed Filter was optional in 6.x.2.10 but not in 6.x.2.16. The "Optional" checkbox no longer existed in the new version. If you are encountering a similar situation in your Drupal site then read on to find the fix.
A few Drupal users happened to chance on this eror "Notice: Undefined property: stdClass::$taxonomy in eval() (line 3 of C:\xampp\htdocs\cxcplus2\sites\all\modules\views\plugins\
views_plugin_argument_default_php.inc(51) : eval()'d code)" after they had tried to create a block to display related content of a node in Drupal 7 using PHP code. If you are encountering an error of a similar nature in your Drupal website then read on to find the solution.
Many Drupal users have expressed their interest in Theming Exposed Filter Forms of the Views they had created. The most commonly requested feature is to change the label of the Submit button to 'Search' or something more useful. Many Drupal users have realized that they lost all the labels on the filter widgets when using the views_exposed_form() function to do the job. If you are encountering the same situation in your Drupal website then read on to find the solution.
Many Drupal users found out that while using Drupal Views that the Is not one of" filter operator was broken. It seemed to be returning the same results as the "Is not empty (NOT NULL)" operation. The error commonly occurred in the text list fields and boolean fields. If you are encountering the same situation in your Drupal site then read on to find out more.
Some Drupal users have realized that Facebook Rules prevents FBOAuth from capturing e-mail addresses in their Drupal website. Uninstalling Facebook Rules brings back the functionality to FBOAuth. If you are encountering a similar issue in your Drupal website then read on to find out more.
A Drupal user had reported that when using multiple Views for displaying images, each with their own separate pager in a grid format, Colorbox popup displays the wrong image belonging to another View when an image has been clicked. If you experiencing the same issue with the Colorbox popup displaying the wrong image when using Views Ajax pager in your Drupal website then read on to find out the solution.
Some Drupal users have reported that the Drupal Google Store Locator module they have been using has been displaying only 10 store locations on the sidebar even though there are 15 store locations appearing on the map. If you are facing the same issue with the Google Store Locator module in your Drupal website and are looking for way to increase the number of stores listed in the side menu then read on for the solution.
A Drupal user encountered a situation in their Drupal site when using the Drupal Commerce Kickstart Module in which the uploaded product images do not fit into the fields for displaying the product images in Node:full content. If you are encountering the same situation in your Drupal site when using the Drupal Commerce Kickstart module then read on to find out more.
A few Drupal 7 users while trying to rewrite the output of a field as a link in a View found out that a space gets added before the file name in the URL. If you are facing the same scenario while using Drupal Views in your Drupal 7 website the read on to know the solution.
A few Drupal users reported that after they installed the Drupal Default Content module in their Drupal website the module lists on their Drupal installation stopped loading followed by the home page failing to load. Turning on detailed error reporting in index.php displayed a "Call to undefined function context_get_plugin() in modules/defaultcontent/defaultcontent.module" error and a "Fatal error: Class 'context_condition' not found in profiles/openenterprise/modules/defaultcontent/plugins/defaultcontent_condition.inc on line 3" error message. The second one was in the modules list page. Disabling the Drupal Default Content module eliminated the problem. If you are facing the same scenario in your Drupal website then proceed to see the solution.