joshuag

Recurme – Processwire Recurring Dates Field & Custom Calendar Module.

Recommended Posts

On September 8, 2017 at 0:14 PM, SoccerGuy3 said:

Working on the detail page now and having a problem getting the date/time of the event to show on the page. If my page array contains this:


[calev_datetime] => {"startDate":1504821600,"endDate":false,"dates":["W36/07/Thu/Sep/2017",...,"W19/07/Wed/May/2025"],"excluded":[],"active":false,"showResults":false,"rrule":"WKST=MO;FREQ=DAILY;DTSTART=20170907T150000Z;INTERVAL=1"}

How can I get the date to output to the page like: 09/07/2017 3:00 pm? I've tried various bits and pieces to get at the startDate or the DTSTART, but always end up with a nothing on screen (in that area).

$event = $recurme->event($page); then use $event->orig_date

Page/$event
	->template
	->orig_date
	->original
		->getDates()
	->start_date
	->dates_count
	->end_date
	->rrule
	->title
	->timestamp
	->time
	->date
	->day
	->month
	->year
	->hour
	->minute
	->second
	->ampm

Share this post


Link to post
Share on other sites
On September 7, 2017 at 5:50 PM, SoccerGuy3 said:

Love the promise of this module. Should save me a bunch of time on this project.

what was the problem? Maybe other people have seen this error? 

Share this post


Link to post
Share on other sites

Answer was actually in the FAQ! :) 

Ajax is not working.

Please make sure that your site contains a hidden page home/recurme-ajax/ using the template "recurme-ajax" and that you have a matching file in your site/templates/ folder. IF for some reason this file is missing, you can copy the template file from the InputfieldRecur/templates/recurme-ajax.php.

Share this post


Link to post
Share on other sites
2 hours ago, joshuag said:

$event = $recurme->event($page); then use $event->orig_date


Page/$event
	->template
	->orig_date
	->original
		->getDates()
	->start_date
	->dates_count
	->end_date
	->rrule
	->title
	->timestamp
	->time
	->date
	->day
	->month
	->year
	->hour
	->minute
	->second
	->ampm

I tried that:

                        $event = $recurme->event($page);
                        echo $event->orig_date . 'x';


But all that outputs to the screen is the "X".

I "solved" it temporarily with:

                        $dates = $page->getDates();
                        foreach($dates as $key=>$date){
                            $evDate = date('F j, Y \a\t g:i A', $date);
                            }

Which isn't going to work I suspect long term.

Share this post


Link to post
Share on other sites
5 minutes ago, joshuag said:

@SoccerGuy3 is it returning any of the other properties/variables? 

No. Tried: template, original, rrule, month. All with the same result, that is nothing was output.

Share this post


Link to post
Share on other sites
1 hour ago, SoccerGuy3 said:

No. Tried: template, original, rrule, month. All with the same result, that is nothing was output.

sent you a private message to hunt this down. :)

  • Like 1

Share this post


Link to post
Share on other sites
On 08/09/2017 at 9:27 AM, joshuag said:

I am trying to solve this problem. I cannot reproduce the error. Making it a bit hard to debug.  I tried removing the circular reference to what modules each file installs. Made no difference to me. 

@Robin S any other ideas? 

@joshuag, I think I have fixed the uninstallation issue. I found a few other issues in the module code too - I will PM you with the details.

  • Like 2

Share this post


Link to post
Share on other sites
16 hours ago, Robin S said:

@joshuag, I think I have fixed the uninstallation issue. I found a few other issues in the module code too - I will PM you with the details.

Amazing! Thank you. 

Share this post


Link to post
Share on other sites
8 minutes ago, SoccerGuy3 said:

@joshuag - Sent you a PM followup to the open issue and an additional question...

sent you a revisions. fingers crossed. 

Share this post


Link to post
Share on other sites

My client wants to print the page with the Calendar Grid. When you print, the grid prints, but not the individual items. Anyone run across this?

