Closed Bug 594794 Opened 14 years ago Closed 4 years ago

calendar does not reload after pressing "check for update"

Categories

(Calendar :: Calendar Frontend, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: doublehp, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; DHP; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100803 Gentoo Firefox/3.6.8
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; fy-NL; rv:1.8.1.23) Gecko/20100130 Lightning/0.9 Thunderbird/2.0.0.23 Mnenhy/0.7.5.0

When an entry is added to server by an other client, pressing reload, what ever the way ... does not make the new entry appear in TB/Calendar

Reproducible: Always

Steps to Reproduce:
1. start TB, and open a network calendar
2. add an entry on the server
3. press reload
Actual Results:  
nothing

Expected Results:  
show new entry

This is specific to Canlendar lightning; it did not happen un Sunbird.

I have tried the following ways to reload:
- press the "update" button in TB bars
- right click on the calendar in the left col, and select reload
- untick and retick

This happens to me while the server is Gmail, either by adding a new entry in gmail web interface, or using an other client (mobile phone).

The new entry will only appear after closing TB compleetely, and restarting.

TCW do you havea network calendar you can test this against?

Flags: needinfo?(thee.chicago.wolf)

(In reply to Wayne Mery (:wsmwk) from comment #1)

TCW do you havea network calendar you can test this against?

By network calendar, do you mean on the local LAN / SMB or a Google cal?

Flags: needinfo?(thee.chicago.wolf)

apparently google

This happens to me while the server is Gmail, either by adding a new entry in gmail web interface, or using an other client (mobile phone).

Flags: needinfo?(thee.chicago.wolf)

I wasn't see this with Provider for Google Cal or, presently, with CalDAV. WFM.

Flags: needinfo?(thee.chicago.wolf)
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.