Jump to content

Recurme – Processwire Recurring Dates Field & Custom Calendar Module.


Recommended Posts

4 hours ago, itsberni said:


i noticed some problem with rendereing german umlauts.

My definition:

'monthFormat'     => '%B %Y',

Is there something to keep in mind?



Bildschirmfoto 2018-12-14 um 12.06.22.png


Do you have your html set to UTF-8? 

<meta charset="UTF-8">

Hope this helps. 

Link to comment
Share on other sites


@joshuag please take a look.
The special characters are represented correctly in the remaining website.

Could you please take a closer look at this issue?!

Many Thanks!


@joshuag Found a dirty solution for this issue.
Changes in the MarkupRecurme.module ( utf8_encode ) will do the trick.


Lines 543 + 1248


'month'			=> utf8_encode($this->wire('datetime')->formatDate($event->start_date, trim($options['renderEvent']['monthFormat']))),


$monthTitle = utf8_encode($this->wire('datetime')->formatDate($startTime, trim($options['monthFormat'])));

Perhaps you will find a cleaner suloution and add it into your next update.

Happy new Year to all you guys!!


Link to comment
Share on other sites

  • 1 month later...
On 3/14/2018 at 9:10 PM, DonPachi said:

Fresh install of PW 3.0.62, I'm getting this error when installing the latest version of Recurme:

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 262144 bytes) in /var/sites/t/X/public_html/wire/core/Modules.php on line 3921

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 262144 bytes) in Unknown on line 0

Never seen this before and I'm a bit stumped... Any ideas?

Edit: Increased memory limit with ini_set on the module to see where this goes and got a 30s execution time error. Can't figure this one out, there must be a loop somewhere as increasing that came back to a 800MB memory limit!

Edit 2: Solved! I'll send you an e-mail with details.

Hi @DonPachi,

I'm having the same issue, how did you solve it? 

Link to comment
Share on other sites

  • 3 weeks later...

@joshuag Thanks for all of you hard work on this module. I agree w/ @chcs re: "The admin field, screens, and some of the tools you provide are very slick... but the object for custom output is harder to figure out, or simply not that useful depending on the nature of recurrence (or not). ".

I am making it work with all the additions you have made (from the feature requests posted in the forum) and from many of the great posts from the wonderful PW community.

I am having an issue w/ a second implementation of your module. When rendering the calendar, the ajax does not work when clicking to the prev/next month. The calendar simply disappears. I have verified the location of the recurme-ajax.php file in my templates/ directory etc...

"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"

I've compared my recurme-ajax.php file w/ InputfieldRecur/templates/recurme-ajax.php. They are identical.

When clicking prev/next in the calendar, $calendar in the recurme-ajax.php file is empty. Line 40     $out .= $calendar->render($options);

I have exhausted any thoughts why this may be happening.

Is there anything you our anyone else can think of as to what would cause this?




Link to comment
Share on other sites

In case anyone else has this issue with the ajax calendar disappearing when clicking on the prev/next month.

My issue was the recurme-ajax template was prepending _init.php and appending _main.php files.

Disabling the prepend and append under the template files tab was the fix.

@adrian Thanks for digging in and discovering the cause.



  • Like 1
Link to comment
Share on other sites

  • 1 month later...
  • 2 weeks later...


I have some difficulties with customize the lay-out.  I have a custom calendar and want to put the month with navigation on top of it (in place of 05 = month may).   Is there an API call $recurme->month()->next  ?  Is there an api call $recurme->month()->prev ?

Screen Shot 05-18-19 at 08.20 PM.PNG

Link to comment
Share on other sites

  • 5 months later...
  • 1 month later...

We purchased the module in August and have run into some issues now that we've had a chance to implement it.

Code > $event = $recurme->event($page);
Result > Notice: Undefined property: stdClass::$timeEndUnix in .../site/modules/Recurme/MarkupRecurme.module on line 856 

Robin raised this issue earlier in this thread and, if a solution was found, it wasn't shared or implemented in the downloads.

Update 12/13/2019