Share this post


Link to post
Share on other sites
6 minutes ago, SoccerGuy3 said:

My client wants to print the page with the Calendar Grid. When you print, the grid prints, but not the individual items. Anyone run across this?

Update: Appears to be browser specific. 

Mac Chrome: Grid only, no details

Mac FF: Everything prints.

Share this post


Link to post
Share on other sites

I was working on a development site (ProcessWire 3.0.75 and PHP 7.0) and downloaded a copy of Recurme to use.  Once I got the module installed, I was confronted with a non-working site.  I SFTP'd to the site and removed the Recurme module.  I was still confronted with the following error:

rm-error1.thumb.png.ee544e65d1d429c996e99df58629164e.png

I was able to revert to a previous version of ProcessWire (3.0.62), which allowed me administrative access to the site again.

rm-error2.png.d8bd2c6928cfe3cc5b651027068dc5b1.png

I haven't had this occur before, so I was a little surprised when I lost all access to the site.  I had good backups, however I was glad I was able to downgrade the ProcessWire version to regain access.  It took awhile to remove all traces of Recurme from the site, however things seem to be back to normal.

Anything information that you could provide on how to get Recurme working or where I possibly went wrong, would be greatly appreciated.

Best Regards,

Charles

Share this post


Link to post
Share on other sites
6 minutes ago, cstevensjr said:

I was still confronted with the following error:

rm-error1.thumb.png.ee544e65d1d429c996e99df58629164e.png

That error from the Repeater module looks like the same thing I raised a GitHub issue for recently, so there's a good chance it relates to PW's caching of module data rather than Recurme specifically. Ryan has pushed a fix for the issue to the dev branch.

  • Like 2

Share this post


Link to post
Share on other sites
6 minutes ago, Robin S said:

hat error from the Repeater module looks like the same thing I raised a GitHub issue for recently, so there's a good chance it relates to PW's caching of module data rather than Recurme specifically. Ryan has pushed a fix for the issue to the dev branch.

Thanks for speaking up about this.

Share this post


Link to post
Share on other sites

I could not find a way to get the value of the "all day" checkbox and found out that its state is hard-coded (checked) in InputfieldRecurme.module. I need to differentiate between "all day" and "normal" events and output them differently on a clients website. Could you please implement something like a $event->allDay property?

Thanks!

Share this post


Link to post
Share on other sites

@joshuag Early on in the thread you mentioned a work-in-progress fix for the 2800 event limit, and also about a more elegant update feature when adding exclusions. Any update on this? I've scanned the posts in the rest of the thread but might have missed it. Have these issues been addressed in the current version?

Share this post


Link to post
Share on other sites

I'm having a similar problem to SoccerGuy above.
All I'm trying to do is display the start date of an event on the event's page, and I can't help feeling this shouldn't be this hard. What have I missed?

Experiment 1 -

$content .= $recurme->renderEvent($page); 

This returns 

<li><a href="?date=" title="Test Event 1">Test Event 1</a></li>

where Test Event 1 is the title of the current page. 

Experiment 2 - 

$rcoptions = ['timeFormat'	=> 'g:i a',
'dateFormat' 	=> 'M d, Y @ g:i a',
'dayFormat'		=> 'd',
'monthFormat'	=> 'M',
'yearFormat'	=> 'Y',
'hourFormat'	=> 'g',
'minuteFormat'	=> 'i',
'secondFormat'	=> 's',
'ampmFormat'	=> 'a',
'xBefore' 		=> 'TEST',
'xItem'			=> '{time} &bull; <a href="{link}" title="{timestamp}">ABCDEF{timestamp}</a>',
'xAfter'		=> ''];
$content .= $recurme->renderEvent($page, $rcoptions); 

This returns the same thing as the first experiment, apparently ignoring the $rcoptions object I passed in. Note that I attempted to change the xItem element, but no joy.

