FireWire

Translate to all languages is on the roadmap. Very desirable feature but a lot of new code separate from the existing buttons/translating UI/error handling. I have an implementation in mind but didn't want it to hold up releasing the module, especially since it was so long overdue. I know this can be really annoying and I want to have this feature implemented as well. I had plans for a "Translate to All Languages" but not buttons for individual languages since it could lead to content that doesn't match between languages. Also want to keep it dead simple for the end user. Open to thoughts on this. I think that the way that tabs show that content has been modified is a good way to know that the content for another language has been updated. Some thoughts about switching to a tab after translation: The person translating the content likely doesn't know how to speak the language they are translating to If they need to go back and edit the content again there's an extra click to get back to the language they do speak The change indicators on the tabs are bound to the state of the Inputfield independent of the translation function, so you can trust that the content has been translated When the "Translate to All Languages" button is implemented, all of the tabs will show that they have been updated so it will be easy to see The flip is a great idea. I left that second select open since it's a "global" translator that provides all of the languages. I don't have any issues with it being pre-selected. Are there instances where you need to use the translator tool rather than on the fields themselves?

@everyone (how annoying would it be if that actually worked...) If you've got a Github account and want to support ProcessWire and the community, why not go give this icon PR a ?? Great way to show the icon repo maintainers that there are people out there who love the platform. https://github.com/devicons/devicon/pull/1905 And while you're at it, go give the ProcessWire repo a ⭐ as well! https://github.com/processwire/processwire

Here's a Google Maps WordPress plugin that takes advantage of needing a Google Maps Platform API key. They redirect the user to this page to promote their $12/mo. paid plan even though Google will charge you $0. They're happy to charge you up to $109/mo. for 10,000 views even though Google's platform affords 26,000 under their monthly free credits. Stay classy.

@bernhard Fixed. https://github.com/SkyLundy/Fluency/releases

Release 0.9.0b is up. This solves the global excluded strings issue, also updated to work with DeepL's new documented method. The excluded strings field now uses a || (double pipe) separator rather than a comma since a comma is punctuation that could be present in an excluded string. This also has two features suggested by @bernhard. The icon next to the translate button under fields is now a button itself that opens up the translation tool. The translate button itself is now styled by the admin theme as a link so changes to the admin colors will carry over. https://github.com/SkyLundy/Fluency/releases/tag/v0.9.0b

Nope. I have a fix coming today, this is a bug. I'll add another comment here when it's ready!

@ryangorley This is helpful and I'll try to replicate this. Have you added anything into the "Global Non-Translated Strings" field on the module config page? What are your settings for "Preserve Formatting" and "Formality"? I was able to replicate this by adding some excluded strings in the module config, let me know if this happened without your having added any. Fluency is compatible up through 8.2, I held off on using some 8.2 features to keep it compatible with more installs and the rest of the code is up to date, this is an isolated bug. So go with 8.2!

Hey @wbmnfktr, now we wait... https://github.com/devicons/devicon/pull/1905

