Stefanowitsch

THANK YOU! Disabling mutagen did the trick! ddev mutagen reset && ddev config global --performance-mode=none && ddev config --performance-mode=none Now newly uploaded images have the correct permissions: 644. UPDATE: This is the typical mutagen behaviour: https://github.com/mutagen-io/mutagen/issues/23#issuecomment-345277107 But there is a also a way to have mutagen enabled and still get the correct file permissions: Add this line to your DDEV config.yaml: upload_dirs: - site/assets/files

Hi! Per default all my web projects are located in my "Websites" folder inside my user folder (I am working on a mac). For testing I moved my current ddev project into a different folder, unlisted the project from ddev, started it new and I still have the problem that the file permissions are set to 600.

Lately I switched from MAMP PRO to DDEV. However since then I noticed some strange behaviour: Everytime I uploaded a finished project to a webserver, some assets like images, CSS files or JS files all threw the "403" Error when visiting the website. After a bit of testing I realised that newly created files (like images that are uploaded through an image field) all get CMOD 600 instead of 644. So on my local machine this is no problem, but on a webserver it is! By the way, this is set in my ProcessWire config: $config->chmodDir = '0755'; // permission for directories created by ProcessWire $config->chmodFile = '0644'; // permission for files created by ProcessWire I tested the same project with MAMP PRO and there all uploaded and newly created files get the correct permissions - 644. The downside is that MAMP PRO is awfully slow compared to DDEV.... and I really don't want to switch back. I have absolutely no clue why this is the case? Why do all new files created by ProcessWire get CHMOD 600 instead of 644 - but only in DDEV and not in MAMP? I did some research and checkt the umask setting inside the DDEV container, which look exactly like it should: umask 0022 There seem to be some workarounds like running a script to re-alter the file permissions, but that does not solve my problem in the long run: #!/bin/bash find /path/to/your/uploads -type f -exec chmod 644 {} \;

Yes that works but my problem is - if define a custom font-family here like this: #Headings h1 { font-family: 'myWebFont' } /* My headline 1 */ The stylesheet does not know where and how 'myWebFont' is defined. I need to place this information somewhere in the stylesheet that the editor is using to make it work: @font-face { font-display: swap; /* Check https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face/font-display for other options. */ font-family: 'myWebFont'; font-style: normal; font-weight: 400; src: url('/site/templates/fonts/barlow-condensed-v12-latin-regular.woff2') format('woff2'); /* Chrome 36+, Opera 23+, Firefox 39+, Safari 12+, iOS 10+ */ } I added this @font-face declaration to my custom editor body stylesheet and it is working there. But not in the Headings Dropdown menu.

Great! This is working. Thank you. Another question. The new styles don't apply to the dropdown menu stylings. Where can I alter those styles so the headlines also use the webfont?

Hello! Has anybody tried this? I want to apply the webfont family that I am using in the frontend of my website to the TinyMCE styles. Per default the editor uses it's own custom stylesheet that defines own font families. So you always this look out of the box: Where can I change these styles? The editor area is embedded via an iframe so external style rules won't apply.

One of the downgrades of front-end editing is indeed the fact that you have to put in some work for making the editor and its appearance not being affected by third party styes. For example I have these overrides in all my projects: .alfred { overflow: visible; } .tox.tox-tinymce-inline { z-index: 100; } This is because the editor toolbar in the frontend sometimes gets overlayed by other elements in the DOM hat have - design wise - a higher z-index for example.

Hi @herr rilke This looks like some CSS styles are interfering with the Editor Toolbar Styles. I would advice you to investigate the markup this dropdown with the developer tools in the frontend and see what CSS rules are applied and from where they come from (maybe some other stylesheets, maybe the frontend framework that you included in the project, etc.)

