szabesz

I left out that I meant this option to be an individual field level setting, not a global one. There are always pros and cons, but this solution also ensures that the default UX/UI of the admin is not changed too much, and if users use both interfaces (standard PW and MediaHub), then less deviation from what they are used to will generate less confusion.

I prefer this one, along with the option to configure which source is shown by default (preferably the first tab is always the default, if possible). A cleaner, more organized interface is better. If image sources are merged, even when page-context images are listed first, how can I tell the actual source? In some cases that does matter. Avoiding confusion up front is the better solution, in my opinion.

@ai_slop Thanks for sharing your experience! Is it what I made this screenshot of? See: I only had the "Upgrade Plan" button, as you can see. Since I have already deleted the account, I have no way to take any further action, except to write to their support.

I recommend not subscribing to a Plaid plan at kimi.com. I wanted to cancel my subscription, but there was no such option, so I had to delete the account, as that was the only option I could find. I wrote to support, but they never replied. I removed my saved credit card on Stripe's interface, but I still receive a message every other day: "...payment to MOONSHOT AI PTE. LTD. was unsuccessful We attempted to charge your card for your MOONSHOT AI PTE. LTD. subscription again, but were unsuccessful. Please update your billing information to continue your subscription." For a theoretically deleted account...

Hello, Interesting "topic". However, what's the site's URL?

Thanks for taking the time to share this info, it is definitely good to know.

Lots of us are interested, I think. @Peter Knight any plans to release it?

As for specs driven development, yesterday I watched this: And started to dive into it using my cheap but pretty good z.ai yearly subscription.

Sure, my question was just too broad, sorry about that. But you nailed it down anyway. I want to implement a page builder based on Repeater Matrix and nested repeaters will likely be required. Does ProDrafts have sort of "partial support" for repeaters or no support at all?

Thank you for the intel! What would you recommend if I need to decide in mid‑April? Should I still buy and rely on the "old" ProDrafts? It wouldn’t be ideal to implement features based on the "old" ProDrafts only to refactor things shortly afterward to "align with the future".

@ryan I have active ProFields license, but I have no access to that board. Can you please provide up-to-date information on what we can expect? I need to tell a client about the state of draft/version management in ProcessWire, and I do not want to provide outdated information.

Gemini AI Pro is crazy good these days. I was stuck why the replace hook had no effect, and this solved it (courtesy of Gemini from Google is in italic): The reason your hook is firing (as proven by your bd() output) but $p->path, $p->url, and $p->httpUrl are reverting back to the original /parent/ path is due to a hook priority conflict, usually caused by ProcessWire's Multi-Language modules (or an SEO/routing module). Here is exactly what is happening under the hood: Your addHookBefore runs, sets $event->replace = true, and sets $event->return to /blog/. ProcessWire skips its native Page::path() method because of the replace flag. However, another module (like LanguageSupportPageNames) has an addHookAfter attached to Page::path. That module runs after your code, looks at the $page object, recalculates the original path from the database tree, and silently overwrites your $event->return before it finally gets handed back to your $p->url call. To fix this, you need to change your hook to an addHookAfter, remove the replace flag, and bump the priority so your code is the absolute last thing to run. Change your hook to the following: $wire->addHookAfter('Page::path', function (HookEvent $event) { $page = $event->object; if ($page->template == 'original-parent') { // Overwrite whatever the core (or other modules) generated $event->return = "/blog/$page->name/"; } }, ['priority' => 1000]); // Priority > 100 ensures this runs AFTER core modules And yes, I have multilingual support installed, and this solution works.

@WireCodex It's strange that you changed your profile name. Now we need to get used to it ;)

How?

Also see: https://processwire.com/talk/topic/31761-developing-while-biking/#findComment-252011

Sounds like a pretty good plan. If you were to implement it and Mikel was happy to merge it into his module that would be awesome.