Welcome to ProcessWire! Hope your experience has been great thus far (well, aside from this error you're seeing) and thank you for the kind words. 1. Absolutely will be adding it to the modules directory. I'd like to get a couple of tweaks in and iron out any bugs that may pop up, I have done as much testing as I can on my own and I need to make sure that "it works for me" means "it works for everyone" haha. @bernhard had a great suggestion for using hooks. As soon as it's had a little bit of usage I think it will be ready for the modules directory, so your feedback and bug reports are very helpful. 2. Translation engine requests are logged, so check the 'fluency-engine' log. That should help figure more out. If that isn't helpful then try using the network tab under your browser development tools, try translating something, then check the JSON response. Another question- does the translation tool accessed by the menu at the top of the page work? I too have had some secondhand experience with the challenges of adding multi-language capabilities to WordPress. My partner manages a WP site for the company they works for and had to try several plugins, some worked partially, all were difficult to use. Fluency was designed to be better than anything WP has available and those problems guided my work. Feel free to share your story over in this forum post celebrating WordPress.

Clients should always have their own accounts! If a features that a client wants or needs that need a 3rd party service, I present the information to the client, explain the pricing, and let them know that the account will be a service that they subscribe to. I like to emphasize that this means that they have ownership of the service and don't have someone in the middle (like me) charging a premium as a reseller. An example besides DeepL is a service called Smarty, which is an API to work with addresses. I am doing work with a client's CRM and explained that their address data isn't high quality enough to complete the work they need. I told them there's a free 30 day trial, and after that it's $54/mo. It sounds steep, but the client understood that it was an important necessity. It's a cost of doing business for them, just like DeepL may be. There are two sets of pricing for DeepL, the price to use their application, and the price to use their API. There are 2 separate pages for subscription plans, and on the "Plans and pricing" page it has both subscription types. It can be confusing due to how they have it presented. Here's where they have that hidden: I looked at the pricing plans and I don't see anything that would prevent a client from using the Free plan, unless 500,000 characters isn't enough. Then it would be €5.49 to sign up for the Pro plan, and then €20.00 for an additional 1,000,000 characters. So 1.5 million characters for €25.49. If it really came to that I would think that in most cases it would be possible to sign up for one month of Pro to translate the initial large amount of content, and then downgrade to the Free plan with 500,000 characters- unless they're publishing a ton of content per month! In Fluency you can switch between Free and Pro accounts without any issues or additional configurations needing to be made. Hope that helps, but if not let me know.

I was going to create a PR but can you give these a second set of eyes first? Specifically the "processwire-original-wordmark.svg" file. The SVG here on the PW website uses transparency, but in lieu of that I used an equivalent color so that no transparency had to be used in the SVG file itself. processwire_devicon.zip

Well here's a big announcement. The full rewrite is done. I bet you thought I forgot about this project, but nothing could be further from the truth... This is a complete rewrite of Fluency and it has a lot of new features- including a big one I said wouldn't be ready... it's now possible to use other translation services besides DeepL. Currently only two are available, DeepL and Google Cloud Translation. However- Fluency now includes a complete framework for creating "Translation Engines" that power fluency. I'm working on documentation and contributions in the future are welcome! There are a lot of features that have been added. Some I mentioned above, but they're here too. Ability to add new translation API services and a framework for developing them Language tabs now have indicators to show where content has been changed since page load. This makes it easier to see if some languages have not been converted Per-engine configurations. The Fluency module config page will dynamically show you the configurations that are needed for each engine. Translation engines retain their own configurations. It is possible to switch between engines with very little work. Full support for all ProcessWire fields, including TinyMCE. Both TinyMCE and CKEditor inline modes are now supported as well Polite and informative error handling Full UI translation for all Fluency components. Errors, buttons, labels, everything in Fluency itself can be translated and therefore customized. Full caching for translations and language lists. Caching can be cleared on demand. DeepL now has full support for translation features, including formality The module config is much nicer Meta tags for alternate languages can be rendered for the <head> element A language select dropdown can be rendered that reloads the page in a selected language You can easily get the language ISO code as well There's more, I'm probably forgetting some stuff. Check the module code. If you want to see what an overengineered ProcessWire module looks like, check the code. Check the methods in Fluency.module.php. Fluency is now globally accessible using the $fluency variable if anyone uses it. The admin REST API is completely documented as well. I'll be following up with more documentation on building Translation Engines, but it's already started and located in the module's subdirectories. Oh- and all documentation within the module is fully formatted and compatible with the outstanding ProDevTools module API Explorer. I've come to love that tool so I made my module work with it as well. I put all of the markup features I mentioned adding in a Pro module into this one. I'm not going to build a Pro module, all future features are going into this one. So it's all free now and forever. https://github.com/SkyLundy/Fluency Let me know what you think and about any bugs found. Also interested in hearing what other translation services you are interested in, and if there's any interest in someone helping out with building new Translation Engines!

3 hours on the books, issue isn't resolved, hosting company is rolling the entire site back due to possible database data loss. Updating core and plugins didn't solve the issue. Online ordering remained down due to broken connection to the merchant service which worked before a random automated WP upgrade last week. It was already rolled back last week, site stayed online for a couple of days and then went down again. In addition to that, an unstable WP plugin API made their custom theme break and return HTTP 500. The amount of casual breaking updates in the ecosystem is... impressive.

Different site I was hired to make simple text edits and remove some menu items. What should have been a 15 minute job ended up taking an hour because the page editor completely broke and it wasn't clear what was causing it. Turns out a jQuery version changed and I had to edit the plugin code directly. This is just tacky.

Here's a different site I was called in to fix. The design has been screwed up because it never quite looks right and the non-designer that edited the pages didn't click the buttons that change the editor size to "Mobile", "Tablet", and "Desktop" to make sure it would look correct across all devices. The semantic HTML was destroyed because, you know, the <h*> tags are to control the size of the text, right? It murdered SEO because tags aren't being used correctly. I love ads and update notifications that have existed there for weeks and also appear to be broken. I'm not doing anything about it because I'm not contracted for it and who knows what it will break. I do like the power that this design editor gives non-developers though, when things don't look right they can just tweak all of these numbers. I mean, who doesn't know and understand the CSS box model? Surely users can rattle off the differences between px, %, em, rem, and vw. Anyway. The amount of work it takes to make sure a page doesn't look like a trainwreck is, and I mean this, a valuable use of everyone's time- just stack the time I'm getting paid to fix it on top of that. I love WordPress, I make a lot of money off of it.

2nd time this has happened this year, 2nd time I've been brought in to fix it. Two different websites, two different clients of a small marketing business I subcontract for. Directly contributing to loss of revenue due to online ordering being down. Currently managing ~4 WP websites for clients, they're all not a fan. Currently negotiating a contract for a website and an employee at the company said "I f****ing hate WordPress". Feel free to spread the WP love here <3

Also want to point out how the video clearly shows that if you write PHP, a very fast and expensive sports car will show up in your garage. You can't argue with that, it's right there next to his big reaction face.

I stumbled on this video by Primeagen. If you're not familiar, he's a highly experience polyglot developer that uses a lot of different languages regularly and talks about them on his channel. His content isn't really my style (I think this is one of the first "reaction" videos I've ever watched), but I enjoyed seeing him get reintroduced to PHP, especially since he states that he hasn't used it since PHP 5.x. The video he reviews is also a really great introductions to modern features of PHP 8+ that I think more developers should adopt- both because they are totally cool and really do provide a better developer experience. So come for the "PHP is cool again", stay for the syntax we should all be using. The original video was by the same person that @wbmnfktr shared in this comment earlier in the thread, if you haven't watched his other videos, check them out!