$timeEndUnix = $data->timeEndUnix;


  $timeEndUnix = $data->timeEndUnix;
} else {
  $timeEndUnix = false;

Removes the error, but I suspect that I was trying to use the method in the wrong way/context given a misunderstanding of the documentation. I'm having to use the JSON decode method (example: $times = json_decode($page->event_times)), with a lot of template-level processing, to populate my event detail pages. Is that the best way?

[/End Update]


itsberni and others have asked about handling time variance for a recurring event, which strikes me as a rather essential feature. Has anyone found a solution or workaround for this? I suspect that adding a second recurme field to an event page will lead to a lot of pain elsewhere (but I could be wrong), and cloning an event's page to support another time would require me to implement measures to connect the clones (doable, but sloppy from both an admin and user standpoint).


A couple of items which may help others:

  1. The "Repeat Never" switch does nothing for me out of the box (other than hiding the rest of the options) as every single-day event I entered was automatically being assigned a default value of End Never and repeating 2,800 days. I had to hack both the rrule-gui.js and InputfieldRecurme.module files to default to After 1 Time(s) to rectify this issue.
  2. Commenting out -- results.find('.inner').scrollTop(0); -- in rrule-gui.js, around line 1153, will save a lot frustration for anyone needing to exclude multiple dates from a results table.
Link to comment
Share on other sites

  • 1 month later...


just a question ... Is this module now free or ...? As I can see you can download a "free" copy of Recurme from the site, but it's not working because you still need a license key. If it is free to try is it possible to get a license somehow? 

If it is no longer supported not sure if I would pay for it. 

Thank you


Link to comment
Share on other sites

4 hours ago, Roych said:


just a question ... Is this module now free or ...? As I can see you can download a "free" copy of Recurme from the site, but it's not working because you still need a license key. If it is free to try is it possible to get a license somehow? 

If it is no longer supported not sure if I would pay for it. 

Thank you


In MarkupRecueme.module file. 
Line 1082
Change the first “false” to “true”:
private function i(){$this->v = false;} // change to true;
Link to comment
Share on other sites

  • 2 weeks later...
On 2/21/2018 at 10:46 AM, adrian said:

1) It looks like the UiKit theme issues are fixed

Hi @adrian, I'm having this same issue with the display but I'm using the most recent version of Recurme and PW. Do you remember how this was resolved or can you point me in the right direction? I know this plugin isn't supported anymore but it looks like it does exactly what I need so I'm hoping I can make it work. Does anyone have plans to take over management of this module? Any help is most appreciated, thank you!! 🙏



Link to comment
Share on other sites

5 hours ago, Ben Sayers said:

Hi @adrian, I'm having this same issue with the display but I'm using the most recent version of Recurme and PW.

You're dragging up some traumatic memories here 🙂 I'll PM my version of the module that mostly works, but still has some limitations because the module uses the non-timezone enabled version of moment.js and it's using a really old version so when you go to update to a recent version and use the timezone enabled version, lots of other things break, etc, etc.

Link to comment
Share on other sites

27 minutes ago, adrian said:

You're dragging up some traumatic memories here 🙂 

Yeah, I'm getting that impression after tinkering with it for the weekend. Should I even bother with it, do you think it's a viable solution or more trouble than it's worth? I did receive the PM, thanks!

Link to comment
Share on other sites

15 hours ago, Ben Sayers said:

Yeah, I'm getting that impression after tinkering with it for the weekend. Should I even bother with it, do you think it's a viable solution or more trouble than it's worth? I did receive the PM, thanks!

Ben - I think the inputfield interface of this module is really nice so it does still have potential. This is obviously just my opinion, but I think the way the data is stored and searched needs an overhaul - it's got some real performance and flexibility problems. I think if someone was to update the way it stores the data and to properly incorporate the timezone enabled version of momentjs, it could be a really great tool, but as it is, I do think it's more trouble than it's worth.

Link to comment
Share on other sites

  • 1 month later...

Speaking of strange behaviours... despite not having changed a single thing with our Recurme installation since early January, it's now returning EXCLUDED DATES with both $recurme->find and $recurme->renderCalendar for any month that's shorter than 31 days. I have no idea why. The Recurme debug report shows no anomalies between months. This issue would have been very noticed for us had it been present in February, and the events that are broken now are the ones we used to build and validate the system. Check your sites. It may have triggered following the leap year date and was difficult to notice since March was not affected.

My event pages (luckily) bypass the Recurme module to work directly with the page-related JSON-entry in the database, so no issues there. Others may not be so lucky.

Link to comment
Share on other sites

We have also noticed issues w/ Recurme dates displaying incorrectly. Similar idea as Arcturus, nothing had changed in months. What we found was the issue was triggered on a month that contained 31 days. From my re-collection it might have also affected the month by bumping it by one month. I'll post the fix that worked for us a bit later this evening.

  • Like 3
