imandreas

BTW - just again: this module is outstanding - love it so much (beside of course PW and other modules :) But the UI is just incredible easy :)

It works now again on production, but I don't know why. I did the following: changed codebase: 2.3.0 => 2.1.1: Fluency - Apply With claude some changes because the API call failed: [Fluency module API failure] JSON.parse: unexpected character at line 1 column 1 of the JSON data - Fluency.js:194:13 und dann: Uncaught (in promise) TypeError: can't access property 0, t.translations is undefined - FtStandaloneTranslatorFieldset.js:147:48 - site/modules/Fluency/resources/scripts/global/Fluency.js - site/modules/Fluency/src/scripts/global/Fluency.js - site/modules/Fluency/resources/scripts/components/FtStandaloneTranslatorFieldset.js - site/modules/Fluency/src/scripts/components/FtStandaloneTranslatorFieldset.js The POST request /page/fluency/api/translation/ failed, the API was not accessible, it returned the page itself, now the return is JSON as expexted for Fluency. I'm really not sure, why it works now.

Btw, it might be something with DeepL. On my localhost with Fluency 2.1.1 and the same API Credentials, the translation works fine, just not on live server. It might be fixed after some timeouts.

Hi there, I got now the response in log file of Fluence 2.1.1: Engine: DeepLEngine /Error: AUTHENTICATION_FAILED /Message: Legacy authentication method 'query parameter' is no longer supported. Please update to header-based authentication. Find more details in our docs: https://developers.deepl.com/docs/resources/breaking-changes-change-notices/november-2025-deprecation-of-legacy-auth-methods. You can find more info in our docs: https://developers.deepl.com/docs/getting-started/auth /Response: {"message":"Legacy authentication method 'query parameter' is no longer supported. Please update to header-based authentication. Find more details in our docs: https:\/\/developers.deepl.com\/docs\/resources\/breaking-changes-change-notices\/november-2025-deprecation-of-legacy-auth-methods. You can find more info in our docs: https:\/\/developers.deepl.com\/docs\/getting-started\/auth"} Then I updated the codebase of Fluency module 2.3.0, API credentials of DeepL are still there, using the Free account type of Deepl. But now I got the error message by Fluency: An unknown error occurred while querying the translation service. Please try again later And no further Log file entries. Modules are already refreshed. Does someone has any idea what might be reason?

The module is fantastic, amazing! Thank you @FireWire Just let you know, I had a long trouble shooting, because I moved the created page "Translation" in the admin navigation into another sub-part of the tree in the navigation That caused a lot of error messages like "An unknown error occurred while querying the translation service. Please try again later." I tried to figure it out, but failed. Finally I found that issue.

@virtualgadjoyes, I'm still exhausted from debugging and researching, but glad, it works again. Uh, I have no idea about the 50, it's just there again, I didn't changed anything and have no clue on this setting.

Hi @virtualgadjothanks a lot for your suggestions. Yes, PHP version and hoster changed. But it was also not working on my localhost. There was one hint, it throwed sometimes the exception message "This request was aborted because it appears to be forged.". But anyhow, this happens sometimes, and does not really indicate any problem. But now I found the reason! The reason is anyhow the module "Session Handler Database" :( If I remove it, then its working! The really strange things are, that even the Session handler is somehow not valid, you can create a page, but saving the fields of a page, it struggles. Maybe it would have been clearly earlier, that something is on the session, if I wouldnt had disabled the above mentioned exception. But again, it is strange, creating a new page with a malformed session is possible, but not the fields. I don't know, why the Session Handler Database is not working. There are parameters in the module: - Track IP addresses in session data - Track user agent in session data? - Disallow parallel sessions? - Session lock timeouts (seconds) = 50 But I don't know, if any of them affect it. So after de-installing this module, I re-installed it, and now it is working as if nothing happend before.

I'm facing a real strange and big problem. The PW installation is 10 months old, but somehow in the backend all content is displayed, also the edit forms are displayed, but when saving the content, no change is saved. Also when creating a new page, it is possible to create the page, but not to publish. Page is saved as unpublished. Clicking "Publish + Exit" is still keeping on the page/edit. There are no log files created beside "session" logs, even the debug mode is enabled. Installed modules are: - ProFields: Custom - ProFields: Repeater Matrix But also creating a page, that is not using any complex field, instead only one, the behaviour is the same. Maybe there is an issue with the primary field required for all pages/templates: "PageTitleLanguage" It is a real strange and scary, that it is not possible to debug and get hints for the problem. Help is really much appreciated!

Hi There, I'm using the module "Admin Custom Pages" to create new pages accessible in the main navigation of the backend. But how is it possible to show the page only, if the logged in user is part of a special Access Role? I can't see any Permissions in Access / Permissions there is no Setup / Template on which I could set the permissions in the Access Tab Can someone give me a hint please?

Hi there, we are experienced and in love with ProcessWire, worked on various projects with it as website, headless CMS or as API system, but we have also very strong skills on Frontend programming. Right now we are looking out for frontend programming tasks as CSS, LESS, HTML etc. We can support you on your ProcessWire projects, take part of frontend programming so that you can focus on the PHP part. We can improve the frontend quality of your projects to a perfect and exceptionell level. So your websites will be the most dazzling ones and your clients will love you even more! Looking forward - Andreas

solved the issue: Unfortunately did redfine some values in the config for: $config->wiremailsmtp = array( .. "extra_headers" => array("Organization" => "My Org", "X-Header" => "") ) So removing them and keeping only the necessary for SMTP solved the issue

Hi, I'm stucked while using the mail sending, also the plugin WireMailSmtp is installed. $m = wireMail(); $m->to('test@example.com') ->header('bcc', 'asdf@example.com') //->from() ->subject( "HMTL | ") ->bodyHTML("DAs ist ein TÄÖÜ") ->send(); is creating the mail attached. I have no clue, but I also do not want to use phpmailer Any help is appreciated!

We made like this, in the header PHP template we checked, if the user is able to edit the page if ( wire('page')->template == "user-item-template" and (wire('user')->hasRole('frontendeditor') ) ) { echo "<!-- skip jquery -->"; } elseif ( wire('page')->template == "user-content-template" and (wire('user')->hasRole('frontendeditor') ) ) { echo "<!-- skip jquery -->"; } else { ?> <script src="<?php echo $config->urls->templates;?>js/jquery-3.7.0.min.js"></script> <? } Then it was possible to call the alfred: <div class="btn btn_default" <?= alfred($item, "title,text,content") ?>> <i class="fa-solid fa-pen-to-square"></i> Edit </div> It was opening the edit mode in a modal view with some administration header stuff.

Hi, it is almost 6 months, since I worked on this, but I remember, that you have to use the jquery version from PW admin. You should see the magic lines "ALFRED is ready :)" in console, if you include the PW jquery, which is loaded by alfred Maybe that helps

Hi, unfortunately not, I had to re-install it, quite bad, but I had not idea howto solve it.