Experiment 3

$event = $recurme->event($page);
$content .= "Event: " . $event;
$content .= "Orig Date: " . $event->orig_date;

This outputs Event: and Orig Date: strings, but nothing else.

Clearly I have no idea what I'm doing - any guidance appreciated.

Share this post


Link to post
Share on other sites
On 19/12/2017 at 10:56 PM, netcarver said:

@joshuag Early on in the thread you mentioned a work-in-progress fix for the 2800 event limit, and also about a more elegant update feature when adding exclusions. Any update on this? I've scanned the posts in the rest of the thread but might have missed it. Have these issues been addressed in the current version?

+1

I would be interested as well.

Share this post


Link to post
Share on other sites
On 1/3/2018 at 5:34 PM, Smoo said:

I'm having a similar problem to SoccerGuy above.
All I'm trying to do is display the start date of an event on the event's page, and I can't help feeling this shouldn't be this hard. What have I missed?

Experiment 1 -


$content .= $recurme->renderEvent($page); 

This returns 


<li><a href="?date=" title="Test Event 1">Test Event 1</a></li>

where Test Event 1 is the title of the current page. 

Experiment 2 - 


$rcoptions = ['timeFormat'	=> 'g:i a',
'dateFormat' 	=> 'M d, Y @ g:i a',
'dayFormat'		=> 'd',
'monthFormat'	=> 'M',
'yearFormat'	=> 'Y',
'hourFormat'	=> 'g',
'minuteFormat'	=> 'i',
'secondFormat'	=> 's',
'ampmFormat'	=> 'a',
'xBefore' 		=> 'TEST',
'xItem'			=> '{time} &bull; <a href="{link}" title="{timestamp}">ABCDEF{timestamp}</a>',
'xAfter'		=> ''];
$content .= $recurme->renderEvent($page, $rcoptions); 

This returns the same thing as the first experiment, apparently ignoring the $rcoptions object I passed in. Note that I attempted to change the xItem element, but no joy.

Experiment 3

On 1/3/2018 at 5:34 PM, Smoo said:

I'm having a similar problem to SoccerGuy above.
All I'm trying to do is display the start date of an event on the event's page, and I can't help feeling this shouldn't be this hard. What have I missed?

Experiment 1 -



$content .= $recurme->renderEvent($page); 

This returns 



<li><a href="?date=" title="Test Event 1">Test Event 1</a></li>

where Test Event 1 is the title of the current page. 

Experiment 2 - 



$rcoptions = ['timeFormat'	=> 'g:i a',
'dateFormat' 	=> 'M d, Y @ g:i a',
'dayFormat'		=> 'd',
'monthFormat'	=> 'M',
'yearFormat'	=> 'Y',
'hourFormat'	=> 'g',
'minuteFormat'	=> 'i',
'secondFormat'	=> 's',
'ampmFormat'	=> 'a',
'xBefore' 		=> 'TEST',
'xItem'			=> '{time} &bull; <a href="{link}" title="{timestamp}">ABCDEF{timestamp}</a>',
'xAfter'		=> ''];
$content .= $recurme->renderEvent($page, $rcoptions); 

This returns the same thing as the first experiment, apparently ignoring the $rcoptions object I passed in. Note that I attempted to change the xItem element, but no joy.

Experiment 3



$event = $recurme->event($page);
$content .= "Event: " . $event;
$content .= "Orig Date: " . $event->orig_date;

This outputs Event: and Orig Date: strings, but nothing else.

Clearly I have no idea what I'm doing - any guidance appreciated.

This outputs Event: and Orig Date: strings, but nothing else.

Clearly I have no idea what I'm doing - any guidance appreciated.

I must not be the only one. I've tried all of the above and emailed. Any help would be appreciated

$event = $recurme->event($page);

I try to output any thing and it's blank.

 

Share this post


Link to post
Share on other sites

