bernhard

Hey @FireWire thx for testing RockCalendar and thx for your feedback and questions! Thx! I'll have to test and then push it to the repo. Just have two launches this week 😅🤞 Looks like a bug! I'll have to investigate next week! Correct. I disagree on this one. I don't think it's possible to get what you are describing without losing many of the features/flexibility that RockCalendar offers (like moving a single event out of the row, having custom fields for each recurring event, etc). BUT: I understand that this is an important need. My solution/idea was to just delete all recurring instances and then recreate them. That was before we had support for custom fields on events, though. So this might be a culprit. I also thought about maybe supporting a "move all", so when one recurring instance was moved it would ask "also move all following instances?" and then it would get the time difference of the move and apply that to all following instances. But when I did tests in that direction I even found bugs in google calendar, which tells a lot... Well... They could always pay someone (you/me) to get it done. But even then this might mean that this might have a side effect somewhere else, for example what about an event that has been pulled out of the series? Would that have to be modified or not? Maybe there would need to be a GUI for that, which asks the user what to do in such a case. But, well, that would be a lot of work, which means a lot of Dollars/Euros. So don't get me wrong. I'm not against it, I just don't have a good solution for it so far and I can't think of one. If you can please let me know and we'll see how we can make it possible! But at the same time I want to mention that Recurme had huge issues with how it stored it's data (as far as I can remember from what I read in the thread). I really don't want to make that module bad - just want to say that it might be a good idea that my module works differently and I'll be very careful about changing that 🙂

It would be great to have an API for keyboard shortcuts that is used across the admin and that can be used by module developers in the same way, something like ProcessWire.on('keydown.cmd+s', ...); ProcessWire.on('keydown.esc', ...); Even greater with support for javascript hooks. And maybe some kind of attribute click magic: <div> 1.2.3.4 <a href pw-click-copy='parent' title='Click to copy IP address to clipboard' uk-tooltip > <i class='fa fa-clone'></i> </a> </div> Early stage ideas but these would have been helpful for many of my modules for sure. Edit: Maybe instead of callbacks we could have attribute notation for keyboard shortcuts as well? <button type="submit" pw-keydown="cmd+s"> Save </button>

Hey @FireWire great thank you! I see some blocks that seem to be regular fontawesome 4 icon buttons, like the one with the map or with the calendar. You are aware that you can use any fontawesome icon for the buttons via the "icon" property of the block? Or are your blocks different?

Great 🙂 Thx for letting me know and I hope you enjoy the journey from now on!

See https://processwire.com/blog/posts/pw-3.0.179/ I think you only need to install the Less module then it should work. Modifying files in /wire is not a good idea as you will lose your changes on the next core update!

Sounds strange. Lacking any better ideas/explanations why this could happen, the first thing that I'd try is to install one of the default/blank profiles without any other modules and see if the behaviour is the same. If it is, then you likely have a problem with your server setup. If it works, the problem is probably in one of your modules or templates 🙂 Or maybe before doing that check from different computers or also different networks to narrow down the issue.

@neophron sent me his project and I fixed it for him. Maybe this is helpful for others as well: If you get an error message like this, please read the instructions and also check the trace of the request. It will tell you WHERE the call happened that caused the error: Aw shucks… Error: Exception: This feature has been removed with version 5 - please see upgrade guide at baumrock.com/rf-upgrade5 (in site/modules/RockFrontend/RockFrontend.module.php line 2794) #0 site/templates/_init.php (9): RockFrontend->styles() ... In this case it shows us that we have a call to RockFrontend's style() method on line 9 of _init.php! So I basically removed that and it worked.

That's just regular HTML/CSS stuff. Inspect the backend page where your textarea is. Get the name of the textarea, then add something like this in admin.less: textarea[name^="your_textarea_field_name"] { // for debugging to make it obvious that this code is active border: 5px solid red; // force a monospace font font-family: monospace; } The ^= selector makes sure that it will also work for repeaters, where your name would be something like your_field_repeater123

If you already have a python script that should be quite easy to do with the help of AI In PW just create a textarea field and make sure to let it use a monospace font so that you can properly paste/write your lyrics. (you can do that in /site/templates/admin.less) Then just grab that content and use your PHP method/function that your AI wrote for you and generate the html that you output on the frontend. PS: Nice idea also by @diogo 🙂

Awesome, thank you! This works perfectly and I have never allowed images in RTE fields, so I'm safe here 🙂 Thx for the note! I have added this as a tweak to RockAdminTweaks: https://github.com/baumrock/RockAdminTweaks/blob/dev/tweaks/General/RemoveVariations/RemoveVariations.php

This seems to be a fundamental feature so I must be missing something... I have a RockPageBuilder element called "Gallery". I don't think that it matters or RockPageBuilder has anything to do with it, but maybe I'm wrong, so I mention it for completeness. In that gallery block the client can upload images and in my code I create thumbnails from that images and show a gallery like this: Images are output like this: $images->eq(0)->maxSize(800,800)->webp->url Today the client contacted me, that she cropped one image, but the image does not update on the website... I thought I forget the cache busting timestamp, but that's in place and not the issue. Looking into the variations of the image I clearly see the issue: Image #0 and #2 are the newly cropped images. All others are outdated. Any idea why ProcessWire does not recreate those variations? I have done some research and found one old issue by myself that has been closed by @netcarver and I found this module by @Robin S But I'm wondering... am I missing something obvious? Why would I need an additional module to make sure that ProcessWire resets image variations when the underlying original image has been cropped? That makes no sense to me? Thank you very much for your help!