@bernhard So you need to know if the buttons still have enough space or are "touching each other"? If you are able to translate/change the text that is shown inside the buttons you never can be quite sure how much space each button will take up in the end! The only thing that comes to my mind is to observe both buttons with JavaScript using the getBoundingClientRect() method. In that case you switch the wrapper CSS class from flex row to flex column. Another approach to make it "CSS ONLY": Make use of the flex-basis property in combination with the flex grow property: <div class="uk-container"> <div class="uk-flex uk-flex-between uk-flex-wrap gap-x-4"> <span class="uk-button uk-button-primary basis-[content] grow">Button with long Text</span> <span class="uk-button uk-button-secondary basis-[content] grow">Button with very very very long Text</span> </div> </div> The only downside: The buttons will expand so you need to make use of a gap.

I can confirm that it is working now as expected when using the native datepicker.

@Juergen okay thanks! By using the Jquery UI Picker it works.

Hi @Juergen! I just installed the current Version of the module on a website. I am using this module in an older version somewhere else and it works fine there. With the current version however I get an error message when selecting a publish date in the jk_publish_from field: The date that I've chosen is tomorrow. So this date is definitely in the "future". Why keep I getting this error message? My field settings are as follows:

It seems that the ajax response value is not a JSON String but a HTML page, it could be some kind of error of 404 page as it seems. You could have a look under the "Network" Tab and filter for "Fetch/XHR" to see the output value of the ajax response.

@bernhard I have a question about the AJAX/HTMX Endpoints feature: Is it possible to get access to the $page API variable inside my endpoint file to "see" from which page the request was sent? When submitting a form I want to include the title of the page form where the form was submitted into the E-Mail subject line. The only way I see right now is to add the page ID as a parameter to the endpoint URL.

@bernhard do you think this is something the RockPageBuilder can handle?

That is an interesting idea to handle fetching data. Would you mind showing us a short code example? I am planning to do the same in a project. Besides from that the the page you built is very avant-garde! It's kind of cool to see that designers go unusual and experimental ways in webdesign. It reminds me of the early days of the internet. Bedsides from that I have to admit - I also had my struggles understanding how navigating this website actually works ?

I think thats also what I've been looking fore. Where do I have to put this config object?

I am glad that it's working for you! I did a quick test with repeater matrix items and as you described it seems not to work with that. I don't use the Repeater Matrix field anymore (instead the RockPageBuilder from @bernhard) but I haven't tried the autocomplete search with that module either!

@bernhard While the new Drag & Drop feature (with the cross icon) works on the RPB Blocks itself it seems not work with repeater items inside the blocks anymore. Can you verify this behaviour? EDIT: ooooops. I just read @netcarver post and your reply on that one. So it will be fixed with the next release.

This error completely disappeared after I changed the PHP ini settings to: open_basedir: none Before that I got all kinds of "open_basedir restriction in effect" error messages.

@Roope I am using this module on PHP 8.1.2 and just received this error message: PHP Deprecated: Implicit conversion from float 521638.00000000006 to int loses precision in /home/users/xxx/site/modules/EmailObfuscation/EmailObfuscation.module:211 The module seems to work normally though. Is this something to be concerned about?

@Robin S I have a question: On the latest sites that are using this module all of a sudden the image URLs get crawled by google and they appear in the search console (they are not indexed, though). This is a bit of a strange behaviour, I've never seen this on my older websites. Does this have anything to do with the way this modules handles the delayed image generation?

Yes it somehow makes sense. I thought if this checkbox is unchecked it will stop sending error mails at all.

Since upgrading Tracy Debugger I always get this message here when logging into the backend: Tracy Debugger "Email Sent" flag has been set. Clear it to continue receiving further emails +1 I find the feature very handy to receive error messages, but I don't always want that so I disabled this checkbox here in the module settings: Anyway after that I always get the message above on all admin pages. Is there an option to disable this behaviour?

Back in the days when almost everything was build via tables in HTML you could actually use Photoshop to export your layout directly as HTML code. I used this for newsletter templates in the past. But beware, no one would ever design a page layout using tables anymore (at least I hope so...). Creating good designs is one thing and converting these designs in to a functional and responsive website is still really a piece of handcraft IMHO. So to answer your question: I use no AI helpers to turn those design files into working code. Too often you have to think around the corner "does this layout work on smaller viewports? How should the elements re-arrange, what elements should be hidden?" etc. etc. There is no way any AI can do that for me or for my clients - yet ?