Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

GhostRider's Achievements

Jr. Member

Jr. Member (3/6)



  1. Thanks to @MarkE for the recommendation to this forum thread and to @OLSA for the post. Very close to what I was trying to solve. One thing to add to @OLSA's example, is the subfield template may need to be set to the template you require.
  2. Hi Jonatan, We have also experienced this issue unfortunately. Thought we had a solution, but having reviewed it once more, sadly it is not the case. I'll post back if we figure something out.
  3. Has anyone using the Recurme module had any issues after updating to the latest PW core 3.0.165? Our tweaked version is no longer returning results. Just curious if the core update has affected an out of the box version of Recurme. All of the $recurme-> methods are returning null.
  4. @teppo Thanks for adding FieldsetPage support. It's working as expected!
  5. Hi @teppo. Thanks for addressing this. I'll give it a test drive later today or tomorrow on a current project.
  6. Amazing! @teppo Really appreciate all your effort.
  7. @teppo Perhaps my comment from February got lost in the mix. This search function is such a great addition to the ProcessWire ecosystem. I am wondering if you would consider adding FieldsetPage fields to the list of searchable fields? I use FieldsetPage fields often to create components. From there it is a mater of adding that one field to a template or a repeater to add the component. Thank you for your time.
  8. Below is what we had changed in the MarkupRecurme.module file. As @adrian posted, our version has had a number of tweaks. So perhaps have a closer look before implementing these changes. Hopefully this helps. Line 271 $m = date('m', strtotime($date[3])); To $m = date('m', strtotime("1st " . $date[3])); AND Line 864 $m = date('m', strtotime($date[3])); $y = $date[4]; To $m = date('m', strtotime("1st " . $exclude[3])); $y = $exclude[4];
  9. We have also noticed issues w/ Recurme dates displaying incorrectly. Similar idea as Arcturus, nothing had changed in months. What we found was the issue was triggered on a month that contained 31 days. From my re-collection it might have also affected the month by bumping it by one month. I'll post the fix that worked for us a bit later this evening.
  10. @teppo Fantastic addition! Searching repeater and page reference fields are working great. Would it be possible to add support for FieldsetPage fields?
  11. Hi Bernhard, Being able to enter and display Events (or the like) is such a valuable tool for many websites. I am thrilled you have started this project. I cannot over emphasize @adrian's comment on all fronts. A few things that are very helpful in displaying recurring events is the ability to only display the event once. Ie. if you have a recurring event from March 10-15th. You may not want the event to display 6 times if you are viewing the Event list page on March 10th. The recurme module does do quite a few things right, unfortunately it wasn't quite there. Two features standout: 1. The user interface to create recurring dates which also has the ability to remove select dates. Ie. A range from March 10-15, but you can then exclude any date in the range. This avoids a second (essentially duplicate) event needing to be created. 2. Displaying recurring events can be quite a challenge, especially when there is a long list of dates. Recurme used a calendar display for this, which could really display a lot of recurring dates in a small space. Rather than displaying a long list dates in text format. I will send you a pm with some live examples we have built to date and how we display events. Perhaps this will help highlight some of the challenges you may be facing or how people may use your module. This will be such a great addition to the Processwire ecosystem!
  12. My apologies, this was user error on my part. I was using the full server paths, rather than the site path. /home/accountname/public_html/site/vendor/ rather than /site/vendor/ @Autofahrn thanks for your post.
  13. Hi Flydev, I have been thinking about one feature request if you are taking any. I don't want to add more work, but perhaps something to think about. On the Duplicator settings page, I have used the "Files and folders excluded from" checkbox (very handy) and also the "Custom excluded files and paths'. I'm wondering if there is any way of excluding any custom file directories, rather than file extensions? Here are a few examples: 1. After adding the AWS library via composer, Duplicator is backing up the Composer directory called vendor (at the same level as wire, files etc...). This file has become quite large over time. 2. We also at times create directories at the same level for legacy files when building a new client sites, where the legacy files need to still be accessible. Our latest client had a very large media folder nearly 7GB. ie /media/ 3. When using ProCache, Proche adds two folders in the assets directory called ProCache-###### and pwpc. The ProCache-#### file is a collection of all the static versions of the pages on the site, which can also become quite large depending on the site. With most of these directories, we do have a good idea what file extensions are being used and can exclude them in the 'Custom excluded files and paths' section. However, with the Composer vendor directory, there are so many file extensions being used with a very deep nested group of folders. This makes for a very large list of possibilities to exclude. With a few of our sites, our backups went from ~90MB to over 700MB. It would be great to hear your thoughts on hiding directories/folders when you have time. Below is a list of some of the file paths we struggle with. /vendor or any custom directory at this level /site/assets/ProCache-### /site/assets/pwpw/* Thanks
  14. Screenshot added of another site giving the same "Invalid Timestamp" under the created column. The "Invalid Timestamp" message is only for the AWS backups. It's not really an issue as the database name has a timestamp. Everything else is working great.
  • Create New...