Jump to content
joshuag

Recurme – Processwire Recurring Dates Field & Custom Calendar Module.

Recommended Posts

13 hours ago, Juergen said:

Works also with UiKit calendar and Bootstrap calendar if you are using a framwork. If you are using UiKit calendar you can make fe a template which outputs all the calendar dates in a json array. Then you can load this template (or lets say the event dates) via ajax into the UiKit calendar template engine. Its very easy.

@Juergen Sorry if I miss something, but where do you find a calendar component at Uikit (https://getuikit.com/docs/introduction)?

Share this post


Link to post
Share on other sites

Sorry, @totoff,

my fault. It mean the Fullcalendar. I use it with Uikit markup (badges,..) so I always call it "UiKit calendar". This was a mistake. Anyway, you can use it with recurme. Here you can find the Bootstrap calendar. Both are available on Jsdelivr CDN. So no need to include the files locally.

Best regards

  • Like 1

Share this post


Link to post
Share on other sites

I'm having an issue when trying to uninstall the Recurme module (v1.0.1) - after checking "Uninstall" and submitting I get a fatal error from PHP timeout (60 seconds).

The issue occurs when trying to uninstall from any of the Recurme sub-modules.

 

Share this post


Link to post
Share on other sites
5 hours ago, Juergen said:

Sorry, @totoff,

my fault. It mean the Fullcalendar. I use it with Uikit markup (badges,..) so I always call it "UiKit calendar". This was a mistake. Anyway, you can use it with recurme. Here you can find the Bootstrap calendar. Both are available on Jsdelivr CDN. So no need to include the files locally.

Best regards

would you mind share some code of your uikit implementation? sounds very interesting. if so, please pm me. thanks.

Share this post


Link to post
Share on other sites

@Robin S Ok, I will do some test and see if I can reproduce this error and fix it. Thanks for bringing it to my attention. 

Share this post


Link to post
Share on other sites

Sorry @totoff, but I have no example here at the moment, but Fullcalendar provides some render functions. I have used them to manipulate the output via Jquery. Fe adding Uikit classes to the buttons (uk-button) and so on. This was the way I have done some manipulations to the calendar. Take a look at this functions and use standard Jquery code to add classes, markup and so on. The calendar itself doesnt need to be manipulated, but as I have written above I have used UiKit markup at the buttons and I have used Uikit badges for the events in the calendar and Uikit tooltips after hovering a link . That was it.

  • Like 1

Share this post


Link to post
Share on other sites

Is it not possible to use recurme within an Repeater? In Repeater Matrix it works, so it is not a big problem, but for my purpose a repeater would suffice...

 

BTW great module and support, Joshua!

Share this post


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

Is it not possible to use recurme within an Repeater? In Repeater Matrix it works, so it is not a big problem, but for my purpose a repeater would suffice...

 

BTW great module and support, Joshua!

I have been working on regular repeater support, but it's not quite there. The current problem is that the event object is taking its data from the parent page, in the case of a repeater, it's the repeater page (not what we want). So I have to do a bit more work detecting if it's in a repeater and use getForPage() to populate the event object. A couple other little details. Getting close, but still not there. 

It's coming though! 

  • Like 2

Share this post


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

I have been working on regular repeater support, but it's not quite there. The current problem is that the event object is taking its data from the parent page, in the case of a repeater, it's the repeater page (not what we want). So I have to do a bit more work detecting if it's in a repeater and use getForPage() to populate the event object. A couple other little details. Getting close, but still not there. 

It's coming though! 

Sounds great, thanks for the quick answer!

Share this post


Link to post
Share on other sites

I am having a complete failure to comprehend the way this field is structured, so while I can use the provided examples to render a list or calendar, from the individual pages I can't manage to access the individual date(s) in the field.

I sent this question to the help email address on Tuesday but haven't received an answer and I'd like to wrap up what seems like it should be a simple thing.

While working on the template for an event page, how do I specify the RecurMe dates from within that template using $page->xxx?

For instance I would normally echo a dateTime field like:

$datefield = $page->datefield;
$pubdate = strftime('j M Y', $datefield);
echo $pubdate; // outputs nothing

But since my recurme field, $page->eventsort, is an array(?), I figured I’d have to crack open the array first like so:

 

$eventsort = $page->eventsort;
foreach ($eventsort as $event) { //it loops through one $event because there is only a non-repeating day listed.
   $pubdate = $event->startDate;
   echo strftime('j M Y', $pubdate); // outputs nothing
}

I used startDate because when I once got the array to output, that was what was listed there. But this returns null. Same with start_date/date/any $event page fields listed in the faqs

I also tried :

$event = $page;
$newsdate = $recurme->event($event); //not sure this is any different than attempting to call $page->xxx?
$nd = $newsdate->start_date;
echo strftime('j M Y', $nd); // outputs "j M Y" on the page.

I've looked in the module files, and in the ready.php hook on page 1 of this thread to see how to take apart the field data, but nothing I've tried has worked.

So rather than continue chasing my tail, I thought I might as you for help with this as well. Thanks!

 

 

Share this post


Link to post
Share on other sites

Hi creativeJay,

Sorry about the slow response. I was away from email yesterday. 

You are correct, It was returning NOTHING if you didn't toggle active. I have fixed it in the attached file. 

Thank you for bringing this to my attention!

Please download the fixed file here:
MarkupRecurme.module

 

Share this post


Link to post
Share on other sites
On 23/06/2017 at 0:12 AM, Robin S said:

I'm having an issue when trying to uninstall the Recurme module (v1.0.1) - after checking "Uninstall" and submitting I get a fatal error from PHP timeout (60 seconds).

The issue occurs when trying to uninstall from any of the Recurme sub-modules.

Hi @joshuag - any update on this issue? Are you able to reproduce the issue at your end?

Share this post


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

Hi @joshuag - any update on this issue? Are you able to reproduce the issue at your end?

Hi Robin :) thanks for checking in. 

