Jump to content

Confluent Design

  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About Confluent Design

  • Rank
  1. I have noticed that all of the logs in site/assets/logs are being automatically cleared, and I'm wondering if there is a setting within ProcessWire that takes care of this? I'd like to prevent this behavior. I've looked around the forums, but have not yet found anything about this issue. If anyone has any insight, I appreciate your help!
  2. Hi @ryan and all, Pre-purchase question on ProDrafts. This is the best place I could find to ask it. Let me know if there is a more appropriate place. Is there functionality for scheduling drafts of existing pages to be published in the future built in to ProDrafts? Or a documented how to in the ProDrafts paid support forum? Thanks, David
  3. Thank you @teppo! This was just the feedback I was looking for. On both counts, that I was on the right track, and that I might be losing some fancy functionality by going away from elasticsearch. Appreciate all of that. I'm going to give your module a try as a replacement!
  4. Any thoughts on this? @teppo? If I am doing something wrong in terms of the form or placement of my inquiry, please let me know that as well. I want to do things the right way. Thanks for your time, and apologies for any inconvenience. Best Regards, David
  5. Hello @teppo and all, I currently run the same processwire site on multiple servers with a shared database and shared asset resources. This has been working fine for years, but we've been using elasticsearch, which has required feeding index updates from our multiple servers to a single elasticsearch index. It looks to me like this module will eliminate the need for that additional complexity, and here's where I would like someone to correct me if I'm wrong or point out any flaws in my understanding. I see that the page indexes are updated with a hook upon page save, and the index info will be stored in the database as a page field. It seems to me that this should work fine in a multi-server environment sharing a single database, as the page save events will only happen once from the server the page is saved on, and the index will be updated for all servers sharing that database. Short of something extreme like simultaneously running a complete re-index from multiple servers (which probably would still work out ok...), does anyone see any problem with this approach, or see considerations in this scenario that I may be missing? Your input is appreciated. Best Regards, David
  • Create New...