Replies to This Discussion

Permalink Reply by Tank-Ridin' Ryan on April 24, 2009 at 3:11pm

MARK, good point, but this is probably a flaw in how the NING software is written.

Leah, perhaps you could bring this to NING's attention?

• ▶ Reply

Permalink Reply by Tank-Ridin' Ryan on April 24, 2009 at 4:47pm

Ok, I see what you're saying MARK.

If NING doesn't have the coding abilities to differentiate between single days vs date spans, then posting rules should be changed on the CHAINLINK. If they can put the code in to make multi-date calendar dates post in each individual day, then they should.

Again, Leah, please look into this when you have time.

• ▶ Reply

Permalink Reply by Leah on April 24, 2009 at 6:01pm

Thanks Mark and Ryan, and h3 for speaking up. h3 pretty accurately summed up our situation here, so I don't want to repeat what he said. I would only add that in most cases, when a multi-day or recurring event is added to the calendar and it appears on the top of the list for multiple days, it was not put there to manipulate the calendar or unfairly take up space in a malicious way. And as h3 said, we have tried as much as possible to reach out to event organizers when something is on the calendar for too long, or there are duplicate events.

The calendar module here needs a few features to make it better, i.e. the ability to do recurring dates or the days vs. dates thing. These would require hard-coding which we don't have the ability to do. One day, if we take the option to "unhook" The Chainlink from Ning, then we can code the calendar differently, but that day is very far in the future.

In the meantime, a set of posting guidelines is a good suggestion. We'll add it to the list of site improvements. If you or anyone else has suggestions for specific guidelines, please feel free to send me a personal message. Thanks!!

• ▶ Reply

Permalink Reply by Leah on July 4, 2009 at 7:56am

Just wanted to echo h3 here, approving events will allow us to keep things tidy and avoid some of the missteps that have happened in the past. We absolutely don't intend to reject events through this process, rather it's simply a way to catch things before they appear on the calendar. :)

• ▶ Reply