If I select the option to disable the webcal:// prefix, the calendar loads perfectly into Outlook, etc. If I deselect it, the file is empty? I need to use the webcal prefix in order to subscribe, though.
Date iCal:7.x-2.8+6-dev
Date: 7.x-2.6+2-dev
Drupal: 7.18
PHP 5.3
iCal Creator Library: 2.18
Views: 3.6
Views:
I am using the new option in Views for showing iCal Fields (in lieu of Entities).
I have followed all of the instructions on the read me page (attached the Feed to a page view, etc.) The icon on that page changes from webcal:// to http:// when I disable the option in the view.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | date_ical-fix-incorrect-error-msg-2047723-7.patch | 1.73 KB | coredumperror |
| #4 | Events.zip | 265 bytes | Mr Richards |
Comments
Comment #1
coredumperror commentedThis may be an effect of the strange way that certain browsers deal with the webcal:// scheme.
Please try this: Set up your view to use webcal://, then load a page that shows the icon. Copy the url linked by the icon, paste it into your browser's address bar, and replace "webcal" with "http", then press Enter. If you still get a blank feed, then this is probably a Date iCal bug. If you get a non-blank feed, then it may be your browser's fault. Try another browser.
Comment #2
Mr Richards commentedCopied the orange icon's url and pasted into address bar and changed webcal to http. I still get an error from Outlook that "The Internet Calendar file does not contain any appointments". It adds it with the correct name, but no appointments. If I switch the view to disable webcal, it works (but I need to subscribe, not just import). I tried to open the webcal with www.30boxes.com, and it says there is no data in the calendar. I would think that would assure it is not a browser issue (as well as Outlook).
Does this have anything to do with the issues open for the new iCal Fields option in Views (escaping too many / or semicolons?, etc.).
Comment #3
coredumperror commentedThat definitely sounds odd. Could you please attach the .ics file that you're getting to this thread, so I can take a look at it?
Also, I released a new version of Date iCal (v2.9) yesterday, so upgrading to that might fix your problem.
Comment #4
Mr Richards commentedThank you for all the help. The .ics file looks like this (attached, as well):
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Drupal: Date iCal//NONSGML kigkonsult.se iCalcreator 2.18//
METHOD:PUBLISH
X-WR-CALNAME;VALUE=TEXT:IT Events
END:VCALENDAR
Comment #5
Mr Richards commentedAlso, I updated Date iCal to the new version and Views gives me this error when I select the Feed to edit:
Fatal error: Call to a member function getName() on a non-object in /home/impact/public_html/sites/all/modules/date/date_api/date_api.module on line 286
Comment #6
Mr Richards commentedOne more update:
I deleted the old view and made a new one. I did not see the above error again until I added the content's body field and assigned it as the "description". It will not generate a preview in views. If the body/description field is removed, the error goes away, but I see this in the view preview:
When using the iCal Fields row plugin, the Date, Title, and Description fields are all required.
Please set them up using the Settings link under 'Format -> Show: iCal Fields'.
I tried using the Title as the description, and received the same error as in the previous post. I tried the webcal link from the orange icon regardless of the issue, and it does not work (similar to previous issue).
Comment #7
coredumperror commentedHmmm, I don't have a clue what's going on with that error you're getting from Date API, but the one about required fields is definitely a bug in Date iCal. I wrote some redundant error checking into the feed plugin, back when the Title and Description fields were still required, and I forgot to remove it when I made them optional.
Thank you for finding that! Here's a patch that will fix that problem. Please apply it and let me know if you're still having issues.
Comment #8
Mr Richards commentedI did your patch and was still receiving the error in views about the date module. I corrected that with a patch I found in that module's section here.
I still have the same error that I have had since the beginning.
Comment #9
Mr Richards commentedNew errors now:
Warning: date_format() [function.date-format]: The DateTime object has not been correctly initialized by its constructor in date_ical_plugin_row_ical_fields->get_row_date() (line 236 of /home/impact/public_html/sites/all/modules/date_ical/includes/date_ical_plugin_row_ical_fields.inc).
Warning: DateTime::getTimezone() [datetime.gettimezone]: The DateTime object has not been correctly initialized by its constructor in date_ical_plugin_style_ical_feed->render() (line 189 of /home/impact/public_html/sites/all/modules/date_ical/includes/date_ical_plugin_style_ical_feed.inc).
Comment #10
Mr Richards commentedWhat version of date are you using? Have you tested with the version I am using? maybe that is it?
Comment #11
coredumperror commentedI'm using Date 7.x-2.6, the latest recommended release. Have you tried downgrading Date to v2.6? I'm also using Views 3.7, so upgrading to that version may help.
Have you tried making a clean Drupal install with only Date iCal and its dependencies? I can't reproduce this problem, and it's so severe that I assume someone else would have reported it if it were a bug in Date iCal itself, so my best guess is that you've either got a module installed that's messing up the process, or this is a bug in Date 2.6-dev. Unfortunately the maintainer, KarenS, appears to have been abandoned Date back in October, so I doubt there will be any help coming from that direction.
Comment #12
Mr Richards commentedI got it working!
I upgraded Views to 3.7, but that did not fix it (it actually broke some stuff and I had to patch some core files to get back up and running)
I am using the Content Access module. I had the view set to Permission:View Content, but I had the content access module allowing only authenticated users to see the type of content in my feed.
The webcal works, but does this mean I cannot limit subscribers to the webcal for only authenticated users?
Comment #13
Mr Richards commentedJust wanted to update for anyone else having trouble with this. I used the token auth module for the feed to work properly with Content Access module.
Comment #14
coredumperror commentedGreat! I'm glad you figured this out.