Yes, I have fixed the problem and it will be part of the updated release in the next couple days. 

Thanks,

  • Like 1

Share this post


Link to post
Share on other sites

Another reason we need to expand the ProcessWire store @ryan . All these modules spread across different sites - this one is even priced the same way as the official modules.

Share this post


Link to post
Share on other sites

Is it possible to run a 'sort' selector on $recurme->find()?

When I attempt to sort by a particular field, only a single result is output. I can reverse the sort and it will output the opposite result so the sort works, but I get only one result.

Share this post


Link to post
Share on other sites
On 7/21/2017 at 11:03 AM, joshuag said:

Hi Robin :) thanks for checking in. 

Yes, I have fixed the problem and it will be part of the updated release in the next couple days. 

Thanks,

Has this updated version been released yet?  Thanks

Share this post


Link to post
Share on other sites
3 hours ago, DonPachi said:

Is it possible to run a 'sort' selector on $recurme->find()?

When I attempt to sort by a particular field, only a single result is output. I can reverse the sort and it will output the opposite result so the sort works, but I get only one result.

The find method needs to have a startDate and endDate to find results, then a selector. The results will always be sorted by date. Any other sort option will be ignored. If you use ->find() with out those dates, it will only return the recurme events for today  

$recurme->find($dateFrom, $dateTo, $selector)

Share this post


Link to post
Share on other sites
Just now, joshuag said:

The find method needs to have a startDate and endDate to find results, then a selector. The results will always be sorted by date. Any other sort option will be ignored.


$recurme->find($dateFrom, $dateTo, $selector)

Thanks, makes complete sense. The issue I had was with a particular date outputting as AM when it was actually saved as PM so appearing before all other results.

The module is fantastic, but I'm having a consistent issue where if I enter and save a recurme field in a page it displays fine, but when I go back to edit another field on the page and save, it will begin outputting the time as AM when it was selected as PM. Going back in and altering the date fixes this until I alter another field again.

Share this post


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

Has this updated version been released yet?  Thanks

 

3 hours ago, DonPachi said:

Thanks, makes complete sense. The issue I had was with a particular date outputting as AM when it was actually saved as PM so appearing before all other results.

The module is fantastic, but I'm having a consistent issue where if I enter and save a recurme field in a page it displays fine, but when I go back to edit another field on the page and save, it will begin outputting the time as AM when it was selected as PM. Going back in and altering the date fixes this until I alter another field again.

I have just sent out a general update via email that resolves the problems mentioned. Thanks everyone :)

  • Like 3

Share this post


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

I have just sent out a general update via email that resolves the problems mentioned.

@joshuag, you say in the email: 

Quote

I have not updated the version number or released the changelog as this is in response to a couple messages on the processwire forum

I think it would be good if you do bump the version number each time you make a release even if it is for bug fixes. Otherwise it isn't clear from the PW modules listing whether that installation has been updated to the latest version, so it's harder to keep track if you have multiple sites running Recurme.

Also, it will be easier for you in terms of support if you can ask what the installed version number is and know from that what release of Recurme the user has installed.

  • Like 2

Share this post


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

I have just sent out a general update via email that resolves the problems mentioned.

Hi @joshuag, unfortunately this update does not resolve the problem I am having with uninstallation. When I do the following steps... 

  1. Remove the existing module files
  2. Add the updated module files
  3. Do a modules "Refresh"
  4. Clear compiled files

...I still get the PHP timeout when I try and uninstall, regardless of which sub-module I try and uninstall from. Sometimes timeouts like this are caused by a circular reference in the code. I'm wondering about the fact that each sub-module installs and uninstalls all the others. That seems non-standard to me: normally where there are multiple sub-modules there is one "main" module file that installs/uninstalls the others. The other modules only require the main module but do not install/uninstall them. See FieldtypeRepeater for example. Could there be some circularity where FieldtypeRecurme tries to uninstall ProcessRecurme, which tries to uninstall FieldtypeRecurme, which tries to... and so on?

Share this post


Link to post
Share on other sites
On 8/6/2017 at 9:09 PM, Robin S said:

Hi @joshuag, unfortunately this update does not resolve the problem I am having with uninstallation. When I do the following steps... 

  1. Remove the existing module files
  2. Add the updated module files
  3. Do a modules "Refresh"
  4. Clear compiled files

...I still get the PHP timeout when I try and uninstall, regardless of which sub-module I try and uninstall from. Sometimes timeouts like this are caused by a circular reference in the code. I'm wondering about the fact that each sub-module installs and uninstalls all the others. That seems non-standard to me: normally where there are multiple sub-modules there is one "main" module file that installs/uninstalls the others. The other modules only require the main module but do not install/uninstall them. See FieldtypeRepeater for example. Could there be some circularity where FieldtypeRecurme tries to uninstall ProcessRecurme, which tries to uninstall FieldtypeRecurme, which tries to... and so on?

Has there been any update to this last posting?  Thanks

Share this post


Link to post
Share on other sites

Hi guys, 

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? 

Share this post


Link to post
Share on other sites

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

Edited by SoccerGuy3
Removed error message. Figured it out 5 minutes after posting.

Share this post


Link to post
Share on other sites

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).

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 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-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 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 Multi currency support Custom order and cart fields 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 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 Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
×
×
  • Create New...