• Content count

  • Joined

  • Last visited

  • Days Won


joshuag last won the day on May 20 2017

joshuag had the most liked content!

Community Reputation

252 Excellent

About joshuag

  • Rank
    Sr. Member
  • Birthday 09/11/1980

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Calgary AB, & Mérida, Yucatan

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. you can use the formats as well for languages other than english.
  2. @GhostRider @adrian Attaching new files for timeEndUnix. Please let me know if you find anything strange. Ps. Also added a fix for missing dates/events if they were set to not repeat. This will all be rolled into the next update as well. thanks for your help. rrule-gui.js MarkupRecurme.module
  3. OK, thanks for testing this. I will give it a look and upload a new file. :)
  4. Adrian, I have added an extra variable to recurme to give you the timeEnd as a unix timestamp so you can format it however you want. $event->timeEndUnix; Here is an example that outputs the exact information you want: <?php $p = $pages->get(1120); $event = $recurme->event($p); echo date('M d - ', $event->start_date); echo date('M d', $event->end_date)."<br />"; echo date('g:i a - ', $event->start_date); echo date('g:i a', $event->timeEndUnix); // outputs // Mar 14 - Feb 16 // 9:03 am - 9:02 am ?> IMPORTANT: We need to re-save an event to add the value of timeEndUnix to the json data. I know this is not ideal, however it was the best compromise until I make date saving & conversions better all around. I have also adjusted the 'timeEnd' value to be effected by the 'timeFormat' option if you prefer to use that instead, however, this will only work if your saved data for the event has timeEndUnix Value. You had mentioned that you have a lot of events, in order to take advantage of the new timeEndUnix variable, you will have to save your events again. Send me a PM and we can work out a way to do it with the API and add the timeEndUnix value to your JSON data for your existing events. Please try these (attached) files and let me know if you find any problems. Hope this helps, rrule-gui.js MarkupRecurme.module
  5. change the timeFormat option instead, or change the xBefore template to use {date} instead of {time}. 'xBefore' => '<li class="rm-list-event {}"><span class="rm-event-date">{time}</span> ', yeah, this looks like a timezone issue. I am digging into it. thanks for bringing it up. Subtracting one day won't work or be consistent.
  6. Try this updated file: I will add this to my next release. Thank you! MarkupRecurme.module
  7. endDate will always be startDate -> till END OF THE CURRENT DAY from the interface if you have a timeEnd (11:59 from your example). endDate always represents the UNIX TIMESTAMP of the day/hour/min in seconds of the END TIME of the event. If you want a date for the events to stop if it is repeating, then it refers the the UNTIL value part of the RRULE UNTIL value. The until value tells recurme to expand the repeating dates up to the UNTIL date. I can see how this is confusing. I might rename these variables now that you have brought it to my attention.
  8. I am not sure that multiple recurme fields in a single page would work as expected. Parsing the Json would work well.
  9. I don’t have a method to add dates via the api, but that is a good idea. If you do add dates by populating the json manually, I could see some complications arising depending on how you have chosen the repeat pattern in the Recurme Field. Because the dates are generated based on the rrule via JavaScript. I will give this some thought and see how we could make this a no-brainer. Thanks for the great idea.
  10. I would love to know what happened. Let me know, if I need to, I will issue an update right away. Thank you!
  11. $event->allDay should be giving you the value of $allDay in the event object true/false. This is also implemented in the json stored in the field.
  12. I did not modify it. I didn't even think of it, but it's a good idea. I'll do a quick update on that. Thanks!
  13. Just wanted to let everyone know that I sent out an email to everyone who purchased Recurme with the updated Recurme Module Package. Thanks again to everyone who tested the changes and feedback. Especially @adrian
  14. I think I have finally fixed this! woot woot. Thanks @adrian for all your help. I have attached a new .js file. Let me know if that works for you. rrule-gui.js