Seems to be broken when looking for dates in Feb 2018, April 2018, June 2018 etc no show up event though there should be.

Share this post


Link to post
Share on other sites
19 hours ago, SC24 said:

I must not be the only one. I've tried all of the above and emailed. Any help would be appreciated

$event = $recurme->event($page);

I try to output any thing and it's blank.

 

$event = $recurme->event($page); is 100% correct way to get the event. However, you must have a recurme field with an event for it to return anything. After that, you can access all your fields for that $page as 

$event->orignal->title (or whatever field you have)

Hope this helps,

- Joshua

Share this post


Link to post
Share on other sites
2 hours ago, joshuag said:

$event = $recurme->event($page); is 100% correct way to get the event. However, you must have a recurme field with an event for it to return anything. After that, you can access all your fields for that $page as 

$event->orignal->title (or whatever field you have)

Hope this helps,

- Joshua

My admin side looks like the attached image.

On the front end I am calling:

doman/events/library/ready-to-learn-story-time-multi/?date=1517514600

$event = $recurme->event($page);

The following outputs nothing:

echo $event->title;

echo $event->original->title;

...etc.

Capture.PNG

Share this post


Link to post
Share on other sites

OK - I have found a temporary solution...I have found that if I set the event to recurring, then the data is output as normal. If I leave it as a single event, that is when my data comes back blank.

I replaced my code with the module file that Josh added on page 2, however, that made all my events recurring regardless if it was active or not(but fields were showing values).

So, now I am using the default code that came with the module(not page 2 code). Except on my event detail page, I am using the $page object. From there I am using json_decode($page->Recurme_Field), then outputting my fields from there.

 

detail page sample:

