Jump to content
joshuag

Recurme – Processwire Recurring Dates Field & Custom Calendar Module.

Recommended Posts

Hi,

i noticed some problem with rendereing german umlauts.

My definition:

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

Is there something to keep in mind?

Thanks

 

Bildschirmfoto 2018-12-14 um 12.06.22.png

Share this post


Link to post
Share on other sites
4 hours ago, itsberni said:

Hi,

i noticed some problem with rendereing german umlauts.

My definition:

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

Is there something to keep in mind?

Thanks

 

Bildschirmfoto 2018-12-14 um 12.06.22.png

Hi, 

Do you have your html set to UTF-8? 

<meta charset="UTF-8">

Hope this helps. 

Share this post


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

Hi, 

Do you have your html set to UTF-8? 

<meta charset="UTF-8">

Hope this helps. 

Hi,

my html is already set to UTF-8.

This effect only concerns the recurme calender rendering

Share this post


Link to post
Share on other sites

Bildschirmfoto-2018-12-22-um-07_18_47.jpg.397c69b7849e9b6540922bbd4f377a2f.jpg

@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!

UPDATE

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

1078445681_Bildschirmfoto2018-12-31um11_25_45.png.752c51414d2c6e37ad6afa0b1bd3b822.png

Lines 543 + 1248

543

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

1248

$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!!
 

 

Share this post


Link to post
Share on other sites
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? 

Share this post


Link to post
Share on other sites

@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?

 

Thanks

 

Share this post


Link to post
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

Share this post


Link to post
Share on other sites

Please note that on line 695 of MarkupRecurme.module, the string 'All day' has not been available for translation:

// if allDay
if($event->allDay) { $event->time = 'All Day'; }
  • Like 1

Share this post


Link to post
Share on other sites

Hi

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

Share this post


Link to post
Share on other sites

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

Replacing

$timeEndUnix = $data->timeEndUnix;

With

