Jump to content

cpx3

Members
  • Posts

    181
  • Joined

  • Last visited

Recent Profile Visitors

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

cpx3's Achievements

Sr. Member

Sr. Member (5/6)

51

Reputation

  1. Safari, Firefox, Chrome... But it is only one particular site that makes problems, all others are fine. I tried to switch the Ui theme but with no success
  2. First all the best for 2026, may it be a Processwire year! I have quite a strange problem: from one second to the other the admin shows only the mobile navigation on the desktop but not the desktop version. It happens in all browsers, I cleared the cache, the cookies, tried all versions of different UIs but nothing seems to help. Any idea what could be wrong? Thanks, Bernhard
  3. The problem with all paid modules kongondo used to sell is that there is no documentation. My (paid) copy of MediaManager never worked properly (the same is true for Padloper 2) and there is no support at all, so I really try to avoid anything that comes from him...
  4. Gemini replied the following after examining things a little bit: The Logic of Date Overlaps The reason your current selector fails is that it only checks if the existing booking completely "swallows" your new request. To catch any overlap (partial or full), you need to use the following logic: A booking overlaps if: The End of the existing booking is after the Start of the new request. AND the Start of the existing booking is before the End of the new request. The Correct ProcessWire Selector Assuming $id->datum is your new Start and $id->datumbis is your new End: // Define your requested range $newStart = $id->datum; $newEnd = $id->datumbis; // Find any page that overlaps // Logic: Existing End > Requested Start AND Existing Start < Requested End $overlap = $pages->find("template=booking, datumbis>$newStart, datum<$newEnd"); if($overlap->count > 0) { // Room is occupied echo "This room is already booked by " . $overlap->count . " existing reservation(s)."; } else { // Room is available echo "The room is available for this period!"; } Why this solves your problems: Existing Booking: 13.08.2025 to 04.12.2025 Problem 1 (01.07.2025 – 03.12.2025): * Is existing end (04.12) > new start (01.07)? Yes. Is existing start (13.08) < new end (03.12)? Yes. Result: Overlap detected. Problem 2 (01.10.2025 – 01.01.2026): Is existing end (04.12) > new start (01.10)? Yes. Is existing start (13.08) < new end (01.01)? Yes. Result: Overlap detected. Pro-Tip: Changeover Days If your system allows a guest to check in on the same day someone else checks out (e.g., Check-out at 11:00, Check-in at 15:00), use strictly "greater than" (>) and "less than" (<). If you use >= or <=, the system will flag the changeover day as a conflict. Using strict operators allows the dates to touch without overlapping. Data Types Ensure that $newStart and $newEnd are in the same format as stored in the database (usually Unix Timestamps or YYYY-MM-DD). If you are using ProcessWire's native Date fields, comparing them as Timestamps is the most reliable method.
  5. No, neither nor. It only happens when I use them inside a combo and only when with TinyMCE.
  6. To be clear: I already bought some useless modules from this author who never provided documentation... That's why I complain.
  7. I tried to figure out how PwCommerce could work and was happy I found those demo pages on GitHub. Only that not a single one works, even if I renamed all Padloper with PwCommerce. E.g. $cart = $pwcommerce->cart; bd($cart); $cart = '' and producing an error. Sorry, I know that this is free software but at least for me it is the same useless as was Mediamanager for which I paid without ever being able to use it thanks to the lack of documentation. And yes, I get the idea that for 100 EUR per hour you might help me set it up working.
  8. Just to get you right: That was the documentation for a product your sold for more than 200 EUR??? Just asking because I abandoned the use of one of the modules I bought from you because of the useless documentation...
  9. Sorry, I was on Holidays with no access to a computer. No, it contains only text and formatting. No other characters.
  10. I still have an extremely annoying problem with TinyMCE Textureas, especially when used in combination with the commercial Combo field type. When working on a site with five combos Processwire randomly deletes the content of the field and saves a blank version, so that all the work is gone. This is totally unpredictable as it has nothing to do with the field I edit, the problem seems to appear randomly. I only see that all the text is deleted (and of course cannot be restored, especially if it was written days ago). Any idea what I a doing wrong? Thanks in advance (for saving me hours of work), Bernhard
  11. Thanks for that! I will love to do that but only next week 🙂
  12. As already stated at the original thread: There seems to be a problem with asmSelects (pages) as I can only select the first two entries. Beside that I love the theme!
  13. First, thanks to everybody for the support! We are talking about normal pages, maximum ten fields on them, no repeaters, just texteareas with TinyMCE. As I am one of the clients I know what I am doing: Just saving the page to realise that all the content, I wrote a month ago, is suddenly gone. So it is not directly after saving but appears suddenly...
  14. There seems to be problem with setting text formatters in ProFields combo. The asmSelect does not appear any more and the textformatter does neither appear nor work. Switching back to the old theme helped. EDIT: Seems that he problem occurs ONLY in the PAID ProField combo, the rest works.
  15. They are normal textareas, put directly on the template.
×
×
  • Create New...