$o = json_decode($page->Recurme_Field);
echo $page->title ."<br/>";
echo date('M d, Y g:i A', $o->startDate) . "<br/>";
echo date('M d, Y g:i A', strtotime($page->Recurme_End_Date_Time)) . "<br/>";
echo $page->Recurme_Location . "<br/>";
echo $page->Recurme_Details;

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      Another little admin helper module...
      Template Field Widths
      Adds a "Field widths" field to Edit Template that allows you to quickly set the widths of inputfields in the template.

      Why?
      When setting up a new template or trying out different field layouts I find it a bit slow and tedious to have to open each field individually in a modal just to set the width. This module speeds up the process.
      Installation
      Install the Template Field Widths module.
      Config options
      You can set the default presentation of the "Field widths" field to collapsed or open. You can choose Name or Label as the primary identifier shown for the field. The unchosen alternative will become the title attribute shown on hover. You can choose to show the original field width next to the template context field width.  
      https://github.com/Toutouwai/TemplateFieldWidths
      https://modules.processwire.com/modules/template-field-widths/
    • By horst
      Croppable Image 3
      for PW 3.0.20+
      Module Version 1.1.16
      Sponsored by http://dreikon.de/, many thanks Timo & Niko!
      You can get it in the modules directory!
      Please refer to the readme on github for instructions.
       
      -------------------------------------------------------------------------
       
      Updating from prior versions:
       
      Updating from Croppable Image 3 with versions prior to 1.1.7, please do this as a one time step:
      In the PW Admin, go to side -> modules -> new, use "install via ClassName" and use CroppableImage3 for the Module Class Name. This will update your existing CroppableImage3 module sub directory, even if it is called a new install. After that, the module will be recogniced by the PW updater module, what makes it a lot easier on further updates.
      -------------------------------------------------------------------------
       
      For updating from the legacy Thumbnail / CropImage to CroppableImage3 read on here.
       
      -------------------------------------------------------------------------
       
    • By MoritzLost
      UPDATE: I have published a stable version of this module!
      Discussion thread:
      Github: https://github.com/MoritzLost/TextformatterPageTitleLinks
      ---
      Hello there,
      I'm working on a tiny textformatter module that searches the text for titles of other pages on your site and creates hyperlinks to them. I'm not sure if something like this exists already, but I haven't found anything in the module directory, so I wrote my own solution 🙂
      It's not properly tested yet and is still missing some functionality I would like to implement, so at the moment it should be considered in BETA. Features include limiting the pages that will get searched by template, and adding a custom CSS class to the generated hyperlinks. As I'm writing this I noticed that it will probably include unpublished and hidden pages at the moment, so yeah ... it's still in development alright 😅
      You can download the module from Github:
      https://github.com/MoritzLost/TextformatterPageTitleLinks
      There's some more information in the readme as well.
      Anyway, let me know what you think! I'm happy about any feedback, possible improvements or ideas on how to improve the module. Cheers.
    • By blad
      Hi guys!
      I just uploaded a module to explore files based on elFinder. By default it will show the "Files" folder.
      Screenshots:

      Video:
       
      To do:
       More options To fix:
       The function of rotating or scaling an image fails  Image editors V 1.01 (view issue)
      Fixed the bug working with the Multi-Language support ( translation of folders ). Fixed the name of elfinder.en  Github:
      https://github.com/LuisSantiago/ProcessElFinder/
      I hope you like it.
    • By BitPoet
      I'm really in love with FormBuilder, but the one thing missing to match all my end users' expectations were repeatable field groups. Think repeaters, in ProcessWire terms. Our primary application of PW is our corporate intranet, so "lines" of fields are quite common in the forms I build. We have all kinds of request forms where the information for a varying number of colleagues needs to be entered (from meal order to flight booking request) and where it is simply impractical to send a form for each, and I don't want to clutter my forms with multiple instances of fields that may only get used ten percent of the time.
      That's why I started to build FormBuilderMultiplier (link to GitHub).
      What it does:
      Adds an option to make a regular Fieldgroup repeatable Lets you limit the number of instances of a Fieldgroup on the form Adds an "Add row" button the form that adds another instance of the Fieldgroup's fields Adds a counter suffix at the end of every affected field's label Stores the entered values just like regular fields Makes the entered values available in preview and email notifications Supports most text based fields, textareas and selects (really, I haven't had enough time to test all the available choices yet) What it doesn't do (yet):
      Support saving to ProcessWire pages (i.e. real Repeaters) I haven't tested all the validation stuff, Date/Time inputs etc. yet, but since I'm utterly swamped with other stuff at work, I didn't want to wait until I have it polished. Any feedback is welcome. There might also be some issues with different output frameworks that I haven't encountered yet. The forms I work with mostly use UIKit.
      Status:
      Still alpha, so test well before using it in the field.
      Known issues:
      When rows are added, the form's iframe needs to be resized, which isn't completely clean yet.
      How it works:
      The Fieldgroup settings are added through regular hooks, as is the logic that adds the necessary field copies for processing the form and displaying previews.
      "Multiplied" field instances are suffixed with _NUM, where NUM is an incremental integer starting from 1. So if you have add two fields named "surname" and "givenname" to a fieldgroup and check the "multiply" checkbox, the form will initially have "surname_1" and "givenname_1" field (I'm still considering changing that to make the risk to shoot oneself into the foot by having a regular "surname_1" field somewhere else in the form less likely).
      When a "row" is added, the first row is cloned through JS and the counter in the fields' IDs, names and "for" attributes as well as the counter in the label are incremented before appending the copies to the Fieldset container in the form.
      To keep backend and frontend in sync, a hidden field named [name of the fieldset]__multiplier_rows is added to the form. Both the backend and the frontend script use this to store and retrieve the number of "rows".
      ToDo:
      Naturally, add the option to store the data in real repeaters when saving to pages. Do a lot of testing (and likely fixing). Make a few things (like the "Add row" button label etc.) configurable in field(set) context. Add a smooth API to retrieve the multiplied values as WireArrays. The mandatory moving screenshot: