December 2014 - support - lists.drupal.org

Can't seem to run Drupal on XAMPP
by kallejagula . 03 Dec '14

03 Dec '14

Hello there, I wonder if someone has encountered the same problem. I want to run a test Drupal site on my laptop's XAMPP apache and mysql. Installation of Drupal works just fine. But after the installation, when I actually visit this newly created site, I cannot log in. Even if I enter correct first user's name & password, I'm denied of access. I've looked from phpMyAdmin, everything seems to be created correctly - there is Admin with hashed password in users' table etc. Just log-in from a browser fails. I've tried Drupal installation from Drupal site & XAMPP Drupal add-on. Both installation was carried out fine but later I could not log in. Ran out of ideas. Regards, KJ

3 3

For Drupal 7 how can I ensure that views RSS channel properties that are added within hook_views_query_alter() remain?
by John Mitchell 03 Dec '14

03 Dec '14

I have applied the below patch (see below link) so the views module will add the following channel properties of pubDate and lastBuildDate. After applying the patch and after running Drupal "Clear all caches" within /admin/config/development/performance these added channel properties are only available for the first page requested and they will not be available until after running another Drupal "Clear all caches". For Drupal 7 how can I ensure that views RSS channel properties that are added within hook_views_query_alter() remain? https://www.drupal.org/files/views-2037185-display_pubDate_and_lastBuildDat… Thanks, John J. Mitchell

1 0

Strict warning: not sure what to do
by Andre Durudas 03 Dec '14

03 Dec '14

Hello, newbie question here: it started recently that I have been getting the error messages below on a Drupal 6 website. All modules and Drupal itself are up-to-date. Actually, I **think** that this started with the latest Drupal update (6.34). Does anyone have any ideas? Thanks! Andre strict warning: Non-static method view::load() should not be called statically in .../sites/all/modules/views/views.module on line 1118. strict warning: Declaration of views_handler_join_nodehierarchy_ancestor::construct() should be compatible with views_join::construct($table = NULL, $left_table = NULL, $left_field = NULL, $field = NULL, $extra = Array, $type = 'LEFT') in .../sites/all/modules/nodehierarchy/includes/views/nodehierarchy.views.inc on line 146. strict warning: Declaration of views_handlehomer_field::query() should be compatible with views_handler::query($group_by = false) in .../sites/all/modules/views/handlers/views_handler_field.inc on line 1148. strict warning: Declaration of views_handler_sort::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in .../sites/all/modules/views/handlers/views_handler_sort.inc on line 165. strict warning: Declaration of views_handler_sort::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in .../sites/all/modules/views/handlers/views_handler_sort.inc on line 165. strict warning: Declaration of views_handler_sort::query() should be compatible with views_handler::query($group_by = false) in .../sites/all/modules/views/handlers/views_handler_sort.inc on line 165. strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in .../sites/all/modules/views/handlers/views_handler_filter.inc on line 599. strict warning: Declaration of views_handler_filter::query() should be compatible with views_handler::query($group_by = false) in .../sites/all/modules/views/handlers/views_handler_filter.inc on line 599. strict warning: Declaration of views_plugin_query::options_submit() should be compatible with views_plugin::options_submit($form, &$form_state) in .../sites/all/modules/views/plugins/views_plugin_query.inc on line 181. strict warning: Declaration of views_plugin_row::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in .../sites/all/modules/views/plugins/views_plugin_row.inc on line 136.

1 0

Log entry question
by Keith Smith 03 Dec '14

03 Dec '14

Hi, Last night the LAMP server that servers our Drupal install crashed. It had too may available processes and ran out of memory. Reduced the number of available Apache processes and everything settled down. Early this morning the server crashed again. In looking at the log files I find two things that I need help understanding. Please understand I am not a Drupal developer - I am just responsible for it.... I'm seeing a bunch of 403 errors for trying to access /node/add - is this a new exploit? What is this? Also I am see lines that contain the following: xx.xx.xx.xx - - [02/Dec/2014:02:40:32 -0800] "POST /httprl_async_function_callback?count=2 HTTP/1.0" 200 486 "-" "Drupal (+http://drupal.org/)" xx.xx.xx.xx - - [02/Dec/2014:02:40:32 -0800] "POST /httprl_async_function_callback?count=1 HTTP/1.0" 200 502 "-" "Drupal (+http://drupal.org/)" xx.xx.xx.xx - - [02/Dec/2014:02:40:32 -0800] "POST /httprl_async_function_callback?count=1 HTTP/1.0" 200 502 "-" "Drupal (+http://drupal.org/)" xx.xx.xx.xx - - [02/Dec/2014:02:40:32 -0800] "POST /httprl_async_function_callback?count=1 HTTP/1.0" 200 502 "-" "Drupal (+http://drupal.org/)" xx.xx.xx.xx - - [02/Dec/2014:02:40:32 -0800] "POST /httprl_async_function_callback?count=1 HTTP/1.0" 200 502 "-" "Drupal (+http://drupal.org/)" xx.xx.xx.xx - - [02/Dec/2014:02:40:32 -0800] "POST /httprl_async_function_callback?count=2 HTTP/1.0" 200 486 "-" "Drupal (+http://drupal.org/)" Any idea what this is? Thank you so much for your help!! -- Keith Smith

2 5

Simpletest Conundrum
by Jeff Greenberg 01 Dec '14

01 Dec '14

Argh. Been so long that I sent this to the dev list by mistake... In Drupal 7, I have a requirement to simpletest a functional group of methods... one test comprised of about 1800 subtest permutations. The issue I have is that these are back-end functions with no UI interaction, yet simpletest unit test, from what I read, does not provide the functionality for accessing the db, creating test tables and data, etc. Do I fudge it by having a menu callback, or by having an admin page with a button if necessary, so that I can webtest, or do I manually include db.inc, etc. so that I can access the db, (though I think it would need to be much dirtier than that)? Jeff --- drupal.org/user/367108 linkedin.com/in/jeffrgreenberg accidentalcoder.com / ayendesigns.com @accidentalcoder

2 2

migrate webform with submissions from D6 to D7
by Bert Van Kets 01 Dec '14

01 Dec '14

Hi all, I need to migrate a webform with all the submissions from D6 to D7. Getting the webform itself over is not a problem using Node_export. That works fine. This module does not migrate the submissions however. So I tried using webform_migrate but either all elements are ignored or I get errors all around the place. There's more than one problem using this module. I follow the instructions in the readme.txt file and get to the Migrate Groups list, but then all elements are ignored when importing. There's no message on the reason why the elements are ignored. The numbers listed are correct though. If I import de default group first I do get the webform elements. There's no content yet though. When going into the Webforms Migrations group I get a WSOD with an error in the apache logs Call to a member function getGroup() on a non-object in /var/www/ta/sites/all/modules/contrib/migrate/migrate.module on line 98 I really don't have time to debug all this so hence my question: what is the best way to migrate a webform nod with the submissions from D6 to D7. I'm using Webform 7x-4.2 and Migrate Webform 7.x-1.1 Thanks for any help. Bert

1 0