BETA 8 bugs: Export to HTML Web-page
 

Ok, I think I found 1 bug in 3 different areas of the EXPORT feature.

When I choose FILE >>> EXPORT and choose "Web Page", the project does export properly but the issues that I have found are with the following links in the "index.html" file:

1) Project milestones
2) "Calendar" under the "Resource Calendars" section
3) "To-do lists" under the "Resource Calendars" section

Rather than getting intelligible information when any of the above are selected, here is what I get:

BEGIN:VCALENDAR
VERSION:2.0
X-WR-CALNAME:CST Automation
PRODID:-//The Omni Group//OmniPlan 0.1//EN
CALSCALE:GREGORIAN
BEGIN:VTODO
SEQUENCE:0
DTSTAMP:20061031T170000
SUMMARY:Phase 1A Complete (25 total)
UID:C28237D9-EF48-4D66-AB76-648AA390E2EB.70
DTSTART;VALUE=DATE:20061031T170000
DUE;VALUE=DATE:20061031T170000
END:VTODO
BEGIN:VTODO
SEQUENCE:0
DTSTAMP:20061130T170000
SUMMARY:Phase 1B Complete (50 total)
UID:C28237D9-EF48-4D66-AB76-648AA390E2EB.71
DTSTART;VALUE=DATE:20061130T170000
DUE;VALUE=DATE:20061130T170000
END:VTODO
BEGIN:VTODO
SEQUENCE:0
DTSTAMP:20061229T120000
SUMMARY:Phase 1C Complete (75 total)
UID:C28237D9-EF48-4D66-AB76-648AA390E2EB.72
DTSTART;VALUE=DATE:20061229T120000
DUE;VALUE=DATE:20061229T120000
PRIORITY:1
END:VTODO
END:VCALENDAR

I can't that this is the desired result - do you guys concur?

That's a file in iCalendar format. Your browser chooses to try displaying it as plain text instead of downloading it, or handing it off to an app that can handle it (iCal, Outlook, etc.). If I remember right, Safari correctly hands it off to iCal.

BETA 8 HTML bug
 

Lizard, ok - thanks for the clarification. I use Mozilla so based upon your feedback, I understand that Firefox is supposed to kick off the API and deliver the information to iCal - do I understand you correctly?

Also, any ideas?

If I open the index file directly from my desktop, it gives the behavior you describe, but if I put it in my public web folder and browse to it with firefox (myMachine.local/MyProject.htmld) then firefox asks me what to do with an ICS file and I can choose an app to open it or to save it to disk. So I think the issue is that you're looking at the file locally, and it won't do that if you actually post it to a web server.

If you don't have a web server you plan to post it to, then browsing the folder with Finder, you can see the .ics files in the Calendars sub-folder, and double-clicking them should open them in your default calendar app.

I can't seem to get this to work either in b8. I get:

BEGIN:VCALENDAR
VERSION:2.0
X-WR-CALNAME:MyProjectName
PRODID:-//The Omni Group//OmniPlan 0.1//EN
CALSCALE:GREGORIAN
BEGIN:VEVENT
DTSTART;TZID=US/Pacific:20061101T080000
DTEND;TZID=US/Pacific:20061101T170000
SUMMARY:My Task Name
UID:8228DEBE-1F95-408B-8E66-5F354A1DF360.162
END:VEVENT
END:VCALENDAR

I'm using Safari and accessing it on a separate server. Any ideas on how to fix this?

realtyler-

Try this:

-Right-click or control-click on the link to save the .ics file to your desktop.

-Right-click or control-click on the .ics file and select "Get Info".

-There should an option named "Open With:". Click on the drop-down menu and select "Other", then select "iCal" from your Applications folder.

-Click the "Change All..." button to set iCal as the default application for .ics files.

That should do it. Let me know how it works for you. :)

Strangely, when I right-click and Download linked file, it saves it as a .ics.txt file. Though, when I just mouse-over the link, it's a straight .ics file.

Hmm, interesting. Could you try deleting the .txt part and then right-clicking on the file to set it to open with iCal?

Ical
 

I am having the same problem.

When I open the html files from my desktop the ical links work fine and open in ical.

But when I open the html files from our intranet server I get what the others are getting just a text blurb in safari ... yes if I download the file to the desktop, tell it to get ride of the .txt suffix and then open from the desktop it does work...

BUT there is no way I am going to try to tell all our users to do that ....

russellb: Sounds like it might be a Safari configuration issue, but I'll poke around a little more, see what I can figure out.