Link to comment
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 MarkE
      This fieldtype and inputfield bundle was built for storing measurement values within a field, rendering them in a variety of formats and converting them to other units or otherwise modifying them via the API.
      The API consists of a number of predefined functions, some of which include...
      render() for rendering the measurement object, valueAs() for converting the value to another unit value, convertTo() for converting the whole measurement object to different units, and add() and subtract() for for modifying the stored value by the value (converted as required) in another measurement. In the admin the inputfield includes a checkbox (which can be optionally disabled) for converting values on page save. For an example if a value was typed in as centimeters, the unit was changed to metres, and the page saved with this checkbox selected, said value would be automatically converted so that e.g. 170 cm becomes 1.7 m.

      A simple length field using Fieldtype Measurement and Inputfield Measurement.
      Combination units (e.g. feet and inches) are also supported.
      Please note that this module is 'proof of concept' at the moment - there are limited units available and quite a lot of code tidying to do. More units will be added shortly.
      See the GitHub at https://github.com/MetaTunes/FieldtypeMeasurement for full details and updates.
    • By tcnet
      File Manager for ProcessWire is a module to manager files and folders from the CMS backend. It supports creating, deleting, renaming, packing, unpacking, uploading, downloading and editing of files and folders. The integrated code editor ACE supports highlighting of all common programming languages.

      This module is probably the most powerful module. You might destroy your processwire installation if you don't exactly know what you doing. Be careful and use it at your own risk!
      ACE code editor
      This module uses ACE code editor available from: https://github.com/ajaxorg/ace

      This module uses the JavaScript dragscroll available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability to drag the table horizontally with the mouse pointer.
      PHP File Manager
      This module uses a modified version of PHP File Manager available from: https://github.com/alexantr/filemanager
    • By tcnet
      This module implements the website live chat service from tawk.to. Actually the module doesn't have to do much. It just need to inserted a few lines of JavaScript just before the closing body tag </body> on each side. However, the module offers additional options to display the widget only on certain pages.
      Create an account
      Visit https://www.tawk.to and create an account. It's free! At some point you will reach a page where you can copy the required JavaScript-code.

      Open the module settings and paste the JavaScript-code into the field as shown below. Click "Submit" and that's all.

      Open the module settings
      The settings for this module are located int the menu Modules=>Configure=>LiveChatTawkTo.

    • By tcnet
      Session Viewer is a module for ProcessWire to list session files and display session data. This module is helpful to display the session data of a specific session or to kick out a logged in user by simply delete his session file. After installation the module is available in the Setup menu.

      The following conditions must be met for the module to work properly:
      Session files
      Session data must be stored in session files, which is the default way in ProcessWire. Sessions stored in the database are not supported by this module. The path to the directory where the session files are stored must be declared in the ProcessWire configuration which is by default: site/assets/sessions.
      Serialize handler
      In order to transform session data easier back to a PHP array, the session data is stored serialized. PHP offers a way to declare a custom serialize handler. This module supports only the default serialize handlers: php, php_binary and php_serialize. WDDX was dropped in PHP 7.4.0 and is therefore not supported by this module as well as any other custom serialize handler. Which serialize handler is actually used you can find out in the module configuration which is available under Modules=>Configure=>SessionViewer.

      Session data
      The session data can be displayed in two different ways. PHP's default output for arrays print_r() or by default for this module nice_r() offered on github: https://github.com/uuf6429/nice_r. There is a setting in the module configuration if someone prefers print_r(). Apart from the better handling and overview of the folded session data the output of nice_r() looks indeed nicer.

      ProcessWire module directory
    • By Robin S
      Repeater Easy Sort
      Adds a compact "easy-sort" mode to Repeater and Repeater Matrix, making those fields easier to sort when there are a large number of items.
      The module also enhances Repeater Matrix by allowing a colour to be set for each matrix type. This colour is used in the item headers and in the "add new" links, to help visually distinguish different matrix types in the inputfield.
      A Repeater field

      A Repeater Matrix field with custom header colours

      Easy-sort mode
      Each Repeater/Matrix item gets an double-arrow icon in the item header. Click this icon to enter easy-sort mode.
      While in easy-sort mode:
      The items will reduce in width so that more items can be shown on the screen at once. The minimum width is configurable in the field settings. Any items that were in an open state are collapsed, but when you exit easy-sort mode the previously open items will be reopened. You can drag an item left/right/up/down to sort it within the items. The item that you clicked the icon for is shown with a black background. This makes it easier to find the item you want to move in easy-sort mode. You can click an item header to open the item. An "Exit easy-sort mode" button appears at the bottom of the inputfield. Configuration
      In the field settings for Repeater and Repeater Matrix fields you can define a minimum width in pixels for items in easy-sort mode. While in easy-sort mode the items will be sized to neatly fill the available width on any screen size but will never be narrower than the width you set here.
      In the field settings for Repeater Matrix you can define a custom header colour for each matrix type using an HTML "color" type input. The default colour for this type of input is black, so when black is selected in the input it means that no custom colour will be applied to the header.
      The easy-sort mode is only possible on Repeater/Matrix fields that do not use the "item depth" option.
  • Create New...