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

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