Jump to content
joshuag

Recurme – Processwire Recurring Dates Field & Custom Calendar Module.

Recommended Posts

5 minutes ago, adrian said:

Thanks @joshuag - just curious - did you also take a look at the rrule code icon idea I brought up?

I did not modify it. I didn't even think of it, but it's a good idea. I'll do a quick update on that. Thanks!

  • Like 1

Share this post


Link to post
Share on other sites

Thanks for the update @joshuag, great to see Recurme continue being updated. 

I haven't had opportunity to update my current installs yet, but have a new project Recurme would be ideal for.

  • Thanks 1

Share this post


Link to post
Share on other sites
On 19.12.2017 at 11:33 AM, snck said:

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!

Hey @joshuag, thanks for the update! The toggle fix did not solve my problem (quoted above) because you still do not store the value of the checkbox/toggle. Could you please implement something like an $event->allDay property with a simple binary value? 

Thank you in advance!

Share this post


Link to post
Share on other sites
On March 12, 2018 at 10:49 AM, snck said:

Hey @joshuag, thanks for the update! The toggle fix did not solve my problem (quoted above) because you still do not store the value of the checkbox/toggle. Could you please implement something like an $event->allDay property with a simple binary value? 

Thank you in advance!

$event->allDay should be giving you the value of $allDay in the event object true/false. This is also implemented in the json stored in the field. 

Share this post


Link to post
Share on other sites

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.

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites
On March 14, 2018 at 2: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.

I would love to know what happened. Let me know, if I need to, I will issue an update right away. Thank you!

  • Like 1

Share this post


Link to post
Share on other sites

Hey @joshuag - not sure if I am just missing it, but is there a method for adding new dates via the API? I have a LOT of events to import. Or, do I have to manually build up the JSON eg:

{"startDate":1518778800,"endDate":1518940740,"allDay":false,"timeEnd":"12:00 pm","dates":["W7/16/Fri/Feb/2018","W7/17/Sat/Feb/2018"],"excluded":[],"active":true,"showResults":true,"rrule":"WKST=MO;FREQ=DAILY;DTSTART=20180216T030000Z;INTERVAL=1;UNTIL=20180217T235900Z"}

and populate with $page->event->date = $jsonStr;

Thanks!

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, adrian said:

Hey @joshuag - not sure if I am just missing it, but is there a method for adding new dates via the API? I have a LOT of events to import. Or, do I have to manually build up the JSON eg:


{"startDate":1518778800,"endDate":1518940740,"allDay":false,"timeEnd":"12:00 pm","dates":["W7/16/Fri/Feb/2018","W7/17/Sat/Feb/2018"],"excluded":[],"active":true,"showResults":true,"rrule":"WKST=MO;FREQ=DAILY;DTSTART=20180216T030000Z;INTERVAL=1;UNTIL=20180217T235900Z"}

and populate with $page->event->date = $jsonStr;

Thanks!

I don’t have a method to add dates via the api, but that is a good idea.

If you do add dates by populating the json manually, I could see some complications arising depending on how you have chosen the repeat pattern in the Recurme Field. Because the dates are generated based on the rrule via JavaScript. 

I will give this some thought and see how we could make this a no-brainer. 

Thanks for the great idea. 

  • Like 1

Share this post


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

I will give this some thought and see how we could make this a no-brainer. 

Thanks for looking into this - right now I am going to have to either build up the JSON, or wait for you to implement an API method. I think the API method is essential because I am sure others will also need to import dates from existing sites. 

I'd appreciate knowing whether you might have time to implement this relatively quickly, or if you think it might take some time to get to - not pressuring, just needing to know if I need to take the JSON approach to meet my deadlines. Thanks for your time!

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, adrian said:

Thanks for looking into this - right now I am going to have to either build up the JSON, or wait for you to implement an API method. I think the API method is essential because I am sure others will also need to import dates from existing sites. 

I'd appreciate knowing whether you might have time to implement this relatively quickly, or if you think it might take some time to get to - not pressuring, just needing to know if I need to take the JSON approach to meet my deadlines. Thanks for your time!

Sending you a pm. 

  • Like 1

Share this post


Link to post
Share on other sites
On 13.3.2018 at 7:42 PM, joshuag said:

$event->allDay should be giving you the value of $allDay in the event object true/false. This is also implemented in the json stored in the field. 

Thanks, it worked for events I received through $recurme->find.

I could not find a way to access the allDay value from an event page.

$allDay = $recurme->event($page->id)->allDay;

Could you please point me in the right direction on how to access the allDay property for one single event?

Thank you!

