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

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 MoritzLost
      This is a new module that provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Beta release
      Note that I consider this a Beta release. Since the module is relatively aggressive in deleting some caches, I would advise you to install in on a test environment before using it on a live site.
      Let me know if you're getting any errors, have trouble using the module or if you have suggestions for improvement!
      In particular, can someone let me know if this module causes any problems with the ProCache module? I don't own or use it, so I can't check. As far as I can tell, ProCache uses a folder inside the cache directory to cache static pages, so my module should be able to clear the ProCache site cache as well, I'd appreciate it if someone can test that for me.
      Future plans
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory

    • By joshua
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="optin" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="optin" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The type has to be "optin" to get recognized by PrivacyWire, the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button> This module is still in development, but we already use it on several production websites.
      You find it here: https://github.com/blaueQuelle/privacywire/tree/master
      Download: https://github.com/blaueQuelle/privacywire/archive/master.zip
      I would love to hear your feedback 🙂
      Edit: Updated URLs to master tree of git repo
       
    • By David Karich
      Admin Page Tree Multiple Sorting
      ClassName: ProcessPageListMultipleSorting
      Extend the ordinary sort of children of a template in the admin page tree with multiple properties. For each template, you can define your own rule. Write each template (template-name) in a row, followed by a colon and then the additional field names for sorting.
      Example: All children of the template "blog" to be sorted in descending order according to the date of creation, then descending by modification date, and then by title. Type:
      blog: -created, -modified, title  Installation
      Copy the files for this module to /site/modules/ProcessPageListMultipleSorting/ In admin: Modules > Check for new modules. Install Module "Admin Page Tree Multible Sorting". Alternative in ProcessWire 2.4+
      Login to ProcessWire backend and go to Modules Click tab "New" and enter Module Class Name: "ProcessPageListMultipleSorting" Click "Download and Install"   Compatibility   I have currently tested the module only under PW 2.6+, but think that it works on older versions too. Maybe someone can give a feedback.     Download   PW-Repo: http://modules.processwire.com/modules/process-page-list-multiple-sorting/ GitHub: https://github.com/FlipZoomMedia/Processwire-ProcessPageListMultipleSorting     I hope someone can use the module. Have fun and best regards, David
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "https://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


×
×
  • Create New...