Using a date contextual filter to get the state of the current day!

I will look into your issue as well, but don't expect a reaction soon.

I'm going to review it, but please be patient. The first impression looks interesting though.

I've updated the patch for the latest dev version (7.x-3.2+21-dev).

Is this feature now available as standard in availability calendar 7.x-4.x?

No, not yet, and I am afraid it won't make it into the 7.x-4.0 release. It might make it into 7.x-4.1 though.

Just trying to getting this working but not having much luck

I have applied the patches to Date and Calendar, but wasn't sure what to do about views as there have been several releases since the dev version you mentioned using.

Also I don't want to go back to an older version of availablity_calenders so had to manually patch it as the patch didn't work on the latest version.

I'm not getting any errors but the status field isn't available in views. Any suggestions?

I will look into this, but will first solve your other issue (bug 1899608) and add some paid for features. But please give it another try yourself, especially when you can code. If possible, try to solve it without being dependent on patches from other modules.

Might the problem be solved by making the calendar an entity on its own? This would increase discoverability and handling by other modules like date and calendar. The field part will then change into a kind of a reference field.

Not sure though if and what other problems this will give when thinking of things like access, editing within the entity edit form of the referring entity, will it gets its own page, etc.?

Well, now that I have a clearer picture of what this is all about and that we seem to have a possible way of solving it without being dependent of other modules, we can focus on solving it the entity way. You will have my cooperation but unfortunately I do not have much time to spent on it. So it might take a while, unless someone is willing to sponsor it (in part).

Entities definitely seems the way forward.

In regards to the patch, I have found that it's because it's an entity that has the availability calendar not a node, and in views you don't get the content option when selecting custom entity fields.

In fact when using a custom entity I only get the option the select the availability calendar, all the other options such as created and updated are not available. Not really sure if it's a problem with this modules or my custom entities, but I've looked and other modules that provide custom entities and the content option isn't available on them either.

@Marc-Antoine, @marcus178: May I ask you to test and review the new 7.x-5.x-dev release? It should contain enough entity and views support to be able to do what you wanted to do. Look at the git commits to see a diff with the current stable version. That should make it easier to see what has been added, moved or changed.

Please post all your remarks, suggestions, improvements, patches in this issue.

This new, still experimental, branch is a start of entity integration. It actually only describes the availability_calendar_calendar table to entity, it describes the availability_calendar field to entity, and it describes the other tables (availability_calendar_availability and availability_calendar_state) to Views, including any relationships between these. This should allow you to create Views that can retrieve any piece of information you want, as well as filter and sort on any property you want.

There are no data model changes, so your data should be save and you should be able to downgrade. But still I would advice you to test on a separate install. Please also read the README.txt and, even more important, CHANGELOG.txt that come with this install before starting your testing.

Thanks in advance

PS: can you let me know if you are able to do any testing (in the near future), so I am not waiting in vain.

Ok thank you, when I get a moment I will have a look at this.

Assuming it works ...