Thank you @maximus I checked both issues and they are indeed resolved. I wonder if you use Tracy Debugger for the admin? It is easy to spot warnings if it always runs, which is the case for me almost all the time. Sometimes, I disable it when I need unmodified HTML in the browser, but after that I reenable it. BTW, could you make the /site/assets/context path configurable? I recently tested PHPStorm with Junie by adding to its .junie directory what @interrobang shared with us: https://processwire.com/talk/topic/29439-cursor-might-be-my-vscode-replacement/#findComment-251674 Specifically: https://github.com/phlppschrr/processwire-knowledge-base/tree/master I adjusted the root SKILL.md (removed references to Python scripts and such) and Junie can pick up all skills perfectly. If I could set the module to generate files to /.junie/skills/docs, the Junie agent would start using them too. That would be real magic :)

Thanks @maximus for sharing. I am testing the module, and found two issues: 1. After the module has been installed the "Submit" button of its settings page must be clicked or else the actual settings are not the same as seen in the GUI. By default, a lot of "Module Configuration" settings seems to be turned on (their checkboxes are on), like "TOON Format Export", "Content Samples", ect. but they are not on. I had to manually "Submit" the settings so that the module settings are actually the same as seen on the module config page. 2. In Context.module.php $matrixTypes = $matrixField->type->getMatrixTypes($matrixField); foreach($matrixTypes as $mt) { if($mt->name === $name) { But $mt->name is meaningless as $matrixTypes is the following kind of array: array 'matrix_email_block_image' => 1 'matrix_email_block_button' => 3 'matrix_email_block_text' => 4 'matrix_email_block_spacer' => 5 $mt->name is an attempt to access the name property of an integer. And that happens in two locations:

Hello, I'd recommend implementing your own solution based on ProcessWire and various other helper modules that are being maintained, as all webshop solutions for ProcessWire are no longer maintained. You can get inspirations from @Mikel's modules such as: https://processwire.com/talk/topic/31455-stripepaymentlinks-–-simple-checkout-integration-for-processwire/ And from other community examples such as: https://github.com/mugdhachavan/cake-shop-processwire https://github.com/lombervid/shoppingcart Also Ryan's https://processwire.com/store/form-builder/stripe/ can simplify Stripe integration a lot.

Visiting https://www.kimi.com/membership/pricing a modal pops up for me and its top part looks like this: To tell the truth, I will probably use it for browser-based prompting, and it shows how many such tasks are still available for that day. For example:

I just paid for 1 month of Allegretto ($39/month) and used it with a deep research prompt asking for an "Intermediate PHP developer who is new to PHP Swiss Ephemeris" demo project (with detailed requirements, of course). It produced runnable code with outstanding results in about an hour. That might seem slow, but for me, it would have taken at least two weeks to figure all that out. It also came with explanations, which provides me a good starting point to learn the topic. So Kimi 2.5's deep research is very impressive, especially regarding coding-related prompts. It performs much better than my (admittedly) cheap Gemini Pro plan. I prompted Gemini with the same request, and it produced half-baked code, clearly running out of "steam" (memory/context window, whatever...). Additionally, Kimi's deep research acts like a programmer, while Gemini's deep research behaves like a very important executive who happens to be good at coding but prefers to give unnecessary executive summaries on the topic. I dislike that as it just consumes "tokens" on something you do not need. Well, my comparison might not be fair, as my Gemini Plan is a lot cheaper than $39/month, but those Gemini deep research unnecessary executive summaries also come with higher plans, I guess. Edit: "unnecessary executive summaries" and yes, I always prompt it not to do that but it does so anyway. The only difference is that they are shorter than the summaries one gets without asking not to do them.

Yes, the issue with blog articles is that they are verbose, and there is no need for such verbosity for an LLM. However, instead of trying to squeeze blog posts and API docs content and examples into a context window, it would be better to do some "sort of LLM training". Like LoRAs for image models. Does anyone have an understanding of how such a thing could be done?

Sure thing ;) Thanks in advance if you make it public.

Same comments with like/dislike just like for processwire.com blogposts, perhaps?

https://processwire.com/talk/topic/31724-wip-wiremedia-–-concept-for-a-central-media-management-module/