Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 440269

Summary:	Can't create or edit Event on LTS web page
Product:	Community	Reporter:	Lisa Lasher <lasher>
Component:	Website	Assignee:	phoenix.ui <phoenix.ui-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	P3	CC:	chris.guindon
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Lisa Lasher

2014-07-23 16:44:21 EDT

I'm trying to create meeting minutes on lts.eclipse.org.  I've logged in, then hit Add Content.  My choices are Article / Basic Page / FAQ.  Event is missing from the list, so I can't get to the event template.  

In possibly related news, if I open an existing meeting, such as https://lts.eclipse.org/content/steering-committee-meeting-may-27-2014, I can't get into edit mode.  If I look at any other (non-event) type of page, such as https://lts.eclipse.org/members, it has the banner at the top that says View / Edit.  But for an event entry, the View / Edit banner is missing.  

So it seems like something has happened to the Event template?

Comment 1 Christopher Guindon

2014-07-23 18:07:50 EDT

After reviewing the permission for the LTS website, only users in the "steering committee" user role could create or edit meeting minutes.

Your user is currently in the "steering committee delegate" user role.

I made an update to the permissions of the LTS website to allow users in the "steering committee delegate" user role to edit meeting minutes.

Can you try and let me know if all is well now for you?

Cheers,

Comment 2 Lisa Lasher

2014-07-23 19:11:09 EDT

Yes, it seems ok now  -thanks.   I don't know what changed, since I've been posting meeting minutes for over a year.  And it was strange that it was happy to let me create / edit other types of content, and only Events were restricted (which is the only thing that I DO create!)

Comment 3 Christopher Guindon

2014-07-24 10:04:17 EDT

Awesome! The meetting module was updated yesterday. It could of triggers this change in behavior.

Closing this bug!