- 🇩🇪Germany Fabianx
Should be fixed now, but for LAT / LON will need 'additional_fields' => TRUE.
WKT is best.
Automatically closed - issue fixed for 2 weeks with no activity.
Hi
I am using the following modules.
I am facing the same issue. Page load time is in minutes and page size in MB’s. I installed and enabled your sandbox module Openlayers Quick Query. But I am using latitude/longitude widget instead of WKT field. Your module is not compatible with latitude/longitude widget. I am getting the following error.
“Fatal error: Cannot access empty property in D:\xampp\htdocs\parkwise22\sites\all\modules\openlayers_quick_query\openlayers_quick_query.module on line 97”
I debug it and I found that $val->{$wkt_alias } is not populated at line #97 in openlayers_quick_query.module file.
// Preprocess basic URL for node/<nid> type links
$b_url = url('node', array('alias' => TRUE));
foreach ($view->result as $key => $val) {
$row = array(
'projection' => $projection,
'attributes' => array(
),
'wkt' => $val->{$wkt_alias}
);
I have implemented hook_openlayers_quick_query_info. I m using title field only for the time being but I will use some additional fields too from my content type.
function parkwise_utilities_openlayers_quick_query_info($view) {
if ($view->name == 'campground_search_map') {
// Add projection and wkt information
$info['projection'] = '4326';
$info['wkt_field'] = 'field_location';
// Add needed fields
$info['fields'][] = array(
'field_name' => 'field_location'
);
$info['fields'][] = array(
'field_name' => 'title',
'additional_fields' => FALSE
);
$info['attributes'] = array(
'nid' => 'nid',
'name' => 'node_link_fast',
'title' => 'title' // Special very fast node_link linking the title using just node/<nid> with no aliases
);
return $info;
}
}
Please guide me how i can resolve this issue?
Thank you,
Zeeshan.
Fixed
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Should be fixed now, but for LAT / LON will need 'additional_fields' => TRUE.
WKT is best.
Automatically closed - issue fixed for 2 weeks with no activity.