if(isset($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.

Share this post


Link to post
Share on other sites

Hello,

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

R

Share this post


Link to post
Share on other sites
4 hours ago, Roych said:

Hello,

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

R

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

Share this post


Link to post
Share on other sites
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!! 🙏

 

calendar.png

Share this post


Link to post
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.

Share this post


Link to post
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!

Share this post


Link to post
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.

Share this post


Link to post
Share on other sites
24 minutes ago, adrian said:

@Ben Sayers - maybe direct your attention and efforts to help @bernhard with his new module: 

 

Nice, thank you for the heads up @adrian! I'm following that thread now.

Share this post


Link to post
Share on other sites

Hey guys,

I've discovered some pretty strange behavior. A date I set from 4/6/20 - 4/19/20 appears in the calendar in May.

can anyone help me with that?

thanks a lot!

 

Bildschirmfoto 2020-03-31 um 14.58.12.png

Bildschirmfoto 2020-03-31 um 14.57.54.png

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
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

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 teppo
      Needed a really simple solution to embed audio files within page content and couldn't find a module for that, so here we go. Textformatter Audio Embed works a bit like Textformatter Video Embed, converting this:
      <p>https://www.domain.tld/path/to/file.mp3</p> Into this:
      <audio controls class="TextformatterAudioEmbed"> <source src="https://www.domain.tld/path/to/file.mp3" type="audio/mpeg"> </audio> The audio element has pretty good browser support, so quite often this should be enough to get things rolling 🙂
      GitHub repository: https://github.com/teppokoivula/TextformatterAudioEmbed Modules directory: https://modules.processwire.com/modules/textformatter-audio-embed/
    • By Richard Jedlička
      Tense    
      Tense (Test ENvironment Setup & Execution) is a command-line tool to easily run tests agains multiple versions of ProcessWire CMF.
      Are you building a module, or a template and you need to make sure it works in all supported ProcessWire versions? Then Tense is exactly what you need. Write the tests in any testing framework, tell Tense which ProcessWire versions you are interested in and it will do the rest for you.

      See example or see usage in a real project.
      How to use?
      1. Install it: 
      composer global require uiii/tense 2. Create tense.yml config:
      tense init 3. Run it:
      tense run  
      For detailed instructions see Github page: https://github.com/uiii/tense
       
      This is made possible thanks to the great wireshell tool by @justb3a, @marcus and others.
       
      What do you think about it? Do you find it useful? Do you have some idea? Did you find some bug? Tell me you opinion. Write it here or in the issue tracker.
    • By Chris Bennett
      Hi all, I am going round and round in circles and would greatly appreciate if anyone can point me in the right direction.
      I am sure I am doing something dumb, or missing something I should know, but don't. Story of my life 😉

      Playing round with a module and my basic problem is I want to upload an image and also use InputfieldMarkup and other Inputfields.
      Going back and forth between trying an api generated page defining Fieldgroup, Template, Fields, Page and the InputfieldWrapper method.

      InputfieldWrapper method works great for all the markup stuff, but I just can't wrap my head around what I need to do to save the image to the database.
      Can generate a Field for it (thanks to the api investigations) but not sure what I need to do to link the Inputfield to that. Tried a lot of stuff from various threads, of varying dates without luck.
      Undoubtedly not helped by me not knowing enough.

      Defining Fieldgroup etc through the api seems nice and clean and works great for the images but I can't wrap my head around how/if I can add/append/hook the InputfieldWrapper/InputfieldMarkup stuff I'd like to include on that template as well. Not even sure if it should be where it is on ___install with the Fieldtype stuff or later on . Not getting Tracy errors, just nothing seems to happen.
      If anyone has any ideas or can point me in the right direction, that would be great because at the moment I am stumbling round in the dark.
       
      public function ___install() { parent::___install(); $page = $this->pages->get('name='.self::PAGE_NAME); if (!$page->id) { // Create fieldgroup, template, fields and page // Create new fieldgroup $fmFieldgroup = new Fieldgroup(); $fmFieldgroup->name = MODULE_NAME.'-fieldgroup'; $fmFieldgroup->add($this->fields->get('title')); // needed title field $fmFieldgroup->save(); // Create new template using the fieldgroup $fmTemplate = new Template(); $fmTemplate->name = MODULE_NAME; $fmTemplate->fieldgroup = $fmFieldgroup; $fmTemplate->noSettings = 1; $fmTemplate->noChildren = 1; $fmTemplate->allowNewPages = 0; $fmTemplate->tabContent = MODULE_NAME; $fmTemplate->noChangeTemplate = 1; $fmTemplate->setIcon(ICON); $fmTemplate->save(); // Favicon source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFavicon'; $fmField->label = 'Favicon'; $fmField->focusMode = 'off'; $fmField->gridMode = 'grid'; $fmField->extensions = 'svg png'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Favicon Silhouette source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFaviconSilhouette'; $fmField->label = 'SVG Silhouette'; $fmField->notes = 'When creating a silhouette/mask svg version for Safari Pinned Tabs and Windows Tiles, we recommend setting your viewbox for 0 0 16 16, as this is what Apple requires. In many cases, the easiest way to do this in something like illustrator is a sacrificial rectangle with no fill, and no stroke at 16 x 16. This forces the desired viewbox and can then be discarded easily using something as simple as notepad. Easy is good, especially when you get the result you want without a lot of hassle.'; $fmField->focusMode = 'off'; $fmField->extensions = 'svg'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Create: Open Settings Tab $tabOpener = new Field(); $tabOpener->type = new FieldtypeFieldsetTabOpen(); $tabOpener->name = 'fmTab1'; $tabOpener->label = "Favicon Settings"; $tabOpener->collapsed = Inputfield::collapsedNever; $tabOpener->addTag(MODULE_NAME); $tabOpener->save(); // Create: Close Settings Tab $tabCloser = new Field(); $tabCloser->type = new FieldtypeFieldsetClose; $tabCloser->name = 'fmTab1' . FieldtypeFieldsetTabOpen::fieldsetCloseIdentifier; $tabCloser->label = "Close open tab"; $tabCloser->addTag(MODULE_NAME); $tabCloser->save(); // Create: Opens wrapper for Favicon Folder Name $filesOpener = new Field(); $filesOpener->type = new FieldtypeFieldsetOpen(); $filesOpener->name = 'fmOpenFolderName'; $filesOpener->label = 'Wrap Folder Name'; $filesOpener->class = 'inline'; $filesOpener->collapsed = Inputfield::collapsedNever; $filesOpener->addTag(MODULE_NAME); $filesOpener->save(); // Create: Close wrapper for Favicon Folder Name $filesCloser = new Field(); $filesCloser->type = new FieldtypeFieldsetClose(); $filesCloser->name = 'fmOpenFolderName' . FieldtypeFieldsetOpen::fieldsetCloseIdentifier; $filesCloser->label = "Close open fieldset"; $filesCloser->addTag(MODULE_NAME); $filesCloser->save(); // Create Favicon Folder Name $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeText"); $fmField->name = 'folderName'; $fmField->label = 'Favicon Folder:'; $fmField->description = $this->config->urls->files; $fmField->placeholder = 'Destination Folder for your generated favicons, webmanifest and browserconfig'; $fmField->columnWidth = 100; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon('folder'); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($tabOpener); $fmFieldgroup->add($filesOpener); $fmFieldgroup->add($fmField); $fmFieldgroup->add($filesCloser); $fmFieldgroup->add($tabCloser); $fmFieldgroup->save(); /////////////////////////////////////////////////////////////// // Experimental Markup Tests $wrapperFaviconMagic = new InputfieldWrapper(); $wrapperFaviconMagic->attr('id','faviconMagicWrapper'); $wrapperFaviconMagic->attr('title',$this->_('Favicon Magic')); // field show info what $field = $this->modules->get('InputfieldMarkup'); $field->name = 'use'; $field->label = __('How do I use it?'); $field->collapsed = Inputfield::collapsedNever; $field->icon('info'); $field->attr('value', 'Does this even begin to vaguely work?'); $field->columnWidth = 50; $wrapperFaviconMagic->add($field); $fmTemplate->fields->add($wrapperFaviconMagic); $fmTemplate->fields->save(); ///////////////////////////////////////////////////////////// // Create page $page = $this->wire( new Page() ); $page->template = MODULE_NAME; $page->parent = $this->wire('pages')->get('/'); $page->addStatus(Page::statusHidden); $page->title = 'Favicons'; $page->name = self::PAGE_NAME; $page->process = $this; $page->save(); } }  
    • By Sebi
      Since it's featured in ProcessWire Weekly #310, now is the time to make it official:
      Here is Twack!
      I really like the following introduction from ProcessWire Weekly, so I hope it is ok if I use it here, too. Look at the project's README for more details!
      Twack is a new — or rather newish — third party module for ProcessWire that provides support for reusable components in an Angular-inspired way. Twack is implemented as an installable module, and a collection of helper and base classes. Key concepts introduced by this module are:
      Components, which have separate views and controllers. Views are simple PHP files that handle the output for the component, whereas controllers extend the TwackComponent base class and provide additional data handling capabilities. Services, which are singletons that provide a shared service where components can request data. The README for Twack uses a NewsService, which returns data related to news items, as an example of a service. Twack components are designed for reusability and encapsulating a set of features for easy maintainability, can handle hierarchical or recursive use (child components), and are simple to integrate with an existing site — even when said site wasn't originally developed with Twack.
      A very basic Twack component view could look something like this:
      <?php namespace ProcessWire; ?> <h1>Hello World!</h1> And here's how you could render it via the API:
      <?php namespace Processwire; $twack = $modules->get('Twack'); $hello = $twack->getNewComponent('HelloWorld'); ?> <html> <head> <title>Hello World</title> </head> <body> <?= $hello->render() ?> </body> </html> Now, just to add a bit more context, here's a simple component controller:
      <?php namespace ProcessWire; class HelloWorld extends TwackComponent { public function __construct($args) { parent::__construct($args); $this->title = 'Hello World!'; if(isset($args['title'])) { $this->title = $args['title']; } } } As you can see, there's not a whole lot new stuff to learn here if you'd like to give Twack a try in one of your projects. The Twack README provides a really informative and easy to follow introduction to all the key concepts (as well as some additional examples) so be sure to check that out before getting started. 
      Twack is in development for several years and I use it for every new project I build. Also integrated is an easy to handle workflow to make outputs as JSON, so it can be used to build responses for a REST-api as well. I will work that out in one section in the readme as well. 
      If you want to see the module in an actual project, I have published the code of www.musical-fabrik.de in a repository. It runs completely with Twack and has an app-endpoint with ajax-output as well.
      I really look forward to hear, what you think of Twack🥳!
      Features Installation Usage Quickstart: Creating a component Naming conventions & component variants Component Parameters directory page parameters viewname Asset handling Services Named components Global components Ajax-Output Configuration Versioning License Changelog
    • By Robin S
      Page Reference Default Value
      Most ProcessWire core inputfield types that can be used with a Page Reference field support a "Default value" setting. This module extends support for default values to the following core inputfield types:
      Page List Select Page List Select Multiple Page Autocomplete (single and multiple) Seeing as these inputfield types only support the selection of pages a Page List Select / Page List Select Multiple is used for defining the default value instead of the Text / Textarea field used by the core for other inputfield types. This makes defining a default value a bit more user-friendly.
      Note that as per the core "Default value" setting, the Page Reference field must be set to "required" in order for the default value to be used.
      Screenshot

       
      https://github.com/Toutouwai/PageReferenceDefaultValue
      https://modules.processwire.com/modules/page-reference-default-value/
×
×
  • Create New...