psy

Hi @Sebi Would you please give some actual code examples? I've tried all sorts of variations and if I manage to get a response, it's always in the default lang (English), eg: <script> // Javscript in page template const testing = async (url) => { let connect = await fetch(url, { method: 'GET', credentials: 'same-origin', mode: 'same-origin', headers: { 'x-api-key': 'xxxxxxxxxxxxxxxxxxxxxxx', } }) let result = await connect.json() return result } // Testing AppApi only // const url ="/api/v1/licki/test" // works. Multilang not tested // const url ="/api/v1/users/41" // works. Multilang not tested // Testing AppApiPage // const url = "/api/page/1/?lang=german" // returns default lang obj {id: 1, name: 'home', title: 'Home', path: '/'}. // title should be German 'Startseite' and path '/de/' // const url = "/api/page/1/de" // fails with {error: 'Method Page::localUrl does not exist or is not callable // in this context', devmessage: {…}} // const url = "/api/page/de/1" // fails with {error: 'Method Page::localUrl does not exist or is not callable // in this context', devmessage: {…}} // const url = "/api/page/home/de" // fails with {error: 'Method Page::localUrl does not exist or is not callable // in this context', devmessage: {…}} // const url = "/api/page/1/?lang=de" // fails with {error: 'Method Page::localUrl does not exist or is not callable // in this context', devmessage: {…}} const url = "/api/page/1/?lang=german" testing(url).then((res) => { console.log(res) } ) </script> Site scenario: Frontend must support 10+ languages No frontend logged in users - currently using PHP session ApiKey and would appreciate your advice/help on best authentication method Aiming for 'Headless PW CMS' so frontend code can be agnostic, eg PW, Svelte, React whatever No requirement for admin side AppApi, just normal PW that may be multi-lang in the future I had all the ajax working, including a simple solution based on page path for multi-lang using vanilla js and PW. When I did the math and realised how big this site could be, I wanted something more robust which is why I've gone with AppApi and AppApiPage. Thanks for all the work you've done with AppApi and the add-on modules. Hope you can help. Cheers psy

Tip for the unwary... My admin site's default lang is 'en' - just happens as per install. Was surprised to see that the new TinyMCE inputfield menus etc defaulted to Russian 🤔. Solution: When configuring Modules -> InputfieldTinyMCE, ensure your 'default' lang is set to the correct lang code, eg "en-US"

@DV-JF it was running 3.0.200 and I upgraded to the latest dev 3.0.207 I also changed line 845 in PagesLoader.php to confirm if $options is an array: $options = is_array($options) && count($options) ? array_merge($defaults, $options) : $defaults; Switched the site back to PHP8 and it's working again. @ryan fyi

It worked before and now not 🤔 The web server was recently upgraded to PHP8 and I know PHP8 is much stricter on argument typing than previous PHP versions, and this blip resulted in a Server 500 error: 2022-11-16 14:56:21 guest https://xxxxxxx.com/api/ Fatal Error: Uncaught TypeError: count(): Argument #1 ($value) must be of type Countable|array, string given in /home/xxxxxxx/public_html/wire/core/PagesLoader.php:845 The code was a 'page get' selector request in an ajax call. It all worked before the PHP update and I'm sure there are others using $pages->get() without issues on PHP8. $pages->get("id=". $sanitizer->int($data->pid)) I also tried it without the "id=". I think the problem is more that $options is a string in the line in the PagesLoader.php: <?php $options = count($options) ? array_merge($defaults, $options) : $defaults; Any ideas on how to fix? Thanks, psy Solution Changed line 845 in PagesLoader.php to confirm $options is an array and the site worked again. $options = is_array($options) && count($options) ? array_merge($defaults, $options) : $defaults;

On many of my sites I have a page for business information which includes: toggle for site down for maintenance or live combo field for business name, address, phone, email, contact name, etc functional field for common phrases The combo field is great in this scenario. The data is fairly static and I only need to add the one combo field for a bunch of 'sub' information, bits of which may be used throughout the site. The alternative is to create a fieldset with individual fields, all of which would only be used in a single template and have one entry per field.

Hi @Jan Romero The PW docs refer to language codes. I didn't realise language codes and country codes were slightly different. Solution discovered by trial and error, and ironically, Google's Search help. Initially the warning only appeared when that lang page loaded, but once done so, the whole site had "Dangerous" in the browser address bar. Refreshing using the default lang cleared the message.

This is my first multi-lang site and client, bless his cotton socks, has chosen to have the site in at least 10 languages. Have figured out many things but Chrome is not playing nice. The default lang is English UK (lang url code is 'default' or 'gb'). On some langs, esp English US (lang url code is 'en-us') and Japanese (lang url code 'jp'), it's flagging the pages as "dangerous - could be phishing". All works fine in Firefox. Questions: 1. How to stop Google flagging valid lang pages as dangerous? ANSWER: Use the language code NOT the country code in the URL, eg English US = en-us (not just 'us') and Japanese = ja (not 'jp'). 2. On langs that don't follow the 'English' convention of text LTR, how do I set alternatives in the HMTL? eg Japanese is 'top to bottom, right to left'. Have done what I can in the CSS using logical properties (eg margin-block-start, padding-inline-end, etc) ANSWER: Add the language name as a class in the body tag then set the writing mode in CSS, eg: /* japanese */ body.japanese { writing-mode: vertical-rl; min-height: auto; overflow-x: auto; } HTH psy

Being able to download full-scale images, including SVG's, directly from an admin->page-edit->images field via a single click on an icon would be a great feature

Not sure I fully understood thei issue but I'd use dev tools to identify the element rule, then add the download icon to :before or :after styling in your custom CSS after SCSS compilation

So, after 5+ years of being a ProcessWire dev, I've bagged my first multi-lang project. Be prepared for questions 🤣

@BrendonKoz Container queries have been on the CSS agenda for a long time. At present the @container rule has limited browser support but it's definitely on its way. See https://caniuse.com/?search=%40container

@maddmac glad the module still works ? It doesn't do anything except create new pages as per the criteria set in the module config. The new pages are simply pages - you can then query whatever you wish as normal. The module only has one method which adds a Hook Event after a page is saved.

Seems to be a problem with namespaces. Try adding namespace ProcessWire to the template: <?php namespace ProcessWire; include '<?php echo $config->urls->templates ?>stripe-php/init.php'; //require 'vendor/autoload.php'; use Stripe\Stripe; Stripe\Stripe::setApiKey('xxxxxxxxx');

Just a thought... maybe change it to findJoin and add the task.tast_status field to ensure it's included in the query? https://processwire.com/api/ref/pages/find-join/

@millipedia So with you on that! Took time to actually learn CSS, and while it's constantly changing, decided to to lose the "Sara Lee" approach - layer upon layer upon layer. Spent far too much time overriding framework defaults instead of actually doing stuff. Now I use SCSS to combine global resets, default classes, colours etc then add small per template or component stylesheets. Same for any per template JS. In the supply-chain world this is referred to as "just in time" vs "just in case"