Share this post


Link to post
Share on other sites

Hey @joshuag - I am quite confused about calling dates via the API.

From the docs it looks like I should do:

$recurme->event($page)->start_date;

but what if I have more than one recurme field on the page?

I am tempted to parse it myself like this:

json_decode($page->event_dates)->startDate;

because this way I can get the start date from my selected "event_dates" field.

However I am sure I am missing something in how this is meant to be used :)

Any tips please?

Share this post


Link to post
Share on other sites

@joshuag - I am also confused about the output of endDate - it's always a day after the specified end date - is this for some reason intentional? It seems confusing to me.

Note that importing using the script you PM'd me is also problematic with this "bug" - if you provide an end date, the end date shown in the field edit dialog is one day before the end, but when you output it via the API it returns the end date I specified on import, so it's quite confusing to the editor.

 

Share this post


Link to post
Share on other sites

Even more confusion. Take these examples - why does the value of enddate vary depending on how I get it?

image.png.74ef1e29bb21d3cac1c7e859afce37f3.png

Share this post


Link to post
Share on other sites

Ok, more details:If I import a date, the json initially looks like this:

{"startDate":1520956800,"endDate":1522440000,"allDay":false,"timeEnd":"02:00 pm","dates":["W11/13/Tue/Mar/2018","W11/14/Wed/Mar/2018","W11/15/Thu/Mar/2018","W11/16/Fri/Mar/2018","W11/17/Sat/Mar/2018","W11/18/Sun/Mar/2018","W12/19/Mon/Mar/2018","W12/20/Tue/Mar/2018","W12/21/Wed/Mar/2018","W12/22/Thu/Mar/2018","W12/23/Fri/Mar/2018","W12/24/Sat/Mar/2018","W12/25/Sun/Mar/2018","W13/26/Mon/Mar/2018","W13/27/Tue/Mar/2018","W13/28/Wed/Mar/2018","W13/29/Thu/Mar/2018","W13/30/Fri/Mar/2018"],"excluded":[],"active":true,"showResults":false,"rrule":"WKST=MO;FREQ=DAILY;DTSTART=20180313T100000Z;INTERVAL=1;UNTIL=20180330T140000Z"}

Then if I open the page in the admin and save the page (without changing anything), it then looks like this:

{"startDate":1520960400,"endDate":1522479540,"allDay":false,"timeEnd":"02:00 pm","dates":["W11/13/Tue/Mar/2018","W11/14/Wed/Mar/2018","W11/15/Thu/Mar/2018","W11/16/Fri/Mar/2018","W11/17/Sat/Mar/2018","W11/18/Sun/Mar/2018","W12/19/Mon/Mar/2018","W12/20/Tue/Mar/2018","W12/21/Wed/Mar/2018","W12/22/Thu/Mar/2018","W12/23/Fri/Mar/2018","W12/24/Sat/Mar/2018","W12/25/Sun/Mar/2018","W13/26/Mon/Mar/2018","W13/27/Tue/Mar/2018","W13/28/Wed/Mar/2018","W13/29/Thu/Mar/2018"],"excluded":[],"active":true,"showResults":false,"rrule":"WKST=MO;FREQ=DAILY;DTSTART=20180313T100000Z;INTERVAL=1;UNTIL=20180330T140000Z"}

Notice the change in the startDate and endDate stamps as well as the fact that "W13/30/Fri/Mar/2018" is removed after saving.

Help :)

Share this post


Link to post
Share on other sites

Sorry, me again :)

When I create a new event through the admin and it's a non-recurring event, it doesn't store the enddate:

{"startDate":1522971420,"endDate":false,"allDay":false,"timeEnd":"08:00 pm"

But you have no API method for getting the end time directly in your API calls (at least not that I can see) - what am I missing?

Share this post


Link to post
Share on other sites
18 hours ago, adrian said:

Hey @joshuag - I am quite confused about calling dates via the API.

From the docs it looks like I should do:


$recurme->event($page)->start_date;

but what if I have more than one recurme field on the page?

I am tempted to parse it myself like this:


json_decode($page->event_dates)->startDate;

because this way I can get the start date from my selected "event_dates" field.

However I am sure I am missing something in how this is meant to be used :)

Any tips please?

I am not sure that multiple recurme fields in a single page would work as expected. Parsing the Json would work well. 

Share this post


Link to post
Share on other sites
14 hours ago, adrian said:

Ok, more details:If I import a date, the json initially looks like this:


