All Activity

I can't say much about it at the moment, as the module I'm currently developing is tailored specifically to a customer's needs. However, I plan to release a slightly different version later on, which will work in a similar way to the WordPress Media Manager.

Thanks. I just checked and found out that the version was already 2.3.0. So the problem is in that version, still.

@lpa I didn't deliver a formal release announcement but Fluency 2.3.0 was released. There were some fixes to CKEditor that may possibly be related. I've had 2 reports of issues with CKEditor fields in the last couple of weeks that hadn't been seen before. Not sure what caused it. 2.3.0 is in the modules directory, you can upgrade from within ProcessWire or download the latest version from Github. Let me know if that fixes the issue. I'm going to be away from my computer over the weekend so I won't be able to come back and check until Monday afternoon at the earliest.

On the contrary, I'd call your version a proper release, thanks in return! What are you building with Alpine if it's possible to share? The only thing i've built is FieldtypeRecurringDates

Thanks for merging @elabx! That is awesome news. My main goal with these changes was to be able to list this module as a dependency ('requires') for my other current and upcoming modules. Now I can rely on a central Alpine.js source instead of bundling/implementing it separately in every single module. That makes maintenance much easier. Thanks again for the collaboration!

Oh sorry, i missunderstood this. Go to "Releases" > "Draft a new release".

Ah meant more in a "github" kinda release.

You can click "Refresh". I increased the version from 005 to 006, this shoud do the job.

Would you happen to know that's the proper way to mark a release now??

Yes of course, let's do a pull request! I've just been running on this version non-stop lol

🙃

Thank you for this great module — it’s very helpful. After upgrading to version 2.2.0, we encountered a strange issue. I personally haven’t been able to reproduce it, but my colleague consistently runs into it. When clicking the “Translate to all languages” link in the Finnish (default) body field using CKEditor, the English translation replaces the Finnish content in the default tab instead of being placed in the English tab. As a result, the original Finnish content is lost. We are using ProcessWire 3.0.229. The CKEditor module version is 1.7.1, which comes bundled with the ProcessWire core. What makes this even stranger is that the issue occurs on both Windows and macOS, and in both Chrome and Edge. However, on my Mac, everything works as expected in both Chrome and Safari.

Hi @elabx, First of all, thank you for the AlpineJS module! I have been working on a fork to modernize the module and make it more flexible for my projects. Instead of shipping a static (and potentially outdated) JS file, I implemented a downloader mechanism. Here is a summary of the new features I added: Local Hosting & Updater: The module can now download the latest Alpine.js core and plugins directly from unpkg.com to the server. This allows for 1-Click Updates via the module config without needing a module update. Plugin Support: Added checkboxes to easily enable official plugins (Mask, Intersect, Persist, Focus, Collapse, Morph, History). You can review the changes in my fork here: https://github.com/markusthomas/AlpineJS I think these changes would be a good addition to the your repository. Would you be interested in a Pull Request? Best regards, Markus

Any news?

Hmm. I took that for granted. Though that existing data structure could be used. Visually mapped to. Sorry for asking questions without doing my part to investigate first.

Hey there, I changed the generation of the IDs to the internal sanitizer pagename function because I had some HTML markup (spans) within the headlines in the text field, which meant that the markup was no longer valid in the frontend. line 56 // Remove html tags before creating slug $cleanText = strip_tags($m[2]); // Use ProcessWire's sanitizer for proper slug generation $slug = wire('sanitizer')->pageName($cleanText, true);

Thanks, Ivan. Screenshots are included in the Readme file on Github and the module directory (when module is approved). Regarding Repeater (Matrix) Fields: As the module handles external (non ProcessWire) data structures, what exactly do you mean by „handled“? It is not possible to map data to an existing template/field structure, if that´s what you are asking for.

@ngrmm I think I found the bug (again), could you try and change TranslateGlossary.php:34 to the following: $entryArr = self::convertGlossaryStringToArray($language->translate_glossary ?? ''); The change is the ?? '' after translate_glossary. This handles empty glossary fields that return null instead of an empty string. Hopefully this will do it!