Outstanding work @flydev! Oh yeahhhhhhhh baby. Ha! I will always have ProcessWire for websites, and having a proper front-end framework is an absolutely fantastic addition to the ecosystem. I reserve Laravel for true applications, my current one being a bit complex where it will have both the traditional web app for users as well as an API- basically standard enterprise features, and a lot more backend processing. There's been some great examples of developers using PW as a backend for an application, and they're awesome and inspiring. Spend any time with an ORM like Eloquent and you start to see many components of the ProcessWire API as a higher level ORM, which I really dig about it. ProcessWire is the go-to choice for websites, and complex sites with app characteristics, where a full fledged framework like Laravel (or conversely a minimalist framework like Slim) inevitably involve too much overhead for what could be done much faster in ProcessWire. This module and implementation has tremendous value. I shall use both! smdh.

Contributed to the thread over here.

I posted about this separately (missed this one) and this has become a recurring issue with DH. The following are some things (some mentioned above) I've confirmed through experience and information from DH support- Any new PW website uploaded requires a ticket into support to disable specific ModSec rules These rules must be modified for every domain separately When changes are made to servers, those ModSec rule exceptions for all sites will be wiped, requiring another support ticket to DH If the changes DH makes to a server are not disruptive (not requiring a restart) that could affect these rules, you won't be notified The only option for managing this yourself is to disable ModSec entirely in the admin panel, per-site Granular ModSec configurations are blocked, i.e. .htaccess cannot be used to modify rules (which is odd given that the alternative is turning it off entirely) The ModSec rules in place could be configured better but aren't- I have more complex applications on the same server that do not trigger violations Violations can still occur without triggering a 418 response or any error log entries, which can (has) lead to a lot of misspent time In lieu of a 418, access.log may show a request with a 200 response, but dev tools in Chrome show a connection error, in Firefox the request just hangs. No response/HTTP status/error log entry I spent time with support a couple of weeks ago and the tech disabled the ModSec rules that were showing up in error.log. It looked like it solved the issue, but a week later a client of mine that contacted me with this issue said it was still broken. The server was rejecting uploads over ~120kb and not logging any errors. This time support just disabled ModSec entirely- we didn't even know where to start without logged errors. You might want to check your upload file sizes during this process. I've been with DH almost 10 years and this didn't used to happen (maybe started when pushing DreamPress? just a guess). Being unable to handle this myself even though I'm on a private VPS (albeit managed) is frustrating. I'm confident in PW security, and I have a significant amount of .htaccess rules to block suspicious activity, but shutting ModSec off entirely isn't cool- especially when their admin, documentation, and support team (correctly) recommend strongly that you shouldn't. At this point I'm considering spinning up a VPS at DigitalOcean. I only used managed hosting because it was supposed to "just work", but I've had better experiences with well-configured unmanaged VPS', which have other perks to boot. C'est la vie.

Great share. I thought I searched hard enough... but apparently not. Looks like some really bad decisions all over again. They removed all of the ModSecurity issues but now the admin just hangs and never gets a response from the server. I was able to upload an image, but the client re-contacted me and said there's another issue with images again so I'm back to looking into it again.

Hello all, Sharing some issues that I've had with Dreamhost that I've seen over the last week for ProcessWire sites. This doesn't seem to be caused by ProcessWire itself or it's code. Wanted to let others know in case anyone has sites currently hosted with them. I have several sites on a VPS through Dreamhost (both PW and non-PW). I've been overall happy and have had very few problems over the ~10 years I've used them. Their support team has been great and they are currently working on the issues. Recently it appears that some server config changes made by their admins broke image uploads within ProcessWire. Uploads fail with the UI continually showing the upload spin animation over the image. I initially contacted support regarding one of my client's sites after they told me they were having issues. I then tested this on a different ProcessWire site hosted on the same VPS to check that this wasn't a code issue specific to that one site and it appears that this may affect multiple ProcessWire sites (maybe just on my VPS, not sure yet). The server would return HTTP 418 (cute) and the upload would fail. All other functionality appears to be unaffected. After testing the second site I thought to throw it out here on the forums to see if anyone else hosts PW sites on Dreamhost and have been experiencing this, or give a heads up to people who may want to check on their sites.

...I thought I knew what love felt like...

I want to give a shoutout to the work that @bernhard is doing with his page builder- and all his modules really. He took the time to share the progress he's made on RockPageBuilder. It really does nullify so many issues that I shared above in my 9 WP examples above. Once again, the quality coming out of the PW community continues to take things that exist on other platforms and do them the right way, just like PW itself. Outstanding work! It's a module, so I'm going to count this as PHP related ?