Leaderboard
Popular Content
Showing content with the highest reputation on 09/18/2023 in all areas
-
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!7 points
-
Speaking of Softaculous, the PW download page links to Bitnami and AMPSS, but Bitnami's apparently dropped support for PW (a broken integration connection somewhere?), and AMPSS, although likely still works since it's a desktop version of Softaculous, doesn't have a landing page for PW. Super pumped to see an across-the-board update of the Pro modules. I commend Ryan's project management abilities. Fighting off scope creep and staying on-task is a very difficult thing to do (at least for me) when solo-developing, so many compliments to you on that!2 points
-
Yes, it's because of the ProcessWire namespace. Add it when setting the function name to your variable: $func = 'ProcessWire\foo';1 point
-
This week I've been finishing updates for many of the Pro modules with new versions posted today for the following modules: FormBuilder (v55) ProCache (4.0.5) ProMailer (v13) ProDrafts (v10) ProDevTools Form Auto Saver and Reminder, also posted in FormBuilder (v3) ProDevTools Page Auto Saver and Live Preview (v8) ProFields Combo (v12) ProFields RepeaterMatrix (v11) ProFields Table (v25) ProFields Verified URL (v6) ProFields Textareas (v10) ProFields Multiplier (v15) These new versions don't necessarily contain new features, with a few exceptions. But they do contain maintenance updates for PHP 8.2+ and jQuery 3.6+ where needed. They also contain various small fixes, improvements or documentation adjustments. Pro modules not mentioned above will also receive updates in the coming week (or weeks). I thoroughly tested all of these modules with ProcessWire 3.0.227 before posting. But all of these versions are posted as "dev" or "development" versions. What does that mean? It means that that at the time it was uploaded, I was the only one using it so far, and thus they've only been tested thoroughly by me, today at least. The term "dev" doesn't mean that the version isn't stable. In fact, often times the dev version may be more stable than the last posted non-dev version. (Kind of like how the core dev branch is often more stable than the master branch). The dev designation just means that I can't claim it to be the most stable version until it's been out for a little while longer, with more people testing it. If you see a dev version posted that has been out for several weeks, then you can usually consider that the current stable version. The exception would be if it also says "beta", or something else to indicate it's a testing version. Early this week the core master/main branch was also updated to version 3.0.227. This version contains fixes for bugs reported since 3.0.226 master/main was released. A 3.0.228 bump is also in the works for the core master/main branch. I'll likely be working on Pro module updates for another 1-2 weeks here, along with issue fixes to the core. As a result, the 3.0.228 version will likely be merged to the master/main branch in the next couple weeks as well. I figure we might as well keep updating the main/master branch with small fixes and such until we get into more major dev branch updates. Thanks for reading and have a great weekend!1 point
-
Since search is usually done using GET, no. You are not actively POSTing something which has side effects and thus CSRF is not feasible / applicable.1 point
-
Hi @ties You don't have the right to add any field / template. Do you know the username which is a superuser or you need to contact your system administrator of the website. Gideon1 point
-
Glad you got a working solution, but what you said is not 100% correct ? I used $page->template != 'something' and this will work. But it will only work if you use the "not equal" (!=) operator. It will NOT work, if you use the "not identical" (!==) operator! Check this out: So if you use the two letter comparison (== or !=) then PHP will try to convert your $page->template into a string and ProcessWire will be smart enough to use the template's name. So you'll end with a string == string comparison and you should get the desired result. If you use a three letter comparison (=== or !==) then PHP will not convert $page->template and object === string will always be FALSE and object !== string will always be TRUE. Hope that makes sense ?1 point
-
I think that as long as the field keeps the Hanna code text formatter, you shouldn't have any issues. About Hannah code insertion in the field, take a look at this: https://github.com/BitPoet/InlineCompleteTinyMCE1 point
-
Figured it out... seems like I have to get the role again and turn of output formatting ... $page_ = wire()->pages->get("template={$name}_blog, name={$name}"); if (!$page_->id) { $page_ = wire()->pages->add($template_, "/", ["title" => "{$blogName}", "name" => "{$name}"]); $page_->save(); } $role_ = wire()->roles->get("{$name}_blog_editor"); if ($role_->id) { $role_->of(false); $role_->save(); } }1 point
-
That's why Softaculous announced a new version in their installer. Until this moment I thought they'd support the DEV versions now and was totally thrilled... but ok. I'm totally for it. That signals ProcessWire is alive and well (see the Softaculous post above) and people can see it. To be honest here: we all should push way more details about your and the overall work on and the features of ProcessWire to the outside world. But that's another topic for another day. Have a great weekend, @ryan!1 point
-
@kater do you have more than one language installed but not activated? And give it a try and replace the title field with another text field,1 point
-
Thank you for your interest and input. The question about JS errors was particularly helpful: apparently a script from the old ListerPro version got stuck in my browser - clearing the browser cache helped. Embarrassing beginner's mistake ? Markus1 point
-
See this...1 point
-
If you mean in the image picker, you can try out the latest dev version here: https://github.com/BitPoet/MediaLibrary/archive/refs/heads/dev.zip
1 point -
Or you can go even shorter with: $fields->yourField->icon1 point
-
Another way is {$page->fields->yourField->icon}1 point
