If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

'Calendar -> Publish' menu item is always disabled

VERIFIED FIXED in 1.0b1

Status

Calendar
Lightning Only
VERIFIED FIXED
9 years ago
8 years ago

People

(Reporter: Andreas Treumann, Assigned: Fallen)

Tracking

unspecified
1.0b1
Bug Flags:
wanted-calendar1.0 +

Details

(Reporter)

Description

9 years ago
STEPS TO REPRODUCE:
===================

- select a calendar in the calendar list
- open the calendar menu
- try to publish the selected calendar

RESULT:
=======

- the 'Publish' entry is disabled

EXPECTED RESULT:
================

- the 'Publish' entry should be enabled

REPRODUCIBLE:
=============

- always

'Publish calendar' via context menu in the calendar list works.

Comment 1

9 years ago
Doesn't the Lightning 'Publish' entry corresponds to 'Publish Selection' entry in Sunbird? That means it will only work if you have at least one event selected?
(Reporter)

Comment 2

9 years ago
The 'Publish' entry is also disabled if I select a event in the calendar view.
Flags: blocking-calendar0.9?
I don't think that this constitutes a blocker.
Recommend blocking0.9-

Updated

9 years ago
Flags: wanted-calendar0.9+
Flags: blocking-calendar0.9?
Flags: blocking-calendar0.9-

Updated

9 years ago
Flags: wanted-calendar1.0+
Flags: wanted-calendar0.9+
Flags: blocking-calendar0.9-

Comment 4

9 years ago
This bug could be fixed / workarounded by removing disabled attribute during e.g. ltnOnLoad(event) but I had problems finding how this attribute got there in the first place... ?
Depends on: 456385
I'm no longer seeing this after the checkin of bug 456385. Please reopen, if you're still seeing this. Marking FIXED.
Assignee: nobody → philipp
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.0
Status: RESOLVED → VERIFIED
(Assignee)

Updated

8 years ago
Target Milestone: 1.0 → 1.0b1
You need to log in before you can comment on or make changes to this bug.