sebibu
-
Posts
63 -
Joined
-
Last visited
sebibu's Achievements
Full Member (4/6)
23
Reputation
-
😅👍 I will create a bug ticket for this tomorrow! -
Ah, did you tried the „ß“ examples?
-
Thanks for testing, @poljpocket! Interesting. Consistent inconsistent at least!😉 Yes, I discovered the punycode in the ascii-only name column. But you are right, this seems to be non-standard when I compare it with e.g. with the results from punycoder.com (Punycode converter IDN converter). I wonder whether the conversion to punycode is still appropriate at all!?
-
I tested a lot the last days also with fresh latest stable installs with blank site profile local in DDEV and on the server. Exported, changed the charset and reimported the database from utf8mb3 to utf8mb4. Now the german special character äöü work, but strangely enough not always!😳🤔 ✓ Die Kölner „Miteinander“ → die-kölner-miteinander ✗ Köln gegen Köln in Köln mit allen Köln Fans – die Kölner „Miteinander“ → köln-gegen-kln-in-kln-mit-allen-köln-fans-die-kölner-miteinander (two missing ö) Furthermore: ✗ Fuß → s (?? should be fuß) ✗ Füße → füsse (should be füße) I thought PageNameTranslate is not used when using $config->pageNameCharset = 'UTF8'; and ß is in the whitelist!? @poljpocket and other: Are you so kind and test if this pagetitles generate the same pagenames in your instances? Thanks a lot!🙏👋
-
Only one which is only for pages with one determined template. But the problem occurs for pages with all templates and even if the hook is disabled. The newest stable one 3.0.229 All modules up to date.😇 BTW.. PHP mbstring extension is enabled.
-
Thanks for testing, @poljpocket! Great to see that it is basically working. Testing with a fresh install would have been my next step to narrow it down.👍 Interesting. I see you are using in your .htaccess RewriteCond %{REQUEST_URI} "^/~?[-_/a-zA-Z0-9äöüß.+!*'(),] instead of RewriteCond %{REQUEST_URI} "^/~?[-_/a-zA-Z0-9äöüß.+!*'(),]*$" So *$" is missing, which is necessary only for resolving the page request. Not build the pagename. 👋
-
Hi @poljpocket, thanks for taking the time! By default PageNameTranslate with this rules is used, that‘s right. But I‘m using the Extended Page Name Feature for UTF-8 support. Then this rules are hidden and not used. Please see here: https://processwire.com/blog/posts/page-name-charset-utf8/
-
Unfortunately I have to come back to my still existing pagename problem. This does not have anything to do with the hook. In general the pagename is shown correct in the preview before saving: But after saving special characters are removed: What am I doing wrong? I'm using this Extended Page Names feature: https://processwire.com/blog/posts/page-name-charset-utf8/ site/config.php: $config->pageNameCharset = 'UTF8'; $config->pageNameWhitelist = "$-_.+!*'(),äöüßÄÖÜabcdefghijklmnopqrstuvwxyz0123456789"; .htaccess: RewriteCond %{REQUEST_URI} "^/~?[-_/a-zA-Z0-9äöüß.+!*'(),]*$" How to debug this? (Haven't configured PHP debug in VSC with DDEV.😆) 🙏👋
-
Thanks @bernhard!👍 Commenting out this line... class Text extends Block { const prefix = "rpb_text_"; public function info() { return [ 'title' => 'Text', //'spaceV' => self::spaceM, ← HERE ... did the trick.☺️ 👍
-
I'm just wondering how to hide the frontend editing block-buttons vspacetop and vspacebottom!? On one website they are already disabled but I don't now how I achieved this.😇 For a quick'n'dirty CSS-hack there is no id or class given. Thx for a quick hint!👋
-
Thanks for your help! Trying.. {var $map = wire('modules')->get('MarkupLeafletMap')} {$map->render($page, 'map')} ..in RockPageBuilder block LATTE-file I get: Call to undefined function wire() in block Trying.. {var $map = $this->$wire('modules')->get('MarkupLeafletMap')} {$map->render($page, 'map')} .. I get: Method name must be a string in block Now I'm confused. 😆 What I'm doing wrong?
-
Thx @wbmnfktr for taking on ProcessWire Recipes and the time for caring and asking this questions! To be honest.. Yes, I would expect (and maybe even demand😇) that ProcessWire related projects like this are built with ProcessWire itself. Especially for sites with structured and tagged content like on ProcessWire Recipes, PW is predestined, I think.😉🙋♂️
-
I really love LATTE (Template Engine by Nette) but here and there I still have problems with the syntax. I'm using RockPageBuilder by @bernhard and try to output the html for this module: https://processwire.com/modules/fieldtype-leaflet-map-marker/ In PHP this would be: <?php echo $map->render($page, 'YOUR MARKER FIELD'); ?> And in LATTE? 😆 I tried this variants and more: {$map->render($page, 'map')} {$map->render($page, 'block->map')} {$map->render($page, $block->map)} Getting: Call to a member function render() on null in block #1158 (rockpagebuilderblock-map) Maybe this topic can be a collection point for smaller Latte syntax questions.
-
Thank you @poljpocket for this good optimizations!👍 While searching for hooks I stumpled across this syntax but didn't tested and then forgot it.🤓
-
Thank you @bernhard for helping optimizing the code!👍 For checking the template field I already used a guard clause, but for the template check it makes sense and is more readable to use it, too. I would like to keep the german special characters like äöüß instead of exchanging (->pageNameTranslate) them with ae, oe, ue, ss. So wire('sanitizer')->pageNameUTF8($title); should be the way to go. Right?