Hey @Cybermano glad it was helpful! That's what I've been using before I had the idea of hooking into WireMail::send. Everything in life has pro's and con's... So I'd not say it's a bad practise. But what I like about the solution is that it fits my credo "simple things should be simple". Sending a beautiful thing should be simple. And what you show might look QUITE simple it's not as simple as my version. If you only have one mail it won't matter or your version would even be easier (because you see everything that is going on). But if you are sending mails from different places in different occasions (eg on registration, on a new post, on a schedule, etc...) then my version keeps your code DRY (don't repeat yourself) whereas your version either tempts the dev to copy and paste those lines of code or be too lazy and just send out an ugly 90s style email. Both is not ideal in my opinion and investing a little more time to setup the hook will be beneficial in the long run. Also, while it's just a few lines of code, when your codebase grows every line of code that is not instantly and easily understandable matters. Your brain has to read the code, understand it, interpret it and remember it. With your str_replace that might be QUITE easy, but things add up and suddenly it might make the difference between easy to read code and a bloat of spaghetti code. It's about building a habit. Another problem with your solution is that if you copy&paste this to 3 spots, for example, and later you add another replacement tag, you have to do a search&replace and you might miss one spot and you introduce a bug. If you have it on a central place this can not happen. On the other hand if you want to render different files or you want different tags for different emails your approach might be the better one. And for someone not familiar with your codebase it might be easier to understand your version vs. the hook, because only seeing the $mail->send() somewhat hides how the mail gets sent with nice HTML and your version makes that obvious.

Thx! I think your fix should be fine and at least did not cause any problems on my end. I've pushed it to v6.3.1

Hey @Stefanowitsch thx for the quick meeting. I updated the docs in the hope that others won't have the same problem of understanding how the toolbar works. Let me know if the docs are still missing anything.

There is a long open issue for UIkit to support CSS variables but unfortunately there seem to be no efforts in that direction: https://github.com/uikit/uikit/issues/4534

First you need to make sure to get the value of the page reference field as PageArray (not a single page object or such). This might depend on your setting of the field and whether output formatting is turned on or off (in the hook it should be off, but just in case...). As ->removeAll() works it should be a PageArray in your case. In my case the field is called "pagelink" and I force the return type to be a pagearray via [] Then from the pagearray you can remove your page via remove("id=...") which is all you need I think

Not sure but a quick shot: use ->removeAll();

I think the concept of /site/ready.php has been there well before I started using PW in 2013 - so I think you can just create it and it should work. Your issue sounds strange though and I'm not sure what would be best to do. But I'd try to see if it works with force-login and then resetting the superuser password. At least that will show you where the problem lies (either a wrong passwort or something else).

Thank you for all your work on this great module!

Hey @teppo no I didn't dig deeper to be honest 😇 But your buffering note makes sense and when working with SSE on RockCalendar with DDEV I think it worked without any strpad or such!

Do you have the same userAuthSalt in config.php? If you change that (or it does not exist) you'll not be able to use the same password. You can also reset/force-login like this: https://processwire.com/talk/topic/29593-solved-do-the-reset-password-tricks-work-for-you-they-dont-work-for-me/?do=findComment&comment=239355 But it would be better if you understand why it does not work and then fix it if needed 🙂

Hmm. That's strange. Your error states that it fails with creating the discounts page. So my guess is that this issue was introduced with the discounts update at v1.1.0 - May I ask you to try v1.0.0? Strange is that I was able to reproduce your issue with v1.1.0 but 1.1.1 fixed it for me. So I'm not sure how to reproduce/fix it but the first step would be to confirm that 1.0.0 works for you. You could then also try to update to 1.1.0, which should work. That's not a solution yet but it might help to narrow down the issue! Thx for your help and sorry for the trouble!!

Hey @bramwolf thx for the detailed request (and of course thx for your purchase 🙂 )! Thx! This was very helpful! I think I have fixed the issue - could you please try v1.1.1? https://www.baumrock.com/releases/rockcommerce/ Sorry for the trouble! Please let me know if everything works now as expected and mark the topic [solved] if it does 🙂

Hey @neophron RockFrontend doesn't change the _main.php file. I guess you mean the RockFrontend Site Profile?! Whatever. As I told you at the very beginning you need to remove all styles() and scripts() calls and add assets manually. How you do that is up to you. You can either add the script/style tags manually to your main markup file or you can use RockDevTools. It's really up to you. But unless you remove all styles() and script() calls your system will not work and is not expected to work. There might be some inconsistencies with the site profile or other references to that old concept. I'm sorry for that and I'm trying my best to remove all those outdated informations. For that it would help to get the exact steps you took to get where you are. I understand that this might be frustrating, but please also understand that it is frustrating for me to try to help but don't get proper information and searching in the dark for issues that I don't see. What is that status on your end? Did you get it working already? What did you try to make it work? I'm very busy until end of next week so it would be nice to get an as detailed report as possible. Alternatively I can offer you that you send me your project and I set everything up so that it works.

Great! It was actually a very little change so I was quite confident it should work as expected 🙂 Problems with multilanguage websites and PagePaths module: I am happy to provide my dirty code, if you'd like so. 😉 I'll look into this when I find time, but I have to launch a project next week myself 😅 My plan for the RRule is to add another option to the GUI: I thought about adding "Simple / Advanced / Expert" - but not sure yet. Maybe just adding all possible options (like in the link above) to the "advanced" tab would be better? I think keeping the very basic "simple" option and a full blown "advanced" gui should be fine from a user perspective...