Jump to content
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

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory (alpha version only available via GitHub) SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Robin S
      This module is inspired by and similar to the Template Stubs module. The author of that module has not been active in the PW community for several years now and parts of the code for that module didn't make sense to me, so I decided to create my own module. Auto Template Stubs has only been tested with PhpStorm because that is the IDE that I use.
      Auto Template Stubs
      Automatically creates stub files for templates when fields or fieldgroups are saved.
      Stub files are useful if you are using an IDE (e.g. PhpStorm) that provides code assistance - the stub files let the IDE know what fields exist in each template and what data type each field returns. Depending on your IDE's features you get benefits such as code completion for field names as you type, type inference, inspection, documentation, etc.
      Installation
      Install the Auto Template Stubs module.
      Configuration
      You can change the class name prefix setting in the module config if you like. It's good to use a class name prefix because it reduces the chance that the class name will clash with an existing class name.
      The directory path used to store the stub files is configurable.
      There is a checkbox to manually trigger the regeneration of all stub files if needed.
      Usage
      Add a line near the top of each of your template files to tell your IDE what stub class name to associate with the $page variable within the template file. For example, with the default class name prefix you would add the following line at the top of the home.php template file:
      /** @var tpl_home $page */ Now enjoy code completion, etc, in your IDE.

      Adding data types for non-core Fieldtype modules
      The module includes the data types returned by all the core Fieldtype modules. If you want to add data types returned by one or more non-core Fieldtype modules then you can hook the AutoTemplateStubs::getReturnTypes() method. For example, in /site/ready.php:
      // Add data types for some non-core Fieldtype modules $wire->addHookAfter('AutoTemplateStubs::getReturnTypes', function(HookEvent $event) { $extra_types = [ 'FieldtypeDecimal' => 'string', 'FieldtypeLeafletMapMarker' => 'LeafletMapMarker', 'FieldtypeRepeaterMatrix' => 'RepeaterMatrixPageArray', 'FieldtypeTable' => 'TableRows', ]; $event->return = $event->return + $extra_types; }); Credits
      Inspired by and much credit to the Template Stubs module by mindplay.dk.
       
      https://github.com/Toutouwai/AutoTemplateStubs
      https://modules.processwire.com/modules/auto-template-stubs/
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.60
      Composer: rockett/jumplinks
      ⚠️ NOTICE: 1.5.60 is an important security patch-release for an XSS vulnerability discovered by @phlp. It's HIGHLY RECOMMENDED that all Jumplinks users update to the latest version as soon as possible.
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! 🙂
    • By Robin S
      Add Image URLs
      Allows images/files to be added to Image/File fields by pasting URLs.

      Usage
      Install the Add Image URLs module.
      A "Paste URLs" button will be added to all image and file fields. Use the button to show a textarea where URLs may be pasted, one per line. Images/files are added when the page is saved.
       
      https://github.com/Toutouwai/AddImageUrls
      https://modules.processwire.com/modules/add-image-urls/
×
×
  • Create New...