Calendar - Clarifications regarding sharing

[snowweb]

First, thanks for such a great plugin. We've been looking for exactly this for some time now. However, I have a couple questions/issues with it which I wonder if you could clarify?

   

• What is the purpose of those weird google feeds which seem to be pre-installed? Are they just for demo? Should they be deleted from each account? Where should I do this?
• When trying to enable shared calendars, I expand 'Confidential feed access [full access (read/write)]' by clicking on the icon beside the field and copy the URL displayed. Then I login to someone elses calendar and in feed settings again, I click on 'Add feed' and paste the URL in there. When I click save, the status bar indicates that http transactions are taking place for a few seconds and then reverts to 'Done', but an error in the info panel at the top of the page, displays, "An error occurred while saving" and the feed is not added.

Regards,

Peter

Client system Info: Ubuntu linux10.10, Firefox 4.0.1

[rosali]

#1
config.inc.php

// event feeds (can be deleted by user)
$rcmail_config['calendarfeeds'] = array(
  'http://www.google.com/calendar/feeds/german__de@holiday.calendar.google.com/public/basic' => 'Google',  
);

// public calendar (can't be deleted by user)
$rcmail_config['public_calendarfeeds'] = array(
  'http://www.google.com/calendar/feeds/usa__en@holiday.calendar.google.com/public/basic' => 'Public',
);

#2
Most propably your PHP cURL Module is missing.

[snowweb]

I don't think it's that Rosali. Yum informs me that...

Package curl-7.15.5-9.el5_6.2.i386 already installed and latest version

and phpinfo at the commandline also informs me...

cURL support => enabled
cURL Information => libcurl/7.19.5 OpenSSL/0.9.8b zlib/1.2.3

Is there something else I need?

Thanks.

[rosali]

You have to give me remote access (IMAP test account and FTP full access to Roundcube folder) to check this issue.

[rosali]

There is a problem resulting in a HTTP 500 error if user has never saved his calendar properties. To go around this modify calendar.php around line 135:

Code: [Select]


      else{
        $backend_type = 'database';
      }
    }
    // user has never saved prefs ... fall back to database
    if(!$backend_type)
      $backend_type = 'database';


[snowweb]

Thanks Rosali. That's done the trick nicely. We can use it now :-)

There is one other little problem though although I don't think it matters to me. That is that when trying to view a calendar shared as read-only, it doesn't show up in the selection list when you are trying to switch to it.

Thanks again for an otherwise excellent plugin.

Peter

[rosali]

This is intended. You can only switch to shared calendar, if you have write priviledges.

Also please update to 2.4 bundle - there were other bugs regarding recurring events fixed.

Notice: The bundle does not contain the above bug fix yet.

[snowweb]

Please forgive my ignorance, but that sounds very strange to me. Why spent effort adding the facility to share calendars as "Confidential feed access [read only]" if when the user chooses to do this, it's not going to do what it says it will (actually, it appears to do absolutely nothing).?

Very confused.

Anyway, thanks for the newer release. I think I'll wait until you fix something more substantial before attempting to upgrade. Hopefully you'll fix this one in the near future, as I think my boss will be chewing my butt within a week about that!

Really grateful for your efforts Rosali (my despite my confusion above).

Peter

[rosali]

See my post above. It seems I have posted it while you were replying. It is not true that it does nothing. It displays a layer with readonly events.

EDIT: It does display a layer - at least on my test environment. I cross-checked it.

[snowweb]

On my system, if you add a read-only shared calendar feed, it does not get added to the drop-down box which prevents a user from selecting it.

Perhaps it's designed not to be necessary to select it(?), but I'd be surprised if that were the case.

Anyway, Rosali, this is not a big issue. The other problems I have are what will delay me implementing this great plugin.

Thanks. :-)