Support for Search API

Do you know which API call should be used to get those Solr-based date fields? I'd be happy to add support for this, but I've never used Solr, so I'm not sure how.

I think this kind of integration may now be possible, with the new iCal Fields plugin. It lets you use Views Fields to populate your iCal feeds, instead of pulling the data directly off the entities themselves. Date iCal v2.9 (which will be released shortly after I post this), and the latest dev version, have the iCal Fields plugin.

Reopening this as I'm trying to get a date ical feed out of a Search API view and it's not working. The issue, I believe, comes from the fact that search API returns views rows in the following format:

stdClass::__set_state(array(
   'entity' => 7408,
   '_entity_properties' => 
  array (
    'search_api_relevance' => 1,
    'search_api_excerpt' => '',
    'search_api_id' => '7408',
  ),
   'index' => 0,
))

Therefore not returning rows as Date ICal expects them...

Yeah, that would definitely not be something that Date iCal expects. I guess Search API must hook into the Views system later in the process, to convert that data to an actual node.

I'm on a super tight deadline at work right now, though, so I haven't currently got any time to put toward Date iCal at the moment. I'll try to look into this next week.

Has there been any movement on this, I have come up against this issue and it would be great if a solution could be found

I'm afraid not. My company is moving away from Drupal, so I'm not going to have much time available for debugging module interoperability issues. I'm going to try to stay on top of major bugfixes with Date iCal itself, but I can't guarantee anything more than that.

@coredumperror - Sorry to hear that. What is the alternative CMS/stack that your company is moving too?

We're moving to Wagtail, which is a Python CMS based on the Django framework. Unlike Drupal, which is designed to enable non-technical admins to create a site, Wagtail is designed to enable programmers to create a site. This lets Wagtail get around some of the (let's face it) totally insane drawbacks of Drupal, e.g. separate tables for each individual field. Drupal has to do it that way to make it possible to edit the site's content types and views from the UI. But since Wagtail doesn't let you do that, the site designers are able to code content types in a way that actually makes sense. And Django's template system is lightyears ahead of Drupal's, in my opinion.

Good to know. Thanks for the explanation. I'll check it out.

Marking this as postponed, since Date iCal is in maintenance-only mode until someone volunteers to be (co-)maintainer.

Setting active, i'll be giving some work into it the next time.

Here is a first attempt at a patch. The one caveat is the 'first_available' function doesn't work. You have to manually select the date field in the view. This also doesn't work with the entity view.

Hope this helps someone!

Hi paul, this is a great start!
After using -p7 patch applied (patches should be relative to module dir, not project root).
Unfortunately it does not work for single-valued fields currently.

Patch flying in that works for single-valued fields too.