Forum Replies Created
-
Posts
-
I am in complete agreement with fixing the javascript bug as the higher priority issue.
As far as #2, the functionality issue, I’d like to make these points:
1) Events may recur at irregular intervals. I might have an event scheduled for 7:30 PM tomorrow, and the identical event scheduled for 2:00 PM the following day. Or an event scheduled for Monday morning this week, and Thursday afternoon next week. To my mind, those are still recurring events.
The way TEC stands today, the only way I can configure TEC to allow these irregular recurrence patterns is to break an event out of its recurrence and save it for a different date or time. (Perhaps you have a better solution?)
It would be nice if TEC were able to deal with irregular recurring patterns like this. From an implementation perspective, you might consider allowing me to configure multiple dates and times when an event will occur, rather than (or in addition to) selecting a recurring pattern. [I’m envisioning an array of dates & times, rather than a recurrence pattern? Make sense?]
2) If an event recurs only a few times, I could achieve the same effect if I were able to duplicate the event within TEC, and assign the duplicated event to another date and time. (A third-party plugin can achieve this result today, but it is less than ideal.)
While that is not as elegant a solution as I described above, it would be a functional solution if an event recurs only a small number of times.
In any case, the functionality to “duplicate an event” within TEC would be useful, and I would like to see it included in the product.
(and since I’ve already hijacked the thread, I’ll do it again to report this …) I’m getting 502 Bad Gateway from your nginx server when I leave a comment. The comment is there when I return to this page, but I’m shunted off to the 502 page in the interim. It’s happened a couple of times.
Awesome, Jonah. Thanks for the update.
If you don’t mind, I’d like to hijack this thread for just a moment: if there was a simple way to COPY an event, it might be a simple solution for solving the more difficult problem of addressing recurring events that don’t recur on a standard schedule. At least for my client, their events recur a few times, at most. If they had an easy way to COPY or DUPLICATE an existing event, change the date / time, and then save it, it would go a long way to addressing the more difficult recurring-event problem.Hey, Rob. That’s great news. I’d be happy to install it. (Any special instructions if there are problems and I need to revert back to the current version?)
Jonah, like David, the problem is intermittent here. I can go several days without a failure, and then have it happen a few times in a row. The bottom line, it makes it very hard to test interactions with other plugins or the theme (I’m using Genesis, for what it’s worth).
The one consistent item: it ONLY happens on events that have recurrence defined.We are following a procedure similar to Jason’s, except we’re leaving the “duplicate” events as non-recurring until this problem is resolved.
Jonah, how much memory would you recommend? I’m experiencing the same problem. My server’s default memory limit is 90M.
Mike
It’s late on Friday, so I may have completely forgotten something important. 😉
All I did was set those wp-config parameters.
In general, the site is served via http save for a few pages where we accept credit-card donations. Since we had the SSL certificate already installed, I was able to set the wp-config parameters, and serve the admin and login via SSL.