@robert – yes line 118 is private static function convertGlossaryStringToArray(string $glossaryString = ''): array { – I'm afraid i don't know what and where the language-specific translate_glossary field is 🙂 – using DeepL API Free UPDATE: ahhh, I updated from an very old version and didn't know that you have to add fields to the language template. Trying now to find out how to edit a language template. UPDATE: my fault. You have to uninstall and reinstall the module. Then the new fields are added to your language templates. Thanks again!

@ngrmmHmm, that might be possible, but unfortunately I can't replicate the issue here. Could you double-check that TranslateGlossary.php:118 has a default value for the $glossaryString parameter in the source code? The line should look like this: private static function convertGlossaryStringToArray(string $glossaryString = ''): array { Also, a few questions to help investigate: – Do you have any entries in your language-specific translate_glossary field? – Are you using the DeepL API Free or Pro plan? Thanks for helping with the investigation! 😅

@robert thanks! I updated to 1.3 and still getting the same error. Is this maybe related to my empty DeepL Glossary ID field?

@ngrmm I think I found the bug, thanks for reporting! Version 1.3 should work now and can be found in the ProcessWire modules directory. Since you mentioned your Fluency version in your comment: it's no longer required for this module to run (but it's still a great module nevertheless 😄)

@update AG Thanks for reporting. I pushed a new version 1.3 to Github which supports PHP 8.1. The DeepL API client uses Symfony HTTP Client as a dependency, which requires PHP 8.2 in version 7.x. I downgraded it to Symfony 6.x, so now PHP 8.1 is the minimum supported version. Regarding ProcessWire compatibility with PHP 8.2: I checked client websites and found one installation running PW 3.0.230 without any errors/warnings, and another with 3.0.213 that has some deprecation warnings but works fine. Edit: I forgot to mention that Fluency is no longer necessary for ProcessTranslatePage to run, both modules work independently.

Wow! Looks super cool! 🎉 Well, reads) Could you please add some screenshots or a video? And a questions right away (I have not install or use the module yet). Are Repeater and Repeater Matrix fields handled somehow? We've got content builder builder based on Repeater Matrix.

Hey, everyone, here at frameless we frequently work with clients who already have a website but aren't happy with it and want us to rebuild it from scratch. Whenever possible, we use ProcessWire for new web projects – no surprise there, given the flexibility and clean API we all love. For smaller sites, migrating content is usually straightforward – a bit of copy/paste and you're done. But for larger projects with hundreds or thousands of records across multiple database tables, this quickly becomes tedious and error-prone. Over the years, we've written various import scripts and parsers to handle these migrations. We finally decided to clean them up and package everything into a proper module that we'd like to share with the community. Introducing: Data Migrator Data Migrator is a Process module that imports external data (SQL dumps, CSV, JSON, XML) directly into ProcessWire's page structure – including automatic creation of templates, fields, and even PHP template files. Key Features Multi-format support – Import from .sql, .csv, .json, and .xml files Automatic type detection – Recognizes emails, URLs, dates, booleans, integers, etc. and maps them to appropriate ProcessWire fieldtypes SQL schema parsing – Extracts column types from CREATE TABLE statements for better field mapping Foreign Key handling – Detects FK relationships and sorts tables by dependency order Dry Run mode – Preview exactly what will be created before committing anything Full Rollback – Undo an entire migration with one click (removes all created pages, templates, and fields) Template file generation – Automatically creates ready-to-use .php template files in /site/templates/ How it works Upload your data file (SQL dump, CSV, JSON, or XML) Review the analysis – the module shows detected tables, columns, suggested fieldtypes, and sample values Fine-tune if needed – override fieldtypes via dropdown, configure FK relationships Run a Dry Run to preview all changes Execute the migration – templates, fields, parent pages, and data pages are created automatically If something's wrong – hit Rollback to cleanly undo everything Requirements ProcessWire 3.0.0+ PHP 7.4+ Links GitHub: github.com/frameless-at/ProcessDataMigrator Modules Directory: /modules/process-data-migrator/ We've been using the methods and classes bundled in this module internally for a while now and it has saved us a lot of time on migration projects. We hope it's useful for others facing similar challenges. Feedback, bug reports, and feature requests are welcome! Cheers, Mike