{"startDate":1520956800,"endDate":1522440000,"allDay":false,"timeEnd":"02:00 pm","dates":["W11/13/Tue/Mar/2018","W11/14/Wed/Mar/2018","W11/15/Thu/Mar/2018","W11/16/Fri/Mar/2018","W11/17/Sat/Mar/2018","W11/18/Sun/Mar/2018","W12/19/Mon/Mar/2018","W12/20/Tue/Mar/2018","W12/21/Wed/Mar/2018","W12/22/Thu/Mar/2018","W12/23/Fri/Mar/2018","W12/24/Sat/Mar/2018","W12/25/Sun/Mar/2018","W13/26/Mon/Mar/2018","W13/27/Tue/Mar/2018","W13/28/Wed/Mar/2018","W13/29/Thu/Mar/2018","W13/30/Fri/Mar/2018"],"excluded":[],"active":true,"showResults":false,"rrule":"WKST=MO;FREQ=DAILY;DTSTART=20180313T100000Z;INTERVAL=1;UNTIL=20180330T140000Z"}

Then if I open the page in the admin and save the page (without changing anything), it then looks like this:


{"startDate":1520960400,"endDate":1522479540,"allDay":false,"timeEnd":"02:00 pm","dates":["W11/13/Tue/Mar/2018","W11/14/Wed/Mar/2018","W11/15/Thu/Mar/2018","W11/16/Fri/Mar/2018","W11/17/Sat/Mar/2018","W11/18/Sun/Mar/2018","W12/19/Mon/Mar/2018","W12/20/Tue/Mar/2018","W12/21/Wed/Mar/2018","W12/22/Thu/Mar/2018","W12/23/Fri/Mar/2018","W12/24/Sat/Mar/2018","W12/25/Sun/Mar/2018","W13/26/Mon/Mar/2018","W13/27/Tue/Mar/2018","W13/28/Wed/Mar/2018","W13/29/Thu/Mar/2018"],"excluded":[],"active":true,"showResults":false,"rrule":"WKST=MO;FREQ=DAILY;DTSTART=20180313T100000Z;INTERVAL=1;UNTIL=20180330T140000Z"}

Notice the change in the startDate and endDate stamps as well as the fact that "W13/30/Fri/Mar/2018" is removed after saving.

Help :)

endDate will always be startDate -> till END OF THE CURRENT DAY from the interface if you have a timeEnd (11:59 from your example). endDate always represents the UNIX TIMESTAMP of the day/hour/min in seconds of the END TIME of the event. If you want a date for the events to stop if it is repeating, then it refers the the UNTIL value part of the RRULE UNTIL value. The until value tells recurme to expand the repeating dates up to the UNTIL date. I can see how this is confusing. I might rename these variables now that you have brought it to my attention. 
 

Share this post


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

I am not sure that multiple recurme fields in a single page would work as expected. Parsing the Json would work well. 

I doubt it's a common scenario, but I have never seen a PW fieldtype work this way - normally you just call $page->fieldname so it's weird to get used to parsing an entire page to $recurme.

  • Like 1

Share this post


Link to post
Share on other sites

Looking at this all again now. I am working with manually created events (so there aren't any complications with API import) and I am still confused.

This is what I set up:

image.thumb.png.193df0834b9bf4c0fcf0eab290681280.png

 

$recurme->renderEvent($page, array('dateFormat' => 'M d, Y @ g:i a'));

results in: Error: Trying to get property of non-object on line: 682 of MarkupRecurme.module

If I do:

image.png.48d9ed3b2ca9ede323d68ad38480a5be.png

you can see that the "time" is off by an hour - probably a timezone issue, but how can I manually output something like:

March 13th - March 30th, 2018
10:00 am - 2:00 pm

This sort of output I am sure is quite common.

The problem is that end_date: 1522562399 is 2018-03-31 11:59 but the event only goes until the 30th. So how do I get the 30th - do I have to parse UNTIL from rrule, or can do take end_date and subtract one day - what is the reliable way to get the actual end date?

Sorry if I am being stupid - I can't believe I am the only person to come across these issues, but I don't think I am missing anything - I think the module just needs more properties with things like actual start date, start time, end date and end time so we can easily output custom formats.

Let me know if you want to spend a little time on a live chat/call about this.

Thanks!

 

  • Like 1

Share this post


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

$recurme->renderEvent($page, array('dateFormat' => 'M d, Y @ g:i a'));

results in: Error: Trying to get property of non-object on line: 682 of MarkupRecurme.module

Sorry, I understand my mistake on this. It needs:

image.png.654a491235782a235c9e172d49044b72.png

Although I still don't know why the dateFormat is not being respected in the output.

Share this post


Link to post
Share on other sites

Hey @joshuag - firstly I wanted to send some kudos your way - I feel like I've been complaining lots in my last few posts :) I have been playing around with RenderList, RenderEvent, RenderCalendar etc, and the backend Calendar views and they really are awesome - thanks for all the hard work!

I do have a request though - I have been looking at the rrule in the json and wondering if you'd consider adding a helper to parse the rule into plain english. I'd love to be able to output this: 

WKST=MO;FREQ=MONTHLY;DTSTART=20180402T100000Z;INTERVAL=1;BYDAY=TU;BYSETPOS=2;UNTIL=20180428T235900Z

as: 

Every second Tuesday from 10 am to 2 pm from April 2nd, 2018 till April 28th, 2018

Do you have any thoughts on this? Is there already an inbuilt method that I missed that would help with this?

Thanks again!

 

 

Share this post


Link to post
Share on other sites

Hi @joshuag - sorry to bump this, but wondering if you've had any thoughts on any of my questions above?

Share this post


Link to post
Share on other sites
On March 28, 2018 at 7:25 AM, snck said:

Thanks, it worked for events I received through $recurme->find.

I could not find a way to access the allDay value from an event page.


$allDay = $recurme->event($page->id)->allDay;

Could you please point me in the right direction on how to access the allDay property for one single event?

Thank you!

Try this updated file: 
I will add this to my next release.

Thank you!

MarkupRecurme.module

  • Thanks 1

Share this post


Link to post
Share on other sites
On April 6, 2018 at 5:54 PM, adrian said:

Sorry, I understand my mistake on this. It needs:

image.png.654a491235782a235c9e172d49044b72.png

Although I still don't know why the dateFormat is not being respected in the output.

change the timeFormat option instead,

or

change the xBefore template to use {date} instead of {time}.
 

'xBefore' => '<li class="rm-list-event {original.name}"><span class="rm-event-date">{time}</span> ',

 

On April 6, 2018 at 5:13 PM, adrian said:

Looking at this all again now. I am working with manually created events (so there aren't any complications with API import) and I am still confused.

This is what I set up:

image.thumb.png.193df0834b9bf4c0fcf0eab290681280.png

 


$recurme->renderEvent($page, array('dateFormat' => 'M d, Y @ g:i a'));

results in: Error: Trying to get property of non-object on line: 682 of MarkupRecurme.module

If I do:

image.png.48d9ed3b2ca9ede323d68ad38480a5be.png

you can see that the "time" is off by an hour - probably a timezone issue, but how can I manually output something like:

March 13th - March 30th, 2018
10:00 am - 2:00 pm

This sort of output I am sure is quite common.

The problem is that end_date: 1522562399 is 2018-03-31 11:59 but the event only goes until the 30th. So how do I get the 30th - do I have to parse UNTIL from rrule, or can do take end_date and subtract one day - what is the reliable way to get the actual end date?

Sorry if I am being stupid - I can't believe I am the only person to come across these issues, but I don't think I am missing anything - I think the module just needs more properties with things like actual start date, start time, end date and end time so we can easily output custom formats.

Let me know if you want to spend a little time on a live chat/call about this.

Thanks!

 

yeah, this looks like a timezone issue. I am digging into it. thanks for bringing it up. Subtracting one day won't work or be consistent. 

  • Thanks 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      A community member raised a question and I thought a new sanitizer method for the purpose would be useful, hence...
      Sanitizer Transliterate
      Adds a transliterate method to $sanitizer that performs character replacements as defined in the module config. The default character replacements are based on the defaults from InputfieldPageName, but with uppercase characters included too.
      Usage
      Install the Sanitizer Transliterate module.
      Customise the character replacements in the module config as needed.
      Use the sanitizer on strings like so:
      $transliterated_string = $sanitizer->transliterate($string);
       
      https://github.com/Toutouwai/SanitizerTransliterate
      https://modules.processwire.com/modules/sanitizer-transliterate/
       
    • 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 to 2.10, add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://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.


    • By thomasaull
      I created a little helper module to trigger a CI pipeline when your website has been changed. It's quite simple and works like this: As soon as you save a page the module sets a Boolean via a pages save after hook. Once a day via LazyCron the module checks if the Boolean is set and sends a POST Request to a configurable Webhook URL.
      Some ideas to extend this:
      make request type configurable (GET, POST) make the module trigger at a specified time (probably only possible with a server cronjob) trigger manually Anything else? If there's interest, I might put in some more functionality. Let me know what you're interested in. Until then, maybe it is useful for a couple of people 🙂
      Github Repo: https://github.com/thomasaull/CiTrigger
    • By Robin S
      I created this module a while ago and never got around to publicising it, but it has been outed in the latest PW Weekly so here goes the support thread...
      Unique Image Variations
      Ensures that all ImageSizer options and focus settings affect image variation filenames.

      Background
      When using methods that produce image variations such as Pageimage::size(), ProcessWire includes some of the ImageSizer settings (height, width, cropping location, etc) in the variation filename. This is useful so that if you change these settings in your size() call a new variation is generated and you see this variation on the front-end.
      However, ProcessWire does not include several of the other ImageSizer settings in the variation filename:
      upscaling cropping, when set to false or a blank string interlace sharpening quality hidpi quality focus (whether any saved focus area for an image should affect cropping) focus data (the top/left/zoom data for the focus area) This means that if you change any of these settings, either in $config->imageSizerOptions or in an $options array passed to a method like size(), and you already have variations at the requested size/crop, then ProcessWire will not create new variations and will continue to serve the old variations. In other words you won't see the effect of your changed ImageSizer options on the front-end until you delete the old variations.
      Features
      The Unique Image Variations module ensures that any changes to ImageSizer options and any changes to the focus area made in Page Edit are reflected in the variation filename, so new variations will always be generated and displayed on the front-end.
      Installation
      Install the Unique Image Variations module.
      In the module config, set the ImageSizer options that you want to include in image variation filenames.
      Warnings
      Installing the module (and keeping one or more of the options selected in the module config) will cause all existing image variations to be regenerated the next time they are requested. If you have an existing website with a large number of images you may not want the performance impact of that. The module is perhaps best suited to new sites where image variations have not yet been generated.
      Similarly, if you change the module config settings on an existing site then all image variations will be regenerated the next time they are requested.
      If you think you might want to change an ImageSizer option in the future (I'm thinking here primarily of options such as interlace that are typically set in $config->imageSizerOptions) and would not want that change to cause existing image variations to be regenerated then best to not include that option in the module config after you first install the module.
       
      https://github.com/Toutouwai/UniqueImageVariations
      https://modules.processwire.com/modules/unique-image-variations/
    • By Sebi
      I've created a small module which lets you define a timestamp after which a page should be accessible. In addition you can define a timestamp when the release should end and the page should not be accessable any more.
      ProcessWire-Module: http://modules.processwire.com/modules/page-access-releasetime/
      Github: https://github.com/Sebiworld/PageAccessReleasetime
      Usage
      PageAccessReleasetime can be installed like every other module in ProcessWire. Check the following guide for detailed information: How-To Install or Uninstall Modules
      After that, you will find checkboxes for activating the releasetime-fields at the settings-tab of each page. You don't need to add the fields to your templates manually.
      Check e.g. the checkbox "Activate Releasetime from?" and fill in a date in the future. The page will not be accessable for your users until the given date is reached.
      If you have $config->pagefileSecure = true, the module will protect files of unreleased pages as well.
      How it works
      This module hooks into Page::viewable to prevent users to access unreleased pages:
      public function hookPageViewable($event) { $page = $event->object; $viewable = $event->return; if($viewable){ // If the page would be viewable, additionally check Releasetime and User-Permission $viewable = $this->canUserSee($page); } $event->return = $viewable; } To prevent access to the files of unreleased pages, we hook into Page::isPublic and ProcessPageView::sendFile.
      public function hookPageIsPublic($e) { $page = $e->object; if($e->return && $this->isReleaseTimeSet($page)) { $e->return = false; } } The site/assets/files/ directory of pages, which isPublic() returns false, will get a '-' as prefix. This indicates ProcessWire (with activated $config->pagefileSecure) to check the file's permissions via PHP before delivering it to the client.
      The check wether a not-public file should be accessable happens in ProcessPageView::sendFile. We throw an 404 Exception if the current user must not see the file.
      public function hookProcessPageViewSendFile($e) { $page = $e->arguments[0]; if(!$this->canUserSee($page)) { throw new Wire404Exception('File not found'); } } Additionally we hook into ProcessPageEdit::buildForm to add the PageAccessReleasetime fields to each page and move them to the settings tab.
      Limitations
      In the current version, releasetime-protected pages will appear in wire('pages')->find() queries. If you want to display a list of pages, where pages could be releasetime-protected, you should double-check with $page->viewable() wether the page can be accessed. $page->viewable() returns false, if the page is not released yet.
      If you have an idea how unreleased pages can be filtered out of ProcessWire selector queries, feel free to write an issue, comment or make a pull request!
×
×
  • Create New...